How to build an asset register for your municipality's street furniture

An asset register sounds like something from the finance department, and in part it is. For the people who look after a town's streets and parks, though, it is simpler than that: a list of every physical thing the municipality is responsible for — litter bins, benches, lamp posts, signs, trees, play equipment, grit bins — with where each one stands and what state it is in.

It is also the list most municipalities don't quite have. There is a spreadsheet from a survey some years ago, a GIS layer that one colleague maintains, the lighting contractor's own inventory, and a great deal of knowledge in the heads of the crews. Each covers a part. None of them can answer a resident who reports “the broken bench by the pond”.

This guide is for whoever has been asked to fix that: a parks manager, a street maintenance coordinator, the person in the technical department who inherited the job. It is based on what we see municipalities do when they build a register that lasts.

Why the spreadsheet stops working

A spreadsheet is a perfectly good place to start, and most registers begin as one. It stops working at a predictable point, for predictable reasons:

• A location in words isn't a location. “Main Street, by the bakery” means something to the person who wrote it and nothing to a summer temp two years later. Without a point on a map, nobody can go and find the thing.
• It can't be used where the work is. Nobody edits a 3,000-row spreadsheet on a phone in the rain, so corrections are written on paper, or remembered, or lost.
• Copies drift. One copy is emailed to the contractor, another sits on the shared drive, and within a year there are three versions of the truth and a file called benches_final_v3.
• It belongs to one person. When the colleague who understands its columns moves on, the register goes with them.

None of that is a reason to throw the spreadsheet away. It is a reason to move what is in it somewhere the whole organisation can see it on a map and correct it from the street.

Decide what the register is for before you count anything

The most common mistake is to start by walking the streets. The second most common is to design a form with forty fields. Both come from skipping the same question: what does the register need to answer?

Write down the five or six questions people actually ask you. They tend to look like this:

• Where are all our grit bins, and which of them have been filled before the first frost?
• How many benches do we have, and which are due for replacement?
• Which lamp posts on the high street are waiting for a repair?
• What stands in the park we are about to renovate?
• Which assets does the contractor maintain, and which do we?

Every field in the register should help answer one of those. A field nobody will ever filter on or read is still one that someone has to fill in, on every asset, for years.

Record less than you think

A good record is short. For almost every kind of asset, this is enough to start with:

• What it is — a category: bench, litter bin, lamp post.
• Where it is — a point on the map, plus a street address for people who don't read maps.
• What state it is in — active, in maintenance or retired. Three statuses get used; ten get ignored.
• Two or three details that matter for that category — the year a bench was installed, the lamp type of a lamp post, the volume of a bin.

Two decisions are worth making up front. First, keep details per category: a lamp post needs a lamp type and a bench doesn't, and a form that asks everything of everyone gets filled in with guesses. Second, when a detail has a fixed set of answers — a material, a model, a contractor — make it a choice list rather than free text. “Wood”, “wooden” and “timber” are three answers to a filter and one answer in the real world.

Photos, serial numbers and inspection histories can all come later, if the questions you wrote down need them. It is far easier to add a field to a register people trust than to get people to trust a register nobody managed to finish.

Start from what you already have

Before anyone goes out with a phone, collect every list that already exists: the old survey spreadsheet, GIS layers from the planning department, the lighting contractor's inventory, purchase records for play equipment, the tree register if there is one. Even an incomplete, outdated list saves a lot of walking — checking that a bench is still where the list says is much quicker than finding it.

Put those on the map first, and the survey becomes a matter of confirming, correcting and filling gaps rather than starting from nothing. If the lists come in different formats and coordinate systems, that is normal. It is exactly the work we do for municipalities moving to mapzaa, described under migration help.

Survey one district at a time

The survey itself goes best in small, finished pieces rather than one big push.

• Divide the municipality into districts that one person can cover in a day or two, and finish each one before starting the next. A register that is complete for three districts is useful; one that is half done everywhere isn't.
• Record where you stand. On a phone, place the pin at your own position next to the asset rather than guessing from an aerial photo afterwards, and check it is on the right side of the road. It matters to whoever is sent out next.
• Pick the season. Snow hides benches and grit bins; summer foliage hides signs. Late spring and early autumn are when it is easiest to see what is there.
• Record the state you find. A survey is also an inspection. If a bench is broken, set it to maintenance there and then — that is the first work list the register gives you.
• Let the crews help. The people who empty the bins already visit every one of them. Adding a pin on the way past takes a minute, and it makes them owners of the register rather than its critics.

Give every asset a name you can say out loud

A bench has no name, and “the third bench from the playground” does not survive a phone call. A register earns its keep when an asset can be pointed to in a work order, on a sticker, in an email from a resident and in a conversation with a contractor.

That takes an identifier that is short, never changes and can't be misread. In mapzaa every asset gets a code like BEN-BY66GW: the first part says what it is, and the second part is permanent and leaves out characters that are easy to confuse when handwritten, such as 0 and O or 1 and I. Written on a sticker on the back of the bench, it lets anyone type it into the search box and land on exactly that record.

Whatever system you use, the principle holds: the identifier should outlive recategorisations, reorganisations and whoever set it up.

Keep it current, or it quietly goes out of date

Every register is accurate on the day the survey finishes. The ones that stay accurate are those where updating the record is part of doing the work, not a separate chore.

• Update from the street. If a crew can correct a record on a phone while standing next to the asset, they will. If it means a note to the office, mostly they won't.
• Retire, don't delete. When a bench is removed, mark it retired. What used to stand on a corner is part of the record, and the history answers questions later.
• Plan maintenance from the register. A round of repairs built from a filtered list — every lamp post in maintenance in the town centre — sends people to the right places and brings the record up to date as they go.
• Know who changed what. A log of changes makes it safe to let more people edit, because a mistake can be seen and put right.
• Review it once a season. Filter on what nobody has touched in a year. That is where the register is most likely to be wrong.

Where to start on Monday

1. Write down the five questions the register has to answer.
2. Choose three to six categories to begin with — the ones those questions are about.
3. For each category, pick two or three details worth recording, and no more.
4. Gather every existing list, spreadsheet and GIS layer, and get them onto the map.
5. Survey one district completely, correcting and filling gaps as you go.
6. Hand the register to the crews, and let them keep it current from their phones.

None of this needs a large project. The first district can be on the map in days rather than months, and the register grows from there as the people who look after the streets start using it.