Building a stormwater asset inventory often begins in a very familiar place, a spreadsheet opened by someone who knows the system well enough to start writing things down. There is nothing wrong with that starting point. In fact, many successful asset management programs begin with a simple table of culverts, catch basins, and outfalls, along with a few notes about location and condition. The problem is not the spreadsheet itself, it is what happens when that spreadsheet becomes the system.
“From spreadsheets to systems” is really about making a transition from informal knowledge to something structured, repeatable, and usable across an entire organization. A spreadsheet can capture information, but it struggles to support ongoing inspection, updates, mapping, and decision making. As your inventory grows, so does the need for consistency, accessibility, and integration with how your team actually works in the field.
The first step in building an asset inventory is not choosing software, it is deciding what you are going to track. At a minimum, most municipalities should be documenting asset type, location, size or dimensions, material, and condition. Even basic location data, such as a road name and nearest address, is enough to get started, although GPS coordinates will quickly become important as your system evolves. The goal is not perfection, it is consistency. A complete but simple dataset is far more valuable than a complex one that is only partially filled in.
One of the biggest challenges early on is dealing with incomplete or scattered information. Records may exist in old paper maps, as-built drawings, maintenance logs, or even in the memory of long-time staff. Bringing that information together is part detective work and part field verification. It is common to discover assets that were never documented, as well as records that no longer reflect reality. Accepting that your inventory will improve over time is critical to maintaining momentum.
As the inventory grows, limitations of spreadsheets begin to show. Version control becomes an issue when multiple people are making edits. It becomes harder to visualize where assets are located or how they relate to one another. Filtering and sorting can only take you so far when you are trying to answer questions like which culverts are in the worst condition or which outfalls discharge to sensitive water bodies. This is the point where many municipalities begin looking toward more structured systems.
A true stormwater asset management system builds on the foundation of your spreadsheet but adds key capabilities. It allows multiple users to access and update data without overwriting each other. It ties assets to a map so that location becomes visual, not just descriptive. It supports standardized condition ratings, inspection histories, and maintenance records. Most importantly, it turns your inventory into something you can use to prioritize work and justify decisions.
Geographic Information Systems, often referred to as GIS, play a central role in this transition. Mapping your assets brings immediate clarity. Patterns begin to emerge, whether it is clusters of failing infrastructure, undersized culverts along a corridor, or outfalls concentrated near water bodies. GIS also allows you to layer in additional information such as soils, flood zones, and land use, which can further inform decision making.
Equally important is how data is collected and maintained. Moving away from paper forms and informal notes toward mobile data collection can significantly improve accuracy and efficiency. Field crews can locate assets on a map, update condition ratings in real time, and attach photos that provide visual documentation. This reduces duplication of effort and ensures that information flows directly into your system instead of being lost or delayed.
It is also worth emphasizing that building an inventory is not a one-time project. Stormwater systems change over time as new infrastructure is installed, repairs are made, and conditions evolve. An effective inventory is a living dataset that is continuously updated. Establishing clear processes for inspections, data entry, and quality control is just as important as the initial data collection effort.
For smaller municipalities or those just getting started, the idea of moving to a full system can feel overwhelming. The key is to think in phases. Start with a spreadsheet if that is what is available, but structure it in a way that can be migrated later. Use consistent naming conventions, standardized fields, and clear definitions. As your needs grow, you can transition that data into a more robust platform without starting from scratch.
Ultimately, the value of a stormwater asset inventory is not in the data itself, it is in what the data allows you to do. When you know what you own, where it is, and what condition it is in, you can move from reacting to problems to managing them. The transition from spreadsheets to systems is simply the path that makes that shift possible.