Choosing an Org Chart Tool for HR: What NZ Teams Actually Need

Most org chart tools are built for presentational charts, not HR workflows. This guide covers what to look for when choosing an org chart tool for HR use — especially in a New Zealand restructure context where the chart becomes a legal document.

If you search for "org chart tool" you will find dozens of options. Lucidchart. Miro. OrgWeaver. Microsoft Visio. Draw.io. Most of them will let you build a presentable hierarchical diagram in under an hour.

None of them were built for HR.

That matters if you are using an org chart as part of a restructure process — because in that context, the chart is not decoration. It is a working document that will be referenced in consultation proposals, decision records, and if things go badly wrong, personal grievance proceedings. Using the wrong tool for that job creates real risk.

This guide covers what an org chart tool actually needs to do for HR use — with specific reference to the NZ restructure context — and how to evaluate the options available to you.

The Difference Between a Diagramming Tool and an HR Org Chart Tool

Most of the tools you will find are diagramming tools. They let you place boxes, draw lines between them, and label everything. They export to PNG or PDF. They are built for slide decks and annual reports.

An HR org chart tool is something different. It needs to:

  • Represent positions, not just people — A diagramming tool puts a name in a box. An HR tool tracks positions (the role) separately from incumbents (the person). Positions persist when employees leave or are made redundant. This distinction is critical during a restructure.
  • Track role status — Each position should be flagged as filled, vacant, proposed, or at-risk. This is how you distinguish your current state from your proposed future state during a consultation process.
  • Support multiple scenarios — You need to be able to model what the organisation looks like before and after without destroying your current chart. This means either version control, scenario branching, or a "proposed state" overlay.
  • Export something useful to HR, not just design — The output needs to be a document you can include in a consultation proposal, not just a diagram you attach to a board presentation. That means structured data export (roles, reporting lines, status) not just image files.
  • Maintain an audit trail — If an employee challenges the restructure process, you need to be able to show what the chart looked like at a specific point in time and who changed what. A diagramming tool does not log edits.
  • Handle teams and matrix reporting — Modern organisations do not have clean hierarchies. Employees report to functional managers and project leads. An HR org chart tool needs to represent both solid-line and dotted-line reporting relationships without becoming unreadable.
  • Why NZ Restructures Require More

    In New Zealand, an org chart produced during a restructure carries more weight than it does in most jurisdictions. Here is why.

    The Employment Relations Act 2000 requires specificity in proposals. When you issue a consultation proposal under section 4 of the ERA 2000, you must identify the specific roles at risk and explain the proposed new structure. A vague "we are reorganising" is not sufficient. The chart has to clearly show which roles exist now, which roles will exist in the proposed structure, and which are being disestablished.

    The chart becomes an exhibit. If a personal grievance is lodged, the Employment Relations Authority may request the consultation documents — including any org charts provided to employees. A chart that cannot be exported cleanly, or that has been modified after the consultation period without a record of the change, is a liability.

    Redundancy selection criteria are linked to the chart. If multiple roles are at risk and the employer is selecting who is made redundant, the selection process typically references the org chart. Who is in scope? Who is being assessed against whom? The tool needs to make this explicit, not leave it implicit in a hand-drawn box.

    Evaluating Org Chart Tools for HR Use: A Criteria Framework

    1. Position-Centric Data Model

    Can the tool represent a position independently of an incumbent? This is the single most important structural question. If a role is vacant in your current state, can the tool show that vacancy? If an employee leaves mid-restructure, does the position persist?

    Tools that only let you put a person's name in a box fail this test. You end up deleting roles when people leave and recreating them, which destroys your change history.

    2. Role Status Tracking

    Can you tag individual positions with status flags — filled, vacant, proposed, at risk, disestablished? This lets you use a single chart to communicate the restructure proposal: existing filled roles remain as-is, proposed new roles are marked "proposed", and roles being removed are marked "at risk" or "disestablished".

    Without this, you need two separate charts (current state and proposed state) which creates version control problems and increases the chance of presenting inconsistent information during consultation.

    3. Scenario Modelling

    Can you create a copy of the current org chart and modify it to represent the proposed future state, without altering the source-of-truth current state? This is essential during consultation. The current-state chart is what you show employees now. The proposed-state chart is what you are consulting on.

    Some tools handle this with version branching. Others let you create a separate "sandbox" scenario. Whatever the mechanism, you need the two states to be distinct and independently exportable.

    4. Export Quality

    What does the export actually look like? PDF and PNG are the minimum. But a well-designed HR org chart tool should also export structured data — a list of positions, their status, their incumbent (if any), their reporting relationships — that can be used to populate a consultation proposal or a redundancy register.

    Check: can you export at A4 size at print resolution? Can you export a specific team or sub-tree, not just the entire organisation? These seem like minor details until you are trying to prepare consultation documents at 11pm.

    5. Access Control

    Who can view and edit the chart? During a restructure, you typically want HR and senior leadership to have edit access, but the chart may need to be shared in read-only form with affected employees during consultation.

    Also consider: can you share a snapshot (the chart as it was on a specific date) rather than a live link? A live link will show the chart as it is today — including changes made after consultation has closed — which can complicate the evidentiary record.

    6. Audit Trail and Change History

    Can you see who changed what and when? This matters both for internal governance and for external scrutiny. If the chart was modified after you issued the consultation proposal, you need to be able to demonstrate that the version provided to employees matched the version in your records.

    A basic "last edited by" timestamp is not sufficient. You want a change log that records each edit with a timestamp and user ID.

    7. Integration with the Broader Restructure Workflow

    Does the org chart tool connect to the rest of your restructure process? The chart is one input into a broader workflow that includes issuing proposals, managing consultation meetings, recording feedback, and generating decision letters.

    If the org chart sits in a separate tool from everything else, you end up manually transcribing role names and structural information from one system to another — which introduces errors and creates alignment problems.

    How Restructured Approaches the Org Chart Problem

    Restructured is built as an integrated restructure management platform, not a standalone diagramming tool. The org chart in Restructured is a live HR data layer — positions, incumbents, status flags, reporting relationships — not a drawing.

    Key org chart features:

    Position-centric model. Every node in the chart represents a position. You can create a vacant position, assign an incumbent to it, or mark it as proposed or at-risk. The position persists independently of the person in it.

    Status flags. Positions are tagged filled, vacant, proposed, or at-risk. The current and proposed states are visible in a single chart view, with visual differentiation between statuses.

    Team grouping. Positions can be grouped into teams or departments. Cross-team reporting lines are visually differentiated from intra-team lines — solid lines for direct reports, dotted lines for matrix/functional reporting, and orange dashed lines for cross-department connections.

    Scenario management. The proposed state is modelled inside the same restructure workflow as the current state. There is no separate tool or file to manage.

    Export. The chart exports to PDF and PNG at print quality. Each node's data (position title, department, status, incumbent) is available for use in consultation document templates.

    Audit trail. All changes are timestamped and attributed to a user. The chart state at any point in the consultation process can be reconstructed from the change history.

    Integrated workflow. The org chart is connected to the proposal builder, consultation tracker, and decision letter generator. Role names and structural information flow through the platform without manual re-entry.

    What Diagramming Tools Cannot Do (and When That Matters)

    To be fair: if you are building an annual report org chart for the board, a diagramming tool is fine. If you are using the chart only for internal planning and no one will scrutinise it later, the flexibility and lower cost of a tool like Lucidchart or Miro is attractive.

    The diagramming tool starts to break down when:

  • The chart is included in a legal consultation document
  • You need to track which roles are at risk vs proposed
  • Multiple people are editing the chart simultaneously
  • You need to export structured data, not just images
  • The chart will be referenced later in a grievance process
  • At that point, the cost of using the wrong tool is not just time — it is legal risk and process integrity.

    Checklist: Questions to Ask When Evaluating Any Org Chart Tool for HR Use

    Use this when assessing any org chart product for HR or restructure use:

  • Does it represent positions separately from people?
  • Can I tag individual roles with status flags (filled, vacant, proposed, at-risk)?
  • Can I model a proposed future state without modifying the current-state chart?
  • What export formats are supported? Can I export at print resolution?
  • Can I share a read-only snapshot rather than a live link?
  • Is there a change log with timestamps and user attribution?
  • Can I export structured role data (not just an image)?
  • Does it integrate with consultation or HR workflow tooling?
  • How does it handle dotted-line or cross-team reporting relationships?
  • What is the per-user pricing model? Does it work for a team of 3–5 HR staff?
  • The answers to these questions will quickly separate tools built for HR from tools built for slide decks.


    *Restructured is a New Zealand-based restructure management platform. The org chart is one component of an integrated workflow covering proposals, consultation, decision letters, and compliance tracking under the Employment Relations Act 2000. See pricing or explore the features.*