Chapter 05
Payment evidence and certification cycles
How to use the captured base to support payment applications and accelerate certification, both upstream from the owner and downstream to subcontractors, and how to read the cycle as a leading indicator of dispute risk.
01
The case for evidence-attached applications
A payment application that arrives with evidence is faster to certify than one that arrives as a number alone. The evidence does not need to be exhaustive; it needs to be enough that the certifier does not have to ask for more. A short evidence pack — site capture of the work front, a 360 walk through the package, a programme extract showing the period certified — turns a fortnight of correspondence into a same-week certification. Multiplied across the contract life, the saving is material. On a typical contractor balance sheet, a two-week reduction in days sales outstanding across all certifications translates into working-capital savings that are visible at the portfolio level. The discipline is to think of the evidence pack as a procurement of certifier time. The certifier has limited time per application; the application that arrives in a form that uses that time efficiently is the application that gets certified first. The application that arrives without evidence is the application that gets the queries, which means the application that gets paid last. The contractor who runs the discipline at scale finds that the application reviewer becomes a partner rather than a gate. The contractor who treats certification as adversarial finds the cycle stretches month on month.
02
Subcontractor certifications and the back-to-back cycle
The same discipline applies downstream. A subcontractor who attaches evidence to their valuation makes life easier for the certifier and tends to be paid faster. The contractor who runs the workflow at scale across all packages tends to find that the cycle smooths and the disputed certifications drop. The discipline costs nothing extra to the project; it uses the captured base that already exists. The downstream cycle should also feed the upstream cycle. The contractor who has assembled the subcontractor packs has half of the upstream pack already in hand, and the upstream certifier benefits from seeing a coherent line of evidence rather than disconnected items. The cycle is a system, not a series of isolated transactions. Where the contract envisages pay-when-paid or pay-when-certified provisions on the subcontract side, the discipline becomes more important rather than less. A subcontractor whose valuation is tied to upstream certification has a direct interest in the upstream pack being strong; a contractor who shares the cadence of evidence with the subcontractor tends to find the subcontract relationship survives the project. The portfolio that runs this cycle as a default has a measurable advantage on cash conversion over the portfolio that runs it as an exception.
03
When the cycle breaks
Payment cycles break in two places. The certifier disagrees with the quantity, and the application has to be reworked. The certifier disagrees with the quality, and the application has to be paused. Both breaks are addressed by evidence. A captured 360 walk showing the installed work, a clip of the work front during the period, an attendance record matching the labour claimed. The break still happens, but it resolves in days rather than weeks. The third type of break, less commonly discussed, is the timing break: the certifier signs the certificate but the payment is delayed downstream of certification by a treasury or financing process that the project does not control. The project cannot solve the timing break with evidence, but it can stop creating its own delays by closing the certification window cleanly. A certificate that issues on day 14 of a 30-day cycle is a certificate that does not need to take 28 days. The discipline that the contractor controls is the front half of the cycle. The discipline of getting the certificate clean is the discipline of writing the application clean. Practitioners who have run the cycle at scale report that the back half tends to follow the front; a clean front half does not guarantee a clean back half, but a messy front half almost always produces a messy back half.
04
Reading the cycle as a leading indicator
The certification cycle is also a leading indicator of dispute risk. A cycle that lengthens month on month, even when each individual delay seems small, is a cycle that is heading towards a formal dispute. The contractor who reads the cycle data at the portfolio level rather than the project level catches the pattern earlier. A project where the certifier has started asking for the same evidence twice is a project where confidence has eroded; a project where the certifier signs without query is a project where the relationship is healthy. The cycle data sits in the cost report whether the project chooses to read it or not. The discipline is to read it. Where the cycle is lengthening, the response is to invest more evidence into the application rather than less, and to ask the certifier directly what would shorten the cycle. The certifier who has been asked tends to be more candid than the one who has not. The project that asks early heads off the dispute that the project that does not ask is heading into. The cost of asking is a thirty-minute conversation; the cost of not asking is the cost of the dispute. The trade is straightforward when it is framed at the right altitude.
Practice
01. Pull the certification cycle times on your current project for the last six months. Identify whether the trend is shortening, steady, or lengthening, and write a one-line cause hypothesis.
Look for: A strong response cites the actual cycle times, names the trend, and offers a specific cause hypothesis (for example a change in certifier, a quality dispute on a particular package, or a query pattern around quantities).
02. Draft the one-page evidence attachment template for your next application. List the four artefacts it will include.
Look for: A strong response names site capture of the work front, a 360 walk through the major packages, a programme extract for the period, and the measured quantity backup, with a note on where each artefact is sourced.
Checkpoint
For the next certification cycle, what would a one-page evidence attachment look like, and what does the cycle length tell you about the relationship?
Recommended reading