DealVeto Field Guide · Multifamily

Construction judgment,
inside the decision workflow.

A plain-language learning path for development and preconstruction teams: understand the site, read the budget, challenge the source, and publish the decision.

Four learning tracks

Learn in the same order the deal is screened.

01Live guide

Site & program

What can this site plausibly support?

  • Parcel and acreage confidence
  • Conceptual unit yield and parking
  • What Site Fit cannot verify
02Live guide

Conceptual budget

What is the right level of precision today?

  • Early estimate class and uncertainty
  • Hard cost, soft cost, and contingency
  • When to engage preconstruction
03Live guide

Cost basis

Where did this number come from?

  • Source class and effective date
  • Baseline, override, and current basis
  • Escalation versus installed cost
04Live guide

Decision control

What changed, who reviewed it, and what happens next?

  • Proceed, Revise, Reprice, Pause, Stop
  • Confidence and blocking assumptions
  • Versioned Decision Memo and BOE

Cost reference hierarchy

A number is only as useful as its basis.

DealVeto separates project evidence, licensed references, public signals, screening benchmarks, and assumptions. They are not interchangeable.

  1. 01Customer-verified actualsPreferred calibration basis when the customer has authorized the project history for use.
  2. 02Licensed referencesUsed only when separately contracted and identified; never implied to be DealVeto-owned data.
  3. 03Official public signalsUsed for context and escalation. BLS PPI indicates trend; it is not a local installed-cost source.
  4. 04DealVeto screening benchmarkA directional multifamily screening band with geography, effective date, and confidence disclosed.
  5. 05Modeled assumptionA visible placeholder requiring professional or customer validation before reliance.

Pilot governance cadence

Cost Basis Quarterly

A versioned release note for benchmark, escalation, geography, and methodology changes.

Pilot process
  1. 01

    Collect permitted customer actuals, licensed references, and official public signals

  2. 02

    Normalize source date, geography, product type, units, and escalation basis

  3. 03

    Review outliers, confidence, and construction-market relevance

  4. 04

    Publish an effective date, version, change log, and validation notes

No silent rebasing. Existing deal versions keep their original cost basis until a user explicitly adopts a newer release.

Organization knowledge & AI safety

Ground answers in approved sources before considering training.

Retrieve from approved organization sources at answer time instead of training a shared model on raw customer files. This preserves citations, makes a source removable, and keeps the deterministic screen—not the language model—as the calculation authority.

Customer deal data is not used to train a shared cross-customer DealVeto model by default. Any exception follows an explicit, customer-specific governance path.

Put the guide to work

Bring one live deal. Leave with a governed first decision.