Org Chart Best Practices for NZ HR Teams

An organisational chart is much more than a visual aid. For HR teams, it is a working document that underpins restructure planning, redundancy risk assessment, compliance documentation, and workforce planning. Yet most NZ HR teams manage their org charts in tools that were not designed for HR — generic diagram software, spreadsheets, or slide decks that cannot represent the nuance of real employment relationships.

This guide covers the best practices for building and maintaining org charts that serve NZ HR teams well.

Why Generic Org Chart Tools Fall Short for HR

Most org chart tools are built for IT or business architecture. They represent reporting lines as simple boxes and arrows. For HR purposes, this is insufficient because:

Not all employment relationships are the same. A contractor looks the same as a permanent employee in a generic org chart. A 0.5 FTE part-time role looks the same as a full-time role. A fixed-term role looks the same as a permanent one.

Vacant positions are invisible. Generic tools represent people. HR needs to represent *positions* — including vacant ones — because a restructure may eliminate a role whether or not it is currently filled.

Matrix and dotted-line reporting is common. Many NZ organisations have functional reporting (to a business unit head) as well as operational reporting (to a project or site manager). Generic org charts cannot represent this clearly.

PII management matters. When sharing an org chart with external consultants, employment lawyers, or the board, you may need a version that shows roles without names. Generic tools require you to manually create a second version.

The Five Layers of an HR-Grade Org Chart

A well-designed org chart for HR purposes should capture five layers of information:

1. Position (not person)

The primary unit in an HR org chart is the *position* (or role), not the person. Every position should have:

A position title

A department or team

A reporting relationship (who the role reports to)

An employment status (permanent, fixed-term, casual, contractor)

A full-time equivalent (FTE) if not full-time

This means that if Jane is in the position "Marketing Manager," the position exists and appears in the chart regardless of whether Jane is still there. If Jane leaves, the position becomes *vacant* — it does not disappear.

2. Employment type

Different employment types have different legal and operational implications under NZ employment law. At minimum, your org chart should distinguish:

Permanent full-time — ongoing employment, ERA 2000 fully applies

Permanent part-time — ongoing employment, prorated entitlements, ERA 2000 fully applies

Fixed-term — specific end date or task, section 66 ERA 2000 requirements

Casual — no guaranteed hours, specific ERA 2000 protections

Contractor — not an employee for ERA 2000 purposes, but genuine employment tests may apply (section 6 ERA 2000)

In Restructured, each of these employment types is visually distinguished: contractors get a dashed border, part-time roles show an FTE badge, and fixed-term roles are flagged for review.

3. Reporting relationships

Capture both primary and secondary reporting:

Primary (solid-line) report — the main reporting relationship for performance management

Dotted-line (matrix) report — functional or project-based reporting to a second manager

Showing both types of reporting prevents the common mistake of restructuring a person's primary reporting relationship without considering the impact on their functional/matrix role.

4. Vacancy status

Every position should have a clear vacancy status:

Filled — an employee is currently in the role

Vacant — the position exists but is unfilled (either actively being recruited or temporarily vacant)

New — a position being created in a proposed restructure (not yet existing)

To be disestablished — a position being eliminated in a proposed restructure

Vacancy status is critical for restructure planning because the ERA 2000 does not require you to consult an empty position in the same way as a filled one — but you should still consider whether the vacancy represents a redeployment opportunity.

5. Department / team groupings

Grouping positions into departments allows you to:

Visualise team boundaries and spans of control

Identify cross-functional roles and dependencies

Calculate FTE totals by department for workforce planning

Support restructure scoping (restricting a restructure to one department vs. organisation-wide)

Maintaining Your Org Chart Between Restructures

An org chart that is updated only when a restructure is planned is not useful for restructure planning. By the time you need it, it is already out of date. Best practice is to treat the org chart as a living system:

1. Update on every appointment, departure, and change

Set a rule: any time an employee starts, leaves, or changes role, the org chart is updated. This is a 5-minute task if done at the time — it becomes a multi-day project if deferred for months.

Specifically:

When a new employee starts: update from "vacant" to "filled," add the employee name

When an employee leaves: update from "filled" to "vacant" (do not delete the position unless the role is also being disestablished)

When a role changes: update the position title, department, reporting line, or FTE as applicable

2. Maintain a "proposed" view for restructure planning

During any restructure process, you should maintain two versions:

Current state — the org chart as it exists today (the baseline for consultation)

Proposed state — the org chart as it would look if the restructure proceeds

The comparison between these two views is central to the consultation document you provide to affected employees. It must be clear what is changing and why.

3. Export PII-safe versions for external sharing

Before sharing the org chart externally — with employment lawyers, consultants, or board members — strip personal information. A PII-safe org chart shows only position titles and departments, not employee names or IDs.

Restructured includes a "hide names" toggle that generates a clean, PII-safe view of the chart without requiring you to create a separate document.

Common Mistakes to Avoid

Mistake 1: Using photos or personal details in the base org chart. Employee photos and personal information should live in your HRIS, not in the org chart. If you use the same org chart for external sharing and internal planning, you risk inadvertent disclosure.

Mistake 2: Deleting positions instead of marking them vacant. Position history matters for restructure planning. If a role has been vacant for 18 months, that vacancy may constitute a redeployment opportunity — or it may indicate the role is no longer required. Either way, the history should be visible.

Mistake 3: Not showing contractors on the org chart. Contractors are not employees, but they often perform work that is integrated into the organisation's structure. If a restructure would affect the work that contractor is performing, that should be visible. Section 6 of the ERA 2000 also means you should periodically assess whether your "contractor" relationships actually meet the genuine contractor test.

Mistake 4: Using a flat list for large departments. For departments with more than 10–15 people, a simple reporting-line tree becomes hard to read. Consider:

Sub-team groupings within the department

A separate "expanded view" for complex departments

FTE totals at the department level on the main chart

Conclusion

A well-maintained, HR-grade org chart is one of the most valuable tools in an HR manager's toolkit — particularly in New Zealand where the ERA 2000 places significant obligations on employers to consult genuinely about structural changes.

Restructured's org chart builder is free to use and was designed specifically for NZ HR teams. It handles employment types, vacancy states, FTE tracking, PII-safe export, and the current/proposed comparison needed for ERA 2000 consultation — in a single tool.

---

*This article provides general guidance on HR best practices and does not constitute legal advice.*