ORGONAUT
Imports and setup
Manual cleanup after import

Manual cleanup after import

Imports get you to a structured baseline quickly. Manual cleanup makes that baseline decision-ready.

Use this guide right after a successful run.

Start with the right context

  • Baseline import: continue in live context
  • Scenario import: continue in the imported scenario

This keeps your cleanup aligned with the exact data you just loaded.

Step 1: Validate hierarchy shape

Check top-level structure first:

  • major departments exist and are named consistently
  • teams sit under the expected parent departments
  • no obvious duplicate units caused by naming drift

Good places to inspect:

  • Charts (/charts) for hierarchy shape
  • Matrix (/matrix) for team/type and member distribution

Step 2: Clean placements for key actors

For priority teams and leaders, verify:

  • primary placement is correct
  • allocation values are realistic
  • stale placements are end-dated

If you skip this step, rollups and scenario deltas will be misleading.

Step 3: Validate positions and budget metadata

Review high-impact roles first:

  • role titles and role types are accurate
  • budgeted team is correct
  • planned FTE and budget fields make sense

Remember: positions are planning metadata. They do not replace placements for membership.

Step 4: Resolve unassigned and edge cases

Use visual views to find cleanup hotspots:

  • unassigned memberships
  • over-allocation patterns
  • teams with missing role coverage

Treat unresolved anomalies as blockers before stakeholder review.

Step 5: Align taxonomy settings

Quality improves when type systems are tidy:

  • team types: /settings/team-types
  • department types: /settings/department-types
  • role types (for matrix rows): /settings/role-types

Normalize labels now so filters and reporting remain consistent.

Decision-ready checklist

Before creating or promoting scenarios, confirm:

  • hierarchy is coherent
  • key placements are accurate
  • positions reflect planned structure
  • obvious quarantined/ignored data trade-offs are documented