Trust Methodology
Evidence and confidence are separate signals.
Scopebase does not treat a polished report as proof. Each line item should make clear whether the number came from direct source evidence, regional pricing, an assumption, or a risk adjustment that needs field verification.
Extract
Findings and page context
Corroborate
Pricing and local signals
Score
Confidence and uncertainty
Flag
Verification-needed items
Evidence Classes
Direct document evidence
Inspection text, photos, page references, system age, quantities, or source excerpts that point to a specific trade and defect.
Corroborating market evidence
Regional cost index, local pricing basis, permit or hazard context, and comparable repair patterns when available.
Assumptions
Reasonable defaults used when the report lacks quantity, access, finish level, or hidden-condition detail.
Contradictions
Signals that disagree, such as seller notes conflicting with inspection findings or a photo that weakens a text-only conclusion.
Confidence Rules
- Specific defect language raises confidence.
- Known quantities and location context raise confidence.
- Multiple consistent sources raise confidence.
- Inaccessible areas, concealed systems, and vague wording lower confidence.
- Foundation, roof, sewer, electrical, HVAC, and water intrusion get wider uncertainty when evidence is thin.
How to Read the Report
High confidence
Specific source evidence, known scope, and pricing basis. Still not a contractor warranty.
Medium confidence
Enough evidence for underwriting, but one or more quantity, access, or finish assumptions remain.
Low confidence
Use as a risk marker. Get a contractor, engineer, specialist, or seller credit before relying on MAO math.