How to Cut Your Cash-Cycle from 52 Days to 9

Securities markets ran cash-cycles of similar magnitude in the 1960s, before the establishment of the Depository Trust Company. Equity trades took five to seven business days to settle, sometimes longer when the paper certificates physically moved between brokerage offices in lower Manhattan. The cycle did not compress because individual brokers got faster. It compressed because a shared infrastructure layer (DTCC) absorbed the reconciliation work and netted the obligations between counterparties.

The same pattern played out in healthcare claims. Claim adjudication took 60 to 90 days through the 1990s. Then the regulatory push for electronic data interchange and the establishment of clearinghouses (Change Healthcare, Availity, Optum) compressed the cycle to days, then to hours for the cleanest classes of claim. Again: not individual operator improvement, but shared infrastructure.

The same pattern played out in logistics. Pre-EDI, freight invoices and shipping confirmations crossed by paper and fax. Cycle time was measured in weeks. EDI 940 and 944 message standards, once adopted by enough trading partners, collapsed the cycle to hours. Again: shared infrastructure, not individual speed.

Construction has not yet had its DTCC moment. The closest analog (the lien-waiver chain backed by state statute) is a paper-era artifact. The ACORD certificate-of-insurance form is a paper-era artifact. The AIA G702/G703 pay application is a paper-era artifact, digitized only as a PDF. None of these are infrastructure. They are conventions implemented in PDF.

Why has the construction sector resisted the move? Three reasons: first, the multi-party complexity (GC, sub, tier-2 sub, owner, lender, surety, architect) is genuinely harder than the bilateral nature of equity trading; second, the labor of compressing the cycle has historically been priced as a back-office expense rather than a financial outcome, which means no single party has had the incentive to fix it; third, the payment rails (ACH, wire, RTP) only matured to the latency required in the early 2020s.

Those barriers are now down. The rail can be built. This book is the manual for what gets built and how it works.

Pick a representative project from the design-partner cohort. The contract value is $24M. The active sub roster is 31. The schedule is 18 months. The owner-equity contribution is 35 percent; the rest is a senior construction loan from a regional commercial bank.

Before onboarding to the Clearinghouse, the project's cash-cycle was 47 calendar days, measured as sub-invoice-received to sub-funds-settled, averaged across the trailing four draws. The loan administration team at the bank was reviewing draw packages on a monthly cadence and was running a 14-day median between submission and approval. The CFO at the GC was carrying $1.8M of working capital deployed against this single project's draw float at any moment.

Onboarding took 11 calendar days from signed agreement to first pay-app on the rail. Days 1 through 3 were data migration: the Schedule of Values, contract documents, sub roster, and active certificates of insurance moved into the Clearinghouse. Days 4 through 7 were compliance amnesty: every active sub was brought to the project's specific insurance requirements, with the gaps closed by the Clearinghouse's operations team rather than the GC's project managers. Days 8 through 11 were lender onboarding: the bank's loan-admin team got read access to the live draw feed and signed off on the new evidence flow.

The first draw on the Clearinghouse cleared at 19 days. The second cleared at 14 days. The third cleared at 11 days. The trailing-four-draw average at month three was 12.4 days, down from 47.

Where did the 35-day compression come from? Roughly nine days came from removing the lien-waiver chase: the Clearinghouse pre-fills the correct waiver type and amount from the approved pay-app and routes the document for signature in a single API call, instead of the office-manager email chain. Roughly seven days came from the lender's review window, which collapsed once the bank could see the live draw evidence instead of waiting for a 600-page PDF to be assembled by the project accountant. Roughly six days came from the COI cleanup that closed pre-existing gaps and stopped the AP team from having to chase certificates mid-cycle. Roughly five days came from the math check on pay-app submission, which previously sat in a project-engineer queue and now runs deterministically at intake. The remaining eight days came from miscellaneous administrative friction (joint-check coordination, retainage release timing, change-order pricing) that compressed in parallel.

The CFO's working-capital position on this project went from $1.8M of trapped float to under $500K. The freed working capital was redeployed into mobilization on the next bid the GC won, a $14M school renovation that they had previously declined to bid because the LOC was already deployed. The cohort calls this 'the second-order effect': the cash-cycle compression unblocks the bid pipeline.

This chapter is the simplest possible illustration of what the rail does. The next volume of the book covers the compliance gates that make this work in practice. The volume after that covers the bonding-capacity expansion that follows from clean compliance breadth. Each piece compounds.