Follow the question structure

Break the request into its actual requirements and respond in the same order where possible. Give a direct answer before adding background. Identify attachments clearly and point to the relevant sections. Avoid replacing a difficult question with a polished company overview. If something is not supported or requires clarification, state that plainly and explain the proposed next step.

Check completeness across the pack

Create a response matrix showing each requirement, answer location, evidence and owner. Review for contradictions between the main response and attachments. Keep assumptions visible, especially where the request leaves scope unclear. Have someone unfamiliar with the preparation process locate several answers using only the final pack. The test is whether an evaluator can assess the response efficiently, not whether the document contains the largest amount of information.

Put the guide to work

Keep a list of explicit assumptions at the start of the internal response review. Evaluators may interpret an unanswered detail differently from the supplier. Making assumptions visible allows the team to seek clarification or explain the basis of its response rather than hiding uncertainty in persuasive prose.

Imagine this

Hypothetical example

A vendor submits an attractive brochure in response to a detailed operating question. Its revised response begins with the specific process, identifies responsibilities and references a supporting sample. The evaluator can assess the requirement without searching through unrelated brand material.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.