Applications go out late or underpriced
The date slips because the build-up starts too late, and the certification pays for it.
What's happening?
The application is the month's one chance to get paid for what the month actually built, and it keeps being assembled in the two evenings before the date. The measure leans on memory, the variations miss the cut because pricing them takes longer than the time left, and some months the date slips altogether. Whoever certifies it can only work from what was claimed: nothing left out of the application comes back in the certificate.
The cost is quiet but monthly. A thin application undervalues the month and you finance the difference until a later cycle picks it up, if one does. A late one can fall foul of the contract's timetable entirely, and on many contracts the application also sets the figure the notices that follow have to engage with, so the sloppier it is, the weaker every later step becomes.
None of this is a knowledge problem. It is a time problem, and it has a routine answer: the build-up run from the site's records to the contract's date, every month, as somebody's actual job.
The solution
The application built to the date, every month.
