Skip to content
FIRST SCOUT

Tools & Guides

From early signal to submitted bid: a simple opportunity record

Keep sources, stages, questions, dates and submission evidence together without turning possibilities into confirmed work.

Published 2026-11-10 · Updated 2026-11-10 · By First Scout · AI-assisted practical guidance · About 5 min read

An opportunity record should show what is known, what remains uncertain and what somebody needs to do next. Without that structure, an early research lead can quietly become a supposed live tender, and a saved draft can be mistaken for a submitted bid. Clear stages help a small business make decisions without claiming more progress than the evidence supports.

The government's central digital platform factsheet explains that procurement information covers different points in the process and that suppliers must follow the buyer's submission method. The record suggested here is an original administrative tool. Its working stages are not official procurement statuses or a replacement for the source documents.

Give the record an identity and source

Start with a short title, the relevant organisation and the original source link. Add the date you read it and a reference that helps you recognise the record. If several documents describe the same procurement, link them together instead of treating each update as an unrelated new opportunity.

Record what the information actually establishes. A council paper may describe a proposal, while a tender notice may invite a response. Retain the distinction and the document date. Do not turn an inferred future requirement into a confirmed job, deadline or promise that the buyer will go to market.

Use stages that describe evidence

A simple working sequence might be research, assess, clarify, prepare, submitted and outcome recorded. Add declined or monitor where useful. Define each stage in your own business so another person understands what must be true before moving a record.

For example, submitted should require appropriate submission evidence, not merely a file saved on your computer. Outcome recorded should refer to the actual decision received. Keep the buyer's published stage separately, because your internal preparation stage is not the same thing as the procurement's official status.

Capture fit and uncertainty together

Write a brief description of the relevant work, delivery area and why your business might be suitable. Add limitations and unresolved questions beside that description. A positive summary without its caveats can mislead the next person opening the record.

Link the important questions to the source requirement. If you need clarification, record the question, the prescribed contact route, the date sent and the response. Do not replace an unanswered question with a note that somebody is probably happy with the arrangement.

Make dates meaningful

If a date is unknown, record it as unknown. Do not invent one to make a task list look complete. When information changes, retain enough context to explain why your plan changed and ensure you are using the current documents.

Connect documents to the requirement

Keep the current specification, questions, relevant evidence, pricing work and response files together in an appropriate location. Use version dates and a clear current copy. Avoid scattering final, final-new and final-revised files across email with no record of which was submitted.

Sensitive business information should remain appropriately controlled. The opportunity record can point to a restricted file without reproducing everything in a general notes field. Follow the buyer's requested submission route and avoid attaching documents that have no purpose in the response.

Record the actual submission and outcome

When a bid is submitted, retain the appropriate acknowledgement or receipt and identify the files or response version involved. Record a problem as a problem; do not mark the step complete simply because an upload or export was attempted. Resolve uncertainty through the relevant process.

When a decision arrives, keep its date and supporting correspondence. Separate an award, an invitation to a next stage, a rejection and a request for clarification. Where feedback is provided, turn useful points into actions for the next relevant opportunity rather than inventing a reason for the result.

Common mistakes

Avoid counting multiple documents as multiple jobs. Do not describe an unadvertised possibility as live work or move a record to submitted without evidence. Another mistake is retaining only a success label and discarding the source, questions and decisions that explain it. A concise record can preserve that context without becoming a complicated project system.

Your next action

Create one record with source, stage, fit, open questions, dates, owner and next action. Update it only when something has actually changed. First Scout can help organise source-linked intelligence and everyday business records, but the original documents and buyer's process remain authoritative. A well-kept record supports decisions; it does not establish eligibility, guarantee a bid result or turn an early signal into confirmed work.

Useful next steps

Sources and review

Reviewed by Jarvis on 2026-11-10. Review scope: Factual/editorial text, source mapping and AI-assisted organisational attribution; not engineering acceptance