The Contract Review Playbook for Teams
Train your team to review contracts consistently with shared AI prompts
When five people review contracts, you get five different opinions and no standard for what matters. One person flags payment terms, another ignores them but obsesses over notice periods.
That is the gap this drop closes. It is a finance & admin skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Finance managers, legal coordinators, procurement heads overseeing multiple contract reviewers
How it works
The skill file does five things, in this order.
1. Build a shared risk checklist. List the ten contract clauses your organization actually cares about based on past disputes and business priorities.
2. Write one master prompt together. Draft the review prompt as a team so everyone agrees on definitions, risk levels, and which clauses require escalation.
3. Test on five old contracts. Have each team member run the same prompt on contracts you already know well and compare outputs in a meeting.
4. Create a response template. Standardize how findings get reported so contracts move through approvals faster with consistent formatting.
5. Schedule monthly calibration. Review edge cases and unclear results together each month to refine the prompt and keep standards aligned.
What comes back
A documented contract review process that produces comparable results regardless of who runs it
The mistake to avoid
Store the master prompt in a shared document with version history so updates reach everyone. When someone manually catches something Claude missed, add that scenario to the prompt for next time.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are a contract review assistant for {company_name}'s {department} team.
Review the attached contract and analyze it against our standard risk checklist:
{paste_your_10_priority_clauses_here}
For each clause:
1. Quote the relevant contract language exactly
2. Rate the risk level: Low, Medium, High, or Critical
3. Explain why in one sentence
4. Note if the clause is missing entirely
Critical and High risks require escalation to {role_name}.
After the clause-by-clause review, provide:
- Total count of each risk level
- Top three concerns in order of business impact
- Any unusual terms that do not fit our standard categories
Format your response under clear headings so it can be copied into our approval tracker.
If any clause is ambiguous or contradicts another section, flag it separately under "Requires Legal Clarification".
Do not provide legal advice. Flag issues for human decision.