01 / Notice identity and amendments
Make sure everyone is reviewing the same source.
- What is the canonical notice URL?
- Which revision and attachments support this review?
- When was the source last checked?
- What changes would trigger a new review?
Worksheet / Requirements and evidence
Read the requirement.
Keep the evidence.
Before you mark an IT RFP as a fit, identify what the notice actually asks for and what your firm can support. This worksheet gives each conclusion a source and each unknown a next step.
One row for one requirement.
Split a sentence that contains several obligations into separate rows. “Migrate the data, provide training and support operations” should not become a single “Cloud” check. Use the notice's wording, then document how each obligation maps to your actual services.
| Column | What belongs here |
|---|---|
| Requirement ID and category | A stable reference you choose, such as TECH-01, grouped under technical scope, eligibility, timing or delivery. |
| Requirement to verify | The specific condition or output you read. Distinguish a mandatory requirement from your own pursuit preference. |
| Notice reference and revision | Section, attachment, page and amendment identifier, plus the time you checked them. |
| Firm evidence reference | A brief reference to the relevant capability, experience record or approved availability plan. Link only to material you are authorized to share. |
| Status | Confirmed, Mismatch or Unknown. The starter rows say Unknown until you supply evidence. |
| Open question and next action | The exact gap, the person responsible for resolving it and the review date. |
| Decision impact | How the answer changes the pursuit: a potential blocker, a clarification task or a planning assumption. |
Six areas to read deliberately.
02 / Eligibility and access requirements
Record requirements as written and seek qualified verification where needed.
- Which registrations, vehicles, set-asides or other conditions does this notice specify?
- What record supports your answer for each one?
- Which items are still unconfirmed?
- Is the assumed role of the firm consistent with the notice?
03 / Technical outputs
Translate broad labels into work that can be evidenced.
- What must be delivered and how is acceptance described?
- Which data, cloud, security or software capabilities are explicitly required?
- Which experience references support each capability?
- What dependencies or client responsibilities need clarification?
04 / Response effort and timing
Separate the official deadline from your internal preparation plan.
- What is the current response deadline and time zone?
- Are there other required dates in the notice?
- How much preparation time does the team need?
- Who checks amendments before the final decision?
05 / Staffing and delivery constraints
A technical match does not establish availability.
- Who can prepare the response and support delivery?
- Are start dates, location and coverage compatible with existing commitments?
- Which assumptions need the delivery lead's confirmation?
- Does the firm have permission to rely on any proposed partner resources?
06 / Commercial review
Keep business questions visible even when the browser checklist does not calculate them.
- What pricing, acceptance or payment terms need specialist review?
- What assumptions affect effort and cost?
- Does pursuing this work fit the firm's priorities?
- Who owns the final decision and its rationale?
A filled row, without a fictional claim of proof.
Synthetic training example: The fictional scope asks for security assessment. The firm's listed capabilities cover data engineering and cloud migration. Record the security requirement as Unknown, note that supporting experience has not been supplied, and assign a qualified reviewer to determine whether the capability can be evidenced. Do not convert a similar-sounding service name into proof.
The browser tool will treat “Security assessment” as unmatched until the exact normalized term appears in the firm's capability list. Adding the term is appropriate only when it accurately reflects the firm; the tool will not validate the supporting experience for you.
Carry the conclusions into the checklist.
- Enter the notice URL and required capability terms you have actually read.
- Convert the notice deadline to the device time zone displayed beside the deadline field.
- Set eligibility, scope and capacity based on the reviewed evidence. Leave unresolved conclusions at Unknown.
- Use the evidence box for concise section references and open questions. Do not paste confidential bid material.
- Run the review, record your decision and keep an export together with the dated source notes.
The worksheet collects a broader review than the tool automates. Commercial terms and delivery assumptions remain human judgments. Neither the worksheet nor the checklist establishes legal eligibility, professional certification or award likelihood.
Put the evidence to work.
Use the free checklist to organize your own source facts, identify blockers and keep a local decision brief.
Review an opportunity