ORGONAUT
Login Signup
Docs
Scenarios
Model changes in edit mode

Model changes in edit mode

Edit mode provides a high-velocity interface for structural modeling.

Instead of opening individual forms for every change, you can perform multiple structural edits in Charts and Matrix using drag-and-drop, review them as a batch, and apply them together through the Change Tray.

Where edit mode is available

  • Charts: /charts (and scenario/snapshot variants)
  • Matrix: /matrix (and scenario/snapshot variants)

Edit mode is only available in mutable contexts. If you are viewing a baseline snapshot, an Applied Scenario, or an archived scenario, Edit mode is unavailable and structural controls are hidden.

Live Baseline vs. Scenarios

While Edit mode works in both contexts, the implications differ:

  • Editing in Live Baseline: Changes are applied directly to your canonical organization data. Use this for routine maintenance and small corrections.
  • Editing in a Scenario: Changes remain isolated within the scenario. This allows you to model complex restructures, evaluate deltas, and seek approval before any changes affect the Live Baseline.

The Change Tray

The Change Tray is a temporary holding area for structural commands. When you drag an item to a new target, Orgonaut stages a command in the tray rather than persisting it immediately.

This batching mechanism allows you to:

  • Reason about groups of changes: Model a complete restructure (for example, moving an entire department) before committing.
  • Preview before applying: See the pending state reflected on the canvas while the commands are still in the tray.
  • Revert easily: Remove individual commands from the tray or clear the entire tray to abandon a modeling pass without side effects.

Commands in the tray are client-side only; they are sent to the server for processing only when you click Apply changes.

Core edit workflow

  1. Switch from View to Edit.
  2. Drag teams, actors, or org units to valid targets.
  3. Optionally adjust allocation percentages via context actions.
  4. Review pending commands in the tray.
  5. Apply changes to persist the batch.

High-value operations

  • Reparent teams: Move a team under a different department or parent unit.
  • Redistribute actors: Move contributors between teams or departments.
  • Unassign items: Intentionally move actors or teams to the unassigned bucket for later placement.
  • Rebalance allocation: Adjust how much of an actor's capacity is assigned to specific placements.
  • Reclassify structure: Change team types or department classifications during a reorganization.

Multi-select and speed patterns

Use shift-click multi-selection to move several items in one pass. For large restructures, apply changes in thematic batches (for example, one department at a time) to ensure the activity log remains readable and easier to review.

Guardrails

  • Invalid targets: The interface rejects drops onto incompatible units (for example, dropping a department onto a team).
  • Read-only enforcement: Edit controls are automatically disabled in locked or archived contexts.
  • Explicit review: The Change Tray forces you to review the list of intended actions before they are applied.

These guardrails prevent accidental mutations and ensure scenario reviews are based on deliberate, explicit actions.

After applying

Always perform a validation pass after applying a batch of changes:

  • Hierarchy: Verify the tree shape in Charts matches your intended structure.
  • Distribution: Check the Matrix view to ensure actors are correctly placed across teams.
  • Placements: Confirm that primary placements still align with home-department intent.
  • Deltas: Review the scenario delta page to ensure the quantified impact (cost, FTE, velocity) matches your expectations.