Spotting Omissions in a Tender Response Document

Cross-reference against the compliance matrix

The most reliable way to spot missing information is to build a compliance matrix at the start of the project and use it as a checklist during the final review. This matrix should list every specific requirement, question, and mandatory document requested in the Invitation to Tender (ITT).

During your review, tick off each item only when you have physically verified its presence in the response. If a requirement asks for three case studies and you have only provided two, the matrix will highlight this gap immediately. Do not rely on memory or the flow of the prose to ensure coverage.

Common areas where information goes missing

Omissions often occur in the transition between technical writing and document assembly. Certain sections are more prone to being overlooked, particularly those that require input from external partners or specific internal departments like Finance or Legal.

Pay close attention to these frequently forgotten elements:

• Appendix references that point to files not included in the final folder.
• Signatures on specific declarations or non-collusion certificates.
• Pricing for optional line items that were buried in a spreadsheet tab.
• Policy documents that must be current and within their expiry date.
• Specific word count minimums or maximums that indicate an incomplete answer.

The mirror review technique

A 'mirror review' involves reading the tender question and your response side-by-side. It is common for bidders to answer the spirit of a question while omitting a technical detail mentioned in the final sentence of a prompt. For example, if a question asks how you manage health and safety 'and how you report incidents to the board', many writers focus on the management aspect but forget the reporting mechanism.

Using automated tools can significantly speed up this verification process. Jittan’s DocumentChecker allows you to compare documents and schedules to spot mismatches and omissions, ensuring that what you promised in your proposal aligns perfectly with the requirements of the source files.

Final assembly and pagination checks

The final stage of spotting omissions occurs after the document is converted to PDF. Formatting shifts can sometimes hide text or push critical tables onto new pages where they might be overlooked. Ensure that all cross-references to page numbers remain accurate and that no content has been cut off by margin settings.

If the tender portal has specific naming conventions for files, verify these one last time. An incorrectly named file can be treated as a missing file by automated procurement systems, leading to a fail mark on compliance before a human even reads your response.