The estimate, the project system and the accounting system each hold a cost code structure, and the mapping between them lives in a spreadsheet maintained by one person.
A project generates a paper chain where each hop is a re-keying. A field condition becomes a time and materials tag, then a potential change order, then a priced request, then an executed change order, then a budget revision, then a line on the next payment application. Every hop is a place the amount can quietly diverge.
Drawings are the authority and they are PDFs. A revised sheet arrives as a bulletin, and if it is not slipped into the current set, somebody builds from a superseded drawing. Automated document handling fails exactly where a human has to recognise that a revision supersedes another and that the change was inside a cloud on one elevation.
Waiver collection is the recurring back-office task that generates the most complaints. Before releasing payment, somebody requests waivers from every subcontractor and supplier, checks the form matches the statutory wording where the state prescribes one, checks the through-date, and holds payment on whoever has not returned.
Estimating carries one cost-code structure. Project management carries another. Accounting carries a third. When the mapping drifts, job cost reports become quietly wrong, and nobody notices until the work in progress schedule looks strange to a surety.
A waiver on the wrong form or carrying the wrong through-date can be void, or can waive more than intended. Templating one form across states is a legal risk rather than a formatting convenience.
The field cannot wait for paperwork, so the physical record and the financial record are out of step for the duration of the job. Any automation assuming approval precedes cost will be wrong most of the time.
Payment applications are uploaded by hand, often with a required naming convention and upload order. The credential is frequently shared, which is a control problem as well as an automation blocker.
The submittal requirements sit scattered through a specification book, in division one general provisions and again inside each technical section that demands one, and the register is the list of every section involved, who owes it, and when it is needed working back from the schedule through fabrication lead time.
The payment run goes out and the waivers have to come back before it, in the exact form the state statutes prescribe, which differs by state and by tier: a subcontractor signs one form, the second tier supplier beneath him another, and a waiver executed on the wrong statutory form is void from the start no matter when it was signed.
An RFI has a contract defined response window, and the clock that matters is the one nobody watches: the day the answer arrived versus the day it reached the drawing set and the subcontractor whose work it changes.
Billing week opens and the same numbers get retyped.
Public work adds a weekly statement of compliance behind every payroll run, and the portal is where it comes apart.
An approved change order lands in more places than anyone remembers.
A tag gets filled out at the end of a shift, signed by whichever superintendent is standing there, then rides around in a truck.
Nothing fires when a policy lapses.
The clock that matters starts at neither the contract nor the invoice.
Final payment waits on a stack that already exists in pieces.
Three structures and one spreadsheet holding them together, maintained by one person.
Every prequalification file ages.
An estimator opens a mailbox holding invitations from BuildingConnected, from iSqFt, from a plan room link that expires, and from a project manager who just attached the drawings.
Public bids fail on paperwork rather than on price.
A three way match is harder in the field than in an office.
Retention is money already earned and then held back.
Photos come geotagged and timestamped at capture, so the field record usually exists.
Lien deadlines are statutory, vary by state and by role, and run from a furnishing date rather than from an invoice date. Two clocks are involved and they start at different moments: a preliminary notice is generally measured from first furnishing, while recording the lien itself is generally measured from last furnishing. Missing one extinguishes the right, which is why anything touching notice timing should calendar and alert rather than file autonomously, and why specific day counts belong to your state rather than to a general rule. Publicly funded work adds prevailing wage and weekly certified payroll with correct classification, and quality certifications add document control requirements: the current revision has to be available where it is used, changes have to be tracked, and records retained. An automation that moves or supersedes a controlled document without preserving that trail breaks the certification itself and not only the workflow.
Related: Field services Manufacturing. Or start from the four shapes of work instead of from an industry.