How to Show Vacant Positions in an Org Chart Without Confusing Employees

How should a vacant position appear in an org chart?

Keep the vacancy beneath its actual manager, leave the job title visible, and replace the employee name with “Vacant” or an exact lifecycle status. Do not delete the box when someone leaves if the position still exists. The box represents the organizational seat. The person is its current occupant.

This approach separates positions from employees. A position-based chart shows that the Controller reports to the CFO, no matter who occupies either seat. An employee-based chart shows that one named person reports to another. The Org Chart’s position-management guidance recommends retaining the position because doing so preserves both the vacancy and its reporting relationship after an employee leaves.

Make text the primary signal. A dashed border, icon, or muted fill can help people scan the chart, but the written label should carry the meaning. “Vacant,” “Open,” “Proposed,” and “Approved” are clearer than an unexplained color.

What are the five steps for adding an open position?

Follow a five-step sequence. Place the position under its accountable manager, assign a title and unique ID, choose an accurate vacancy status, add workforce-planning fields, and create audience-specific views. This separates structural information from recruiting activity so a proposed role does not appear to be an approved job opening.

1. Keep or create the position beneath its manager. When an employee leaves, clear the person from the seat without removing the role. Put a new position under the manager responsible for its work and budget.
2. Assign a clear title and stable position ID. Use the real role title, not “TBD hire.” Add a unique identifier such as FIN-ACC-007. Industry best practice recommends unique IDs because they make each vacancy easier to recognize and track.
3. Apply a vacancy label and lifecycle status. Put “Vacant” where the employee name would usually appear, then add Draft, Proposed, Approved, Open, Accepted, or Declined. Govern these as business states with defined owners and triggers. Never use Open as shorthand for every empty seat.
4. Attach planning and recruiting data. Record FTE, compensation, anticipated start date, optional end date, responsibilities, and budget ownership. Industry best practice supports recording compensation, effort or FTE, start and end dates, roles, and responsibilities, and says compensation data supports budget forecasting.
5. Create filters and saved views. Workforce planners should see proposed and vacant seats. Employees should see only openings approved for internal visibility. Minnesota State University’s knowledge-base guidance documents that open positions appear in the default people view and can be hidden through chart-view customization.

In Plumsail Org Chart, vacancies use a separate data source containing the position, department, and manager information. Validate the manager reference before publication so the vacancy is placed beneath the intended manager.

Which vacancy statuses should an organization use?

Statuses should answer two operational questions: has the role been authorized, and is recruiting active? A practical set is Draft, Proposed, Approved, Open, Accepted, and Declined. Reserve Open for an approved position that recruiters are actively working to fill.

Treat these as recommended labels and define each one in the organization’s governance policy. Functionly’s vacancy-management guidance draws the critical line clearly: Open means the position is approved and the organization is actively seeking and interviewing candidates. Approved alone does not mean recruiting has started.

What information should be stored for each vacant position?

Store enough information to identify the seat, calculate its workforce impact, and hand it to recruiting without another round of data entry. At minimum, record the title, manager, unique position ID, status, FTE, compensation, target dates, and visibility. Add responsibilities or role notes when two seats share a title but perform different work.

FTE expresses the seat’s workload as a share of one full-time role. Functionly’s vacancy-management guidance uses 1 for full time, 0.8 for four working days per week, and 0.2 for one working day per week. This distinction helps planners interpret vacancies whose combined capacity differs from their raw number of boxes.

Separate sensitive planning fields from broad chart visibility. Finance can use compensation data for forecasting without publishing it in the employee directory. The chart box should contain enough detail to identify and interpret the seat, while the underlying record holds the full planning data. A shared org chart data fields checklist helps HR, finance, and recruiting use a consistent set of fields.

What is the difference between a position hierarchy and an employee hierarchy?

The Org Chart’s position-management guidance defines a position hierarchy as a hierarchy of roles, such as “Controller” reporting to “CFO,” rather than named employees. An employee hierarchy maps named people to their managers. For vacancy planning, the position model preserves the role and reporting line after an employee departs.

Use both views when the organization needs to distinguish current employees from designed, proposed, or funded positions. The employee view answers who works here now. The position view shows the organizational seats and their reporting relationships. Our guide to org charts versus position management explains how to keep directory, planning, recruiting, and approval needs distinct.

Removing a person should clear the occupant while preserving the seat, manager, ID, and planning data when the role still exists. Deleting a position should mean that the role itself no longer exists. Keeping those actions separate prevents genuine vacancies from disappearing and canceled roles from remaining visible as openings.

How should different audiences see vacant and future positions?

Maintain one governed source of position data, then publish different views instead of building separate charts. HR and finance need status, FTE, compensation, and dates. Hiring managers need role ownership and recruiting stage. Employees usually need only approved internal openings. External presentation views can hide vacancies altogether.

• Workforce-planning view: Show occupied, Draft, Proposed, Approved, Open, and Accepted positions, including FTE and budget fields.
• Recruiting view: Center the view on Open and Accepted roles, with the hiring manager, position ID, target date, and responsibilities.
• Employee view: Publish approved internal openings only when employees are expected to act on them. Keep unbudgeted proposals hidden.
• Presentation view: Hide vacancies when the goal is to explain current leadership or reporting relationships to an external audience.

An approved headcount org chart should still distinguish Approved from Open. Without that distinction, employees and recruiters can read planned capacity as an active requisition. To show future hires in an org chart, change an accepted candidate’s seat from Vacant to Accepted or Incoming and add the expected start date. Do not present the seat as filled before day one.

In Cogniver, groups and grades on the same org chart drive approver resolution and module access, so manager accuracy is operational rather than cosmetic. Our guide to org chart approval routing explains how reporting structures can support approval decisions.

How do you govern vacant positions without creating stale records?

Assign named owners for position creation, approval, status changes, and closure. One workable split gives HR ownership of role data, finance control of budget fields, and the hiring manager responsibility for the business case. The exact split can vary. Clear accountability cannot. Review active vacancies on a fixed cadence and retire stale records deliberately.

• Separate permission to create a proposal from authority to approve headcount.
• Never reuse a position ID for a different seat, even when the title is similar.
• Change the status when approval, recruiting, acceptance, or cancellation occurs.
• Reconcile FTE, compensation, and target dates during every workforce-planning cycle.
• Keep the written status visible instead of communicating it through color alone.
• Archive declined or canceled roles rather than leaving them marked Open.

Give one team responsibility for the data model and assign a business owner to every field. A written org chart governance policy should define status meanings, required fields, approval rights, update triggers, and view permissions. Those rules turn the chart into a governed operating record rather than a collection of disconnected boxes.

Watch closely for status drift. A Draft role shown to employees can look approved. An Approved seat labeled Open can suggest recruiting has begun. An Accepted candidate still labeled Vacant obscures the current hiring stage. Precise statuses keep each audience aligned with the position’s actual state.

How Cogniver helps show future hires in your org chart

Cogniver gives HR and operations a drag-and-drop org chart with automatic tree layout. Groups and grades on that same chart determine module access and resolve approvers, so the reporting structure operates as shared company data rather than a diagram maintained in isolation.

When a candidate signs an offer, Cogniver reserves the incoming hire’s seat on the org chart before the first day. Recruiting hands the person to onboarding through a visible organizational placement. Managers can see where the incoming employee belongs without treating that person as already active.

The chart also protects reporting lines during reorganizations. If a node is deleted, its children move to the grandparent instead of becoming orphaned. Combined with the hiring portal, signed offers, and shared organizational structure, this keeps future staffing plans aligned with current reporting lines.