Org Chart
Visual reporting structure across every position — useful for proposal staffing and client demos.
Drag any position under another to set its reporting line. Render the whole org as a tree. For GovCon teams: print it directly into a tech volume to show key personnel structure. For commercial teams: show hiring managers the team they're building.
What you get
Built to solve the actual problems hiring teams hit every day.
Tree view across all positions
Every position you've created appears as a node. Open reqs show in green. Filled and draft are color-coded.
Cycle-safe reporting lines
Server-side walks the parent chain before saving — you can't accidentally create a reporting cycle.
Display labels
Override how a node renders on the chart without changing the position's actual title.
Proposal-ready
Use the same data structure for staffing tables on government proposals. Key personnel show in context.
How it works
Four steps from setup to value.
Open org chart
Navigate to /org-chart. Every position renders as a node, indented under its reporting line.
Edit a node
Click "Edit" on any position. Pick its parent from the dropdown — descendants are hidden so you can't make a cycle.
Set display label
Optionally override the chart label (e.g. show "Cleared Cloud Architect" instead of "Senior SWE — Position 47").
Reuse for proposals
When drafting a proposal, the org-chart structure can be exported into key personnel narratives.
FAQ
Quick answers to common questions.
What stops me from creating a reporting cycle?
Both the database (CHECK constraint blocks self-reports) and the API (walks the proposed parent chain to look for the position's id).
Can positions report across organizations?
In the current schema, no — reports_to_position_id is a FK to another position in the same data set. Multi-org reporting is a roadmap item.
Is there a print-friendly view?
Use your browser's print-to-PDF on the org-chart page. A dedicated export is on the roadmap.