Short answer
Contract review evaluates proposed agreements for obligations, ambiguity, and risk, then records clear recommendations. These expectations assess review work and decision support without claiming a legal outcome.
About Contract review
Evaluates proposed agreements for obligations, ambiguity, and risk, then records clear recommendations. The competency supports informed decisions but does not guarantee enforceability, compliance, or a particular legal result.
Use this competency for
- Roles that analyze proposed terms, document issues, or recommend contract changes.
- Functions that coordinate contract positions, approvals, exceptions, and negotiation handoffs.
Do not use this competency for
- Roles that only administer signatures or storage without evaluating proposed terms.
Important distinctions
Supplier negotiation
Supplier negotiation exchanges positions to reach terms. Contract review identifies obligations, ambiguity, and risk and records the recommended position.
Regulatory compliance
Regulatory compliance translates applicable requirements into controls and evidence. Contract review evaluates the obligations and language in a specific proposed agreement.
Expectations by level
IC1
Reviews standard terms
Reviews well-defined agreements with guidance, uses the current issue checklist, and records clauses, questions, and approvals without presenting assumptions as conclusions.
Observable behaviors
- Maps flagged language to the current review guidance.
- Records the clause, issue, and requested clarification together.
- Escalates nonstandard terms through the defined approval path.
Examples
- Flagged a conflicting renewal date and cited both clauses for review.
- Recorded a liability exception with the requester, approver, and open question.
IC2
Owns agreement reviews
Independently reviews agreements with ambiguous or competing obligations, recommends practical options, and coordinates business and specialist input to a documented decision.
Observable behaviors
- Summarizes obligations, uncertainty, and operational impact in plain language.
- Compares proposed terms with approved positions and relevant context.
- Tracks unresolved issues and approvals through the final agreed text.
Examples
- Presented two revision options for a data-use clause and named the operational effect of each.
- Found that an exhibit changed a main-term obligation and reconciled the wording before approval.
IC3
Sets review standards
Defines contract review standards across agreement types, frames unfamiliar issues for decision makers, and improves review patterns using exception and outcome evidence.
Observable behaviors
- Defines review playbooks, decision rights, and exception records.
- Reviews complex agreements for interacting obligations and unresolved assumptions.
- Uses recurring issues to improve templates or approved positions.
Examples
- Created an exception taxonomy after similar issues were approved differently across teams.
- Led review of linked agreements and produced one decision record for conflicting obligations.