What to do in the first 24 hours after an RFP arrives

0 to 4 hours

Preserve the issued package and identify the first expiring action

Start at the authoritative delivery channel. Record the portal or sender, receipt time, procurement identifier, buyer entity, title, lots, access account and visible status. Save the original notice and permitted files without renaming away their source identities. Create a manifest with filename, buyer label, version, date, format, size, location and relationship to any replacement. Include portal-only instructions, message-center notices and links. A forwarded ZIP is not proof that the package is complete.

Open every file enough to confirm readability and identify references to absent schedules, drawings, forms, data rooms or external policies. Check whether a main document says an annex forms part of the procurement even though it is not available. Record access constraints and confidentiality requirements before inviting contributors. The World Bank and EBRD both maintain procurement frameworks in which standard documents, forms and contract materials operate as connected packages. The practical lesson is simple: a headline document rarely defines the whole response obligation.

Find the first event that can no longer be recovered after it passes. It may be registration, acknowledgement, expression of intent, mandatory briefing, site visit, clarification cutoff, consortium declaration or submission. Record exact source wording, date, local time, time zone and required action. Set a conservative internal owner and verification point, but do not silently replace the buyer’s time with an internal one. If dates conflict, mark the conflict for clarification rather than choosing the convenient entry.

4 to 12 hours

Build the deadline card and test disqualifying conditions

Create one deadline card from all documents, not from the notice alone. Include questions, buyer responses, registrations, visits, samples, demonstrations, submission, presentations, validity, standstill or anticipated award, contract start and any lot-specific variation. For each event, record source, responsible bidder action, dependency and internal consequence. Distinguish buyer dates that are informational from bidder deadlines that require evidence. Have another person re-read the original sources for the earliest and final actions.

Then test gates before quality themes. Extract the exact requirement and evidence for legal entity, establishment, exclusions, financial capacity, references, licenses, insurances, certifications, key people, consortium or subcontract reliance, signatures, forms, language and file constraints. Mark confirmed, unresolved, curable by a named date, or not met. Do not call a condition green because someone expects a certificate renewal or believes the buyer will accept equivalence. Record the evidence file and holder, not only the answer “yes.”

Separate submission-time proof from an award or contract-start condition where the documents do. Do not infer a universal timing rule from prior tenders. Where an interpretation could determine whether the organization spends substantial bid effort, create a concise clarification candidate before the question deadline. The first-day team does not issue a legal conclusion; it identifies the condition, source, evidence gap, responsible specialist and decision consequence.

• Reconcile every date to exact source and bidder action.
• Independently verify early and final deadlines.
• Treat pass-fail proof separately from scored quality.
• Name the legal holder and current evidence for each condition.
• Raise decision-critical ambiguity before clarification closes.

12 to 20 hours

Map the shape of the work without starting to write it

Create a one-page scope map: required outcomes, service lines, lots, locations, users, volumes, operating hours, transition, term, options, buyer inputs, incumbent interfaces, data, technology, reporting and key service levels. Label buyer facts, bidder assumptions and missing information separately. Record whether volumes are guarantees, estimates, ceilings or historic observations. Outline the proposed bidding entity and any partner need, but do not treat an unapproved consortium as the baseline.

Map the response architecture. List questionnaires, narrative volumes, pricing schedules, declarations, evidence attachments, signatures, portal fields, file limits, page or word limits and cross-references between them. Identify which buyer templates control content and which bidder-created files are allowed. This is not a writing plan yet. It reveals the number and type of deliverables so the organization can estimate capacity and find dependencies such as one scope decision that affects solution, staffing and price.

Read enough of evaluation and contract material to expose decision-level issues. Capture mandatory versus weighted criteria, headline weights, price evaluation basis, contract term, liability or service-credit concerns, data and security obligations, transition, termination and material deviations rules. Route interpretation to qualified owners. The first day is too early for a complete contract review, but it is not too early to discover that a proposed obligation may change the bid decision or require immediate clarification.

20 to 24 hours

Finish with a conditional decision, not a vague sense of momentum

Assemble a short decision pack containing source manifest, deadline card, gate register, scope map, response architecture, material contract flags, critical unknowns and a first capacity range. State what is verified and what remains an assumption. Name the earliest irreversible action and the next decision point. Do not bury a failed gate in a long opportunity summary. Do not turn incomplete analysis into a persuasive sales narrative.

Use explicit statuses. Proceed to full qualification means no known stop condition prevents the next bounded investment. Conditional proceed names each condition, owner, closure evidence, due date and consequence if it fails. Hold means no further material capacity beyond defined preservation actions until a named fact arrives. Stop records the reason and authority. The opportunity owner should not convert “conditional” into “go” by omitting the condition from the calendar.

Set up only the immediate controls needed for the next stage: controlled repository, package owner, opportunity decision owner, specialist requests, clarification queue, confidentiality boundary and review date. The later kickoff can then assign authors, reviewers and detailed schedule from a stable basis. If package or dates change, reopen the relevant parts of triage. The value of the first 24 hours is not speed for its own sake. It is preventing early enthusiasm from becoming an unexamined organizational commitment.

• Present verified fact and assumption in separate fields.
• Give every conditional decision closure evidence and expiry.
• Limit capacity until material gates and gaps are resolved.
• Preserve stop and hold rationales for later learning.
• Use the controlled fact pack as the input to kickoff.