Evidence is disconnected
The conclusion appears in the model while the supporting clause or authority response sits elsewhere.
Model & evaluate
Validate what can be approved and delivered.
Connect planning evidence, physical constraints, infrastructure dependencies and delivery risks to every material conclusion about the opportunity.
Maple AvenueFeasibility
Current✦ AI Assist
Developer questionIs the preferred development case supportable—and what must be resolved before we rely on it?
12Sources reviewed
10Inputs verified
3Open diligence items
The feasibility problem
A confident conclusion can still rest on a weak assumption.
Planning controls, servicing information and consultant interpretations are often copied into models without a visible source, date or verification status.
- Planning documents→
- Consultant notes→
- Model assumptions→
- Conflicting interpretations→
- Late diligence
Unknowns look like facts
Pending utilities, overlays and approval interpretations can disappear inside a single feasibility status.
Risk appears too late
Material constraints emerge after design, consultant and acquisition work has already advanced.
Evidence-led feasibility
Separate what is known, calculated, assumed and still open.
Every material output retains a visible basis so the team can challenge it before commitment.
Assemble evidence
Collect current parcel, planning, policy, constraint and infrastructure sources.
Qualify the inputs
Record jurisdiction, effective date, source extract, owner and verification status.
Test the case
Evaluate compliance, physical capacity, servicing, access, approvals and delivery dependencies.
Expose conditions
Show conflicts, uncertainties, required verification and their impact on the preferred scenario.
Feasibility conclusion
Advance the case with its unresolved conditions still visible.
The result is not a binary green light. It is a supportable development pathway with the remaining decision risk clearly assigned.
“Is the preferred development case supportable—and what must be resolved before we rely on it?”
Maple Avenue · DallasCurrent decision view
CurrentPrimary controls10 supported2 require interpretation
Buildable capacity392K sfCalculated from linked inputs
Infrastructure1 pendingUtility capacity response
Planning riskLow–mediumAs-of-right pathway
✦
RecommendationSupport the preferred scheme and continue to underwriting.
What the team receives
A usable decision output—not another disconnected report.
Every result stays connected to the opportunity, the assumptions behind it and the workflow that comes next.
Evidence register
Keep every material fact linked to the source, date and jurisdiction behind it.
Planning pathway
Distinguish clearly permitted, interpreted and discretionary elements.
Constraint map
Show physical, infrastructure and policy constraints affecting delivery.
Diligence register
Assign open questions, decision impact, owner and required resolution date.
Next in the development workflow
Continue Continue to Underwriting
Connect the supported development case to cost, capital, return and sensitivity.
Feasibility FAQ
Questions development teams ask.
How is Feasibility different from Test-Fit?+
Test-Fit generates physical development options. Feasibility validates the planning, infrastructure and delivery basis those options depend on.
Can teams see where a planning conclusion came from?+
Yes. Material findings retain the source, extract, date, classification and review status behind them.
What happens when evidence conflicts?+
Conflicts remain visible as diligence items with an assigned owner and downstream decision effect.
Model & evaluate
Book a tailored demo See Feasibility work on a development opportunity your team already knows.
Bring a live deal, your current assumptions and the decision your team needs to make.