Why Facility Handover Packages Still Live in Excel — and What Breaks When They Do

Turnover packages, readiness trackers, and punch lists still live in spreadsheets for a defensible reason: Excel is the one tool every owner, EPC, and package vendor already runs. Any plan that starts with “everyone stops using Excel” fails at the first subcontractor. The problems are real, though, and they're specific:

What actually breaks

• Version forking.The tracker is emailed, edited in parallel, and merged by the youngest engineer at 9 p.m. The owner's copy and the site's copy disagree by Friday.
• Silent formula rot. Insert a row above the SUMPRODUCT range and the milestone rollup quietly stops counting it. Nobody audits a summary tab that looks plausible.
• No field path.Workbooks don't get updated from a scaffold. Progress waits for a desk, then gets typed twice — once wrong.
• No memory. When a percent changes, nothing says who, when, or what it was before. The audit question gets answered with archaeology.

Round-trip, don't rip-and-replace

The pragmatic architecture keeps Excel as an interface while moving the system of record somewhere with structure:

• Import with a diff. Returned workbooks are planned as a dry run — creates, updates, conflicts, and warnings shown row by row — and committed in one transaction only on confirmation. No silent overwrites.
• Export to the template.The owner keeps receiving the layout they've always received; it's simply generated from live data instead of hand-maintained.
• Stable row identity. Rows match on a stable key across the round-trip, so re-imports update rather than duplicate.

This is exactly how Fieldcurve treats spreadsheets: the tracker moves into a structured, audited, field-capable system; Excel stays as the lingua franca for everyone who never leaves it.