Why lender-financed construction runs on evidence, not paperwork
A project financed by a bank does not pay for work. It pays against a record of work. The crew can be ahead of schedule and the site can be immaculate, and the drawdown still does not move until someone hands over documents the lender will accept. That is the whole difference between paperwork and evidence: paperwork describes what happened, evidence proves it to a reader who was not there and is not inclined to take your word for it.
The record is the payment mechanism
On a development-bank or IFI-financed build, compliance reporting is contractual rather than optional. Environmental and social action plans, periodic reports, grievance logs and contractor flow-down are written into the loan. Conditions precedent gate the first disbursement. Covenants run to remedial actions and, at the far end, to an event of default. Payment certificates are issued against evidence, not against assertion.
Which is why the argument that actually lands with a borrower is never “you will be fined.” In the IFI regime there is generally no statutory penalty at all. The bite is contractual, and it shows up as a drawdown that stops moving and a risk rating that follows the borrower into the next financing application. The consequence is cash timing, not a citation.
What turns a document into evidence
A document becomes evidence when a stranger can reconstruct it without asking anyone. That means four things attached to every claim: who reported it, when, which source backs it — a photo, a reading, a signed line — and what changed after someone reviewed it. Append-only, so the trail cannot be quietly tidied up before an audit.
Language models will happily produce the document. That is not the hard part and, on its own, it is worth very little. The hard parts sit on either side of it: getting a signal off the work at all, through what a crew in a trench already carries; and structuring that signal with real consequences attached, because a wrong number becomes a wrong payment.
The failure mode is quiet
Bad evidence rarely fails loudly. It fails as a certificate that comes back for clarification, a report cycle that slips, a reconciliation nobody can close because the records and the contract disagree and neither side can show its work. The project keeps running. The money arrives later than it should have, every time, and the reason is never written down anywhere.
Building for evidence rather than paperwork means designing backwards from the reader who releases the payment, and accepting that the chain of custody is the product. The document is only its last page.
This is the work we do: see how we work.