Tender portal receipt vs a timestamp: what each one shows

Tender portal receipt vs a timestamp at a glance

What portals and buyers say

Rules differ by buyer, so read the tender documents. These public examples show the pattern.

• The City of Sydney’s expression of interest conditions say respondents "will receive a Successful Submission Receipt timed and dated upon completion" of an online submission, and that submissions received after the closing date and time will not be considered unless the regulation provides otherwise (City of Sydney conditions). Its tender page says late tenders "won’t be considered, even if they’re lodged only a few minutes late" except in circumstances set out in law (City of Sydney: submit a tender).
• NSW Government procurement guidance tells buyers they must not accept a late submission unless their own action or omission caused the lateness, or they are sure no other bidder will be disadvantaged (NSW buy guidance).

The practical point is the one every bid manager knows: leave time to lodge, keep the receipt, and don’t treat a record created elsewhere as a substitute for lodging.

What a timestamp adds

• A record of the set before lodging. If you fingerprint the final files before you start uploading to the portal, you can later show that the set you hold matches the set that existed at that time.
• A record of the concept stage. Competition and tender work often begins weeks earlier. A timestamp on early concept files shows what existed then. See design competition entries.
• A record outside the portal. Portals move closed tenders to an archive after a period (the NSW eTendering guide describes closed tenders being viewable for 30 days before they are archived), and what suppliers can see later varies. Your certificate and files are yours to keep.
• A way to match your copy to what you lodged. Download or export the exact package you lodged, fingerprint it, and keep it with the portal receipt.

What a timestamp does not do

• It does not make a late tender on time, and it does not replace the receipt.
• It does not show the buyer received your files. Only the portal’s own records show that.
• It does not show who produced the content or that your design is original.
• It does not mean a panel must accept it as evidence of anything. Ask the buyer if you plan to rely on it.

Competitions with anonymity rules

Some design competitions require anonymous entries. A TimeBinder certificate carries your account details, so don’t include it in an anonymous entry unless the rules allow it. Keep it in your own records, and check the competition brief on what you may add or reveal.

A simple routine for a submission

1. Finish and freeze the submission set. Save the exact PDFs, models and design statement you plan to lodge.
2. Make a TimeBind of up to 10 files. Use ASAP if the lodgement date matters and you want its own transaction, sent straight away.
3. Lodge through the portal or the route the buyer requires. Allow time before the deadline.
4. Save the receipt, the certificate and a copy of the lodged package together.

When a timestamp isn’t the right tool

• The buyer requires a specific format of proof. Follow the tender documents.
• You need to show the buyer received something. Use the portal receipt or the buyer’s confirmation.
• You need a witnessed or certified copy. See blockchain timestamp vs notary.

Why a second record helps if a bid is questioned

A portal receipt confirms receipt but is held by the portal. A TimeBind is a separate, checkable record of the exact files before you lodged them. If a submission is later questioned, or someone presents an edited copy, you can compare what you hold with the certificate. It supports your evidence and does not guarantee how a panel or court will treat it.

General information, not legal advice. A TimeBind shows that this exact file existed no later than the recorded time and still matches its fingerprint. It does not show authorship, ownership, copyright status or how any court, tribunal, client or insurer will treat it.