Dendra
Private beta for NZ planning teams

Forward the brief.
Shape the draft.
Approve when ready.

Email Dendra the messy context. It returns a structured Google Doc, then keeps refining it as your planner replies with questions, corrections or new material.

Inbound

Subject

Fwd: Sample site, pre-assessment request

Client notes attached

Council letter included

Please identify planning pathway

Working draft

Pre-assessment, sample site

01

Planning pathway

02

Effects issues

03

Missing information

Awaiting planner reviewOpen in Docs →
Planner reply

“What changes if the activity status is discretionary?”

Dendra update

Consent pathway and effects section revised for review.

How it works

Email-first. Iterative by design.

Start with a forwarded brief, then keep refining the work through replies, comments and updated context.

  1. 01

    Forward the context

    Send the site details, client email, council letter, meeting notes or draft fragments to Dendra.

  2. 02

    Dendra prepares the draft

    Dendra reads the context, organises the work and prepares a structured Google Doc for planner review.

  3. 03

    Ask, correct, add context

    Reply with follow-up questions, missing information, council feedback or planner corrections. Dendra uses the new context to revise the working draft.

  4. 04

    Planner approves

    The planner reviews the final version, edits where needed and decides what, if anything, is sent.

What it produces

Working documents your planners can keep refining.

Every output is delivered as a Google Doc, ready for questions, corrections, review and approval.

  • Pre-assessments

    A structured first view of the planning issues, missing information and likely next steps, ready to refine as more context arrives.

  • Planner briefs

    A concise summary of the file, the request and the decisions the planner needs to make, updated as the thread develops.

  • Response letters

    Draft response text for client or council correspondence, prepared for planner review and revision.

  • Options memos

    A clear comparison of possible planning pathways, with space for the planner to test and refine the recommendation.

  • Draft consent-report sections

    Structured report sections that help planners move from context to reviewable prose, then improve the wording through follow-up prompts.

  • Cover letters

    Clean supporting letters for planning workflows, ready for human editing, iteration and approval.

Trust boundaries

What Dendra does not do.

Saying what we are not is part of building trust in a category that often overclaims.

Dendra can revise drafts from your replies, but the planner remains responsible for the final judgement, wording and external send.

  • It does not send for you

    Dendra does not email clients or councils. The planner decides what leaves the firm.

  • It does not replace judgement

    Dendra drafts the document. The planner owns the professional advice.

  • It does not manage your projects

    Dendra is not a CRM, Kanban board or council portal.

  • It does not lodge applications

    Council submission and lodgement workflows remain with the planner.

Private beta

By referral. Human-reviewed onboarding.

Dendra is being calibrated with a small number of sole-trader and small-firm planning teams. Access is by referral, onboarding is human-reviewed, and every output stays inside planner review.

Built by ShiftCurve

Dendra is a ShiftCurve product built with practising NZ planners. We build practical workflow tools where professional judgement stays in control and software works inside the tools teams already use.

ShiftCurve Limited, Auckland, New Zealand.

Get in touch

Tell us about your firm.

One short form. A real person reads every submission.

We will only use these details to respond to your enquiry and manage private-beta access.