What it means
A contract may contain performance targets, deadlines and duties that fade from view after signing, and a periodic review brings them back into daily management. A supplier could meet its headline delivery rate while repeatedly failing a critical product line, and a customer might miss required approvals and then blame the supplier for delay, so both sides' obligations matter.
Start with the correct version of the agreement, including schedules and approved variations, and identify measurable requirements, notice rules, exceptions and remedies. Compare those with delivery records, service reports, invoices, complaints and meeting notes.
Do not rely on a dashboard that measures a different definition from the contract, and if evidence is incomplete, record the gap rather than calling the target met or missed with confidence. Choose a review period suited to the service: a daily critical operation may need weekly checks, while an annual licence may need a quarterly review before renewal.
Segment results where useful, because an average across all locations can hide one repeatedly failing site. Consider volume, seasonality and customer-caused delays, using the agreement's actual exclusion rules where they apply.
Discuss performance with the people who experience the service, since finance can find unexpected fees, operations can describe workarounds and customer service hears complaints, and each unresolved item needs an owner. Separate a factual performance gap from a disputed contractual interpretation, because a service-level credit may require a formal claim within a deadline and a meeting note may not preserve that right.
Agree corrective actions with dates and evidence, asking whether late deliveries stem from capacity, planning, handoff or transport, because a vague promise to "improve" cannot be tested next month. Record improvement plans and later results, and if repeated failure creates exit risk, prepare alternatives early rather than waiting until notice is due; do not threaten termination without checking authority and terms.
Use the review for commercial planning by asking whether actual volume has changed, making pricing tiers or minimums unsuitable, whether services are being paid for but unused, and whether a different scope or supplier would be better. Keep formal contract changes in the approved variation process, because the performance review informs a decision but is not a signed amendment.
For owners, regular review helps a contract earn its ongoing cost. It also gives fair notice of problems and a chance to fix them before a renewal or dispute turns into a rushed decision.
In practice
Real-world examples.
Example
A business compares a cleaning contractor's signed schedule with visit records and finds recurring misses at one site hidden by a strong overall score. It raises the site-level result at the next review and asks for a dated corrective plan.
Example
A software customer reviews outage data, support response and unused modules before renewal negotiations. The evidence supports a request for a smaller package and for any service credits the contract allows.
Example
A supplier shows that repeated late customer access approvals contributed to missed installation dates, leading both sides to revise the process. The review treats the delays as a shared problem to fix rather than a one-sided failure.
Formula
Calculation
Contract target achievement = Eligible events meeting the agreed target / Eligible events measured under the contract x 100
Worked example. An invented service agreement requires on-time completion for eligible jobs. Of 200 eligible jobs, 186 meet the defined window.
- Achievement = 186 / 200 x 100 = 93%.
- Compare 93% with the signed target and investigate the 14 misses, including valid exclusions and customer impact.
The formal calculation may differ by contract; use its exact denominator and timing rule.
Segmenting shows why a single percentage can mislead. Suppose the 200 jobs split into 40 critical faults and 160 routine tasks, with 34 critical faults and 152 routine tasks on time. Critical achievement = 34 / 40 x 100 = 85%, routine achievement = 152 / 160 x 100 = 95%, and the combined result is (34 + 152) / 200 x 100 = 93%, so the headline hides a weaker result on the work that matters most.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Riverbank Offices, an invented company using a facilities contractor. Monthly reports showed 96% of jobs completed on time. Site managers still complained about recurring lift repairs. The contractor's summary mixed routine tasks with critical faults, and one building generated most of the delays. Riverbank reviewed job-level data against the signed priority definitions.
It found that critical faults at that building missed their target more often than the headline suggested. The contractor identified a parts-availability problem and agreed a stock and response plan with dates. Finance checked whether any contractual credit needed a timely claim. At the next review, both teams checked the specific critical-fault result and open actions. The owner had a more useful view of value than a single overall percentage, and the discussion remained grounded in the agreed contract.
Watch out
Common mistakes.
- Using a dashboard metric that does not match the contract's target definition.
- Reviewing only the supplier's duties while ignoring customer dependencies.
- Treating a meeting agreement as a formal variation without required approval.
Questions
People also ask.
How often should performance be reviewed?
Match the cadence to service risk, contract length and the time needed to act before renewal or claim deadlines.
What if the parties disagree on the data?
Preserve source records, identify the definition in dispute and agree a verification route rather than forcing a result.
Can the review change the price or scope?
It can inform a negotiation, but changes need the approval and documentation required by the agreement.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%