A schedule of values exported from certain project-management systems uses a merged header row above the change-order block. Our column mapper read that row as data, then skipped every line beneath it. The base contract imported correctly, so the totals looked plausible and the omission was easy to miss.
What changed
- Merged headers are detected and skipped, and the change-order block is mapped to the same columns as the base contract.
- Line-count validation on import. If the number of lines written does not match the number of lines read, the import fails loudly instead of completing with a short schedule.
- Affected routes were re-synced. Any lender or program-manager route that received a truncated schedule since 3.1.0 has been refreshed with the corrected version, and the audit log records the correction.
Who was affected
Workspaces importing a schedule of values from a file with a merged change-order header between 3 January and 24 February 2026. We contacted the twelve affected workspaces directly before this note was published. No other route data was involved.