This article is part of our Contract Management guide for B2B revenue teams.
Five checklists, all copy-paste, covering the full life of a contract: review it before signing, record it after, monitor it during, decide about it at renewal, and evaluate the software you use to do all four. Take what you need and delete the rest.
A checklist is worth having for one reason. It makes the same things happen regardless of who is doing them or how busy they are. Most contract failures are not knowledge failures. Somebody knew the notice period mattered. They were just not the person handling it that week.
Use the notice date calculator alongside these to work out the date that actually governs each contract, and the contract tracker template to hold the results.
How to use a contract management process checklist
A contract management framework is only useful if it is applied consistently. These lists exist to help you stay organized across the lifecycle of a contract, from initiation through contract negotiations to renewal, and to make sure the same key terms get checked whoever is handling it.
Three principles before the lists themselves.
Standardize before you automate. Pre-approved contract template language and a consistent approach to contract management reduce risk more than any tool. Once the process is stable, digital contract management and a contract management system can automate the repetitive parts: automated alerts on the renewal date, approval routing, and real-time contract status.
Check compliance both ways. Ensuring compliance means adherence to what you owe as well as what the supplier owes. Service level agreements, termination conditions and essential terms all need someone accountable for them.
Be concise and proactive. A short checklist that gets used beats a long one that gets skipped. Identifying potential problems early, whether unfavorable terms in a draft or a vendor drifting on SLAs, is what makes contract management cost-saving rather than administrative.
Procurement, legal, in-house counsel and revenue teams all use versions of these lists. Adapt the wording to your organizational context and delete anything that has never caught a problem.
1. Pre-signature contract review checklist
Run before signature, on every contract, including your own paper. Twelve checks.
PARTIES AND AUTHORITY
[ ] Correct legal entity names on both sides, not trading names
[ ] The person signing has authority to bind their organisation
[ ] Notice addresses are current and go to a monitored destination
TERM AND EXIT
[ ] Start date and initial term length stated explicitly
[ ] How the contract ends: fixed expiry, fixed auto-renewal, or rolling evergreen
[ ] Notice period stated in days, and the method notice must be given in
[ ] Termination for convenience: does either side have it, and on what notice
[ ] Termination for cause: what counts, and is there a cure period
MONEY
[ ] Price, currency, and what exactly is included
[ ] Escalation or uplift clause: stated percentage or index, or explicitly none
[ ] Payment terms and what happens on late payment
SCOPE AND PERFORMANCE
[ ] Deliverables described in terms someone could verify
[ ] Service levels stated as measurable numbers, with remedies if missed
[ ] Change process: how scope changes get agreed and priced
RISK
[ ] Liability cap, and what sits outside it
[ ] Indemnities, and whether they are mutual
[ ] Data protection obligations, if personal data is involved
[ ] Assignment and change of control: what happens if either side is acquired
ESCALATION RULE
[ ] Anything on non-standard terms escalates regardless of contract valueThat last line is the one most review processes omit. Value-based thresholds catch big contracts. They miss the small contract with an unusual indemnity, which is the one that causes the problem.
For a master service agreement specifically
An MSA runs for years and sits above individual statements of work, so four extra checks:
[ ] Order of precedence: does the MSA or the SOW win where they conflict
[ ] Whether the term is evergreen or fixed, and what happens to live SOWs on termination
[ ] Whether liability caps are per-SOW or aggregate across the whole relationship
[ ] Whether the agreement survives a change of control on either sideAggregate versus per-SOW liability is the one people miss, and on a long relationship the difference is substantial.
2. Post-signature record checklist
The least interesting list here and the one whose absence causes the most expensive failures. Run within 48 hours of signature, every time, no exceptions.
[ ] Executed document filed in the repository, not in an inbox
[ ] Contract record created with these fields populated:
counterparty contract value (annual)
contract start date contract end date
notice period (days) <- as a NUMBER, not text
notice date <- calculated: end date minus notice period
auto-renews? (y/n) uplift / escalation terms
contract owner contract type
[ ] One named person assigned as owner, and told they own it
[ ] Alert schedule set, counting back from the NOTICE date
[ ] Billing notified of amount, start date and invoicing schedule
[ ] Any obligations we owe recorded with their own due dates
[ ] Any service levels we are owed recorded so performance can be trackedTwo of those deserve emphasis.
Notice period as a number. “Sixty (60) days’ prior written notice” is correct English and useless to a calculation. Store 60.
Alerts count back from the notice date, not the end date. On a contract with a 90-day notice period, an alert set 90 days before the end date fires on the deadline itself. The mechanics are in evergreen contracts and auto-renewal clauses, and the notice date calculator will do the arithmetic for you.
Where these fit in the contract lifecycle
The five lists map onto the stages of the contract management process, one per stage, which is how to decide which one you need.
| Stage | Checklist | Question it answers |
|---|---|---|
| Negotiation and pre-signature | 1. Contract review | Should we sign this, and on these contract terms |
| Execution | 2. Post-signature record | Is this contract now something the business can see |
| Oversight | 3. Monitoring | Are the contract obligations on both sides being met |
| Renewal | 4. Renewal readiness | Do we continue, renegotiate, or exit, and by when |
| Ongoing | 5. Risk assessment | Which contracts deserve attention first |
| Buying software | 6. Requirements | What do we actually need this to do |
The sixth is not a lifecycle stage, it is the one you run when the other five have shown you where the process breaks.
Most teams adopt these in the wrong order. They start with the review checklist, because pre-signature feels like the responsible place to be thorough, and never build the post-signature record. The result is contracts that were reviewed carefully and then forgotten completely.
Start with number two. It takes the least time and prevents the most expensive failures.
3. Contract monitoring checklist
Quarterly, across the portfolio. Fifteen minutes if the records are good.
[ ] Any notice window closing in the next 120 days, and is it owned
[ ] Any contract with no owner
[ ] Any contract missing an end date or a notice period
[ ] Service levels: met, missed, or not tracked
[ ] Obligations due this quarter, ours and theirs
[ ] Any contract where the signing stakeholder has left
[ ] Any contract renewed in the last quarter with no price change
[ ] Total contract value by expiry quarter, and does it match the forecastThe last two are the ones that find money. Renewals that repeatedly close with no price change usually mean the escalation clause is not being applied, which over three years is a substantial real-terms discount granted by default. Our guide to renewal quotes and price increases covers recovering it.
4. Renewal readiness checklist
The messages this checklist tells you to send are written out in our renewal and non-renewal notice templates.
Run 90 days before the notice date, not the end date. On a 60-day notice period that means starting five months before the contract ends.
TIMING
[ ] Notice date confirmed, and the window is still open
[ ] Owner assigned and aware
[ ] Decision deadline in the calendar
EVIDENCE
[ ] Usage trend over the term: up, flat, or down
[ ] Support history: volume, severity, anything unresolved
[ ] Service levels met, with the numbers
[ ] Value delivered against what was promised at the start
[ ] Stakeholder map current, and the original champion still in place
COMMERCIAL
[ ] Current price and what the escalation clause permits
[ ] Target price for the next term, and the walk-away line
[ ] Expansion or cross-sell opportunity identified
[ ] Term length being proposed
RISK
[ ] Risk rating assigned, with the reason
[ ] If at risk, a save plan with named actions
[ ] Concessions we are prepared to trade, and what we want back for each
EXECUTION
[ ] Renewal record created in the CRM with value, stage and close date
[ ] Line items rebuilt with any uplift applied
[ ] Conversation booked with the customerThe last block is where most renewal processes stop one step short. A reminder announces the work rather than doing it, and if nobody builds the renewal record with correct line items, the renewal stays invisible to forecasting no matter how early the alert fired. The full timeline is in the contract renewal process guide.
5. Contract risk assessment checklist
A risk assessment that scores every contract the same way is a list, not an assessment. Score on factors you can actually observe, rank, and spend your attention on the top.
Six factors, three points each, eighteen maximum:
| Factor | 0 points | 1 point | 3 points |
|---|---|---|---|
| Share of total contract value | Under 1% | 1 to 5% | Over 5% |
| Renewal mechanism | Negotiated renewal | Fixed auto-renewal | Rolling evergreen |
| Notice window | Over 180 days away | 60 to 180 days | Under 60 days |
| Service levels | Met throughout | One miss | Repeated misses or untracked |
| Signing stakeholder | Still in role | Changed role | Left the company |
| Contract terms | Our standard paper | Minor amendments | Their paper, non-standard |
[ ] Score every contract above your value threshold
[ ] 12 or above: review this month, named owner, written plan
[ ] 6 to 11: review this quarter
[ ] Under 6: leave it alone
[ ] Re-score quarterly, or on any stakeholder changeAdapt the weights to your business. The structure matters more than the exact numbers: a small number of observable factors, scored consistently, producing a ranked list rather than a flat register.
Note the third row. A contract can move from low to high risk purely by the calendar advancing, which is why re-scoring quarterly matters more than getting the initial score precisely right. And note that “untracked” scores the same as “repeated misses” on service levels, because for renewal purposes not knowing is no better than knowing it went badly.
6. Contract management software requirements checklist
Use when evaluating tools. Ordered by how often each one turns out to matter.
THE ONES THAT DECIDE IT
[ ] Stores a notice period as a number and alerts on a calculated notice date
[ ] Search covers document text, or only metadata: know which you are buying
[ ] Pricing model fits occasional users (per-seat rarely does)
[ ] Connects to the system where commercial work actually happens
[ ] Honest implementation estimate, including getting existing contracts in
THE STANDARD ONES
[ ] Alerts create tasks with owners, not just notifications
[ ] Escalation when a task goes unactioned
[ ] Reporting on portfolio value by expiry period
[ ] Audit trail of who changed what and when
[ ] Role-based access control
[ ] SOC 2 Type II or equivalent, if that matters to you
THE ONES PEOPLE FORGET
[ ] What happens to your data if you leave, and in what format
[ ] Whether the price changes as your contract count grows
[ ] Whether you can bulk-import and bulk-edit
[ ] Who at your company will actually maintain this in year twoThe first line is the one to lead with in a demo, and several tools in this category fail it. If your contracts auto-renew, a tool that only alerts against a single stored date will faithfully tell you about decisions after they were made. Real prices and an honest tier comparison are in contract management software compared, and the small-business view is in contract management software for small business.
How to actually use these
Three suggestions, learned from watching checklists fail.
Put them where the work happens. A checklist in a shared drive is decoration. In a CRM this is a task template attached to the record; in a simpler setup it is a pinned note on the contract row.
Cut them to fit. These lists are deliberately more complete than most teams need. A twelve-point review that gets done beats a thirty-point review that gets skipped. Delete anything that has never once caught a problem in your business.
Make one person accountable for each list running, not for doing it. The failure is almost never that somebody did the checks badly. It is that nobody ran them.
Frequently Asked Questions
What should be on a contract review checklist? Parties and signing authority, term and start date, renewal mechanism and notice period, price and escalation, payment terms, scope, service levels and remedies, liability caps, termination rights, and assignment on change of control.
What is a contract management checklist? A standing list of the checks a contract passes at each stage, used so the same things happen regardless of who handles it. Most teams need five: pre-signature review, post-signature record, monitoring, renewal readiness, and risk assessment.
What should you check before signing a contract? That commercial terms match what was agreed, that you know how the contract ends and how much notice that needs, that escalation is stated rather than assumed, that service levels are measurable, and that someone with authority signs. Non-standard terms escalate regardless of value.
What is a contract administration checklist? The post-signature list: create the record with key dates as structured fields, assign a named owner, calculate and store the notice date, set alerts, file the document, notify billing.
What is on a contract renewal checklist? Confirm the notice date and that the window is open, review usage and health, check what escalation allows, verify service levels, set a target price and walk-away line, then open the conversation. All before the notice window closes.
How do you do a contract risk assessment? Score each contract on a few observable factors: value concentration, renewal mechanism, notice proximity, service level performance, stakeholder changes, and non-standard terms. Rank, then spend attention on the top.
What should be on a software requirements checklist? Whether it calculates and alerts on a notice date, whether search covers document text, how it prices occasional users, whether it connects to your commercial system, and what implementation really involves.
What is a master service agreement checklist? Order of precedence between MSA and SOW, evergreen or fixed term, termination and notice, liability caps and whether they are aggregate or per-SOW, intellectual property, data protection, and survival on change of control.
SWOTBee builds HubSpot-native contract and renewal operations for mid-market teams: contract dates and notice periods as real properties, alerts anchored to the date that actually decides the renewal, scheduled renewal deals with line items and uplifts, and NRR reporting, all inside your portal, and you own everything we build.
