
The paperwork breaks when a subcontractor bills for installed work and the superintendent cannot identify where it went. I recommend checking the reporting process before award: every claimed activity needs a location, a scope reference, supporting field evidence, and a clear approval status.
By Marco Ruiz
Check whether the subcontractor can connect its daily reports, delivery tickets, and payment backup to work your superintendent can locate and inspect.
License, insurance, and bond verification establish important parts of a subcontractor’s qualifications. Field documentation answers another hiring question: can this company explain what happened onsite well enough for your team to supervise, approve, and pay for it?
During bid review, I would request a blank daily report and a redacted example of the records normally submitted with a payment request. The blank form shows the intended process. The completed example shows whether that process survives actual use. Remove confidential project and commercial information before sharing examples.
Look for recognizable locations, descriptions of the activity performed, and references connecting attachments to the report. A photograph becomes more useful when its location and capture date travel with it.
For subcontractor sourcing, SubSource helps contractors find and vet verified construction subcontractors. I would carry that review into the preaward meeting by asking who prepares field records, who checks them, and who answers discrepancies. Include the proposed field contact. The estimator’s filing habits may tell you little about the foreman’s daily process.
Use consistent location and scope references across the subcontract, daily reports, inspection records, and payment backup.
“Electrical rough-in complete” leaves the reviewer guessing about the area covered and any unfinished work. A usable entry identifies the location, activity, applicable drawing revision, and conditions still affecting completion.
Before mobilization, agree on location names. If the schedule uses a different area designation from the drawings, document the connection during the handoff. Otherwise, every payment review requires someone to translate between systems.
I would put these requirements into the reporting instructions:
Then follow a claimed activity through the documents. Can the superintendent find the installation? Can the payment reviewer identify the corresponding scope? Can someone opening the file later understand an unresolved inspection? Any answer that depends on remembering a conversation exposes a documentation gap.
A daily report should distinguish installed work from work awaiting inspection, correction, access, or another prerequisite.
“Complete” can mean the installation crew has left the area while the superintendent is still waiting for an inspection before releasing the next trade. Billing introduces another question: what progress does the subcontract allow the reviewer to recognize?
Record the actual condition. Write that installation awaits inspection when that is the status. Identify an inaccessible area and explain which planned activity it prevents. Keep the unresolved condition attached to the location so it remains visible during scheduling and payment review.
Concealed work deserves particular attention. Before enclosure, agree on the required inspection and documentation process, then connect the resulting records to the affected installation. A general progress photograph may establish that a crew was active without showing the condition the reviewer needs to evaluate.
I would also keep correction records connected to the original entry. A later photograph should identify what it resolves. Otherwise, the folder grows while the status remains uncertain.
Payment backup should explain the claimed progress, stored materials, and applicable withholding using the governing contract’s requirements.
A useful public benchmark is FAR 52.232-5, Payments Under Fixed-Price Construction Contracts. For federal contracts containing that clause, estimates supporting progress-payment requests must include itemized amounts related to the contract’s work elements, amounts for subcontractor work, subcontract amounts, and previous payments to subcontractors.
The same clause permits retainage of up to 10% of the payment amount when satisfactory progress has not been made. It also says the contracting officer shall authorize full payment without retention when satisfactory progress has been achieved. That figure belongs to this federal clause; your subcontract’s retention provisions need their own review.
The operational lesson is practical: a deduction should have an identifiable contractual basis and a visible calculation. Keep claimed progress, approved progress, stored materials, and retention distinguishable in the payment review.
For quantity-based work, agree on measurement methods and units before installation. A delivery ticket establishes receipt; a field measurement supports an installed quantity. Identify which event supports the requested payment under the subcontract.
For stored materials, check the actual payment conditions. FAR 52.232-5 allows consideration of materials delivered onsite and preparatory work, while materials stored elsewhere require specific contract authorization and satisfactory evidence of title and intended contract use. Use those distinctions to examine your own requirements before accepting a warehouse ticket as sufficient backup.
Field tickets become disputed when their signatures and references leave the parties uncertain about what was acknowledged or authorized.
A ticket may document labor, equipment, and materials used. Its signature block should make the signer’s role clear. Review whether the signature acknowledges field facts, accepts quantities, or approves additional compensation, and have your contract reviewer resolve ambiguous language before the forms reach the trailer.
Connect changed work to its originating direction or request. Identify the affected scope, location, relevant drawing revision, and authorization status. Preserve the pricing and schedule information needed for review alongside the field record.
Notice requirements can make the dates consequential. FAR 52.243-4, Changes, generally requires a contractor to assert its right to an adjustment within 30 days after receiving a written change order or furnishing the specified notice, unless the contracting officer extends that period.
For certain changes arising from other directions, that clause also generally excludes costs incurred more than 20 days before written notice, with an exception for defective specifications. These are provisions of that federal clause. Private subcontracts and other public contracts may set different procedures and deadlines.
I would use those figures to frame a preaward question: who recognizes a potential change, who sends the required notice, and where is the submission date recorded? A signed time ticket alone may leave that workflow unfinished.
Ask the bidder’s proposed field contact to demonstrate how its normal records would support payment for a scope item in your bid package.
Have that person explain the location reference, supporting attachments, inspection status, and review responsibility. Then ask how the same record would identify changed work and reach the person responsible for contractual notice.
Keep the agreed process usable in the field. Specify where records are submitted, who reviews discrepancies, and how corrections remain connected to the original submission. Documentation requirements belong in the subcontract handoff where the foreman and project manager can act on them.
On the next bid, select a scope item and add this preaward agenda entry: “Show the daily record and payment backup you would submit for this work.” Write the agreed requirements into the handoff before issuing the notice to proceed.