Submit the right offer and retain proof

Submission is an operational task with its own failure modes. A well-written offer is not useful if the wrong version is sent, a required field is missing or the portal remains at the draft stage.

Common to all countries

Prepare the submission route early

Read the instructions before the final day. Confirm the account, authorised submitter, authentication, required signatures, file formats, size limits and fields to complete. Check whether technical and price information must be placed in separate sections.

The Scottish Government’s PCS-Tender guidance illustrates that a tender platform has its own access and response workflow. Other systems differ. Do not assume that registering on a notice website also gives you everything needed to submit through the designated platform.

Record the authoritative deadline with its date, time and time zone. Translate it into the team’s working calendar carefully, including any daylight-saving difference. Assign one submission owner and a backup who has the necessary access and understands which version is approved.

Work backwards from the official deadline

Set internal milestones with enough buffer for the size and complexity of the bid. A fictional Luma schedule might reserve two days before the deadline for the integrated review, the previous day for approval and file preparation, and several hours before the deadline for submission and confirmation. These are planning choices, not legally sufficient buffers or universal deadlines.

Checkpoint	What must be true before moving on
Content review	Every requirement has a complete, consistent response
Approval	The authorised internal decision-makers approve the actual final offer
File preparation	Names, formats, signatures and required fields match instructions
Submission	The required final action is completed in the designated system
Confirmation	Status and receipt are checked and retained

Where the platform offers a training area or validation function, use it as intended. Do not use a live final-submission button merely as a test without understanding its consequences and the rules on replacement.

Check the package, not just the prose

Open the final exported files. Check that tables are complete, attachments correspond to the right question, formulas and totals are correct and there are no tracked changes, drafting notes or accidental confidential material. Use the required templates and preserve the correct separation of price and technical content.

Ask a second person to verify the final package against the requirements matrix. Make the review specific: “price schedule row 8 agrees with the unit definition” is more useful than “looks fine”. If a late change is approved, update the package and its record together.

Worked example: uploaded is not submitted

Luma uploads its files and sees them in the portal. The status still says “draft”. The coordinator follows the instructions, completes the required final action and checks the confirmation identifying the submitted response. Only then does the team record the submission as completed.

Save the exact files submitted, the confirmation and any relevant portal messages in a controlled folder. A receipt establishes a submission record; it does not mean the buyer has found the offer compliant or selected it for award.

Country specific — what to verify

Check signature and authority requirements, accepted transmission channels, time-limit rules and procedures for technical incidents. Confirm whether and how a submitted response may be replaced or withdrawn, and what happens to earlier versions.

If a problem occurs, use the designated support and incident process promptly and keep time-stamped evidence. Do not assume that an email to a familiar contact, a screenshot of an error or a request for an extension makes a late response admissible. That depends on the applicable process and rules.

Put it into practice

Write a one-page submission runbook for your next bid. Include the official deadline, internal milestones, owner and backup, final checks, incident contact and the evidence to retain.

Self-check: someone using the runbook should know how to distinguish “files uploaded”, “submission completed” and “receipt verified”. After submitting, keep monitoring the authorised communication channel for the next stage; the opportunity does not end when the upload finishes.