Why is removing names only one check?
The Australian Information Commissioner's de-identification guidance explains that removing direct identifiers may be insufficient: combinations of other details and the release context can permit identification. That privacy guidance supports a careful identification review; it does not establish permission to disclose a company's confidential project information.
Check the applicable confidentiality commitments and authorised release process separately. This guide is a writing workflow, not legal advice. Returnables Agency does not disclose Elora Grid client, project, person, site or job-number information.
Sources: Office of the Australian Information Commissioner: De-identification and the Privacy Act
What belongs in the permission register?
Keep restricted evidence in its approved location. The widely shared register should contain references and statuses, not copies of private records. A writer can substantiate a statement and still lack permission to publish it.
| Check | Record | Release condition |
|---|---|---|
| Claim support | Exact statement and controlled evidence reference | Evidence owner confirms the statement is supported |
| Permitted purpose | Actual approval or governing restriction | Use is permitted for this tender audience |
| Identification review | Names, locations, combinations and unique details | Authorised reviewer accepts the disclosure version |
| Approved copy | Document revision and approval reference | The submitted text matches the reviewed version |
| Attachments | Each image, extract or supporting file | Permission and redaction apply to the actual files |
| Change trigger | New audience, revised claim or new attachment | Review is reopened when the approved scope changes |
How can a redacted paragraph still be identifiable?
Illustrative example. A fictional case study removes the customer name but retains a precise location, an unusual installation description and a distinctive completion date. Those details may identify the project to the tender audience. The reviewer records the combination and requests an authorised rewrite or omission.
Do not replace restricted facts with invented project achievements. If a supported claim cannot be disclosed, leave it out or obtain an approved alternative evidence route. Label any synthetic example clearly and never present it as delivered client work.
Review attachments as carefully as the prose. A drawing title block, photograph or filename can reintroduce details removed from the paragraph. Confirm the actual submission files against the approved disclosure version.
How should the final returnable be controlled?
Keep the evidence status, release permission and copy approval distinct in the tender evidence map. A single green status can conceal whether one of those decisions remains open. Identify the authorised owner for each pending check.
Before submission, compare the final paragraph and attachments with the approved version. If a late edit adds a number, location or project detail, route the affected copy back through the relevant review. Do not assume the earlier approval covers a materially different statement.
Retain the submitted version and approval references within the authorised records process. The register prepares a credible, controlled returnable; it does not promise an evaluation score or transfer confidentiality decisions to the writer.
Common questions
What else should the bid team know?
Does anonymising a client name grant permission?
No. Permission and identification risk are separate checks.
Can an illustrative example replace a delivered case study?
Only when clearly labelled and appropriate to the question. It must not be presented as actual client work.
Should evidence files be pasted into a shared register?
No. Use controlled references and the authorised access process.
Primary sources
- De-identification and the Privacy ActOffice of the Australian Information Commissioner