The Risk Assessment Engine, explained
A structured risk score across two tracks: developer and realtor.
The Risk Assessment Engine runs a structured questionnaire and produces a single risk score from 0 (low risk) to 10 (high risk). It has two separate tracks; developer and realtor, because the risk exposure of each role is genuinely different. Only the developer track's score feeds the Financial Decision Engine; a realtor's listing-risk score is kept separate so it doesn't silently influence a capital decision it wasn't designed to inform.
A deal can look sound on paper and still carry risk that only shows up once money has moved. This engine surfaces that risk before commitment, not after.
Developer track
Covers five categories: Financial, Legal and Title, Execution, Market and Sales, and Exit and Coverage. Questions cover funding structure, off-taker deposit terms, title perfection, contractor reliability, buyer pool depth, and fallback plan if sales run slow.
Realtor track
Covers Mandate and Listing, Buyer-Side, Property-Side, Market, Legal and Regulatory, and Reputational and Operational risk, questions specific to representing or transacting on an existing property rather than building one.
Reading your result
The result page shows an overall score plus a breakdown of how many questions landed in the Critical (7 or above), Moderate (4–6), or Clear (below 4) band.
See this against your own project's numbers
The Property Viability Engine runs this logic against your actual location, standard, and size, free without limitation.
Check Compliance For FreeQuestions people also ask
Does the realtor risk score feed the Financial Decision Engine?
No. Only the developer track's score is wired into the Financial Decision Engine. A realtor's listing-risk score measures something different and is kept separate.
Hit a confusing step, or something missing? Tell us.