To respond to a tender in Canada, distinguish the documents your team has written from the files it has actually approved for submission. A file manifest is a simple internal register that makes that distinction visible. It connects each requested attachment to its final filename, version, owner and destination, helping the person submitting the bid avoid an accidental mix of drafts and approved material.
What CanadaBuys says about preparing the response
The CanadaBuys checklist for preparing a bid stresses that each opportunity has its own instructions and evaluation requirements. It describes possible technical, management and financial sections and specifically advises against putting pricing information in the technical section. This federal guidance is a useful starting point; it is not a single packaging rule for every Canadian buyer. The current solicitation determines the required files, their contents and the permitted route for delivering them.
Build the manifest from the buyer's requested outputs
Our recommended approach begins with a clean list of deliverables from the solicitation. Do not begin by copying the contents of your shared folder: that folder may contain alternative drafts, working calculations and background documents the buyer never requested. For every required item, record where the final response will appear and who can approve it.
Use one naming convention internally, while preserving any mandatory filename or form specified by the buyer. Keep approval status separate from editing status. An author marking a document complete means the writing has stopped; it does not establish that the technical lead, commercial owner or authorised signatory has accepted the commitments inside it.
| Manifest entry | Internal control | Final check |
|---|---|---|
| Technical response | Named owner and approved version | Required answers present; inappropriate price content removed |
| Financial attachment | Commercial approval and calculation review | Figures match the approved scope |
| Supporting evidence | Claim, source and permitted disclosure | Attachment is relevant and readable |
| Submission package | Release owner and delivery route | Only approved files are selected |
Inspect the exported file, not just the working document
A Word document can look correct while its exported PDF hides a table or changes a page break. A spreadsheet can contain comments, external links or hidden sheets that were useful during preparation but inappropriate for release. Open the actual output files and review the visible content, properties and supplementary material using your organisation's normal controls.
Check the relationship between files as well. The quantities in a financial workbook should describe the same delivery model as the technical response. If an attachment is replaced, update the manifest and withdraw the superseded internal release version from the submission folder. This is version discipline, not a recommendation to alter files already submitted outside the permitted process.
A fictional example: an unapproved pricing workbook
Imagine an Ottawa consultancy with two similarly named financial workbooks. One includes a revised travel assumption; the other is the version approved by management. The submission coordinator notices that the selected filename differs from the manifest. The team pauses, confirms which scope was approved and reconciles the technical travel schedule before releasing the package. This fictional example shows why file identity matters even when both workbooks appear complete.
Agree a handover point after which any change triggers renewed approval of the affected files. Keep the person responsible for submission informed of both the change and its consequences. A quick verbal instruction to use the latest attachment is less reliable than an explicit version recorded in the release list.
Connect preparation to human review
See our guide to Canadian tender sources and submission planning and the final response review checklist. MyWiseDocs supports document analysis and response preparation, but people must validate the approved files and complete the buyer's submission process.
Frequently asked questions
Is a file manifest a mandatory Canadian form?
Not on the basis of this article. It is our suggested internal control. Use any mandatory forms and attachment lists in the actual solicitation; do not substitute this working register for them.
Should every attachment be combined into one PDF?
Only if that is compatible with the instructions. Combining files can destroy required separation or make a mandatory workbook unusable. Confirm the requested format and destination for each item before assembling the package.
Does approval of every file prove successful submission?
No. Approval and delivery are separate events. After following the authorised submission route, check the available acknowledgement or receipt and retain it with the released versions, without assuming it establishes technical compliance or award.