A town owns an improbable mix of things: mowers and radios, laptops and folding chairs, chainsaws and projectors, all bought from public money and spread across departments that each keep track their own way. Public works has a clipboard, the parks crew has a memory, town hall has a spreadsheet - and the clerk answers for all of it when the auditor, the insurer, or a council member asks. This guide covers how municipalities put everything on one register without a consultant-led project.
What you will learn
- Why town equipment drifts
- What belongs on the town register
- One town, many borrowers
- Audit-ready by default
- Getting started without a project plan
- FAQ
Why town equipment drifts
Municipal equipment has a particular set of failure modes:
- Departments are silos by design. Public works, parks, admin, the library, the fire hall - each buys, stores and lends its own gear, and no list crosses the boundaries.
- Seasonal equipment hibernates. Mowers, plows, event kit and holiday decorations spend months in storage between uses - long enough for their location, and sometimes their existence, to be forgotten.
- Shared kit belongs to everyone, so it belongs to no one. The event tent, the portable PA, the trailer - borrowed across departments on a phone call, returned whenever, condition unknown.
- Turnover erases the map. Staff retire, elected officials change, and the knowledge of where things are - which was never written down - leaves with them.
- The audit always comes. Auditors, insurers and grant administrators all eventually ask for the same thing: what do you own, where is it, what condition is it in, and who is responsible. Per-department spreadsheets cannot answer that, for the same reasons Excel fails at asset tracking everywhere else.
What belongs on the town register
Track per item anything that moves, breaks, or would be missed at audit:
- Town hall and office IT - laptops, headsets, conference room equipment, external drives, and the software licenses that renew whether or not anyone remembers buying them.
- Public works tools and small plant - generators, pumps, saws, compaction gear, traffic equipment. The heavier end of this overlaps with the public works register pattern.
- Parks and grounds equipment - mowers, trimmers, sprayers, and the seasonal kit that hibernates.
- Radios, safety and emergency equipment - issued to people, inspection-dated, and exactly what the fire and police departments track on their side.
- Event and civic kit - tents, staging, barriers, PA systems, tables and chairs that every department borrows.
Bundle low-value accessories rather than itemising them: a box of chargers and cables can be one stock record, not forty asset records. A register clogged with cables is a register nobody updates.
One town, many borrowers
The cross-department borrowing that makes towns efficient is also what loses their equipment. The fix is running shared kit on a lending library model:
- Every pooled item has one owning department responsible for its condition and storage.
- Every borrow is a checkout to a named person or department, with a due date - not a favour remembered by two people.
- Returns capture a condition report: who returned it, when, and what state it was in, so damage traces to a loan rather than a rumour.
- QR labels make it self-service. The parks crew scans the trailer with a phone and checks it out in seconds; nobody has to find the one person with the binder.
Tip: your capitalisation threshold decides what finance must report, not what you should track. A radio or a chainsaw below the threshold never appears on the fixed asset schedule - but it still walks off, and it is still public money. Track by operational value, report by accounting rules.
Audit-ready by default
A register maintained as part of daily work makes the annual scramble unnecessary. The division of labour looks like this:
| Department | Typical assets | Tracking approach |
|---|---|---|
| Admin / town hall | IT, AV, office equipment | Assigned per employee or room |
| Public works | Tools, small plant, traffic kit | Checked out per crew or vehicle |
| Parks and grounds | Mowers, trimmers, seasonal kit | Assigned to facility; serviced on schedule |
| All departments | Event and civic kit | Pooled, checkout with due date |
| Finance | The whole picture | Exports for schedule, insurer, audit |
Because every checkout, transfer, status change and disposal is logged against the asset, the answers auditors want - existence, location, custody, condition - come from asset tracking history rather than reconstruction. Grant-funded equipment is the sharpest case: years after the award, you may need to show the item still exists and is still in public use. A record with purchase details, attached invoices and a custody trail does that in minutes.
Getting started without a project plan
- Pick one department with visible pain - usually whoever manages the shared event kit, or public works.
- Walk the storage areas and list what is actually there, with serials and photos. Reconcile against the old spreadsheet afterwards, not during.
- Label as you go - durable QR labels on equipment, standard labels on office kit.
- Assign everything an owner: a person, a department, a vehicle, or a building. No anonymous equipment.
- Move the shared pool to checkouts first - it produces the fastest visible win, because the tent stops disappearing.
- Add a department per month. Each one is days of work once the pattern exists.
Where AMPthilly fits
AMPthilly is built for exactly this shape of organisation: one register, many departments, light administration. Assets carry serials, photos, purchase details, warranty dates and attached invoices; departments and roles let public works run its own equipment while the clerk keeps the town-wide view; checkouts, returns and transfers are logged automatically into a permanent audit history with CSV export for finance, the insurer, or the auditor. Printable QR labels turn any phone camera into the checkout desk - staff scan in the browser, with no app to install and SSO via Google or Microsoft on every plan. The free plan covers 3 users and 25 assets with no card required, enough to pilot the event kit pool before anything goes near a budget line; see pricing for the full picture.
FAQ
How should a small municipality track its assets? One shared register: unique IDs and QR labels, an owner for every item, departments managing their own gear, and a consolidated view for the clerk and finance.
What is the difference between the fixed asset schedule and an asset register? The schedule is accounting - capitalised items only. The register is operational - everything that can walk off. Run the register; export to feed the schedule.
How do town departments share equipment without losing it? Pool shared kit under one owning department and make every borrow a recorded checkout with a due date and a condition note at return.
Can an asset register help with municipal audits? Yes - existence, location, custody and condition are answered from logged history and exports instead of an annual reconstruction.
Is asset tracking software affordable for a small town? Yes - pricing scales with users and assets, and free tiers like AMPthilly’s (3 users, 25 assets) cover a one-department pilot.
The takeaway
Municipal equipment drifts because each department keeps its own incomplete list and shared kit belongs to nobody. The remedy is structural: one register for the whole town, an owner for every item, every cross-department borrow a recorded checkout, and audit answers generated from daily activity rather than annual heroics. Start with the department that hurts most, label as you walk, and let the first clean audit make the case to the rest.