What does the portal acknowledgement show?
Queensland QTenders' response-document guidance describes an email acknowledgement for each uploaded document and a receipt listing uploaded files and failed uploads. Those features are specific to that platform. Check the actual portal instructions and evidence available for your tender rather than assuming every system produces the same receipt.
Tender Glossary is independent and is not affiliated with QTenders. This guide is an original evidence worksheet, not legal advice or an interpretation of a buyer's submission rules.
Which entries should be reconciled?
Prepare the approved manifest before uploading. Use the final deliverable names and revisions, not working filenames from an earlier review. Keep the receipt and submitted files in the authorised records location.
| Manifest field | Portal evidence | Decision to record |
|---|---|---|
| Required item | Corresponding uploaded filename | Present, missing or unresolved |
| Approved version | Uploaded file identity and available revision evidence | Matches the approved submission |
| Upload result | Success or failure as reported | Failed items remain visible |
| Replacement attempt | Earlier file and replacement outcome | Which version the portal actually received |
| Submission reference | Receipt identifier and reported time | Retained under the correct tender |
| Issue owner | Missing item or mismatch reference | Authorised response under the tender rules |
| Final record | Receipt, approved manifest and submitted copies | Evidence can be reviewed together |
What if a replacement upload fails?
Illustrative example. A fictional manifest approves Technical-Response-v3.pdf. The portal receipt records Technical-Response-v2.pdf and shows a failed attempt to upload v3. The register must show the mismatch. An internal approval of v3 does not establish that the buyer received v3.
Preserve both outcomes and notify the authorised submission owner through the project process. Follow the portal and tender instructions for any permitted remedy. Do not infer a right to resubmit after closing or change the receipt record to match the intended submission.
A successful upload with a similar filename can still require checking the actual file identity. If the portal does not expose enough evidence, record that limitation and retain the submitted copy and available receipt rather than claiming certainty.
How should the final submission evidence be closed?
Compare each required item against the receipt and record unresolved differences. Keep a document-level result even if the portal also displays a general submission confirmation. The general message may not answer which revision was uploaded.
Retain the issued tender instructions, approved manifest, receipt and actual files together. Keep personal or confidential content within the authorised audience; a receipt reference can be shared without attaching the full tender unnecessarily.
Do not treat a receipt as technical acceptance, eligibility approval or an award notice. Those are separate buyer decisions. The reconciliation establishes the evidence available for the submission event and the precise questions that remain open.
Common questions
What else should the bid team know?
Does an acknowledgement prove the bid is compliant?
No. It reports receipt under the portal process; compliance and evaluation are separate decisions.
Can the approved filename replace the receipt filename in the record?
No. Preserve the actual portal evidence and show any mismatch.
What if the receipt does not identify a revision?
Retain the submitted copy and available evidence, and record the limitation honestly.
Primary sources
- Submitting response documentsQueensland QTenders