Phase 1 shipped.
Phase 2 begins.

When you rate a roof or call a paving year, that judgment is captured the moment you make it — in structured fields the system can read directly. No re-keying from Excel into the funding plan into a Word draft.

Smart Intake takes over the engineer-facing input. The Phase 2 FPA UI patches use the same field names, the same condition-rating vocabulary, the same shape — so engineers feel the relief now and the eventual transition to the form is a UI swap, not a relearn.

When the draft hits something that calls for your judgment — an unmatched cost, a component without a clear analog, an interpretation that’s yours to make — the system makes that hand-off explicit. You don’t hunt for what to look at.

How that hand-off shows up is a conversation, not a decision: highlighted inline in the draft, listed in an insights email, queued as a review note. The commitment is the principle — the system never silently fills what it isn’t sure about.

Instead of starting from a copy of a previous community’s report and editing it down, every report composes from your inputs and a clean renderer. Less copy-paste. Less drift. None of the carryovers that happen when a draft inherits material from an earlier study.

The transition is staged. A template-lint pass catches the specific patterns we know about today. A programmatic renderer takes over once the QA data shows the template file itself is the limiting factor — not the inputs flowing into it.