Direct answer
To write terms of reference for an industrial service, state the objective and the expected result, define scope and exclusions, list technical and safety requirements, set deliverables with dates and measurement rules, and fix objective acceptance criteria. Bidders then price the same work and you can compare proposals fairly.
Institutional content: Authomathika
Published:
Terms of reference (TR) are the document that tells bidders what you need, under which conditions and how you will judge the result. A vague TR produces proposals that cannot be compared, change orders during execution and disputes at acceptance. This guide walks a maintenance, construction or engineering manager through writing a TR with a clear scope and measurable criteria.
If you still need the basics, read Terms of Reference: What They Are and Why They Matter. To decide whether a TR is the right document at all, see Terms of Reference vs Basic Design: Which to Use and When.
What is the objective of the contract and what do you want to receive?
The objective is one or two sentences stating the problem to be solved and the result you will hold in your hands at the end. Write it as an outcome, not as a list of activities: "a recalibrated and documented set of field instruments in unit X" is better than "perform calibration work".
Include the context bidders need to price correctly:
- Where the work happens: plant, area, unit and access conditions.
- Why now: a planned shutdown, a failure history, an expansion or a regulatory need.
- What the work is tied to: the process, the equipment list, drawings and existing documents.
How do you describe the scope and what stays out of it?
Describe scope as a list of work items, each with a quantity or a clear boundary, and add an explicit list of exclusions. Scope is the single biggest source of cost disputes, and exclusions are what protect both sides.
Use this structure for each work item:
- What is done, in field vocabulary: equipment tags, systems, areas, drawings.
- How much: counts, lengths, points, equipment, hours or areas.
- Starting condition: what the contractor receives and in what state.
- Finishing condition: what "done" looks like for that item.
- Interfaces: who supplies what, and who coordinates with operations and other contractors.
Then define the boundary between supplier and owner. A simple table avoids guesswork:
| Item | Contractor | Owner |
|---|---|---|
| Labor and supervision | Supplies | Provides access and permits |
| Tools and instruments | Supplies | Not applicable |
| Materials | Defined per item | Defined per item |
| Temporary utilities | Defined per item | Defined per item |
| Waste and cleanup | Defined per item | Defined per item |
For work done during a plant stoppage, the scope should come from a prioritized work list. Shutdown Scope Definition: How to Gather and Prioritize Work shows how to build it.
Which technical and safety requirements should you include?
Include the standards, documents, qualifications and site rules the contractor must follow, and refer to the current edition of each standard. Do not copy standard text into the TR; name the standard and require compliance.
Typical blocks to cover:
- Applicable standards and internal specifications: for example NR 10 for electrical work and NR 12 for machinery, plus your own engineering standards. Always point to the edition in force.
- Personnel qualification: required training, authorizations and supervision roles. Work involving electricity, machinery, height, confined space or classified areas requires qualified, authorized professionals and your plant procedures.
- Safety management: work permits, risk analysis before each task, lockout and tagout, emergency response and incident reporting.
- Quality requirements: inspection and test plans, records, calibration of measuring tools and traceability of materials.
- Documentation: procedures to be approved before start, and as-built records at the end.
How do you define deadlines, deliverables and measurement criteria?
Define each deliverable with a name, a format, a due date or milestone and a person who approves it, then link payment to measurable progress. A deliverable that cannot be verified cannot be accepted or measured.
| Stage | Deliverable | Approved by |
|---|---|---|
| Mobilization | Work plan, schedule, safety documents | Owner's contract manager |
| Execution | Daily or weekly progress reports, inspection records | Owner's field supervisor |
| Testing | Test reports against the agreed criteria | Owner's engineering or operations |
| Closing | As-built documentation, punch list closed | Owner's contract manager |
For measurement, state the unit (per equipment, per point, per hour, per milestone), the cutoff date and the supporting evidence required. This is where many contracts fail, so read Service Measurement: How a Progress Measurement Report Works before fixing the rules.
Schedule requirements should be realistic: state the window, the constraints (operating areas, shutdown dates, access limits) and what happens if the window moves.
How do you set evaluation and acceptance criteria?
Separate two sets of criteria: how you will judge proposals and how you will accept the finished work. Both must be written in the TR, before bids arrive, so nobody can change them later.
Criteria for judging proposals:
- Technical compliance with every scope item and requirement.
- Demonstrated experience in similar work, with verifiable references.
- Quality of the execution plan: sequence, team, equipment and safety approach.
- Clear list of assumptions and exclusions.
- Commercial terms, compared only after technical compliance is confirmed.
Criteria for accepting the work:
- Each scope item has its finishing condition verified.
- Tests and inspections are completed and recorded against stated limits.
- Documentation is delivered and approved.
- Punch list items are closed or formally agreed.
- Site is cleaned and handed back in the agreed condition.
Where the service involves calibration, What to Ask for in a Calibration Service Proposal lists useful acceptance points.
Companies like Authomathika, an engineering integrator working across electrical, automation, electromechanical assembly and EPC projects, evaluate each service by scope and budget, which is exactly why a precise TR shortens the proposal phase.
What checklist should you use before publishing the TR?
Run this checklist with operations, maintenance, safety and procurement before release. Anything you cannot answer yet will become a question from bidders or a change order later.
- Is the objective stated as a result, not a list of tasks?
- Does every scope item have quantity, start condition and finishing condition?
- Are exclusions and owner responsibilities written down?
- Are standards named, with the instruction to use the current edition?
- Are qualification and safety requirements defined for the type of risk involved?
- Does every deliverable have a format, a date and an approver?
- Are measurement units, cutoff dates and evidence defined?
- Are proposal evaluation and work acceptance criteria written?
- Is there a single point of contact and a deadline for bidder questions?
- Did someone who was not involved in writing it read it and explain the scope back?
If you want to discuss a specific service, you can send the draft through the request a quote page or review the services offered.
