Check contract restrictions before changing prices
Review existing agreements before a proposed price change. Build a customer-by-customer table of notice periods, caps and consent requirements.
How this works
Review existing agreements before a proposed price change. Build a customer-by-customer table of notice periods, caps and consent requirements. Use this before preparing a price increase across existing accounts. It creates an evidence matrix showing which agreements may require notice, consent or different timing, so commercial owners can plan the change.
Analyze the effective contract set per account, including amendments and renewals. Extract constraints with exact references and apply date arithmetic only after the interpretation is confirmed. The assistant prepares questions for legal and commercial reviewers instead of deciding enforceability.
Before you start
Affected account list
Define the products, customers and proposed pricing change included in this review.
Effective agreement set
Collect signed agreements, amendments and renewal records, retaining document status.
Review rules
Identify the legal and commercial owners and agreed extraction fields.
Prepare the inputs
- proposed_change
- Required
old price, proposed price, currency and effective date
Separate list-price intentions from contractual account pricing.
- account_contracts
- Required
account ID and versioned document references
Flag missing amendments or unsigned versions.
- constraint_schema
- Required
notice, caps, consent, renewal and exceptions
Allow unknown and conflicting values for every constraint.
- notice_calendar
- Required
business-day convention and confirmed receipt rules
Use only rules supplied or confirmed by the reviewer.
Implementation, step by step
Establish contract coverage
- Map every affected account to its effective agreement set.
- Keep missing or conflicting documents visible rather than substituting a standard template.
Checkpoint: A contract coverage register is complete.
Extract change provisions
- Locate pricing, renewal, notice, consent and indexation clauses.
- Capture exact paragraph references and short factual summaries without assuming standard terms apply.
Checkpoint: Each extracted restriction has source evidence.
Compare with the proposal
- Calculate the proposed percentage change and dates deterministically.
- Mark apparent conflicts with caps or timing while keeping interpretation questions separate.
Checkpoint: The matrix shows proposal versus extracted terms.
Prepare account options
- Draft possible timing, consent or clarification paths based on confirmed facts.
- Avoid suggesting that silence, an email draft or an unsigned amendment establishes acceptance.
Checkpoint: Reviewers can see decisions needed for each account.
Finalize the reviewed matrix
- Record corrections and approved interpretations with owner and date.
- Prepare notice drafts only if requested, using the reviewed matrix rather than the original extraction.
Checkpoint: The matrix distinguishes pending and approved interpretations.
Decisions along the way
Amendment overrides an older clause
Show both references and ask the reviewer to confirm precedence.
Notice period uses business days
Use the applicable holiday calendar after the rule is confirmed.
Contract set is incomplete
Mark account unassessed and withhold a compliant-change conclusion.
What you will produce
pricing-constraints.xlsx
SpreadsheetA customer-level preparation matrix for commercial planning.
Include: account_id · clause_ref · cap · notice · consent · proposed_change · questions · status
pricing-review-questions.md
MarkdownA focused queue for qualified interpretation.
Include: account_id · conflict · evidence · decision_owner
Check the result
- Verify every constraint against the cited current document.
- Recalculate price percentages and notice dates independently.
- Check every affected account appears, including unassessed ones.
- Ensure approved interpretations are distinct from AI suggestions.
When something goes wrong
Scanned clause unreadable
Request a clearer copy and keep that account unassessed.
Different products have different terms
Split the account into product-level rows.
Effective date changes
Recalculate affected timing checks and retain the previous proposal version.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: assess a proposed account price increase.
Inputs
Account A4 pays 100 units monthly. Proposal is 108 from 1 October. Clause C7 permits a maximum 5% annual increase with 30 calendar days' notice; consent for larger increases is unclear.
Expected result
Synthetic result: proposed increase is 8%, exceeding the extracted 5% cap. Flag legal review and do not label the 1 October change permitted or draft a confirmed notice.
Run a small pilot
Start small
Review a small set of agreements with known amendments and pricing exceptions.
Record the baseline
Record time spent finding clauses and reviewer corrections.
Agree success criteria
Agree extraction completeness and critical-constraint recall before portfolio-wide use.
Stop or revise
Stop conclusions when the effective agreement set or precedence is unresolved.
Keep the scope clear
- This is contract-review preparation; qualified owners determine interpretation and permissible action.
- No prices, contracts or customer notices change merely because a matrix was generated.
Check before using
Legal and commercial owners approve interpretations before customer notices or changes.
Business activities
- Run sales conversations and proposals
- Manage finances and accounting
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Agreements and amendments · Proposed price change
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow