Pre-Development Software For The Window Between LOI And Permit Submittal

Pre-development is the six-to-twelve-month period between the closed acquisition and the permit submittal. It is where the schematic-design retainer is committed, the GC is invited to bid, the entitlement strategy is executed, and the capital stack for vertical is arranged. It is also where most of the deal's actual timeline lives — acquisition is fast, construction is expensive but predictable, and pre-development is the messy middle where most schedules quietly slip six months.

This software structures the pre-development window. It carries the parcel record, the entitled program, the buildable envelope, and the assumption log forward from acquisition, and it adds the four workstreams that live only in pre-development: architect scoping, GC bid preparation, permit-submittal strategy, and vertical financing readiness.

Why pre-development schedules slip

The schematic-design phase produces a set of drawings that either match the pro-forma assumptions or diverge from them. When they diverge, the developer has three options: accept the divergence and re-underwrite, ask the architect to revise, or override the architect on a specific decision. All three consume time. Teams that budget three months for schematic almost always spend four to five because the divergence-and-revision loop was not modeled in the schedule. The fix is to give the architect a briefing that constrains the schematic phase to the pro forma's assumptions. A briefing that says 'we underwrote 24 units at 850 average square feet, with a $325/sqft hard cost, in the C-2 setback' is different from a briefing that says 'design a residential building on this parcel.' The first produces a schematic that plugs into the pro forma. The second produces a schematic that will require a revision loop.

The architect briefing

Every pre-development record produces an architect briefing PDF: the entitled program, the buildable envelope, the pro-forma assumptions (unit count, unit mix, average unit size, quality tier, hard cost band), the target permit-submittal date, and the residual-risk register from due diligence. The architect starts schematic design against a constraint set instead of a blank page. Architects who receive the briefing report that it removes roughly two weeks from the schematic phase — the two weeks that would otherwise go to interviewing the developer about the pro-forma intent. The developer saves those two weeks and the schematic phase costs less because there is less rework.

GC bid-package scaffold

The GC bid package traditionally lives in a shared Dropbox folder that assembles gradually over pre-development. The software provides a scaffold from day one: the parcel record, the program, the schematic-phase drawings once received, the hard-cost band, the target permit-submittal date, and the target construction-start date. GCs invited to bid work against the same scaffold instead of a folder that changes weekly. The scaffold is not a bid package — the final bid package includes construction documents and specifications that come later. But it lets the developer pre-qualify GCs and get preliminary bid ranges before schematic is complete, which is the phase where the actual cost commitment lives.

Permit-submittal strategy

The submittal-strategy workstream tracks the jurisdiction's current review backlog, the discretionary-review calendar, the neighbor-appeal window, and the target submittal date. A submittal filed the week before a holiday freeze loses a month; a submittal filed the day before a discretionary-review meeting sits until the next agenda. The software surfaces those windows so the submittal date is chosen deliberately. This is the workstream most teams treat as an afterthought and it is where six-week schedule slips silently accumulate. Making the strategy explicit turns it into a scheduled decision instead of a reactive one.

Vertical financing readiness

Construction lenders want to see a specific packet before they commit: the appraisal, the architect's sealed drawings, the GC's fixed-price bid or GMP contract, the permit or the permit-ready confirmation, and the pro forma with sources and uses. Assembling that packet is a two-month project if it is left to the end of pre-development. Assembling it in parallel across pre-development compresses the timeline. The software tracks readiness for each lender-required artifact. When the schematic-phase drawings land, the appraisal timeline updates; when the GC bid is fixed, the sources and uses can be finalized. The construction-loan close becomes a scheduled event instead of a scramble.

A real-world workflow: compressing a 14-month pre-development window to 9 months

A 40-unit multifamily project historically runs 12-14 months from LOI close to permit submittal. The platform-based workflow targets 9 months. Month 1 — the architect briefing exports on Day 3 of pre-development with the entitled program, envelope, pro-forma assumptions, and target permit-submittal date. Month 2 — schematic-design phase 30% deliverable lands; the platform compares the drawings against the pro-forma envelope and flags a 2% divergence in the unit-count. Month 3 — GC pre-qualification round runs with the bid-package scaffold; two GCs return preliminary bid ranges within the pro-forma band. Month 4 — schematic 60%; permit-strategy calendar flags a two-week window before the November discretionary-review freeze. Month 6 — construction documents 50%; debt-broker briefing exports to two construction lenders. Month 8 — permit submittal filed; construction-loan term sheet in negotiation. Month 9 — permit issued, contract signed, mobilization scheduled. • Month 1 — Architect briefing exports Day 3. • Month 2 — Schematic 30%, envelope divergence flagged. • Month 3 — GC pre-qualification with bid-package scaffold. • Month 4 — Schematic 60%, submittal window identified. • Month 6 — CDs 50%, debt-broker briefing to lenders. • Month 8 — Permit submittal filed. • Month 9 — Permit issued, contract signed.

Implementation guidance for the pre-development lead

The pre-development lead's KPI is 'weeks-to-permit-submittal.' The platform contributes to that KPI by removing the architect briefing week, the GC pre-qualification week, and the permit-strategy calendar week — three weeks that historically ran in series after schematic 100%. On the platform they run in parallel from Day 1. The failure mode is scope-changing after schematic 60%. Late scope changes ripple through construction documents and re-open the pro-forma envelope. The discipline is to freeze scope at schematic 60% and route any late change through the assumption log with the impact quantified. Most teams that miss the 9-month target miss it because of one uncontrolled scope change in month five.

A real-world workflow: compressing a 14-month pre-development window to 9 months

A 40-unit multifamily project historically runs 12-14 months from LOI close to permit submittal. The platform-based workflow targets 9 months. Month 1 — the architect briefing exports on Day 3 of pre-development with the entitled program, envelope, pro-forma assumptions, and target permit-submittal date. Month 2 — schematic-design phase 30% deliverable lands; the platform compares the drawings against the pro-forma envelope and flags a 2% divergence in the unit-count. Month 3 — GC pre-qualification round runs with the bid-package scaffold; two GCs return preliminary bid ranges within the pro-forma band. Month 4 — schematic 60%; permit-strategy calendar flags a two-week window before the November discretionary-review freeze. Month 6 — construction documents 50%; debt-broker briefing exports to two construction lenders. Month 8 — permit submittal filed; construction-loan term sheet in negotiation. Month 9 — permit issued, contract signed, mobilization scheduled. • Month 1 — Architect briefing exports Day 3. • Month 2 — Schematic 30%, envelope divergence flagged. • Month 3 — GC pre-qualification with bid-package scaffold. • Month 4 — Schematic 60%, submittal window identified. • Month 6 — CDs 50%, debt-broker briefing to lenders. • Month 8 — Permit submittal filed. • Month 9 — Permit issued, contract signed.

Implementation guidance for the pre-development lead

The pre-development lead's KPI is 'weeks-to-permit-submittal.' The platform contributes to that KPI by removing the architect briefing week, the GC pre-qualification week, and the permit-strategy calendar week — three weeks that historically ran in series after schematic 100%. On the platform they run in parallel from Day 1. The failure mode is scope-changing after schematic 60%. Late scope changes ripple through construction documents and re-open the pro-forma envelope. The discipline is to freeze scope at schematic 60% and route any late change through the assumption log with the impact quantified. Most teams that miss the 9-month target miss it because of one uncontrolled scope change in month five.

Managing the debt-broker and construction-lender relationship during pre-development

Construction lending relationships take months to build. Pre-development is when the developer engages the debt broker with the emerging project story: parcel, program, schedule, sources and uses. The lender needs to see the story evolve, not receive it fully-formed the week before permits issue. The platform's debt-broker briefing exports at three natural points: schematic-phase 60% (initial engagement), permit-submittal (term-sheet negotiation), and construction-documents 90% (final commitment). Each export is a snapshot of the current state — the lender sees the evolution and updates the term sheet as the project firms up. The failure mode is a debt broker who receives the story only at construction-documents 90%. The broker has no time to shop the loan; the developer accepts whatever term sheet the first responder offers. Teams that engage the broker at schematic 60% get competitive term sheets by permit-submittal and can negotiate rate, structure, and covenants rather than accepting the first offer. • Schematic 60% — Initial debt-broker engagement. • Permit-submittal — Term-sheet negotiation. • CDs 90% — Final commitment and closing prep. • Every export — Snapshot with the same parcel record and assumption log.

Use Cases

  • Architect briefing PDF: One-document handoff that constrains the schematic phase to the pro-forma assumptions — saves ~2 weeks of schematic time.
  • GC bid-package scaffold: Pre-formatted bid scaffold that populates as pre-development progresses; ready for GC pre-qualification early.
  • Submittal-strategy calendar: Jurisdiction backlog, discretionary-review windows, and holiday freezes — submittal date chosen deliberately.
  • Vertical financing readiness tracker: Lender-required artifact tracking so construction-loan close is a scheduled event, not a scramble.
  • Assumption-log carry-forward: Every acquisition assumption preserved into pre-development — the answer to 'why did we do it this way' is queryable.
  • Schematic-drawing envelope check: 30% and 60% schematic deliverables auto-compared against the pro-forma envelope; divergences flagged before they compound.
  • Submittal-window optimizer: Jurisdiction backlog, discretionary-review meeting dates, and holiday freezes surfaced as a submittal-window calendar.
  • Schematic-drawing envelope check: 30% and 60% schematic deliverables auto-compared against the pro-forma envelope; divergences flagged before they compound.
  • Submittal-window optimizer: Jurisdiction backlog, discretionary-review meeting dates, and holiday freezes surfaced as a submittal-window calendar.

Frequently Asked Questions

How can developers reduce due-diligence time in pre-development?
Due diligence formally ends at closing, but the residual-risk register continues into pre-development. The software carries it forward so pre-development addresses risks with a running clock, not a new discovery.
How does AI improve development planning during pre-development?
By carrying the pro-forma assumptions into the architect briefing and flagging divergence when schematic drawings return. The AI is not designing — it is enforcing consistency.
How can Buildora IQ streamline pre-development workflows?
By providing a single record for the four parallel workstreams — architect, GC, permit strategy, financing — and by surfacing the intersections that historically cause schedule slippage.
How does AI improve development planning during pre-development?
By enforcing consistency between the pro-forma assumptions and the schematic-design output. The AI is not designing the building; it is checking that the building being designed is the building the pro forma priced.
What information should be available before signing the construction-loan term sheet?
The permit issuance date or a defensible submittal date, the finalized GC contract or GMP scope, the appraisal, and the assumption log. Signing a term sheet without those forces a re-negotiation later when the actual numbers land.
How does AI improve development planning during pre-development?
By enforcing consistency between the pro-forma assumptions and the schematic-design output. The AI is not designing the building; it is checking that the building being designed is the building the pro forma priced.
What information should be available before signing the construction-loan term sheet?
The permit issuance date or a defensible submittal date, the finalized GC contract or GMP scope, the appraisal, and the assumption log. Signing a term sheet without those forces a re-negotiation later when the actual numbers land.
What information should be available before signing the schematic-design retainer?
The architect briefing (program, envelope, pro-forma assumptions), the target permit-submittal date, and the debt-broker's preliminary reaction to the sources and uses. Signing the retainer without those three commits the schematic-phase spend against unverified assumptions.
Does the software design the building?
No. Architects still design. The software briefs the architect and preserves the pro-forma assumptions so schematic-phase divergence is minimized.
Can the software handle a design-build delivery?
Yes. In a design-build delivery the GC scaffold and the architect briefing consolidate into a single design-build briefing.
How does this relate to project management?
Pre-development ends when construction starts. Project management (Procore, Buildertrend) picks up at that point. Some pre-development artifacts export cleanly into the PM tool.
What if we change the program after schematic?
The assumption log is versioned. A program change re-runs the pro forma and updates the architect briefing; the change is on the record with the reasoning.
Is the software useful on a single-family custom build?
The full workstream is calibrated for multifamily and small commercial. A single-family custom build uses roughly half the workstreams — the architect briefing and the assumption log — and skips the GC pre-qualification and the vertical-financing packet.
How long does the average pre-development cycle take on the software?
Teams report six to nine months on projects that historically ran nine to fourteen. The compression is entirely in reduced rework, not in accelerated permit review.
What happens if the architect returns drawings that diverge more than 5%?
The platform flags the divergence and produces a comparison PDF. The developer decides whether to revise the drawings, revise the pro forma, or accept the divergence with an override in the assumption log.
Can the software handle a design-competition delivery model?
Yes. Design competitions produce multiple briefings; the platform tracks each competitor's scope and runs the winning entry through the standard pre-development workflow.
How is the debt-broker briefing kept confidential?
Debt-broker briefings export as branded PDFs with configurable redaction of specific pro-forma line items. Some developers redact the return threshold; the debt broker gets the sources-and-uses view.
What happens if the architect returns drawings that diverge more than 5%?
The platform flags the divergence and produces a comparison PDF. The developer decides whether to revise the drawings, revise the pro forma, or accept the divergence with an override in the assumption log.
Can the software handle a design-competition delivery model?
Yes. Design competitions produce multiple briefings; the platform tracks each competitor's scope and runs the winning entry through the standard pre-development workflow.
How is the debt-broker briefing kept confidential?
Debt-broker briefings export as branded PDFs with configurable redaction of specific pro-forma line items. Some developers redact the return threshold; the debt broker gets the sources-and-uses view.
How does the platform handle a construction-loan takeout to permanent financing?
Takeout financing is modeled as a separate scenario after stabilization; the takeout debt-broker briefing exports similarly with the operating pro forma and the DSCR projection.
Can we run pre-development on a project with existing bridge debt?
Yes. Existing debt is a scenario input; the platform models the payoff or roll-over against the new construction loan and surfaces the timing constraint.

Related Resources

Get Started

Buildora IQ analyzes any property and generates floor plans, cost estimates, and feasibility reports in minutes — done in under 2 minutes. Start free See all features.