solicitation document drafting
Solicitation document drafting turns a purchasing organization’s requirements into instructions suppliers can understand and evaluators can apply. In Canadian public procurement, the document’s structure and wording need to fit the organization’s policies and the relevant jurisdiction. A clear starting point is to identify the purpose of the solicitation and the information suppliers must provide.
Key Takeaways
- Effective solicitation documents describe requirements in plain language so suppliers can respond clearly and evaluators can assess submissions consistently.
- Every document should begin with a clear statement of purpose, which helps the drafting team stay focused on what the purchasing organization actually needs.
- Because public bodies operate under different policies and jurisdictions across Canada, drafters should align wording and structure with their own organizational rules and the applicable official guidance.
- Deciding early what information suppliers must provide makes the rest of the document easier to organize and helps readers follow a logical sequence.
- This overview is introductory and educational, so for a specific solicitation you should rely on your organization’s policies, relevant government guidance and qualified professionals.
For a newcomer, the key connection is between what the document asks and how responses will be assessed. The sections below explain that connection and introduce common solicitation types, while recognizing that terminology and practices can differ among public bodies.
What a solicitation document is and why drafting quality shapes the outcome
A solicitation document is the set of information a public body shares with potential suppliers to invite responses to a purchasing opportunity. It describes the need, explains how to submit a response and sets out how the purchasing organization will assess submissions. Solicitation document drafting is the work of making those parts clear, consistent and aligned with the organization’s stated process.
Plain-language definition and where it sits in the procurement lifecycle
The document sits between planning and the assessment of supplier responses. Before it is prepared, a team needs to understand the requirement and the intended outcome. After release, suppliers use the document to decide whether and how to respond, while the procurement team uses it to guide the process. The solicitation may include instructions, requirements, evaluation information, pricing forms and proposed contract terms. The exact package depends on the opportunity and applicable organizational rules.
How the words you draft become the criteria evaluators score later
Evaluators can assess a response against the requirements and criteria stated in the solicitation. If the document says a feature is required, it should be distinguishable from a feature that earns additional consideration. Likewise, evaluation criteria need to describe what the team will assess, not leave important expectations implicit. For example, a request to “provide a suitable delivery plan” gives less direction than a request that identifies the planning information suppliers should explain. The wording shapes what suppliers submit and what evaluators can consistently review.
Terms newcomers should know before drafting begins
A requirement describes a need the response must address. A mandatory requirement is presented as a condition suppliers must meet; a rated criterion is assessed using a stated evaluation approach. Weighting describes the relative importance assigned to rated criteria when that approach uses weighted scoring. A submission instruction tells suppliers how to prepare and deliver a response. Teams should use these terms consistently and confirm their meaning against their own policies.
For learners who want structured study of solicitation and award topics, Public Sector Procurement Program: Solicitation and Award (PSPP®® 202) is one course option. Its subject matter includes solicitation methodologies and evaluation criteria design.
Choosing the right solicitation type: RFI, RFP, RFQ and ITT compared
What each RFx type asks the market to provide
RFx is a general shorthand for different types of requests issued to suppliers. The abbreviations are not used identically by every organization, so treat these descriptions as a learning orientation rather than a universal rule. A Request for Information (RFI) generally seeks information to help a public body understand a market or need. A Request for Proposals (RFP) invites proposed approaches to a requirement. A Request for Quotations (RFQ) commonly focuses on pricing for defined goods or services. An Invitation to Tender (ITT) invites a tender response under the issuing organization’s stated requirements.
Comparison table: purpose, typical structure and best-fit situations
The table shows broad distinctions in the information each request may seek. A label alone does not determine the process: the actual document, applicable policies and jurisdiction guide suppliers and evaluators. Read the organization’s instructions alongside the title.
| Type | Typical purpose | Information the document may request | Drafting focus |
|---|---|---|---|
| RFI | Gather information about a need or market | Supplier capabilities, available approaches or comments | Explain the information sought and the purpose of the exercise |
| RFP | Invite proposals responding to a requirement | Approach, experience, delivery plan and pricing, as specified | Describe the requirement and how proposals will be assessed |
| RFQ | Request quotations for a defined requirement | Price and requested details about the offered goods or services | Make the requested items, quantities or service details clear where applicable |
| ITT | Invite tender submissions against stated requirements | Required response information and pricing details | Set out submission instructions, requirements and assessment information |
How the type you choose changes what you must draft
The request’s purpose affects which sections need the most detail. A market-information exercise needs clear questions and an explanation of what information is being gathered. A proposal-based request needs a readable description of the need and assessment criteria that match the response requested. A request focused on quotations needs a sufficiently clear description of what suppliers are being asked to price. Solicitation document drafting should begin with that purpose, then align instructions, response forms and evaluation details.
There is no single solicitation format that applies to every Canadian public body. Requirements and terminology can vary by jurisdiction and organizational policy. Before selecting or adapting a document, teams can check the relevant official government guidance and internal rules. The Public Sector Procurement Program: Solicitation and Award (PSPP®® 202) also covers solicitation methodologies, offering a learning route for readers building foundational knowledge.
Section-by-section anatomy of a Canadian public-sector solicitation document
A complete solicitation package gives suppliers the information needed to prepare a response and gives the procurement team a consistent reference during evaluation. Its sections should work together: the scope describes the need, the instructions explain how to respond, and the evaluation information explains how responses will be assessed. The exact contents depend on the opportunity, the public body’s policies and the applicable jurisdiction. Treat the outline below as a drafting aid, not a universal template.
Anatomy table: section, purpose, what to include and common errors
Start with the reader’s task in each section: what must a supplier understand, provide or confirm? Keep each instruction in the section where a supplier would expect to find it, and use consistent terms throughout the package. Avoid leaving important details in an attachment without pointing to it in the main document.
| Section | Purpose | What to include | Common drafting error |
|---|---|---|---|
| Opportunity overview | Orient suppliers to the request | Purpose, background and a plain-language summary of the need | Using broad statements that do not explain the requirement |
| Scope and requirements | Describe the work or goods sought | Deliverables, required features, boundaries and relevant context | Mixing essential requirements with preferences |
| Submission instructions | Explain how to prepare and submit a response | Required response parts, format and submission process | Leaving a required form or instruction unclear |
| Evaluation approach | Explain how responses will be assessed | Mandatory requirements, rated criteria and any stated weighting method | Assessing a factor that suppliers were not told about |
| Pricing schedule | Collect comparable pricing information | Requested price details and the structure for providing them | Asking suppliers to price an undefined item or service |
| Proposed contract and terms | Show the terms associated with the opportunity | Relevant draft agreement and referenced attachments | Including terms that do not align with the described work |
Writing a clear scope of work: specifications versus performance-based requirements
The scope of work describes what the purchasing organization needs. A specification may identify a required feature, material or service component. A performance-based requirement describes the outcome or level of performance sought, while leaving room for suppliers to explain how they would meet it. The appropriate form depends on the need and the organization’s rules. Whichever approach is used, define unfamiliar terms, identify boundaries and make requirements understandable without relying on unstated assumptions.
For a hypothetical learning example, “provide regular updates” leaves the expected information and timing unclear. A clearer draft would identify the update contents and the schedule required by the solicitation. The example illustrates a writing choice, not a prescribed contract term. Ask whether different suppliers could reasonably interpret the requirement in different ways.
Drafting evaluation criteria: mandatory versus rated criteria and weightings
A mandatory criterion states a condition a response must meet, while a rated criterion is assessed for its relative merit under the approach described in the solicitation. Label these categories clearly and explain what evidence suppliers should provide. If the evaluation uses weightings, state them in the document and ensure the criteria and scoring descriptions support the stated approach. Do not rely on evaluators to infer what “strong” or “suitable” means.
In solicitation document drafting, the requested response and the evaluation criterion should match. If a criterion assesses a delivery plan, ask for the information evaluators need to consider that plan. The team can then review whether each criterion is clear, relevant to the stated need and consistently described.
Where instructions to bidders, pricing schedules and terms and conditions belong
Place submission instructions together so suppliers can find the required response format and process. Put price questions in a distinct schedule or clearly marked section, with enough context for suppliers to understand what they are pricing. Present proposed contract terms as part of the package, and identify attachments or forms that suppliers must review or complete. Clear labels and cross-references help readers navigate without duplicating or contradicting information.
For structured learning about these drafting topics, Public Sector Procurement Program: Solicitation and Award (PSPP®® 202) covers solicitation methodologies and evaluation criteria design. The Public Sector Procurement Program: Solicitation and Award (PSPP®® 202) is one option for learners seeking a focused course on solicitation and award.
Drafting mistakes that lead to addenda, complaints and weak bids
Unclear wording can leave suppliers unsure what to submit and evaluators unsure how to interpret a response. Contradictions between the main document, an attachment and a pricing form can create further uncertainty. During review, check whether terms are used consistently and whether each instruction has one clear meaning. A hypothetical example: “provide regular updates” does not say what information an update contains or when it is due. Naming those details makes the request easier to understand without leaving suppliers to guess.
Ambiguous language and contradictory clauses
Watch for broad words such as “adequate” or “timely” when the document does not explain the expected standard. Also check that cross-references point to the correct section and that attachments do not introduce different instructions. A careful read by someone unfamiliar with the draft can reveal wording that seems clear to its authors but allows multiple interpretations.
Unclear evaluation detail and inherited clauses from copied documents
Evaluation information should match the response requested. If a factor is meant to be assessed, the document should explain what suppliers need to provide and how the factor fits the stated approach. Copying a past document without checking it can carry forward outdated dates, names, definitions or requirements that do not fit the current need. Treat every inherited clause as a draft to verify, not as automatically suitable text.
How fairness and transparency considerations start in the document itself
Suppliers need a shared understanding of the opportunity and its stated assessment approach. Clear instructions and consistent terminology help reduce avoidable uncertainty. When a team notices unclear or conflicting wording, it can pause to consult the appropriate internal reviewers and applicable guidance. This is general learning information, not advice for responding to a live complaint or procurement matter.
Standard templates versus custom drafting
A template can support consistent organization and remind a team to consider common sections. It can also preserve language that is no longer relevant. Custom drafting can reflect a particular requirement, though it needs careful review for completeness and consistency.
Practical trade-offs when using a template
Pros
- Provides a familiar structure for organizing the package.
- Can help teams notice sections that need review.
Cons
- May contain clauses or references that do not fit the current opportunity.
- Can create conflicting instructions if attachments are not updated together.
Pre-release review checklist and next steps for building drafting confidence
A pre-release review gives the team a chance to check whether the package is complete, readable and internally consistent before suppliers see it. Assigning reviewers clear roles can help surface different issues, such as missing attachments, unclear instructions or inconsistencies between the main document and forms. The checklist below is a general learning aid. Local approval steps and requirements vary, so follow the relevant public body’s policies and official government guidance.
Pre-release checklist: completeness, clarity, consistency and approvals
Use these prompts to guide a team review. They do not replace the organization’s review or approval process.
- Completeness: Are referenced schedules, forms and attachments present and labelled?
- Clarity: Can a supplier understand each instruction without relying on an unstated assumption?
- Consistency: Do key terms, dates, cross-references and requirements align across the package?
- Evaluation: Does the requested response information match the assessment approach described?
- Approvals: Have the appropriate internal reviewers considered the document under the organization’s process?
Questions to explore with official guidance and your own policies
Before release, identify which jurisdiction and organizational rules apply. Ask which official source or internal policy governs the process, which review roles are required, and whether the organization has current approved templates or clauses. Canadian public bodies do not all follow one identical process, so a document from another organization may not fit. For a specific situation, consult the relevant official government guidance, your own policies and qualified procurement or legal professionals.
Where to build foundational drafting skills
Learning can help you recognize how instructions, requirements and evaluation language fit together. The Public Sector Procurement Program: Solicitation and Award (PSPP®® 202) is a focused option for learners developing knowledge in solicitation and award. As you review the course outline, consider whether its topics align with the skills you want to develop. The Public Sector Procurement Program: Solicitation and Award (PSPP®® 202) can be a next learning step for building confidence with these subjects.
Frequently Asked Questions
What sections must a public-sector solicitation document contain?
A public-sector solicitation document commonly includes instructions to suppliers, the requirement or need, evaluation information, pricing forms and proposed contract terms. The exact package depends on the opportunity and the purchasing organization’s policies, so confirm section expectations against your own organization’s rules and the relevant jurisdiction.
How do I choose between an RFP, RFQ, ITT and RFI?
Start with your purpose: a Request for Information (RFI) gathers market knowledge, a Request for Proposals (RFP) invites proposed approaches, a Request for Quotations (RFQ) focuses on pricing for defined goods or services, and an Invitation to Tender (ITT) invites submissions against stated requirements. Terminology and practices can differ among public bodies, so read the organization’s instructions alongside the title.
How should evaluation criteria and weightings be drafted?
Evaluation criteria should describe clearly what the assessment team will review, so that expectations are not left implicit. Where an approach uses weighted scoring, weighting assigns relative importance to rated criteria. Draft criteria so that rated criteria are distinguishable from mandatory conditions, and confirm definitions against your organization’s policies.
What makes a bid requirement mandatory versus desirable, and how is that written down?
A mandatory requirement is presented in the solicitation as a condition a supplier must meet, while a rated criterion is assessed using a stated evaluation approach. Document drafting should make that distinction explicit in the wording, because evaluators assess responses against the requirements and criteria as written in the document.
How do Canadian trade agreements affect how I draft a solicitation?
Applicable laws, policies and agreements vary by jurisdiction and circumstance, so drafting needs to fit your organization’s policies and the relevant jurisdiction. Rather than interpreting specific obligations, check official government procurement guidance for your jurisdiction and your organization’s internal rules before adapting any solicitation document.
Why does the wording of a solicitation document shape the outcome?
Evaluators can assess responses only against the requirements and criteria stated in the document. A request to provide a suitable delivery plan, for example, gives less direction than one that identifies the planning information suppliers should explain. Clear wording shapes what suppliers submit and what evaluators can consistently review.
Where does solicitation document drafting fit in the procurement lifecycle?
Solicitation document drafting sits between planning and the assessment of supplier responses. Before drafting, a team needs to understand the requirement and intended outcome; after release, suppliers use the document to decide how to respond while the procurement team uses it to guide the process.