Owner-ready reports and billing backup field guide for data centers

The field record behind the report and the pay app

Owner-ready reports and the billing backup behind them are only as good as the field record they are built from. The progress report the owner reads and the pay application that gets you paid both trace back to the same source: the photos, the daily reports, the signed tickets, the delivery slips, and the test records the field made while the work was live. Document the work and it gets paid and accepted. Leave it undocumented and it gets argued, and the argument happens months later when the people who saw the work are gone.

The pattern is constant across every job. The field builds the work well, then the office tries to bill it from memory, a phone full of unsorted photos, and an email thread nobody can find. The progress report becomes a status nobody can defend, and the pay application gets cut because the certifier has nothing to certify. The gap is never the work. It is the record between the work and the money.

This guide is about closing that gap: turning the contemporaneous field record into the owner-ready progress report and the pay-application backup without rebuilding it from scratch at the end of the month. The standards here are commercial, not code. The contract and its Division 01 billing requirements control what your report and your pay application must contain, so read that section first and write to it.

What is a G702 pay application?

The AIA G702 is the application and certificate for payment, the one-page cover sheet that summarizes what you are owed this period and gets certified by the architect or the owner's representative. The G703 is the continuation sheet behind it, where the schedule of values is broken into line items and each line carries its numbers. They are not two forms. They are two halves of the same document, and the bottom totals on the G703 have to tie to the summary on the G702 or the application stalls.

The G702 shows the status of the contract: the original contract sum, the net change by approved change orders, the total completed and stored to date, the retainage held, the previous payments, and the current payment due. The G703 is where that total comes from. For each line it carries the scheduled value, the work completed in prior periods, the work this period, the materials stored but not yet installed, the total to date, the percent complete, the balance to finish, and the retainage on that line.

AIA G702 and G703 are the common framework on commercial and data center work, but ConsensusDocs and EJCDC have their own application forms, and many owners run a custom format. Verify the form and the required backup against your contract, because the contract, not the form's reputation, controls what gets certified and what has to sit behind it.

The schedule of values

The schedule of values, the SOV, is the contract sum broken into billable line items, and it is the spine of every pay application that follows. Each line is a piece of the work with a dollar value, and the values across all the lines add up to the contract sum. Once the owner and the architect accept the SOV early in the job, you bill against it every period by reporting how complete each line is. Get the SOV right and billing is mechanical. Get it wrong and you fight every month.

The structure of the SOV decides how cleanly you can bill. Lines that are too coarse, one line for a whole floor of electrical, make it impossible to show real progress and easy for the certifier to dispute the percent. Lines broken the way the work actually installs, by system and area, let you bill what you built and back it with the field record. Carry separate lines for stored materials and for general conditions where the contract allows, because those bill differently than installed work.

Front-loading is the open secret of the SOV. Contractors weight the early lines high to improve cash flow in the first months, and owners and lenders push back because front-loaded billing means paying for more than is in place. An unbalanced SOV that the owner catches damages trust for the rest of the job and invites scrutiny on every later application. A fair SOV that matches value to work bills faster because nobody is fighting it. The contract and the owner's review govern how much weighting survives.

What backup does a pay app need?

A pay application needs the backup that lets the certifier verify the percent complete without taking your word for it: the progress photos, the daily reports, the delivery and stored-material proof, the signed change tickets, and the test and inspection records. A pay app without backup is an assertion, and an assertion gets cut to whatever the certifier can see for themselves, which is always less than you claim.

Each piece backs a different part of the application. Photos prove the installed work behind the percent on each SOV line. The daily reports prove the manpower and the production that built it, and they are the contemporaneous record the construction daily report and documentation guide gets into in depth. Delivery slips and stored-material documentation back the materials line. Signed T and M and change tickets back the change-order lines, which the field change order and takeoff guide covers. Test and inspection records back the lines that cannot be billed until they pass.

The reason a clean pay app gets certified fast is that it leaves the certifier nothing to question. When the photo, the daily, and the ticket all say the same thing the SOV line claims, the percent is verified and the line gets paid. When the application says 60 percent and the backup shows 40, the certifier cuts it to what is proven, and now you are financing the difference until next month. Build the backup as the work happens, attached to the line it supports, and the application defends itself.

Conditional vs unconditional lien waivers

A lien waiver is the document you sign giving up your right to file a mechanic's lien for the work covered by a payment, and it almost always travels with the pay application. The distinction that matters is conditional versus unconditional. A conditional waiver takes effect only when the payment actually arrives and clears. An unconditional waiver takes effect the moment you sign it, whether the money shows up or not.

That difference is where contractors get hurt. The safe sequence is to submit a conditional waiver with the pay application, before you are paid, and to sign the unconditional waiver only after the check has cleared your account. Sign an unconditional waiver before the money clears and the check bounces, and you have waived your lien rights on money you never received. There are four common forms: conditional and unconditional, each on progress payment and on final payment. The conditional progress waiver is the one you use most during the job.

Lien rights and waiver forms are state-specific. Some states, California among them, set statutory waiver language that the form has to match to be valid, and the deadlines to preserve a lien are short and unforgiving. Do not sign a waiver form you have not read, and confirm the form and the lien deadlines against your state's statute and your contract, because this is one place where the wrong signature on the wrong day forfeits a real right.

Retainage and the money held back

Retainage, or retention, is the percentage the owner holds back from each payment as security that the job gets finished and the punch list gets done. A common figure is 5 to 10 percent withheld from each pay application, but the percentage and the rules are set by the contract and, on public work, often by statute. The retainage line shows on the G702, and it is real money. On a large data center the retention held across a long job is a number worth managing, not ignoring.

Two moves protect the retention. First, bill it correctly every period so the held amount on your records matches the owner's. Second, chase the release on the schedule the contract allows. Many contracts permit a reduction of retainage at substantial completion or at a milestone like topping out, and a contractor who never asks leaves that cash sitting. Public-work statutes often cap the retention percentage and set a deadline for its release after completion, so the rules are not always the owner's to write.

Getting retention released is a closeout problem as much as a billing one. The final retention does not come loose until the punch list is complete, the closeout documents are in, and the final lien waivers are signed. The cleaner the closeout record, the faster the last check moves, which is why the closeout package and the retention release are the same fight.

The owner-ready progress report

The owner-ready progress report is the document the owner and the lender actually read, and it is a different animal from the internal report the team runs the job on. The owner wants the percent complete against the schedule, the photos that show it, the schedule status with the milestones, the open issues and their impact, and the manpower trend. The lender wants the same picture because the draw depends on it. What neither wants is the internal detail the field uses to manage the work day to day.

The difference is altitude and audience. The internal report is granular, blunt, and full of the problems the team is solving. The owner-facing report is accurate but framed for a reader who is not on site every day and who is deciding whether to release money. The monthly report is the formal version, often tied to the pay-application cycle, and it is frequently a contract deliverable in its own right. A report that contradicts the pay application is a problem, so the percent complete in the narrative and the percent on the G703 have to agree.

The trap is two separate efforts: a pay application built one way and an owner report built another, from different numbers, by different people, at the end of the month. When both come from the same field record, the photos in the report are the photos behind the pay app and the progress in the narrative is the progress on the SOV. They agree because they came from one source, and the owner trusts a report that lines up with the billing.

Stored materials and billing for what is not installed

Billing for stored materials is how you recover the cost of equipment bought and delivered but not yet installed, and on a data center it is a large number, because the long-lead gear, the switchgear, the PDUs, the generators, gets bought and staged months before it lands in place. The materials-stored column on the G703 is where it bills. What makes it billable is the proof, and stored-material billing gets cut faster than any other line when the proof is thin.

The owner wants to see that the material exists, that it is paid for or invoiced, that it is properly stored and protected, and that it is insured and free of competing claims. For material stored off site, the requirements get stricter: a bonded warehouse, separate identification of the owner's material, proof of insurance, and sometimes a bill of sale transferring title. The photo of the gear with a visible identifier, the supplier invoice, and the insurance certificate are the backup that gets the line approved. Without them the certifier has no way to know the money is not going to a unit sitting in someone else's yard.

Bonding and insurance sit underneath all of it. The owner is paying for material they do not yet have in place, so they want the security that if the contractor fails or the material walks, they are covered. Confirm the stored-material requirements in the contract before you bill the line, because the documentation the owner demands for off-site storage is the part contractors underestimate every time.

The closeout and turnover package

The closeout package is the final documentation deliverable that the contract requires before final payment and retention release, and it is a deliverable in its own right, not an afterthought. It commonly includes the as-built drawings, the operation and maintenance manuals, the warranties, the spare parts, the training records, the final lien waivers, and the consent of surety where there is a bond. The contract's Division 01 closeout requirements spell out the list, and final payment is usually conditioned on delivering it complete.

Closeout is where a year of loose records gets reckoned with. The jobs that close fast are the ones that kept the record as they went, so assembling the package is collection, not reconstruction. The jobs that drag through closeout for months are rebuilding from memory the as-builts, the test records, and the photos that should have been captured while the work was live. The retention does not release until the package is accepted, so a slow closeout is a direct cost in cash held.

Treat closeout as something you build all along, not a phase at the end. Every test record, every inspection signoff, every as-built markup captured when it happened is one less thing to chase at the close. The owner-ready report and the pay-application backup you kept through the job are most of the closeout package already, which is the payoff for keeping the field record clean from day one.

The commissioning record in the owner deliverable

On a data center the commissioning record is a major part of the owner deliverable, because the owner is buying systems that have to work under load, not just equipment that is installed. The functional tests, the integrated systems test, the level-by-level commissioning results, and the deficiency log all roll up into the turnover package the owner accepts. The data center commissioning and operations program runs that witnessing and the deficiency tracking. The billing side cares because lines tied to commissioned systems often cannot be fully billed or released until the tests pass.

The link between commissioning and the money is the witnessed test. A test the commissioning agent witnessed and accepted is a milestone, and the record of who witnessed it and what the result was backs both the closeout package and the pay-application line that depended on it. When commissioning kicks back a deficiency that adds scope, that becomes a change, and the field change order and takeoff guide covers turning that into a priced, signed line on the next application.

The owner report should carry the commissioning status the same way it carries construction progress, because to the owner and the lender, a system that is installed but not yet commissioned is not done. Reporting commissioning progress honestly, against the plan, keeps the owner's expectation aligned with what is actually billable, and it keeps the final lines from being a surprise at turnover.

How do approved change orders get into the pay app?

An approved change order is not money until it is added to the schedule of values as its own line and billed on a pay application like any other line. The change gets its own SOV line, carries its own percent complete and retention, and flows through the G703 into the G702 summary, where the change-order total shows separately from the original contract sum. A change that is signed but never added to the SOV quietly never gets billed, and that happens more than anyone admits.

The discipline is to reconcile the approved changes against the SOV every billing period. Get the executed change onto the next application after it is signed, not the one after that, because every cycle it sits unbilled is cash you financed for the owner at no charge. Keep a running change log and check it against the billing so an approved change does not fall into the gap between the change process and the pay application.

Directed but unsettled work is the harder case. A construction change directive without an agreed price cannot be billed as a fixed line, but the documented force-account cost is real, and many contracts allow billing that cost pending final adjustment. The field change order and takeoff guide covers the change process end to end. The billing point is simple: an approved change that is not on the SOV is a change that is not getting paid.

Why the field record drives the money

Every recurring fight at billing time comes down to the field record. The owner says the work is 40 percent complete and you billed 60. The owner says the extra was always in the base contract. The certifier cuts the pay application because the backup does not support the claim. In each case the resolution is the same: the contemporaneous record of what was actually built, when, and by whom. The side with the clean record wins, and it usually wins without a fight, because there is nothing to argue.

The fights are not really about the percent or the extra. They are about evidence. A disputed percent complete ends the moment you show the photos and the daily reports that prove the installed quantity. An unbacked extra dies on its own. A rejected pay app gets certified when the backup arrives. The work that is documented gets paid. The work that is not gets argued, and the argument is expensive whether you win it or not.

This is the practical case for keeping the field record in one place as the work happens. FieldOS is the offline-first field tool a lot of crews use for exactly this: the photos, the daily logs, the tickets, and the proof packets live together, attached to the job and the SOV line, so the owner report and the pay-application backup assemble from the record that was already kept. The point is not the software. The point is that the field record becomes the report and the billing backup without anyone rebuilding it from scratch at the end of the month.

The takeoff and the quantity backup for the bill

Unit-price and quantity-based billing is only as defensible as the takeoff behind it. When a line bills by installed quantity, conduit by the foot, devices by the count, busway by the section, the number you bill is the number you measured in the field, and the owner's reviewer can check it against the same field. A quantity pulled from the plan instead of the installed reality is a quantity the reviewer can dispute, because the routed and installed work rarely matches the straight-line drawing.

The cleanest billing happens when the field quantity flows straight into the priced line without being retyped, rounded, or lost between the deck and the office. You count and measure once, where the work is, and that count becomes the basis for the line on the application. Taking off in the field with takeofffielddc keeps the measure and the money tied together, so the quantity you bill is the quantity you can stand behind when the certifier asks how you got it.

This matters most on the change-order lines and the unit-price work, where the quantity is the whole argument. A change billed on a field takeoff with the photos and the measurement behind it gets certified. A change billed on a number nobody can source gets cut. The quantity backup is the bridge between the work installed and the dollars on the line.

The searchable record vs the email-and-spreadsheet scramble

Billing time on a job run out of email and spreadsheets is a scramble, and the scramble is where money leaks. The photos are on three foremen's phones. The daily reports are in a notebook in a truck. The signed tickets are in an email thread. The delivery slips are in a pile at the trailer. Each piece is real, and together they are useless, because nobody can assemble them into a pay-application backup package in the days before the application is due.

The binder is the old version of the same problem. A wall of paper in the trailer is unsearchable by definition, and it cannot be in two places at once, so the office and the field never have the same record. When the certifier questions a line, the answer is buried in a binder somebody has to drive to. The digital record beats the binder on every axis except needing power, because a photo that carries its own date and location, in a record you can filter by SOV line and date, is a backup that produces itself.

The objection on a real data center is signal: a steel box with no service three levels down. An offline-first tool that captures the photos and the log locally and syncs when the device gets back to signal is the only kind that works where the work is. FieldOS is built that way, so the record gets made at the gang box and the pay-application backup is already assembled when billing comes due, instead of being chased across four apps and a truck cab.

What gets pulled in a payment dispute or an audit?

In a payment dispute or an audit, what gets pulled is the contemporaneous record behind every line that was billed: the SOV and its approval, the pay applications and their backup, the change orders and their tickets, the lien waivers exchanged, the delivery and stored-material proof, and the daily reports that show the work. A lender audit, an owner audit on a cost-plus or guaranteed-maximum-price job, or a dispute headed to a claim all reach for the same evidence, the paper made before anybody had a reason to shade it.

The record that holds up is the one made at the time. An auditor trusts a dated photo, a signed ticket, and a daily report written the day the work happened. An auditor discounts a narrative typed up later to support a number, because a reconstruction made under audit pressure is exactly the record that gets picked apart. On a guaranteed-maximum-price or cost-plus job the owner has audit rights into the actual costs, and the contractor who cannot produce the backing for a cost line loses that line, not because it was not real but because it was not proven.

The defense is built during the job, not after the demand letter. A clean, searchable, contemporaneous record is the difference between an audit that confirms your billing and one that strips it. Keep the record as you go and the audit is a formality. Reconstruct it after the fact and the audit is a loss waiting to be quantified.

Owner trust and the next job

A clean report and a clean pay application do more than get this job paid. They win the next one. Owners and developers build repeatedly, and the contractor whose billing is straight, whose reports match reality, and whose closeout package shows up complete is the one who gets the call without a competitive bid. The report is a sales document whether you treat it as one or not, because it is the most consistent thing the owner sees from you all year.

Trust at billing compounds. A front-loaded SOV the owner catches, a pay application that overstates progress, a stored-material line with no proof, each one teaches the owner to scrutinize everything you submit, and scrutiny slows every payment for the rest of the job. The opposite compounds too. A few months of applications that tie out cleanly and a few reports that match what the owner sees on a site walk, and the reviews get faster because you have earned the benefit of the doubt.

The record outlives the job. The property and job history the owner keeps, the reports, the closeout package, the commissioning record, becomes the baseline for the building's operation and the starting point for the next phase. A contractor who hands over a clean, organized record is the contractor the owner wants back, because the alternative is a successor who inherits a mess. The clean field record is not just how you get paid this month. It is how you get the next job.

What to document each pay period

Track the same fields on every pay application from the first one, so each period reconciles cleanly against the last and against the contract. The table below is the working set for a data center or large commercial application. Match it to the contract's Division 01 billing requirements and the owner's required format, which control what you actually submit.

The rule behind the list is that every field is something the certifier, the lender, or an auditor will check. Fill it so the application defends itself, with the backup attached to the line it supports, not stored somewhere a reviewer cannot reach.

Common mistakes

• Submitting a pay application with no backup, so the certifier cuts the percent to what they can verify.
• Billing stored materials with no invoice, photo, insurance, or storage proof, and watching the line get cut.
• Signing an unconditional lien waiver before the check has cleared, waiving rights on money not yet received.
• Building the owner report from memory at month end instead of from the field record.
• Leaving an approved change order off the schedule of values, so it never gets billed.
• Front-loading the SOV hard enough that the owner catches it and scrutinizes every later application.
• Letting the percent complete in the owner report disagree with the percent on the G703.
• Never asking for the retention reduction or release the contract allows, and leaving the cash held.

Field checklist

Standards and references

The governing document is the contract, not a code. The general conditions and the Division 01 administrative and billing specifications spell out the application form, the required backup, the schedule-of-values approval, the retainage, the lien-waiver exchange, and the closeout requirements. That language is project-specific and it controls. When the contract and any general practice conflict, the contract wins, every time.

The AIA documents are the common framework on commercial and data center work. AIA G702, the application and certificate for payment, and G703, the continuation sheet, are the widely used application forms, and the AIA A201 general conditions carry the payment, retainage, and certification provisions behind them. ConsensusDocs and EJCDC are the other widely used families and handle the same ideas with their own forms and articles. The forms get amended by supplementary conditions and owner requirements, so read the documents you signed for what actually applies.

Two areas are law, not contract, and both vary by jurisdiction. Mechanic's lien and lien-waiver rules are state-specific, and some states set statutory waiver forms and short, strict deadlines to preserve a lien, so confirm the form and the dates against your state's statute. On public work, prompt-payment and retainage statutes often cap the retention and set release deadlines the owner cannot rewrite. This is commercial and legal ground, not code, so name the document that controls the point and verify the specifics against your contract, your state's statutes, and your counsel.

Terms and definitions

Billing carries its own vocabulary, and the same idea goes by different names across contract families. Using the terms precisely is part of keeping a pay application that gets certified without a back-and-forth.

The terms below are the ones that decide how the work gets billed, backed, and released. The difference between a conditional and an unconditional waiver, and between the scheduled value and the percent complete, is exactly where applications get held up.

G702 / G703

The AIA application and certificate for payment (summary) and the continuation sheet (line-item detail); two halves of one pay application

Schedule of values (SOV)

The contract sum broken into billable line items, the basis billed against each period

Percent complete

The portion of a line finished to date, most defensible when tied to a countable quantity rather than an eyeball

Retainage / retention

The percentage withheld from each payment as security, released at completion or a milestone per the contract

Lien waiver

A signed release of lien rights; conditional takes effect on payment, unconditional on signing

Stored materials

Material delivered but not installed, billable with invoice, photo, insurance, and storage proof

Backup

The contemporaneous records, photos, dailies, tickets, deliveries, tests, that verify a billed line

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What goes in a construction daily report?
• What is a field change order?
• What is an as-built drawing?
• Why do battery rooms need ventilation?
• What is the maximum cable tray fill?