What this is
What is a contractor review meeting record?
What is a contractor review meeting record?
It is the record of a periodic meeting between the site and a contractor covering performance, incidents, feedback and any actions arising, chaired by the contract owner. It exists so that performance data collected elsewhere is actually discussed with the contractor, rather than filed and only surfaced at renewal.
How is this different from the scorecard itself?
The scorecard is a scoring instrument produced from safety, quality, schedule and cooperation data over a period. This record is the conversation about what that score showed, whether the contractor agrees with it, and what either side is going to do about it.
Who needs to attend?
The contract owner from the site side, and someone with enough seniority on the contractor's side to commit to actions. A meeting with only junior attendance on one side is recorded as such, because it changes what the 'continue engagement' decision is actually worth.
Scope
When is a contractor review meeting record required?
A review meeting is a governance instrument for an ongoing engagement, not a substitute for raising problems as they happen.
Use this template when
- A significant or higher-risk contractor is due their periodic performance review
- The scorecard, incidents, violations or audit findings for the period need to be discussed rather than only filed
- A decision on whether to continue, continue with conditions, or end the engagement needs to be made and recorded
- The contractor's own feedback on access, information and cooperation needs a structured channel
- Actions from a previous review need to be checked for closure before new ones are raised
Do not use it for
- Contractor Performance Scorecard, which is the scoring instrument being discussed, not the discussion itself
- Contractor Safety Violation Record, used to record an individual breach at the time it happens
- Contractor Incident Record, used for an individual incident, not a summary count of how many occurred
- Contractor Work Completion Record, which closes out one job, where this record reviews the relationship over a period
- Insurance or contract renewal decisions, which belong in the dedicated insurance and indemnity records even when they come up in the conversation here
Compliance mapping
Which ISO 45001 cl.8.1.4 requirements does this satisfy?
There is no clause that mandates a quarterly meeting; the requirement is that contractor performance is coordinated and monitored on an ongoing basis, and a structured periodic review is the practical way most sites satisfy it.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.9.1.1 | Trend data on contractor performance reviewed at defined intervals, not only at annual audit | Header |
| ISO 45001 cl.7.4 | Two-way communication established and evidenced with external providers on matters affecting their OH&S | Attendance |
| ISO 45001 cl.8.1.4.2 | Contractor performance verified against the requirements agreed at award, not assumed from a satisfactory scorecard alone | Performance discussed |
| ISO 45001 cl.9.1.1 | Monitoring and measurement of incidents, violations and audit findings over the period reviewed | Performance discussed |
| ISO 45001 cl.8.1.4.2 | Coordination arrangements such as access, permits and information tested from the contractor's side, not just assumed to be working | Their feedback |
| ISO 45001 cl.10.2 | Nonconformities and their corrective actions tracked through to closure, not merely raised again | Actions |
| ISO 45001 cl.8.1.4.2 | A named person accountable for reviewing contractor performance and deciding whether the engagement continues | Close |
What it does not cover
- Contractor Performance Scorecard, which is the scoring instrument itself; this record is the conversation about what the scorecard showed, not a re-score.
- Contractor Safety Violation Record, used to log an individual breach at the time it happens, not restated here as a summary line.
- Contractor Incident Record, used for an individual incident; this record only counts how many were reviewed.
- Insurance Expiry Review or Indemnity and Contract Record, which is where contract and cover renewal is actually tracked, not the 'continue engagement' decision here.
- The corrective action itself, linked here by CAPA ID, which is tracked to closure in its own record rather than inside this meeting note.
Global
Contractor Review Meeting Record requirements by country
The meeting itself is not mandated anywhere; what several regimes require is ongoing coordination with, and monitoring of, contractors, and a periodic review is the common way that duty is evidenced.
HSE guidance HSG159, Managing Contractors
Recommends monitoring contractor performance throughout an engagement, not only at selection.
A quarterly record like this one is close to what HSE's own guidance describes as good practice, and its absence is conspicuous in an audit.
OSH Act General Duty Clause
No standard requires a review meeting; liability attaches through the underlying hazards the contractor's performance data reveal.
Incidents and violations discussed here are the evidence a General Duty Clause citation would draw on if a pattern was known and not acted on.
ISO 45001 cl.8.1.4.2 and cl.9.1.1
Contractor performance must be coordinated and monitored on an ongoing basis, not assessed only at prequalification or renewal.
A certification audit will ask for evidence performance was actually reviewed at a defined interval, which this record provides.
How to complete it
How to complete a contractor review meeting record, step by step
The template prompts for what was discussed. What determines whether the meeting achieved anything is what happened to what was raised last time.
The scorecard tells you what happened; it does not ask whether access, permits and information actually worked for the contractor day to day. 'What makes working here difficult' and the access-delay field exist because that answer is the one a site's own data never surfaces.
The field exists because meetings that are only ever criticism stop producing honest conversation, and a contractor who only hears problems has no reason to keep volunteering feedback. Recognition is not softness; it is what keeps the next meeting's feedback candid.
'Previous actions closed: few' should stop the meeting, not pass through it. A review that keeps re-raising the same action without asking why it was not closed the first time is not reviewing anything; it is repeating a note.
Where relationship health is strained or poor and the same access or payment issue has come up before, 'with conditions' needs the condition written into a dated action with an owner. Left as a tone in the meeting notes, it commits nobody to anything by the next review.
What auditors find
Most common contractor review meeting record findings
Review meetings almost always happen for a significant contractor on schedule. The findings concern whether anything from the meeting actually changed.
| Finding | Clause | What fixes it |
|---|---|---|
| Meeting held but the scorecard not actually reviewed, with no reason recorded. | ISO 45001 cl.8.1.4.2 | Block 'Rating Agreed' until 'Scorecard Reviewed' is Yes or a documented exception is given. |
| Meeting one-sided: only senior representation on the site's side, no contractor decision-maker present. | ISO 45001 cl.7.4 | Record 'Senior Representation Both Sides' honestly and treat a one-sided meeting as notification, not agreement. |
| Contractor's own feedback field left blank meeting after meeting. | ISO 45001 cl.8.1.4.2 | Make the feedback prompt required, with a distinct 'nothing raised' option rather than leaving it empty. |
| Actions carried over from a previous meeting with no explanation of why they remain open. | ISO 45001 cl.10.2 | Reconcile 'Previous Actions Closed' against the prior meeting's action list rather than answering from memory. |
| 'Continue Engagement: Yes' recorded despite 'Relationship Health' marked Strained or Poor. | ISO 45001 cl.9.1.1 | Require a written rationale whenever the continuation decision and the relationship rating point in different directions. |
| Payment or access complaints raised repeatedly with no action ever assigned. | Standard-specific | Route a complaint repeated across two consecutive meetings into a named action with an owner, not a recurring text note. |
Case in point
Case in point: the review meeting that kept agreeing to disagree
A site ran quarterly reviews with an electrical contractor. Three meetings in a row recorded 'access or permit delays reported: some' and 'information provided adequate: partly', each time noted as a comment. Each time the meeting closed with 'continue engagement: yes', because the scorecard rating itself was satisfactory and nobody wanted to escalate a working relationship over what read as a minor gripe.
The contractor eventually raised it informally with a director outside the review process, and it turned out the recurring delay was costing their crew close to two hours per visit, traced to a single permit issuer who was rarely available at the contractor's start time. Nobody had connected three consecutive comments into a pattern, because each meeting's record only carried the comment forward, not an action. The fix was procedural: a theme repeated across two consecutive meetings is required to become a named action with an owner, whether or not the scorecard rating looks fine.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
6 sections
- Reference
- CON-019
- Archetype
- Record
- Record ID
- CRM-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 45001 cl.8.1.4
- Links
- Links Vendor, Scorecard
- Tags
- Contractor, Governance
- Sections
- 6
- Fields
- 42
- Follow up fields
- 0
- Repeating sections
- 1
- Links out
- 4
Header
12 fieldsMeeting ID*
Auto sequence. Format CRM-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Contractor*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Meeting Date*
Period Reviewed*
Meeting Type*
Routine review, performance concern, or annual contract review.
Two Way, Not A Telling Off
Contractors see problems on your site that your own people have stopped noticing. Ask what makes working here difficult and you will get useful answers.
Attendance
3 fieldsOur Attendees*
Their Attendees*
Senior Representation Both Sides*
- Yes3 pts
- One side only1 pt
- No0 pts
Performance discussed
9 fieldsScorecard Reviewed*
- Yes3 pts
- No0 pts
Scorecard ID
Links to CON-014 Scorecard ID
Rating Agreed*
- Yes3 pts
- Disputed1 pt
- No0 pts
Incidents Reviewed*
Violations Reviewed*
Audit Findings Reviewed*
- Yes3 pts
- None3 pts
- No0 pts
Previous Actions Closed*
- All3 pts
- Most1 pt
- Few0 pts
Improvement Demonstrated*
- Yes3 pts
- Some1 pt
- No0 pts
Good Performance Recognised*
Meetings that are only ever criticism stop producing honest conversation.
- Yes3 pts
- No0 pts
Their feedback
6 fieldsWhat Makes Working Here Difficult
Access Or Permit Delays Reported*
- None3 pts
- Some1 pt
- Frequent0 pts
Information Provided Adequate*
- Yes3 pts
- Partly1 pt
- No0 pts
Our Staff Cooperative*
- Yes3 pts
- Mixed1 pt
- No0 pts
Payment And Commercial Issues
- None3 pts
- Some1 pt
- Significant0 pts
Suggestions Made
Actions
Repeats5 fieldsAction*
Owner*
Due Date*
Ours Or Theirs*
CAPA ID
Links to FDN-014 CAPA ID
Close
7 fieldsRelationship Health*
- Strong4 pts
- Good3 pts
- Strained1 pt
- Poor0 pts
Continue Engagement*
- Yes3 pts
- With conditions1 pt
- No0 pts
Next Meeting Date*
Contract Owner*
Signature*
Contractor Representative*
Second Signature*
CON-019 · record IDs look like CRM-2026-000 · Links Vendor, Scorecard
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The meeting is the easy part to hold. Carrying a theme from one review to the next, and turning a condition into an action someone owns, is the work that actually slips.
Holds the review meeting record against the scorecard and prior actions, and flags a theme repeated across consecutive meetings before it needs escalating outside the process.
Feeds incident, violation and audit data into the meeting so the discussion is grounded in the period's actual record, not recollection.
Tracks whether a 'continue with conditions' decision has a linked action, owner and due date, rather than sitting as an unactioned note.
Coordinates the crew around the meeting cycle, rolls open actions and repeated themes into one view, and holds every write for your approval before it touches a record.
This template lives in KnowContractor — contractor management. Prequalification, approval, induction, permits and performance.
Meet KnowContractor→Glossary
Contractor Review Meeting Record definitions and key terms
- Contract owner
- The person accountable for the contractor relationship, who chairs this meeting and signs off the continue-engagement decision.
- Relationship health
- A qualitative rating of how the engagement is functioning day to day, separate from the scorecard's measured performance rating.
- CAPA
- Corrective and preventive action: the tracked record an action from this meeting is linked to when it needs formal follow-up to closure.
- Continue engagement (with conditions)
- A decision to keep working with a contractor subject to specific, agreed changes, which only functions if the conditions are written down as actions.
- Senior representation
- Attendance by someone with the authority to commit to actions, distinct from someone merely present to relay information.
FAQ
Frequently asked questions about contractor review meeting record
How often should this meeting happen?+
Quarterly for significant contractors as a baseline, and more frequently for higher-risk engagements or where performance is already a concern. The cadence should be set by risk, not left at whatever interval is convenient to schedule.
Who chairs it?+
The contract owner. That is deliberate: the person accountable for the relationship should be the one deciding whether it continues, rather than a safety or procurement function running the meeting on their behalf.
Should poor performance be raised for the first time in this meeting?+
No. Violations, incidents and audit findings should already exist in their own records; this meeting discusses the pattern across them. A meeting where the contractor first hears about a problem here has been let down by whatever should have flagged it earlier.
What if the contractor disputes the rating?+
Record 'Rating Agreed: Disputed' and capture why, even briefly. An unrecorded dispute reads as agreement at the next review, which is worse than the disagreement itself.
Does 'continue engagement: with conditions' need more detail?+
Yes. The condition belongs in a linked action with an owner and a due date, not as a phrase in the meeting notes that nobody is accountable for actioning.
What if the contractor sends no senior representative?+
Record it as one-sided attendance and treat that itself as an outcome of the meeting, not proceed as though full agreement was reached with whoever turned up.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Contractor Onboarding and Management
Contractor Prequalification Questionnaire
Collects a contractor's safety, insurance, training and performance information before they are approved
Contractor Safety Statistics Review
Reviews a contractor's injury rates, citations and experience modifier over recent years
Contractor Risk Classification
Classifies a contractor by the risk of the work they do, from low risk services to high risk construction
Contractor Approval Record
Records the decision to approve a contractor to work on site
Contractor Safety Program Review
Reviews the contractor's own written safety programme against your requirements
Subcontractor Declaration
Records any subcontractors a contractor intends to use
More in Performance
Contractor Performance Scorecard
Scores a contractor on safety, quality, schedule and cooperation over a period
Contractor Safety Violation Record
Records a breach of your safety rules by a contractor
Contractor Incident Record
Records an incident involving a contractor worker on your site
Contractor Toolbox Talk Record
Records safety talks the contractor delivers to their own crew on your site
Contractor Work Completion Record
Confirms contractor work is finished, the area is clean and safe, and any permits are closed
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 clauses 8.1.4, 9.1.1 and 10.2
- HSE guidance HSG159 — Managing Contractors: A Guide for Employers
- OSH Act Section 5(a)(1), General Duty Clause (US)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.