Our last piece made the case that a baseline’s first real output is a list of what was wrong, not a clean record, and that resolving that list properly is what makes a baseline worth building on. This is the practical half: what reconciling a baseline actually involves, step by step, from four separate sources down to one view anyone can trust.
Four sources, four different truths
Every site sits inside at least four systems, each right for its own purpose. Leasing and commercial records hold the contracts, the rent, and the wayleaves. Network systems, usually an OSS/BSS, hold what equipment is installed and what capacity it’s rated for. Field and ops records hold whatever the last truck roll actually found. Permitting and compliance records hold what’s been approved and what’s still pending.
None of these is wrong on its own terms. Each is accurate for the process it supports. The problem is that a baseline needs a single answer, and none of the four was built to give one on its own.
Building one view
Reconciliation starts by pulling all four into the same frame, site by site, and comparing them directly rather than assuming any one is authoritative. Where they agree, that’s confirmed. Where they don’t, that’s a discrepancy, and it needs a rule, not a guess, for which source wins and why.
The rule isn’t always the same. A capacity figure might defer to the network system, since that’s what engineering plans against. A lease term might defer to the commercial record. A wayleave status might defer to permitting. What matters isn’t picking one system as authoritative across the board. It’s deciding, deliberately, which source governs which fact, and applying that consistently across every site rather than resolving each conflict ad hoc under deadline pressure.
Then field verification
Even a perfectly reconciled desk record is still a set of claims about the physical world, and physical infrastructure doesn’t always match what any system says. Equipment gets swapped without the paperwork catching up. A site gets decommissioned informally before anyone updates the record. The only way to close that last gap is to check: a field verification pass against a sample, or in higher-risk cases the full portfolio, before the baseline is treated as settled.
This step is usually the one that gets skipped under time pressure, because it’s the slowest and most expensive part of the process. It’s also the one where the cost of skipping it lands hardest. A gap caught here is a correction. The same gap, uncaught, surfaces later as a resourcing decision built on the wrong picture, a schedule that has to be re-planned, or a delivery commitment that can’t be quietly walked back. The error doesn’t get any bigger between now and then. What it costs to fix does.
Sequence matters
Doing this out of order costs more than doing it slowly. Field verification before reconciliation means technicians go out working from whichever single record was closest to hand, not the consolidated picture. Information sitting in one of the other three sources, a lease that just renewed, a capacity change, a permit still pending, never gets checked against what’s actually there, and it can get overwritten or lost the next time that record is updated. Reconciliation without field verification produces a document that looks resolved but was never tested against reality. The order is: pull the four sources, reconcile the conflicts with clear rules, then verify what’s left in the field. Skipping ahead doesn’t save time. It moves the same work later, at the point where it’s most expensive to redo.
This is what “get the baseline right” actually means in practice. Not a faster starting point, a properly sequenced one, built once and then held to the same standard every time it’s touched again.
Where we come in
Sitenna’s Management Cloud is built to make this process fast rather than painful. It pulls leasing, network, field, and permitting data into one consolidated view, applies consistent rules to resolve conflicts, and tracks exactly what still needs field verification, instead of leaving that step to a spreadsheet someone has to chase down manually. That means reaching real asset data confidence in days rather than months, and building a baseline that’s protected against the inconsistencies and gaps that would otherwise surface later, when a change means delay and additional cost instead of a quick correction.
If you’d like a faster, more reliable way to consolidate your baseline, get in touch today.
About Sitenna
Sitenna is the intelligent operations platform built to eliminate blind spots across modern infrastructure. By centralizing fragmented asset data and automating workflows from site acquisition through execution and management, Sitenna delivers the real-time visibility and control needed to keep projects on track. With Sitenna, infrastructure teams move faster, collaborate smarter, and scale confidently – turning complexity into clarity at every stage.
Contact us at sales@sitenna.com