Guide · Public Sector

Writing a scope of work for IT and managed services tenders

Most disputes in IT contracts start with a vague scope. A structure for scopes of work that bidders can price accurately and buyers can enforce.

In short: a good scope of work states what must be delivered, where, in what quantity, to what standard, by when, how it will be accepted and measured, and what happens when things change or the contract ends. Bidders can then price it accurately, and buyers can enforce it. Vague scopes produce low bids followed by disputes.

The sections every scope needs

  1. Background and objectives: what the programme is for and how success will be judged.
  2. Sites: a list with addresses, site type and any access or security constraints.
  3. Quantities and specifications: equipment and services per site, with functional specifications and required approvals.
  4. Responsibilities: what the supplier does and what the buyer provides (space, power, network, permissions).
  5. Schedule: milestones, dependencies and site-readiness assumptions.
  6. Acceptance: tests per site and for the whole system, and who signs off.
  7. Service levels: measurable targets, how they are measured and credits when missed.
  8. Reporting: what is reported, how often and in what format.
  9. Change control: how additions, removals and rate changes are agreed.
  10. Exit: handover of assets, data, documentation and knowledge at the end.

Service levels that can be measured

Define each service level by priority, location category and measurement window, and say which system's timestamps count. "Resolve within 8 business hours for priority-2 calls at district sites, measured monthly from the service-desk tool" is enforceable; "prompt resolution" is not.

Specify outcomes, not brands

Functional specifications and required approvals (for example RDSO or STQC for surveillance) allow fair competition. Over-specified or brand-locked requirements narrow the field and can conflict with procurement rules.

Read the scope as a bidder would

Before publishing, ask: could two bidders price this the same way? Where answers would differ, the scope is ambiguous. Pre-bid meetings and written clarifications reduce the risk further. See also buying through GeM and choosing an IT support contract.

Nuclear Edge prepares and delivers GeM and tender-based contracts for ministries, PSUs and state departments. See government and public sector.

Frequently asked questions

What should a scope of work include for an IT tender?

Objectives, sites, quantities and specifications, responsibilities of both parties, schedule, acceptance tests, measurable service levels, reporting, change control and exit arrangements.

How do you write a measurable SLA?

Define the metric, target, priority, location category, measurement window, the system whose timestamps count, and the credit or remedy when the target is missed.

Should tenders specify brands?

Generally no. Functional specifications and required approvals allow fair competition; brand-locked requirements narrow the field and may conflict with procurement rules.

About the author

Abhinav Pillai

Chief Risk & Governance Officer

Abhinav Pillai is Chief Risk & Governance Officer of Nuclear Edge, the Bengaluru deeptech and IT services company, and strengthens enterprise resilience through risk frameworks, internal controls, governance reviews and clear accountability. Abhinav's areas of focus are enterprise risk management, internal controls, governance, audit readiness, operational resilience and compliance frameworks. Abhinav holds an MBA in Finance from IIM Calcutta and a B.Com from St. Joseph's College of Commerce, Bengaluru, and holds the Certification in Risk Management Assurance (CRMA) and Certified in Risk and Information Systems Control (CRISC) credentials. Abhinav writes on choosing IT support contracts and on writing scopes of work for IT tenders.