Your next contract starts with a stronger bid. Prepare it with TenderProSA.
Illustration of a checked tender folder, review checklist and calculator
Tender preparation

Before you submit: a final tender review your team can repeat

By TenderProSA•14 November 2026•7 min read

Give your team a clear way to check the finished bid, resolve the last open items and hand over the right version for submission.

The documents are assembled. The estimator has finished the pricing. Someone is waiting for permission to submit. This is where a clear final review earns its place: it turns “I think everything is there” into a record of what was checked, what still needs attention and who approved the handover.

This guide starts after the bid pack has been compiled. It is for the person coordinating the final check, whether you work with a bid team or run the business yourself. Use it with the actual invitation, returnables schedule and latest addenda. Those documents determine the requirements for your bid.

  1. 1. Freeze the version
  2. 2. Trace the requirements
  3. 3. Reconcile the details
  4. 4. Check the delivery route
  5. 5. Approve and retain proof

1. Freeze the version being reviewed

Create a clearly named review copy and give it a version number. For example, Bid-Example-Review-v03 tells the team more than three folders called “final”. Keep the working files separately so a reviewer can tell which documents belong to the proposed submission.

Record the invitation version, any addenda received, the date and time you last checked the issuing authority’s update channel, and the closing instructions. Open the exported PDFs and other required files, rather than relying on the editable originals. Look for cut-off tables, missing attachments, unreadable scans and pages that were lost during export.

Nominate one person to control changes during review. If an updated quote changes the pricing, they should identify which totals, schedules and approvals need checking again. Version control can be a shared folder and a short log; it does not require a new system.

2. Match each requirement to evidence in the finished pack

Work down the buyer’s returnables schedule and submission instructions. For every applicable requirement, record the exact file and page, the reviewer and the result. A tick should mean that somebody opened the evidence and checked it against the instruction.

Use three results: checked, action needed, or not applicable, with a reason. If the instructions are unclear, record the question and use the buyer’s stated clarification process. Do not mark an unresolved question as checked.

A published example shows why this matters. GCIS’s RFQ 012 2026/2027, which closed on 6 November 2026, required supporting videos on a readable USB and says files that cannot be opened will be treated as not submitted. A checklist that only asks whether the USB is present would miss that requirement. Source: GCIS RFQ, section 3.2.1.1.5, page 3.

Apply that principle to your own bid: check that each required item is usable and meets its stated conditions. Do not copy the USB requirement into an unrelated tender.

3. Cross-check the details that appear in more than one place

Compare the pricing schedule with the detailed estimate and the offer being submitted. Check quantities, units, line calculations, carried totals, discounts and the tax treatment you have used. Confirm that the same scope and approved assumptions run through the technical response and pricing. Follow the tender’s instructions for blanks, alternatives and corrections.

Then check the bidder’s name and reference number, the dates, and the places requiring a signature, initials or evidence of signing authority. Look at the actual instructions for each form. A signature requirement in one document does not establish a rule for every other document.

Where practical, ask someone other than the preparer to review the numbers and returnables. In a one-person business, make a separate pass through the exported pack using the requirement list. Record that it was a self-review; do not describe it as an independent check.

A final review that catches a version mismatch

Illustrative example, not a customer case: an estimator updates a material allowance in the spreadsheet, but the coordinator’s exported pricing schedule still contains the previous total. Both files open correctly and every required document is present.

The reviewer compares the submitted schedule with the approved estimate and records the mismatch as an open action. The estimator reconciles the figures, the coordinator exports a new version, and the reviewer checks the affected totals again. Approval refers to the new version, so the person submitting knows which pack to use.

4. Check the submission route before the deadline

Copy the submission method, destination, closing date and time directly from the current instructions. Do not assume that the website where you found the opportunity is also where you submit it.

For a physical submission, verify the correct delivery location, tender box where specified, envelope labels, packaging and required copies. Give the person delivering the bid those instructions and the exact approved pack. Set an internal handover time that leaves room for the journey and foreseeable access delays.

For an electronic submission, confirm account access, the correct opportunity, the required fields and the specified file formats or size limits. Review how the system distinguishes a saved draft from a completed submission. Check the actual attachments before taking the final submission action.

GTAC’s vendor portal advises bidders to start well ahead of closing and save progress because sessions or connections can be interrupted. Its instructions also require the account to be linked to the correct supplier profile for an invited tender. These are GTAC-specific instructions; use the guidance for the system your buyer has selected. Source: GTAC vendor portal bidder notice.

5. Make the handover decision explicit

Finish the review with one of two decisions: ready for submission or hold for a named action. Every open action needs an owner and an internal resolution time. The person authorised within your business to release the bid should see the outstanding issues before deciding.

Keep internal approval separate from the buyer’s submission confirmation. Your signoff proves which version your team approved; it does not prove that the buyer received it or that the bid meets every evaluation condition.

After submission, retain the submitted pack and the confirmation available through the specified process. For an electronic submission, that may be a reference number, confirmation screen or email. For a physical delivery, keep any official acknowledgement provided and your delivery record. A courier tracking entry alone may not establish that the pack reached the required tender box.

A reusable final-review and handover record

Copy this structure into your bid folder. Expand it into one row per returnable where needed. The blank fields are for your team to complete; this is an internal working record, not a replacement for the buyer’s forms.

RecordWhat to captureDecision or evidence
Bid and versionTender reference, bidder, pack version and file locationExact copy reviewed
InstructionsInvitation, addenda and update check timeSource and section references
ReturnablesRequirement → file/page → reviewerChecked / action needed / not applicable with reason
Figures and scopeEstimate, pricing schedule and proposal cross-checkMismatches resolved and rechecked
Signatures and filesRequired signing authority, signatures, dates and file-opening checksEvidence and reviewer
DeliveryChannel, destination, closing time and submission ownerAccess and handover confirmed
Open actionsIssue, owner, internal deadline and affected versionResolution and recheck
Release decisionReady / hold, approver, date and timeApproved submission version
Submission proofSubmitter, actual submission time and reference where availableConfirmation and pack stored together

Download the plain-text review record

Make the next submission easier to hand over

Start with one upcoming tender. Use the record to make the final version, open actions and submission owner visible to the team. Keep the method that helps you review clearly, whether that is a shared folder, spreadsheet or dedicated bid workspace.

If you want to bring your preparation into one workspace, see how TenderProSA supports bid preparation. Use the review record above to keep the final decision with your team. The aim is a prepared team and a checked submission, with less last-minute uncertainty.

TenderProSA

TenderProSA editorial team

Practical guides to tender selection, bid preparation and submission for South African businesses.

Published: 14 November 2026•7 min read•LinkedIn