Two Sides of the Same Coin

In construction lending, two financial documents sit at the center of every deal: the capital stack and the project budget. They're deeply interconnected — but they serve fundamentally different purposes, and confusing them leads to structural problems in loan administration.

The capital stack answers: Where is the money coming from?

The budget answers: Where is the money going?

Understanding this distinction — and more importantly, understanding how changes to one affect the other — is essential for anyone managing construction loans. Yet in practice, many lenders track these in separate spreadsheets with no formal linkage, creating data integrity risks that compound over the life of the project.

The Capital Stack Explained

The capital stack (or "cap stack") describes the layers of funding that finance a construction project. It's a vertical structure, arranged from most senior (lowest risk, first claim) to most junior (highest risk, last claim):

Senior Debt (First Position)

The primary construction loan. This is typically the largest layer, covering 60-75% of total project costs. The senior lender has first claim on the property and first priority in the disbursement waterfall.

Key metrics: Loan-to-cost (LTC) ratio, loan-to-value (LTV) ratio, interest rate, maturity date, extension options.

Mezzanine Debt (Second Position)

Subordinate financing that sits behind the senior loan. Mezzanine lenders accept higher risk in exchange for higher returns. Mezzanine debt typically covers an additional 10-20% of project costs.

Key metrics: Blended LTC with senior, intercreditor terms, standstill provisions, subordination agreement terms.

Preferred Equity

An equity-like investment with a preferred return — paid before common equity but after all debt service. Preferred equity doesn't have a lien on the property but has priority over common equity distributions.

Key metrics: Preferred return rate, participation rights, liquidation preference.

Common Equity (Sponsor's Investment)

The developer's own capital contribution. This is the most junior layer — the first to absorb losses and the last to receive distributions. Lenders require a meaningful equity contribution (typically 10-25% of total project costs) to ensure the developer has "skin in the game."

Key metrics: Equity percentage, developer experience, track record.

How the Cap Stack Affects Draws

Every time a draw is funded, the capital flows according to the cap stack waterfall. In a typical structure:

1. The borrower submits a draw for completed work

2. The senior lender funds their pro-rata share first

3. Mezzanine or preferred equity may fund concurrently or after the senior tranche is fully drawn

4. The equity contribution is typically funded first (before any debt draws) or pro-rata throughout

The cap stack determines who funds what and when. When a draw is approved, the loan administration system needs to correctly allocate the disbursement across capital sources and track remaining commitments for each layer.

The Project Budget Explained

The budget is the detailed plan for how project funds will be spent. It's organized by cost category, each with a budgeted amount, and it tracks actual spending against those budgets throughout the project.

Hard Costs

Direct construction costs — the money that goes into the physical building:

• Site work and demolition
• Foundation and structural
• Framing and rough-in
• Mechanical, electrical, plumbing (MEP)
• Finishes (drywall, flooring, paint, fixtures)
• Landscaping and hardscape

Hard costs typically represent 60-70% of the total budget.

Soft Costs

Non-construction costs required to complete the project:

• Architecture and engineering fees
• Permits and entitlements
• Legal fees
• Insurance
• Property taxes during construction
• Marketing and leasing (for commercial projects)
• Developer fees

Soft costs typically represent 15-25% of the total budget.

Financing Costs

The cost of the capital itself:

• Loan origination fees
• Interest reserve (pre-funded interest payments)
• Lender's inspection fees
• Title and recording fees
• Appraisal costs

Contingency

A reserve for unexpected costs — typically 5-10% of hard costs. The contingency is not allocated to any specific work category; it's a buffer that can be deployed via change orders when actual costs exceed budgeted amounts.

How Cap Stack and Budget Connect

Here's where things get critical — and where most spreadsheet-based systems fail.

The Total Must Match

The sum of all capital stack layers must equal the total project budget. If the budget is $20M, the cap stack must total $20M. This seems obvious, but in practice, budgets change constantly (change orders, contingency draws, scope adjustments), and the cap stack must be updated to reflect any increase in total project cost.

What happens when they don't match: If the budget increases by $500K due to a change order but the cap stack isn't updated, the loan administration system will show a funding gap. Either the developer must contribute additional equity, or additional debt must be arranged. Catching this misalignment early is critical — discovering it mid-project creates urgent and expensive problems.

Versioning Must Be Atomic

When a change order increases the budget, several things must happen simultaneously:

1. The budget line items are updated

2. The total budget increases

3. The cap stack is updated to show where the additional funds come from

4. The draw waterfall adjusts to reflect the new total

If these changes happen asynchronously — the budget updates in one spreadsheet, the cap stack in another, and the draw tracking in a third — you're guaranteed to have a period where your numbers don't reconcile. In a regulated environment, that's an audit finding.

The solution: atomic versioning. When any change is made to the budget or cap stack, both must update together as a single, linked version. You should be able to look at any point in the project's history and see a consistent snapshot where the cap stack and budget are perfectly aligned.

The Draw Connects Both

Every draw request touches both the cap stack and the budget:

• Budget side: The draw reduces the remaining balance on specific budget line items based on the SOV (Schedule of Values). After a $500K draw, the "Framing" line item might show $400K remaining instead of $900K.
• Cap stack side: The draw reduces the remaining commitment from the funding sources. If the senior lender funded $375K and the equity funded $125K, each layer's remaining balance decreases accordingly.

When these two views are tracked independently, reconciliation becomes a manual, error-prone exercise. When they're linked in a single system, the draw automatically updates both views — and any discrepancy is caught immediately.

Change Orders Are the Stress Test

A change order that increases the project budget by $200K triggers a cascade:

1. Which budget line items are affected?

2. Does the contingency cover it, or is the total budget increasing?

3. If the budget increases, which cap stack layer absorbs the increase?

4. Does the senior lender need to approve a loan increase?

5. Does the developer need to contribute additional equity?

6. How does this affect the draw waterfall going forward?

In a spreadsheet world, this cascade requires manual updates to 3-4 different files, each maintained by different people, with no guarantee of consistency. In a unified platform, the change order triggers automatic updates across budget, cap stack, and draw projections — all version-linked.

Why This Matters for Lenders

If you're administering construction loans, the cap stack and budget are the two most important data structures in your system. When they're disconnected:

• Audit risk: You can't prove that your funding allocations match your approved budget at any given point in time.
• Compliance risk: Regulatory examinations expect consistent, version-controlled financial records. Spreadsheet-based tracking with manual reconciliation is a finding waiting to happen.
• Operational risk: Misaligned cap stacks and budgets lead to incorrect draw amounts, funding gaps, and disputes with borrowers and co-lenders.
• Reporting risk: When your data isn't consistent, your reports to investors, auditors, and regulators aren't reliable.

The Solution: Linked, Version-Controlled, Atomic

The architecture that solves these problems has three requirements:

1. Linked: The cap stack and budget exist in the same system with explicit relationships. Changes to one automatically reflect in the other.

2. Version-controlled: Every change creates a new version. You can view the cap stack and budget at any point in history and see a consistent snapshot.

3. Atomic: Changes to the cap stack and budget are committed together — never one without the other. There's no window where the data is inconsistent.

This isn't just a nice-to-have. It's the foundation of reliable construction loan administration. Everything downstream — draws, reporting, compliance, auditing — depends on the cap stack and budget being correct and aligned at all times.