Building a Development Pro Forma That Survives Reality
Short answer
A development pro forma survives reality when it models cash timing, separates major cost and revenue assumptions, and makes site, approval, financing and schedule risks visible. It should be updated with project-specific information and tested against plausible delays, cost increases and weaker revenue before the owner relies on it for a decision.
Most pro formas fail in the same three places: the schedule is optimistic, the site work is underestimated, and the contingency is decorative. Fixing those three inputs changes the answer more than refining rent assumptions to the dollar.
Structure before precision
A pro forma has four blocks:
- Acquisition — land or building price, closing costs, due diligence, survey, geotech, environmental
- Soft costs — design, engineering, permits, impact fees, legal, insurance, financing, owner''s rep
- Hard costs — site work, shell, interiors, sitework restoration, contingency
- Revenue and exit — lease-up or sale, operating expenses, capitalization or sale price
Getting the structure right and the numbers roughly right beats a precise model with a missing category.
Soft costs are consistently underestimated
On many small and mid-size projects, soft costs run a meaningful share of total project cost, and owners often carry a placeholder that ignores half the list. Build the line items explicitly: design fees by discipline, permit and review fees, impact and tap fees, survey, geotechnical, environmental, testing, legal, title, insurance, financing fees, interest carry, and owner-side management.
Carry cost is a schedule input, not a cost input
Interest carry, general conditions, taxes, and insurance are all duration-driven. If your model assumes a permitting window that a jurisdiction cannot actually deliver, every carry line is wrong by the same percentage.
Test the model at three durations:
- The optimistic schedule the team promised
- The realistic schedule based on recent comparable approvals
- The optimistic schedule plus six months
If the third case kills the deal, you have found the real risk.
Site work is where Lowcountry projects break
Coastal sites carry conditions that a generic cost-per-square-foot number does not contemplate: high water table, poor bearing soils, required fill, stormwater detention area, wetlands and critical area buffers, deep utility runs, and elevation requirements.
Before you finalize hard costs:
- Get a geotechnical report, not a neighbor''s anecdote
- Price structural fill by the yard with a real haul distance
- Confirm stormwater approach and the land area it consumes
- Confirm finished floor elevation requirements and what that does to fill and access
- Confirm utility capacity and connection point distance
Contingency has to be sized to unknowns
Contingency is not a fixed percentage. It is a function of how much you know. Early feasibility with a concept plan warrants far more than a fully permitted project with complete drawings and a bought-out subcontractor list.
Practical approach: set contingency high at feasibility and step it down at defined milestones — schematic design, permit set, buyout complete — releasing the difference back to the model only when the underlying uncertainty is actually resolved.
Sensitivity, not certainty
Run the model against a handful of shifts and look at which single variable moves the outcome most:
- Hard cost up ten percent
- Schedule extended six months
- Rent or sale price down five percent
- Interest rate up one point
The variable with the largest swing is the one that deserves your management attention and your due diligence dollars.
The go / no-go discipline
Write down, before you are emotionally committed, the conditions under which you walk. A stated walk-away number is the only reliable defense against escalating commitment.
Next step
If a site is under consideration now, the highest-value work is verifying the site work and schedule assumptions before the due diligence period closes. Those two inputs decide most deals.
Account for Lowcountry Site and Approval Risk
A development pro forma in the Lowcountry should separate ordinary construction costs from site-specific exposure. Floodplain requirements, wetlands, drainage, utility availability, access, tree protection and soil conditions can affect both cost and schedule. These items should remain visible rather than being buried in a general contingency.
The approval path also needs its own assumptions. Identify the applicable jurisdiction, zoning and land-use requirements, design review, utility approvals and any state or federal permits that may apply. Tie carrying costs and the construction start date to that sequence, then test what happens if a key decision takes longer than planned.
Test the Deal Before Treating It as a Forecast
A base case alone does not show whether a project can absorb change. Build downside cases for a later start, longer construction period, higher costs, slower lease-up or sales, and weaker revenue. The purpose is not to predict every outcome, but to identify which assumptions have the greatest effect on feasibility.
Use clear decision points as information improves. Survey, environmental review, civil work, pricing and entitlement feedback should replace early allowances with project-specific inputs. If the return depends on every assumption holding at once, the pro forma is identifying risk rather than resolving it.
Build the Model Around Cash Timing
A useful pro forma shows when money moves, not just the final totals. Start with acquisition and closing costs, then place design, surveys, consultants, permits, site work, construction and financing costs in the periods when they are expected to occur. Separate one-time expenses from recurring carrying costs so a delayed start does not disappear inside a lump sum.
Revenue needs the same treatment. For a sale project, show when closings are expected and what costs are deducted at closing. For a rental project, distinguish construction completion from occupancy, stabilization and steady operations. A project can appear profitable in total and still face a cash shortfall if expenses arrive well before revenue.
Keep Sources and Assumptions Visible
Every important input should have a source, date and level of confidence. Label figures as quoted, estimated, historical or assumed. Record what each allowance includes, whether escalation or taxes are included, and how long a price is expected to remain useful.
Maintain an assumptions log alongside the model. When zoning feedback, civil plans, contractor pricing or financing terms change, update the affected inputs and note the reason. This gives owners and investors a clearer basis for approving the next round of spending.
Start With the Development Program
Define what is being evaluated before building the spreadsheet. Record the proposed use, unit or building count, approximate area, parking, site improvements and likely development sequence. If the program is still uncertain, model the realistic alternatives separately instead of blending them into one case.
State the measurement basis for every input. Land area, gross building area, rentable or sellable area, unit count and parking count serve different purposes. Keeping those measures distinct prevents a cost or revenue assumption from being applied to the wrong quantity.
Separate Costs Into Useful Categories
Organize costs so the owner can see what is driving the deal. Typical groups include acquisition, due diligence, design and consultants, permits and fees, site work, vertical construction, owner-provided items, financing, insurance, taxes, operations and disposition costs. Contingency should be shown separately rather than used to conceal missing scope.
Avoid carrying one broad cost-per-square-foot assumption too far into due diligence. It may help with an early screen, but it does not show unusual foundations, drainage work, utility extensions, off-site improvements or jurisdictional conditions. Replace broad allowances as surveys, plans and pricing become available.
Account for Lowcountry Site and Resilience Costs
Start with conditions that can change the project before design is complete: flood zone and design elevation, wetlands and buffers, stormwater requirements, utility availability, access, tree constraints, poor soils and potential environmental issues. These are not miscellaneous contingencies. Each condition can affect usable area, foundation design, permitting time and the amount of land that can produce revenue.
Carry separate allowances for civil work, utility extensions, fill, dewatering, erosion control, flood-resistant construction and other resilience measures identified during due diligence. Keep insurance assumptions visible as well, including construction-period coverage and the owner’s expected property, flood and wind coverage after completion. The pro forma should show who is responsible for each item and when the estimate will be replaced by a survey, report, design or quote.
Match the Pro Forma to the Governing Jurisdiction
Identify the controlling municipality or county before assigning a permitting duration or approval budget. A Charleston mailing address does not establish the governing jurisdiction, and zoning, design review, tree protection, stormwater, utility and building permit requirements vary among the City of Charleston, surrounding municipalities and unincorporated counties. Overlay districts, historic review and agency approvals may add separate steps.
Build the schedule around the actual approval sequence: due diligence, concept review, rezoning or variance if needed, design review, civil approvals, utility coordination, building permits and any state or federal authorizations. Tie consultant fees, deposits, impact or capacity charges, financing costs and land carry to that sequence. If jurisdiction or entitlement status is unresolved, model it as an explicit risk rather than using a single assumed permit date.
Build Costs and Cash Flow in the Right Sequence
Organize uses into land and closing, due diligence, design and consultants, entitlement and permit fees, sitework and utilities, vertical construction, owner-furnished items, insurance, financing, leasing or sales costs, operating deficits and reserves. Separate hard costs, soft costs and financing costs, and state whether each line includes escalation, taxes, bonds, deposits or retainage. Do not rely on one broad contingency to cover missing scope.
Then place each cost in the month or phase when it is expected to occur. Include deposits and preconstruction spending before closing where applicable, progress payments during construction, interest on drawn funds, and revenue only when the project can legally and practically deliver space or units. Monthly cash flow reveals the peak equity requirement, the timing of debt draws and the cost of delays more clearly than a total development budget alone.
Set Decision Gates Before Committing More Capital
At acquisition, confirm title, survey, access, zoning, allowable use and density, flood and wetland conditions, utility service, environmental concerns and a preliminary site plan. Before design development, require a jurisdiction-specific approval path, a basis-of-design narrative, an updated area or unit program, and a reconciled estimate. Before construction, confirm permits, final plans, contract scope, allowances, alternates, insurance, financing conditions and the owner’s remaining decisions.
For each gate, list the unresolved assumptions, the person responsible for closing them, the required document and the date by which the answer is needed. Update the base case and downside case when a major assumption changes. A pro forma survives reality when it functions as a controlled decision record, not a spreadsheet that is refreshed only for a lender or investor meeting.
Common questions
- How often should an owner update a development pro forma?
- Update it whenever new information materially changes scope, cost, schedule, financing or revenue. Major due-diligence findings, design milestones, approval decisions and contractor pricing are practical review points.
- Should contingency cover unknown site conditions?
- Contingency can address uncertainty, but known concerns should receive separate allowances when possible. Keeping drainage, utility, soil or access exposure visible helps the owner understand what is driving the risk.
- What should an owner request with a pro forma review?
- Request the current model, an assumptions log, source dates and a comparison with the prior version. The review should also identify unresolved items and explain which assumptions have the greatest effect on feasibility.