How to Read a Public Tender Before Preparing a Proposal
Updated 17 October 2026 · SparkGuild editorial
Start with five questions: what must be delivered, who can respond, which procurement stage is open, when that stage closes, and where the response must be submitted. A title such as “website services” gives too little information to decide whether preparing a proposal is worthwhile.
This guide is an original screening worksheet. Use it to organize the published requirements and identify missing information. Eligibility and submission instructions belong to the issuing organization and its procurement documents.
Distinguish the kind of opportunity
| What you are reading | What to establish before acting |
|---|---|
| A project request from an individual or team | The actual deliverable, budget, decision maker and agreed response channel |
| An institutional procurement notice | The procedure, applicant qualifications, required evidence and formal submission deadline |
| A request to participate | What must be submitted at the application stage and whether a later invitation is required |
| An award, correction or planning notice | Whether it creates a current opportunity or updates an existing procedure |
SparkGuild labels the institutional notices reviewed in the current collection. Other source entries include project requests, service pages and reference material. The source label is a starting point for reading, not confirmation that you qualify.
Open the latest original notice
TED explains that a correction receives a new publication number while earlier versions remain searchable. Check the notice's changes and related records so that a recent publication date does not lead you to count an old project twice. TED notice-view help.
Record the buyer, publication number and procedure identifier together. If two notices concern the same buyer, site and deliverable, compare their scope and lots before treating them as separate projects. A supplier may need to evaluate a particular lot even when a directory counts the overall project once.
Separate the deadline from the delivery date
A participation deadline, tender deadline, clarification date and contract end date answer different questions. Keep the name of the deadline beside its date. Preserve the original time zone before converting it for your own calendar.
When a source provides only a date, check the original documents for the time. Do not assume that it closes at midnight. SparkGuild keeps dates without a time and timezone uncertain from 00:00 UTC+14 on that date until 00:00 UTC-12 the following day; it does not archive them before the latest possible cutoff. A deadline that has not passed also does not establish that the procurement is unchanged or that your organization is eligible.
Read the qualification requirements before the technical brief
Use a short evidence table instead of a yes/no guess. Copy the requirement reference into your private worksheet and state whether you have the evidence. Useful questions include:
- Does the notice require an organization, a named professional qualification or a particular registration?
- Which relevant projects, staff, language skills or local delivery arrangements must be demonstrated?
- Does the scope require on-site work, named equipment or integration with an existing system?
- Which declarations, forms and supporting documents must accompany the response?
- What remains unclear and should be asked through the issuer's designated channel?
A directory summary can flag these issues; it cannot replace the complete documents. The TED entries in this collection were reviewed through the official Search API. Tender attachments were not reviewed. The API is intended for reuse of published notice data. TED Search API documentation.
Convert the scope into deliverables
For a software notice, separate licenses, configuration, migration, training, support and acceptance. For a design notice, separate concepts, production files, print quantities and revisions. For research, identify the population, method, sample or outputs actually specified. Avoid assuming that “digital” means remote or that one budget figure includes every option and expense.
A practical response decision is: proceed with evidence, ask a bounded question, or stop because a stated requirement cannot be met. Keep the reason in the worksheet. An attractive title is not enough to justify preparing a long proposal.
Copy this opportunity review worksheet
Original notice URL and publication number:
Issuing organization:
Procedure identifier and relevant lot:
Latest change checked on:
Required outcome and deliverables:
Place of performance and working language:
Current response stage:
Submission channel:
Deadline type, date, time and original time zone:
Qualifications and evidence:
- Requirement / evidence available / missing information
- Requirement / evidence available / missing information
Documents still to read:
Questions for the official clarification channel:
Decision: proceed / clarify / stop
Reason and next concrete step:
If you are commissioning your own work
Use an example to clarify your own outcome and acceptance checks. Publish a requirement that you own or are authorized to represent. An external notice does not become your task merely because you found it in a directory.
For your own software, design or research project, use the task brief template, then describe your request on SparkGuild. Responses to an external procurement must go through the channel specified in its original documents.
Browse institutional procurement summaries, or explore resources by topic.
Sources and scope
TED's notice-view help supports the explanation of corrections and related records. Its Search API documentation describes access to and reuse of published notices. Both were checked on 17 October 2026. The screening questions and worksheet are SparkGuild editorial material; the issuers and TED do not endorse SparkGuild.