How the register works for a contractor
- Open long-lead PO lines come from your ERP or PO log export.
- Required-on-site dates come from your schedule export (P6 XML, MS Project XML or CSV), mapped to PO lines by a table your PM approves.
- Every line compares the ERP date, the vendor's latest written date and the required-on-site date, and shows float in weeks.
- Lines under your float threshold go on the slip list for the PM, and the weekly owner or GC update is drafted for the PM to edit and send.
Put the log in the proposal
Archdesk advises separating price from deliverability on 2026 bids: put a named long-lead log in the proposal, price expediting, and link buyout dates to a live cost report. A Long-Lead Check on a current project produces that log for one project in 10 business days, in a format your team can reuse.
Questions
Does this replace our PM's lookahead?
No. The PM still owns the lookahead and the owner conversation. The register gives the PM each long-lead line's latest vendor date and float, plus a drafted update to edit.
Can it read our P6 schedule?
Yes, from an export: P6 XML, MS Project XML or CSV. The desk never writes to your schedule.
Sources
- Archdesk, 2026 US Data Center Construction: $85B Market Breakdown, archdesk.com/blog/2026-us-data-center-construction, published 2026-04-16, read 2026-09-25
Updated . Lead times are public planning ranges, not quotes; your vendor's written date governs.