Ask a controller what is slowing their capital reporting down and you will hear about systems, headcount and the sheer number of projects. Then ask to see the project list, and the real answer is usually sitting in the first column, wearing four different outfits.

Bldg 4 Reno. BUILDING 4 RENOVATION - PHASE 2. B4 renov (Smith). 2024 Cap - Bldg 4.

Four projects. Possibly one building. Nobody in the room can say which without opening all four — and I say that with real affection, because I have opened all four more times than I can count.

Naming is not cosmetic — it is the join key

A capital portfolio only becomes reportable when costs can be grouped reliably. Grouping requires that two people describing the same thing land on the same string, or at least on the same structured identifier. When they don't, every roll-up becomes a manual reconciliation, and the analysis leadership actually wants — spend by site, by asset class, by funding source, by year — needs a person with institutional memory to assemble it by hand.

That person becomes the bottleneck. Worse, that person becomes the reporting capability, and the day they take a better job, it rides along in the passenger seat.

What free-text naming actually costs

  • Duplicate projects. The same work opened twice under two names, costs split across both. Neither balance is right, and both look plausible.
  • Orphaned costs. Invoices coded to a project nobody recognizes at close, so they sit in CIP indefinitely instead of being capitalized or expensed.
  • Impossible portfolio views. "How much have we spent at the north campus since 2022?" becomes a research project rather than a query. That question should take nine seconds.
  • Audit friction. Sampling a CIP balance is easy when project identity is unambiguous. It is a long afternoon when the auditor has to ask what four similar names mean.
  • Lost componentization. When the name does not encode what kind of work it is, the person capitalizing it four years later has no signal at all about how it should be broken apart.

A convention that survives contact with reality

The usual mistake in a naming standard is ambition. A twelve-segment code that captures everything will be abandoned inside two quarters, because the people opening projects are facilities managers under deadline, not data stewards, and they are right to prioritise the building.

What holds up is short, structured and enforced at entry:

  • Location. A controlled list, matching the site codes finance already uses. Never free text.
  • Asset class or work type. Building, building improvement, fixed equipment, moveable equipment, software, infrastructure. Six to ten values, not forty.
  • Year initiated. Makes aging visible in the name itself, which is a small piece of quiet genius.
  • A short human description. Free text belongs here, and only here.

The load-bearing word is enforced. A convention living in a policy document is a suggestion. A convention implemented as required dropdowns in the system where projects are actually opened is a control. If somebody can type a project name into a blank box, they will, and your standard is already a memory.

The bottleneck was never the volume

When capital reporting gets slow, organizations reach for more staff or a new system. Sometimes those are the right answers. But in most of the fixed asset environments I have walked into, the constraint was not capacity or software — it was that the underlying data had no consistent identity, so every question needed a human to interpret it first.

Standardizing project identity is a small piece of work with a wildly disproportionate payoff. It is also the prerequisite for everything downstream: componentization, in-service date governance, and clean conversion into a fixed asset system. And it matters more every year, because the analytics and AI-assisted tooling arriving in this space can only group what has been consistently identified. Loading badly-named data into a smarter system just produces the same problem at higher speed, with more confidence attached.

What's in a name? For a capital portfolio: whether you can report on it at all.