Terms of Reference (TOR)

Terms of Reference (TOR) is the scope document that defines what a consultant must do in a consultancy assignment. It is the central document in an RFP for consultancy procurement, setting out the background and rationale for the assignment, the specific tasks the consultant must perform, the deliverables to be produced, the timeline, reporting requirements, and the government's expectations for the quality and form of outputs. The TOR is to consultancy procurement what the BOQ and technical specifications are to works and goods procurement.

What is the TOR in government procurement?

In Indian government consultancy procurement, the TOR is typically included in the RFP as a distinct section, clearly labelled. It is the primary document that defines the scope of the assignment, and it is the reference against which evaluators score the technical proposals in QCBS or LCS evaluation.

A well-structured TOR begins with background and context: why the government needs this consultancy, what decisions will be informed by the outputs, and what previous work (if any) has been done on this subject. It then specifies objectives: the three to five key outcomes the assignment must achieve. The main section covers tasks, presented as a numbered or lettered list of discrete activities the consultant must carry out. Tasks might include data collection, stakeholder consultations, analysis, modelling, option assessment, and recommendation preparation. The deliverables section lists the specific documents, reports, models, or other outputs the consultant must submit, with required format, language, and timing. A timeline shows the sequence and duration of tasks mapped to the total assignment period. Reporting requirements state how frequently the consultant must meet the client team and submit progress reports.

The TOR also typically defines the team composition required: the key positions (team leader, sector experts, field survey teams) with minimum qualifications and years of relevant experience. These requirements become the basis for scoring key personnel in the technical evaluation.

A clear TOR makes a consultancy tender competitive because firms can price accurately and evaluate their fit realistically. An ambiguous TOR leads to wildly varying proposals that are hard to compare and often results in scope disputes during execution.

Why it matters for bidders

The TOR is the starting point for proposal writing in consultancy bids. A firm that thoroughly reads the TOR and structures its methodology to address each specified task, produces specific deliverables in the formats stated, and demonstrates its understanding of the context will score higher in technical evaluation than one that submits a generic methodology unconnected to the TOR.

Bidders should map their technical proposal section by section to the TOR. If the TOR has seven tasks, the methodology should have seven corresponding sections. If the TOR defines five deliverables, the work plan should show when each deliverable will be produced. Evaluators score what they can see explicitly in the proposal; they do not give credit for relevant work that is implicit but not stated.

During the pre-bid clarification period, bidders should raise any ambiguities in the TOR. Unclear task definitions, deliverable formats not specified, or data availability assumptions that seem unrealistic are worth flagging. Answers become part of the official RFP through a corrigendum and protect all bidders from scope uncertainty during execution.

Example

A state highways department issues an RFP under QCBS for a pre-feasibility study for a ring road project. The TOR specifies five tasks: (1) review of existing data and site reconnaissance; (2) traffic surveys at 12 specified locations; (3) alignment options development (minimum three alternatives); (4) comparative cost-benefit analysis of alternatives; and (5) recommendation and report preparation. Deliverables are an inception report within two weeks, an interim report with traffic data and alignment options at two months, and a final report with recommendation at three months. A firm preparing its proposal structures its methodology around these five tasks, assigns specific team members to each, and shows a work plan with the three deliverable dates mapped against team input.