Understanding the Output

Understanding the Output

Every contract scan produces a structured report. Here’s how to read it.

Output structure (always in this order)

Every scan follows the same structure. This consistency is intentional - it makes outputs easy to compare across contracts.

1. ⚠️ Legal disclaimer
2. 📋 Executive summary
3. 📑 Contract metadata
4. 🎯 Risk score and recommendation band
5. 📊 Risk register
6. ❌ Missing or ambiguous clauses
7. ❓ Negotiation questions
8. ✏️ Suggested redlines (Negotiation Prep mode only)
9. 📧 Executive email draft (optional)
10. 💾 Export artifacts

Section 1 - Legal disclaimer

Every output starts with:

⚠️ Not legal advice. This analysis is for issue-spotting and review preparation only. Consult qualified legal counsel before signing.

This is non-negotiable. Contract Risk Scanner accelerates review; it does not replace legal counsel.

Section 2 - Executive summary

A 3–5 sentence overview answering:

• What kind of contract is this?
• What’s the overall risk posture?
• What’s the top concern?
• Should this be escalated?

Section 3 - Contract metadata

A table of key facts extracted from the contract:

“Not specified” means the field was missing or unclear in the source document. The agent never guesses.

Section 4 - Risk score and recommendation band

A 0–100 score with a recommendation:

The score is always shown with its breakdown so you can see what drove it:

Score breakdown: Liability (+25), Missing indemnification (+15), Auto-renewal (+10), Vague SLA (+8) = 58 (High)

📖 Read more: Custom Risk Registers

Section 5 - Risk register

The core of the output. A table with one row per identified risk:

💡 Pay attention to Confidence. A “High severity / Low confidence” finding may be a false positive worth a second look.

Section 6 - Missing or ambiguous clauses

Clauses the agent’s risk rules expected but couldn’t find in the contract:

• Missing: The clause is absent entirely
• Ambiguous: The clause is present but unclear, conflicting, or insufficient

If you uploaded a custom risk register, missing clauses reflect your custom required clauses.

Section 7 - Negotiation questions

5–10 questions to ask the counterparty, ranked by importance:

1. Can liability be capped at 12 months of fees?
2. Will you commit to 72-hour security incident notification?
3. What is your subprocessor list?

These are designed to be ready to send.

Section 8 - Suggested redlines (Negotiation Prep mode only)

For each high-severity item:

Current language:
"Vendor shall have unlimited liability..."

Proposed redline:
"The total liability of either party shall not exceed
the fees paid in the twelve (12) months preceding..."

Rationale:
Caps financial exposure at predictable level; standard in market.

Section 9 - Executive email draft (optional)

If you ask, the agent will draft a 4–6 sentence email summarizing risk for leadership.

“Draft an exec email for this scan”

Section 10 - Export artifacts

Every scan offers downloadable files. See Exporting Results.

Confidence levels explained

Always treat Low-confidence findings as prompts for human review, not conclusions.

Severity vs. Confidence

These are independent:

• High severity + High confidence = act on it
• High severity + Low confidence = verify before acting
• Low severity + High confidence = note for awareness
• Low severity + Low confidence = often ignorable

Related reading

• 🎚️ Analysis Modes
• 💾 Exporting Results
• ✏️ Custom Risk Registers