How can districts connect monthly payments to work installed?
A central principle of construction monitoring is straightforward: the amount billed for completed work needs to make sense when compared with what’s actually installed.
The process often begins before the monthly Owner-Architect-Contractor (OAC) meeting. The general contractor provides a preliminary, or pencil, draw package for review. Examining that package in advance gives the district an opportunity to identify trades, billing percentages, stored materials, change orders, or other items that deserve closer attention during the site visit.
During the walkthrough, the owner’s representative can compare those requests with physical progress. Different areas of a building may be at very different stages, which means completion percentages can’t be evaluated solely by looking at the project as a whole.
Consider a classroom renovation that includes new ceilings in 30 rooms. If only about three and a half classrooms have completed ceiling work and little or no related material is installed elsewhere, a request showing substantially more progress deserves further discussion. There may be a reasonable explanation, such as materials stored on site or supporting work completed in other rooms, but the billing needs documentation that connects the request to actual progress.
This review repeats across the trades included in the payment application. The resulting picture helps the district assess whether the overall amount requested is reasonable for the work completed to date.
What should districts review before approving a pay application?
Monthly construction payment packages can run hundreds of pages. A consistent review process helps district teams focus on the information most likely to affect project cost and risk.
Items to review in each payment cycle
Contract value and approved changes. Confirm the current contract amount reflects authorized changes and agrees with supporting documentation.
- Trade progress. Compare each subcontractor’s requested completion percentage with field observations and available backup.
- Stored materials. Verify requested payments for stored materials are supported and meet the applicable contract requirements.
- Previous payments. Confirm prior payments and the current amount due reconcile throughout the package.
- Retainage. Review amounts withheld under the contract and confirm they’re calculated consistently.
- General conditions. Compare general contractor administrative and project-support costs with overall project progress and the applicable contract terms.
- Change orders. Confirm approved changes appear accurately in the current contract value and related billing.
- Supporting invoices. Look for charges that lack adequate documentation, appear duplicated, or don’t align with the applicable scope.
General conditions deserve particular attention. When those charges progress significantly faster than the work itself, the district may need additional explanation. Early use of those funds could create financial pressure later, particularly if the project schedule extends beyond its planned completion.
Questions identified during the review can be documented and resolved before the district approves the final payment package.
How can schedule monitoring reveal cost risk early?
Construction schedules and construction budgets are closely connected. A delay can extend staffing, supervision, temporary facilities, equipment rental, or other project costs. It can also affect when students and staff can use a renovated or newly constructed space.
Monthly monitoring gives the district a chance to compare current progress with the baseline schedule and review a short-term look-ahead identifying work expected over the coming weeks.
Schedule indicators to monitor
- Planned milestones are being met
- The trades expected on site are actually mobilized
- Available labor appears sufficient for upcoming work
- Delayed activities could affect later phases or building occupancy
- Rework or rejected installations could affect completion
- Spending patterns remain reasonable given the project's physical progress
Reviewing the schedule alongside the pay application can expose mismatches. A project may appear to be financially far along even though field progress is lagging, or physical construction may be advancing while billing remains unexpectedly low. Either pattern can justify questions.
The district can then understand the cause while there may still be time to respond.
How should districts evaluate RFIs, change orders, and contingency use?
A Request for Information (RFI) is a formal question used to clarify information in the construction documents. An RFI doesn't automatically result in additional cost. If the answer changes the required scope, however, it may lead to a proposed change order.
Change-order review requires the district to understand both the reason for the change and its financial effect. Before approving a proposed change, owners can examine who initiated it, whether the work represents a legitimate modification to the contracted scope, how the price was developed, and whether applicable overhead or profit calculations comply with the contract.
An owner-requested upgrade to a more expensive finish, for example, may represent a valid change in scope. A cost arising because a contractor missed work already required by the contract may warrant a different discussion, depending on the agreement and circumstances.
Questions to address before approving a change
- What created the change?
- Does the requested work fall outside the existing contract scope?
- Is the proposed pricing supported?
- Do markups align with the governing contract?
- Does the change affect the schedule?
- How much contingency would the change consume?
- Has the change been logged and reflected accurately in project reporting?
Tracking potential changes before approval is especially valuable. A district that looks only at executed change orders may miss the growing financial effect of changes still under discussion.
Contingency tracking provides the other half of the picture. District leaders need visibility into what has been committed, what remains available, and what potential costs could draw on those funds later.
What reporting helps school boards and stakeholders understand project risk?
Construction teams work with detailed information, but district leaders and community stakeholders often need a clearer summary.
A useful monthly report can combine budget, schedule, project changes, and major risks in one view. A red, amber, green (RAG) indicator can also provide an at-a-glance signal of where additional attention may be needed, as long as the underlying criteria are clearly defined.
Information a monthly project report can include
- Overall physical completion
- Actual spending to date
- Current contract and amended budget values
- Forecast or expected completion date
- Schedule performance against the original plan
- Contingency committed and remaining
- Major unresolved issues
- Project and bid-package status
- Identified financial or schedule risks
For a bond program containing several projects or phases, consistent reporting also helps district leadership understand how each component is performing within the larger capital plan.
Clear reporting strengthens transparency because it connects financial data with what’s happening on the project. That context can make school board and community discussions more useful than reporting expenditures alone.
How can districts reduce disputes and prepare for audit?
Many construction disagreements become harder to resolve when decisions, questions, and approvals haven't been documented consistently.
Written RFI logs, change-order logs, meeting records, payment documentation, and regular project reports create a record of how issues developed and how the project team addressed them. When a question resurfaces, the district can refer to the documented discussion rather than reconstructing decisions months later.
The same discipline can support future audit readiness. For bond-funded construction, financial documentation is easier to review when project-level accounting, approval processes, and supporting records are organized from the beginning.
For Michigan school districts, the source material also identifies several post-bond-sale activities that may support stronger financial administration, including establishing project-level accounting, maintaining required post-issuance procedures, formalizing program budgets and contingencies, following applicable procurement requirements, and maintaining a clear audit trail for construction spending. Districts need to apply those practices in accordance with current state, local, contractual, and bond requirements.
Construction monitoring brings these elements together through a recurring review of physical progress, schedule, cost, project changes, and documentation. Used consistently, that process can give district leaders earlier visibility into emerging risk and clearer information for decisions involving bond-funded construction.