1. Establish the source and procurement stage
Open the buyer’s original notice and keep the identifier, URL and time of review. Confirm that the record concerns a specific procurement. A search snippet, supplier-registration page or secondhand summary may help discovery but cannot replace the notice and documents. Identify whether the record is an invitation to respond, advance information, a modification or an award.
SAM.gov contains several notice types, while UK Find a Tender has published notice sequences for different procurement stages. A planning signal can be worth tracking without being an open bid. Keep those decisions separate: “monitor future need” is different from “prepare a response now.” If you cannot establish the stage, mark it for investigation.
2. Confirm deadlines and the effort needed to meet them
Record the submission date, exact time, time zone and submission method from the current documents. Check amendment notices, buyer questions and answers, mandatory meeting dates and the deadline for requesting clarification. Do not assume that the original deadline in an alert remains unchanged when you return to the procurement later.
Work backward from submission. Allow time for reading, estimating, collecting evidence, getting approvals and testing the required portal or file format. A project can fit your services yet leave too little time for a careful offer. Use a realistic preparation threshold and assign an owner to recheck the source before the final submission.
3. Verify the deliverable and place of performance
Read the specification and individual lot, rather than relying on the headline. Separate the core deliverable from supporting context. A tender discussing a digital platform might request a software license, custom development, training, equipment or a complete operated service. Identify what you must actually supply and which responsibilities remain with the buyer.
Confirm the work location, on-site obligations, delivery dates and required language. The buyer’s mailing address is not sufficient evidence of the place of performance. For cross-border work, check the stated participation and execution conditions. Do not treat the country selected in a monitoring tool as confirmation that your company may fulfill the contract.
4. Map requirements to evidence you possess
Create a brief requirement register. For each condition, record the document and section, what is requested, your available evidence and the unresolved question. Relevant items can include references, financial information, qualifications, insurance, security requirements, registrations or restrictions stated in the notice. The applicable documents determine which items matter; this is not a universal legal requirements list.
Use three labels: evidenced, unresolved and not met. An unresolved certificate is not automatically satisfied because your technical experience is strong. For US solicitations, read any assigned NAICS classification, size standard or set-aside restriction where applicable. For UK and German tenders, follow the specific supplier instructions and evidence requirements in the current documents.
5. Check capacity and the cost of pursuing the bid
Estimate proposal effort as well as delivery effort. Identify the people who will prepare the response and those who would perform the contract. Review dependencies, lead times, payment provisions and any commercial obligations that need specialist review. Published value alone does not tell you whether the work is profitable or whether the team can support it.
A practical comparison is the proposed scope against available staff, delivery calendar and pursuit budget. If two opportunities compete for the same specialist, make that constraint visible before both bids begin. Record why the opportunity is worth the work, rather than treating a large contract amount as sufficient justification.
6. Record the decision and revisit unresolved facts
Consider a fictional development consultancy reviewing an integration tender. The scope matches, the delivery country is serviceable and the closing date leaves three weeks. However, the documents request a type of comparable reference the team has not yet verified. The sensible initial outcome is investigate, with an owner and deadline to check the evidence or ask a permitted clarification. A high relevance score should not turn that gap into a proceed decision.
RFPscope’s score, explanation and source report can support this triage. Review verification limits and return to the buyer documents for the final decision. Record the outcome, responsible person, reasons and next review date. Declining for a genuine capacity or requirement gap is a useful result: it keeps proposal resources available for opportunities you can properly pursue.
- Proceed: current opportunity, sufficient preparation time, supported requirements and an agreed delivery plan.
- Investigate: name the missing fact, its owner and the date by which it must be resolved.
- Decline: record the decisive mismatch or constraint so the team can improve future searches.
Sources and further reading
Put your company profile to work
Describe what you can deliver and where you can work. Review source checks and matching reasons before preparing a proposal.
Create your free company profile ↗