It lands somewhere on purpose
The application is filed against the project and the period it covers, with the date it is owed back attached from the start. It stops being an attachment and becomes a record with a clock on it.
They rarely come through Procore or anything else. A PDF lands in somebody’s inbox between two other things and sits there. BuildCycle gives it somewhere to land, a date it is owed back, and a running number for how far along the job actually is.
A pay application arrives as an attachment, on a day that already has forty. It joins no queue. Nothing turns red as it ages. The only reminder it exists is the GC asking where it went — and by then you are late, and the answer is somewhere in a thread you now have to go and find. Everyone who has run CA has lost one. The good ones have lost one.
The application is filed against the project and the period it covers, with the date it is owed back attached from the start. It stops being an attachment and becomes a record with a clock on it.
An application sitting uncertified stays visible as exactly that, and gets louder rather than quieter. The reminder comes from BuildCycle, before the phone call. That is the whole feature, and it is the one that pays for itself.
Percent complete comes out of what has actually been certified, not out of somebody’s read of the site. Money billed against money remaining is the plainest measure of how far along a job is, and it is already in the record.
Watch ninety days of a job run in four seconds. Money is the one measure of progress nobody argues with — and set against the calendar, it is the earliest honest warning you get.
Certified, held as retainage, and not yet billed.
Dollars certified against contract time elapsed.
The GC’s money you are holding, and for how long.
How long each one sat before it was signed.
The money line should not trail the calendar line. When dollars certified fall behind contract time elapsed, the job is running out of schedule faster than it is running out of work — and that gap opens months before anybody says the word “delay” out loud.
The tall bar on the right tells the other half of the story. One application sat nineteen days because it was in an inbox rather than in a queue. That is not a judgment call anybody made — it is the one that got lost, and it is the reason a pay application needs somewhere to live that is not email.
And on a public job, being a day late is not being a day late. Pay schedules are fixed: miss the cycle and the GC waits another thirty days to be paid for work already in the ground. If the late one then goes astray in their accounting as well — which happens — everybody is two months from where they thought they were. That is the cost of one PDF sitting unopened, and it comes out of somebody else’s cash flow.
A pay application is the only document in construction administration that measures the job in the same unit the Owner thinks in. Certified against remaining tells you where the project really is — not where the schedule says it is, and not where it felt like it was on the last site visit.
Late once is a bad week. Late as a habit says something you never meant to say — that the work in the field matters less than whatever else was in the inbox that morning. From the other end it is indistinguishable from not caring whether the people who did the work get paid, and the GC is the one who has to explain the wait to their subs. A certification that goes out on time is the quietest way there is to say the opposite.
You’ll land in a live CA project with real RFIs and real numbers already in it. Poke around; we’ll follow up once you’ve had a look, not spam you.