5 minutes
How to Score and Route Contracts for Sign-Off with Eigent
Generate a Contract Safety Score and a clear three-way routing recommendation — legal can sign, negotiate first, or escalate to the CFO — so whoever makes the call has the evidence in one place.
What you need
- Eigent desktop app
- Eigent legal skill (`npx skills add eigentai/legal-skill`)
Best for
- Legal teams that need a documented basis for sign-off decisions
- Procurement leads who need a one-line summary to forward to finance or executives
- Post-negotiation checks to confirm a revised draft clears the risk threshold before signing
Starter Prompt
/legal-risk-assessment — Score this contract [paste full text or paste review output]. Give me a Contract Safety Score from 0 to 100, a severity breakdown (critical / high / medium / low issue counts), and a routing recommendation: can legal sign off as-is, should we negotiate first, or does this need CFO / executive sign-off? State the single most important reason for the routing call.
How it works
- Pass either the full contract text or the output from a previous review to
/legal-risk-assessment— passing the full contract is more thorough, passing review output is faster. - Eigent returns a Contract Safety Score (0–100), a four-level severity breakdown, and a routing recommendation: sign, negotiate, or escalate.
- Use the recommendation to action the decision — include the scoring card in your sign-off email as documentation of the basis for the decision.
- If negotiation is needed, take the open issues into redlines and run scoring again on the revised draft.
- Chain review and scoring in a single prompt using
thenbetween commands to save a round-trip when you need both outputs.
More prompts to try
- /review-contract then /legal-risk-assessment — Review this MSA [paste revised draft] against our playbook and then score it. I need a sign / negotiate / escalate recommendation by end of day.
- We've accepted the governing law deviation as a business decision. Score the contract treating §9.1 as resolved.
- Score this contract but weight data rights and liability issues more heavily than the others — those are our primary concerns on this vendor.
- The counterparty came back with a revised draft after negotiation [paste]. Re-score it and confirm the critical issue from the previous review is now resolved.
How to use
Always run scoring on the final draft after negotiation, not the original — conditions change and the score should reflect the current state of the agreement. Include the scoring card in your sign-off communication so the decision is documented. If you believe a flagged issue is acceptable given your business context, note it as an accepted risk in the prompt so the score reflects your actual position. A score above 70 with no critical issues means legal can proceed, but a high score still warrants counsel review when contract value is material or the counterparty is a strategic partner.
Expected output
A numeric Contract Safety Score (0–100), a severity breakdown with counts of critical / high / medium / low issues, a three-way routing recommendation (sign / negotiate / escalate), and the single most important reason for the routing call.
Limitations
- The score reflects identified clause risk, not business context — it does not account for your relationship with the counterparty, the strategic value of the deal, or the regulatory environment your business operates in.
- A legal opinion from qualified counsel includes all of those factors; the score is a structured brief, not a substitute.
- Scoring cold (without a prior full review) gives you a number without the underlying clause-level detail that makes it meaningful.
Related workflows
Review Any Contract with AI
Run a full clause-by-clause analysis on any legal document — NDA, vendor MSA, DPA, or AI vendor term…
Generate Contract Redlines
Turn contract review findings into ready-to-send negotiation language — with replacement clauses wri…
Track Your Contract Renewal Pipeline
Surface every contract with a cancel-by deadline in the next 90 days, see the last deviations you ac…