Direct answer
Terms of reference (ToR) are the document that defines what a buyer needs from a service or project: objective, scope, deliverables, requirements, and acceptance criteria. Suppliers price and propose against it, and it later guides the contract. Authomathika, an engineering integrator, works with ToR as the starting point of proposals.
Institutional content: Authomathika
Published:
Every industrial contract starts with a question: what exactly does the buyer want delivered? The terms of reference answer it in writing, before any supplier prices a single hour. This guide explains the concept and its role in contracting. It does not cover how to draft one step by step.
What are terms of reference?
Terms of reference (ToR) are the written document in which a buyer describes the need, the scope, the expected deliverables, the technical and managerial requirements, and the criteria for accepting the work. In Brazilian procurement the same idea is called termo de referência (TR). The ToR is the buyer's side of the conversation: it states the problem and the limits of the job, not the supplier's solution.
A useful ToR usually covers:
- The objective and the context of the plant or asset involved.
- The scope included and, just as important, the scope excluded.
- The deliverables, such as drawings, lists, reports, and as-built documents.
- The technical requirements, referenced standards, and site conditions.
- The interfaces with other contractors and with the operations team.
- The acceptance criteria and the tests that prove the work is done.
What is a ToR used for in public bidding and private contracting?
The ToR gives every bidder the same description of the job, so proposals can be compared on equal terms. In public bidding it is a formal part of the process and supports the choice of the winning offer. In private contracting it is not always mandatory, but buyers who use it get proposals that are easier to compare and fewer surprises during execution.
In both settings the ToR does three jobs:
- It aligns the buyer's internal areas (maintenance, engineering, operations, procurement) on one definition of the need.
- It lets suppliers estimate cost and schedule against a common baseline.
- It becomes the reference to settle disputes about what was or was not included.
What is the difference between terms of reference and basic design?
The ToR describes the need and the rules of the contract, while the basic design (projeto básico) describes the technical solution in enough detail to estimate cost and schedule. A ToR can exist without a basic design, but a basic design usually sits inside or alongside a ToR when the buyer already knows what solution it wants.
| Aspect | Terms of reference | Basic design |
|---|---|---|
| Main question | What do we need and under what conditions? | What solution will meet the need? |
| Typical content | Scope, deliverables, requirements, acceptance | Drawings, specifications, quantities, technical criteria |
| Who usually prepares it | Buyer, sometimes with engineering support | Engineering, by the buyer or a hired designer |
| Best fit | Services and performance based work | Works with a defined solution |
For a deeper comparison, see Terms of Reference vs Basic Design: Which to Use and When.
When can you skip a terms of reference?
You can skip a formal ToR when the need is small, repetitive, and fully described by a standard order, such as a catalog item or a routine purchase. In public procurement, the rules of the applicable law define which cases are exempt, so check the current legislation and your legal department. In private contracting the decision is yours, but the more complex the job, the riskier it is to go without one.
Signs that you should write one anyway:
- The work involves several disciplines, such as electrical, automation, and mechanical assembly.
- The job happens during a tight maintenance window.
- More than one contractor works on the same site.
- Acceptance depends on tests that need to be agreed upfront.
How does the ToR connect to the contract and the proposal?
The supplier's proposal answers the ToR, and the contract usually incorporates both as annexes. The ToR fixes what is requested, the proposal states how the supplier will deliver it and at what commercial terms, and the contract binds the two with obligations, schedule, and acceptance.
A clean chain looks like this:
- The buyer issues the ToR to selected suppliers.
- Suppliers send technical and commercial proposals, flagging assumptions and exclusions.
- The buyer compares proposals against the ToR and clarifies deviations.
- The contract lists the ToR, the accepted proposal, and the clarifications as binding documents.
- Delivery and acceptance are measured against the ToR's criteria.
When the ToR is vague, the proposal fills the gaps in the supplier's favor, and the contract inherits the ambiguity. Related topics worth reading are Scope of Supply: What It Is and How to Define It and Documents to Require When Contracting Industrial Projects.
How does this apply to industrial projects?
In industrial work, the ToR is the place where engineering, procurement, and construction interfaces are made explicit. For a turnkey or EPC scope, it defines where the contractor's responsibility starts and ends. Authomathika is an engineering integrator that delivers EPC projects, and each scope is evaluated individually, so a clear ToR is the best starting point for a proposal. If you want to see how a hired scope is organized, the Contact page is the route to request a proposal.
For guidance on drafting, read How to Write Terms of Reference for an Industrial Service.
