Guidelines for honest project records

Why records fail after handover

A landscape project is judged in public long after the design team has moved on. Maintenance crews, asset managers, researchers, regulators, and community reviewers inherit drawings, models, and spreadsheets that often look authoritative while the underlying claims remain implicit. “Native planting,” “climate resilient,” “sustainable,” “culturally appropriate” — these phrases travel well in marketing copy and poorly in archival metadata unless someone has encoded what was meant, what evidence supports it, and what must stay restricted.

The failure is structural, not moral. Practices in London, Singapore, Toronto, and Melbourne face the same handover gap: BIM objects without taxon identifiers, sustainability narratives without links to assessment methods, synthetic vegetation without lineage, and cultural references that cannot be published openly but still need to be traceable inside a project archive. An honest record is one that states its claims precisely enough to be reviewed — and modest enough to admit where evidence ends and professional judgement begins.

International clients increasingly ask for digital asset registers that survive contractor changes and software migrations. EU taxonomy-aligned reporting, corporate nature-related disclosures, and municipal digital-twin programmes all converge on the same demand: show your work in a form someone else can verify. Landscape teams that treat metadata as an afterthought discover, at handover, that their most defensible design decisions are the least retrievable.

Encode claims, not slogans

TLA-185 does not replace professional judgement, client sign-off, regulatory audit, or community protocol. It supplies a published field dictionary so teams can align on what to disclose and how to structure it in an interchange bundle. Australian modules in the current profile reflect where the standard was first exercised; international adopters map the same structural slots to local taxonomies, climate datasets, and procurement rules through published crosswalks rather than improvising parallel vocabularies.

Start with botanical identity: stable taxon identifiers, growth form, and planting role — not marketing common names alone. Pair climate context with documented screening methodology and banded estimates rather than single-point predictions that read as guarantees. Sustainability fields should carry evidence links or explicit “not assessed” states, not empty checkboxes that imply certification. Synthetic assets need lineage metadata — model source, training or capture method, revision date — distinct from photographic or surveyed specimens.

• Replace generic labels with dictionary-backed field values wherever a claim will be reviewed after handover
• Attach evidence URIs, report IDs, or internal reference codes to sustainability and performance fields
• Use sensitivity classes so restricted cultural detail routes to appropriate repositories, not open file shares
• Document synthetic versus surveyed assets explicitly; do not let render-ready geometry imply botanical certainty

Cultural protocol and restricted metadata

Landscape work intersects with Indigenous and local knowledge systems worldwide. Not every field belongs in a public repository — yet projects still need internal traceability. Clear records distinguish what may be cited openly from what requires restricted handling, and keep restricted detail out of generic open labels.

Practices should treat cultural metadata as co-authored where protocol requires it: who approved a representation, which sensitivity class applies, and where the authoritative record lives. The Foundation publishes structural slots for these disclosures; it does not substitute for Traditional Owner organisations, cultural advisors, or local consent processes. These guidelines are published for consultation — teams should align with both the open specification and the legal and cultural requirements of each jurisdiction.

A minimum bundle before you call a record “complete”

Before declaring a project archive complete for handover, ask whether an independent reviewer — another practice, a university studio, a client asset team, a regulator — could answer basic questions from the bundle alone. Which species or communities were specified, with what identifiers? What climate and site context informed selection? Which sustainability claims were made, with what evidence? Which assets are synthetic, and what is their revision history? Which fields are intentionally withheld, and under what protocol?

Perfection is not the bar; retrievable honesty is. A bundle that marks uncertainty clearly is more valuable than one that implies certainty through polished graphics. Draft Foundation awards discussion explores recognising archival diligence alongside design excellence — the same questions already belong as shared professional expectation. Publish what you can cite; restrict what you must; document the difference.

Working with vendors without surrendering the archive

Honest records are compatible with commercial tooling. The Foundation’s responsibility split is explicit: open structural definitions and conformance rules remain public; high-fidelity datasets, automation, and certified implementation tooling may remain licensed. A practice can use proprietary inventories while still exporting dictionary-aligned interchange bundles — provided the team maps product-specific labels to published field slots and preserves evidence outside the vendor’s closed export formats where necessary.

Procurement teams should ask vendors how conformance is validated, not merely whether a checkbox exists. Can project metadata be exported without losing taxon identifiers? Can sensitivity classes be preserved through round-trip exchange? Can synthetic lineage survive a platform migration? These questions belong in international briefs alongside fee and schedule. They protect the client’s long-term archive and the profession’s ability to compare projects honestly across markets.

Next Steps

Open Foundation materials for one studio deliverable are on the adoption guide. A short Archive page for practices is also available.