By Joseph Adekale, Toronto Transit Commission (TTC)
As public procurement professionals, we have all been there. A business unit (BU) submits a requisition with a scope of work that reads like a tech manual, a wish list, or a single page of vague bullet points. When we ask to get involved earlier in the drafting process, we are sometimes met with pushback: “Why does procurement care about the technical details? Just paste it into the template.”
But we know the truth. Procurement is responsible for the document quality of the entire RFx package scope included.
The scope of work is not just a technical addendum; it is the foundation of the commercial contract. When we step out of our siloed administrative boxes and sit down at the scope-drafting table, we protect our organizations, maximize market response, and drive true value.
Here is why procurement needs a seat at the scope-writing table, and how you can confidently participate in that conversation.
The Strategic Case for Our Involvement
- Breaking Down Silos
The scope directly impacts both technical evaluation and financial requirements. If a business unit drafts a scope in isolation, they often create requirements that do not align with how the market prices things. Reviewing the scope from a procurement perspective ensures that what the BU wants matches how the market will bid.
- Capitalizing on Our View from the Center
As procurement professionals, you see more RFx documents and resulting market submissions than any single business unit. You possess a wealth of institutional memory. You know what wording causes bidder questions, what clauses lead to contract disputes, and how successful vendors structure their solutions. It is time to capitalize on that experience.
- Boosting Team Credibility
When we move from being “process cops” who just check boxes to strategic advisors who help shape the project, our credibility skyrockets. By providing guidance early, we shift the dynamic from finding the right way to make suggestions later to being actively asked for advice up front.
How to Participate in the Conversation
You do not need to be a technical expert in HVAC systems, IT infrastructure, or civil engineering to review a scope. You just need to look at it through a procurement lens at key stages of the process.
- At the Kick-Off Meeting: Don’t wait for a finished draft. Use the kick-off to establish scope-drafting expectations. (Pro-tip: Add scope-drafting guidance directly to your team’s Standard Operating Procedures).
- In the Procurement Templates: Pre-populate your appendices and schedules with clear headings. Show the business unit exactly how the scope expects to be structured before they type a single word.
- During Document Review: Put yourself in the shoes of a respondent. Read the scope and ask yourself: “If I were a bidder, would I know exactly what is expected of me, or would I have to guess?”
The “W5H” Framework for Clear Scopes
When guiding your business units, remind them that any solid description of services must answer the fundamental W5H questions:
- WHO is required to deliver the work?
- WHAT specific services or deliverables are being requested?
- WHERE will the services be delivered?
- WHEN must they be delivered? (Milestones, commencement, and expiry dates).
- HOW will they be delivered? (e.g., document reviews, physical installations, design phases).
- WHY are these services required? (The underlying problem the agency is trying to solve).
Scope Review Checklist
Keep these essential cues in mind during your next document review to ensure the scope balances market competition with contractual protection.
The Competitive Balance
- Are the mandatory requirements too limiting? If they are too tight, you risk choking out a healthy bidding pool.
- Are they too broad? If they are too loose, you will waste time evaluating unqualified, low-quality submissions.
- Can they be evaluated? Ensure the scope is detailed enough that you can extract clear criteria later to differentiate competing proposals.
Precision in Language
- “Shall” vs. “Will”: Check for proper context. Shall is a binding provision on the Supplier (“The Supplier shall supply…”). Will is a declaration of future action by the public entity (“The Department will provide…”).
- Plain Language: Strip out acronyms, jargon, and rambling sentences. Ask: “What would a reasonable person looking at this conclude?”
- No Legal Creep: Ensure the scope is completely void of warranties, representations, or legal terms and conditions. Those belong in the main agreement, not the technical schedules.
- Commercial Neutrality: Always use generic, non-proprietary terminology to keep the bidding process fair and open.
Deliverables and Payment
- The Golden Rule: Schedule x (the scope) and its appendices are usually the only parts of the RFx package that live on through the life of the contract. It must stand alone.
- Clear Mapping: Every technical requirement should map directly to a tangible deliverable.
- Acceptance Criteria: Is it completely clear what it takes for a bidder to complete the work to your satisfaction, and how that work will be certified for payment?
- Payment Structures: Ensure the milestones align with one of these three structures:
- A single deliverable paid by one invoice upon completion.
- A single deliverable broken into multiple milestones for progress payments.
- Multiple independent deliverables, each with its own milestone/invoice structure.
Anatomy of a Perfect Scope Document
When designing your pre-populated templates for business units, structure them using these standard, logical sections to ensure comprehensive capturing of data:
- Title & Overview
A succinct summary of the requirement that answers at a glance: Who is buying what, and via what contracting mechanism?
Example: Identify the type of service, the specific department/agency acquiring it, and the resulting contract type.
- Background & Rationale
Provides the crucial context, objectives, and key drivers for the work.
- Articulate the agency’s program or internal operational requirement.
- The Policy Check: Clearly state why the agency needs to source this externally rather than handling it in-house.
- Specify if this is a recurring need, a single “one-off” project, or a specific phase in a multi-phase initiative (including any conflict-of-interest restrictions on future phases).
- Objective
The overall outcomes-based goal of the contracted work. This provides an enforceable benchmark and states whether the intent is to award to a single or multiple suppliers.
- Definitions & Reference Documents
Mitigates ambiguity by spelling out industry specific acronyms and listing all applicable legislation, policies, and guidelines that will govern the work.
- Business & Technical Environment
Identifies the operational realities the vendor must navigate.
- Business Environment: Hours of operation, service level window requirements, and on-call expectations.
- Technical Environment: The exact hardware, software infrastructure, or technical standards the supplier must work within (critical for IT and engineering files).
Final Thought
We aren’t just paper-pushers; we are risk managers, market navigators, and commercial advisors. By taking ownership of the scope-review process, we bridge the gap between technical need and procurement excellence. The next time a project kicks off, don’t wait for the scope to land on your desk — help write it.