Validation engine
Catch the costly mistake before the lender does.
A two-stage validator. Deterministic rules cover the cases you can specify in advance. An LLM cross-check covers the cases that depend on project context. Runs on the budget, on every transaction, and before every draw submits.
What it covers
Deterministic rule engine
The rule engine catches duplicate line items, missing trades, allocations outside budget, unapproved vendors, and retainage miscalculations.
LLM cross-check
A second pass reviews the project against its broader context and catches cases the rules cannot enumerate, such as framing usually finishing before drywall starts.
Severity-tiered output
Errors block submission, warnings require acknowledgement, and notes inform without interrupting the flow.
Auditable
Every validation run is stored with the rules that fired, the LLM response, and the decision made. The history is defensible if a draw is questioned later.
How it fits the workflow
- Step 1
Validation runs automatically on key actions such as draw submit and budget lock
- Step 2
Engine flags issues by severity
- Step 3
You resolve, accept with note, or override (audit-logged)
- Step 4
Clean validation clears the path to submit
Related
Budget & transactions
Every line item is enforced by schema, and every transaction reconciles back to a budget line with no orphan spend.
Draw management
AIA-style draw schedules, lender-ready PDF packages, and e-signed waivers all run through a single workflow.
Lien waivers
Conditional, unconditional, partial, and final waivers are generated from vendor data and tracked through e-signature.