1 · Survey to Twigged
For exact set-out, first select one surveyed edge from the garden lower-left datum towards project +X. Then select a named bed Group or Component and send it. In a hurry, skip the datum and Twigged will offer quick alignment from the first bed.
The brief is carried into this bed’s Twigged Planner workflow; it does not trigger paid AI work until you review and choose to generate.
Make each bed its own named Group or Component; identity follows that container. Name or tag walls, buildings, hedges and trees to improve context classification. Twigged sends the bed and up to 200 prioritised visible object bounds, not the whole model. Verify the red +X marker against the survey before issuing work.
2 · Reviewed design
The Twigged project group keeps its survey alignment. Updates reconcile stable plants and objects in place and flag competing edits for review.
3 · Refine safely
Select a component already in the model, map it to a botanical name or Twigged identity, then send supported moves and size changes back for review.
4 · Issue and present
Create a counted plant key in the model, save a revision-stamped CSV schedule, or switch Twigged’s lightweight symbols between design colour and technical monochrome. Issue is blocked if reviews, unsent edits, alignment or plant codes are unresolved. Your own mapped components are never recoloured.
JSON files are versioned and reviewable. A saved bed file can resume a transfer without losing its survey registration.