VALUATION REVIEW14 documents · 26 comparablesLease data, market evidence and model inputs
Analysing
NowStep 3 of 5
DECISION FOUND
Analysis continues while you decide
FOR VALUATION SOFTWARE TEAMS
Resolve the valuation judgment.
Keep the analysis moving.
When document analysis reveals a conflict or judgment call, ask one decision before the model needs it.
One decision, with context — or nothing at all.
ONE DECISION PER RUN
Five moments where one answer keeps work moving.
Each card loads a separate simulated workflow stage. The full decision appears above with the context needed to answer it.
MODEL INPUTWhich floor area enters the model?Try this decision →
LEASE INPUTWhich passing rent enters the model?Try this decision →
REFERENCE REVIEWKeep Transaction A as a primary comparable?Try this decision →
DUPA 2.0Is office the asset’s main use?Try this decision →
OCCUPANCY STATUSIs the unit occupied on valuation date?Try this decision →
One decision. Then you’re done. If nothing can move the work forward, WIT stays quiet.
THE SECOND PAYOFF: YOUR PRODUCT LEARNS
The answer helps this run. The pattern can improve future runs.
Valuation requires professional judgment. The learning layer should therefore make the software more helpful without turning previous choices into automatic valuation assumptions.
01
Current workflowThe answer is immediately written back to workflow state, so the later stage does not have to stop and ask again.
02
Reusable rule candidateRepeated workflow preferences — source precedence, review patterns, comparable ranking signals — can become suggested defaults. The valuer still confirms the professional decision when it matters.
03
Router learningAnswered, skipped and overridden questions improve the ranking. Low-value interruptions naturally disappear.
04
No silent professional autopilotCase-specific judgment stays case-specific. Reusable defaults are proposed and confirmed instead of silently inferred.
THE PRODUCT QUESTION
Why wait until the model stops to resolve a conflict the analysis already found?
→Keep the core analysis running.
→Ask one answerable, consequential decision.
→Return the answer before the model needs it.
→If nothing can move the work forward, stay quiet.
ONE WORKFLOW IS ENOUGH TO TEST IT
Show us where your user waits today.
We’ll identify one predictable human dependency, move it into the existing wait window and measure whether the workflow needs fewer stop-and-ask cycles.