Documentation
Excel round-trip: import with a dry-run diff, export board-clean
How Fieldcurve imports an existing Excel tracker safely — the dry-run diff, conflict handling, one-transaction commits — and exports workbooks your stakeholders already read.
Your program’s owners, contractors, and steering decks live in Excel, and pretending otherwise just re-forks the truth. Fieldcurve treats the spreadsheet as an interface: import what exists, export what stakeholders expect.
Importing a tracker
- Upload the .xlsx. Fieldcurve reads the MAT structure — phases, milestones, activities, tasks — plus weights, percents, statuses, and owners.
- Review the dry-run diff: every row classified as create, update, or conflict, with warnings called out (a duplicate name, a percent on a non-leaf, a row that moved). Nothing has been written yet.
- Approve. The commit is one transaction under your own permissions — the same checks as manual edits — and rollups recompute as part of it. A failed import changes nothing.
Re-importing a returned workbook works the same way: the diff shows what changed against the live tree, so a contractor’s markups become a reviewed update instead of a paste-over.
Exporting
Exports are board-clean workbooks that match your template’s layout — the people who stay in Excel keep reading the format they already trust, now stamped from one live source. Export anytime; copies are read-only snapshots with a date, exactly what an emailed tracker should have been all along.
Leaving (yes, really)
The same export is the exit: your full structure and numbers in clean .xlsx, any time, no ransom. We’d rather earn the renewal than lock the door.