Delivery anatomy

How the parts of a TwinzWorks delivery work together.

Method demonstration — not a client case Illustrative content — no client data

Depending on scope, one reviewed project becomes coordinated books, plans, schedules and spatial files. This page walks through that structure so you know what arrives and how the pieces relate — before any engagement.

01

Project question and input record

Every delivery starts from the decision the project needs to support. Each input you provide is recorded against its purpose, so what can be answered — and what cannot — stays visible from day one.

02

Source and accuracy level

Each source is labelled before it is used — client-provided, public context, screened, modeled or measured. Labels are not interchangeable, and nothing upgrades silently.

03

What the books look like inside

The visual brief reads as opportunities, constraints and next checks; the concept book carries the landscape thesis, interventions and planting character. The spreads below are illustrative anatomies of those two book families.

Illustrative page anatomy of a T1 Site Intelligence Brief — Inside a T1 Site Intelligence Brief — illustrative deliverable anatomy.

Illustrative two-book set of a T2 Landscape Concept package — The two books of a T2 Landscape Concept — illustrative deliverable anatomy.

04

How plans, schedules and spatial files relate

The plan carries placement, the XLSX schedule keeps plant, water and quantity logic usable, and the GeoPackage keeps the spatial evidence usable outside the PDF — three views of one reviewed decision.

Illustrative relation of plan, schedule and spatial file around one reviewed decision — Illustrative flow — no client data

05

Named review and revision

A named human review releases every design-facing output. Corrections are plain-language requests, and revisions supersede rather than overwrite, so the history stays traceable.

Demonstration only — no client data Action needed

Type of request

Replace or update a file

What is needed

Please upload the issued scaled base plan with a visible revision date. Visual direction can continue, but scaled placement remains unavailable.

In the live portal, this sends the correction request.

Demonstration only — no client data Current visible

Revision 03Current

Minor layout adjustments after review.
Revision 02Superseded

Planting character and path alignment updated.
Revision 01Superseded

Initial private concept draft.

06

Private review room

Over an expiring private link you comment on pages and figures, then approve or request a revision. Nothing is released automatically.

Demonstration only — no client data 1 open comment

“The revised path hierarchy is clear. Please retain the planting buffer before the next issue.”

Page 08 · Figure 03Demo comment

In the live portal: Approve or Request a revision.

07

Final package anatomy

The delivery lists books, plans, schedules, spatial files and the source/method/QA record with their review states — a controlled, labelled handoff, not a file drop.

Demonstration only — no client data 3 ready · 2 in review

Final concept book Reviewed PDF · demo Ready
Concept plan Illustrative placement · demo Ready
Plant and water schedule Technical review state In review
Evidence GeoPackage Source and method register included Ready
QA and limitation register Named review pending In review

08

What this does not claim

A delivery is not a survey, not a permit approval, not a contractor bid and not a built result. Proposed visuals stay labelled as proposed, and every number keeps its source, scale and date.

Coming after acceptance

When the first approved, publication-cleared work exists, a real example will appear here through the same slot system — with its rights, claims and review records intact. Until then, everything on this page stays clearly illustrative.