Operating model
How the work flows, end to end.
An operating model is a map of how your processes connect. See the handoffs and systems involved, then explore a different flow on a copy before changing the live model.
5 processes free. No credit card. Includes 1,000 AI credits for your first 30 days.
Inside the tool
Harborline
Organization operating model · Editor
People Ops
Offer & Contract
VerifiedIT Operations
IT Account Setup
VerifiedPeople Ops
First-Day Orientation
VerifiedPeople Ops
30/60/90 Check-ins
StalePeople Ops
New-Hire Paperwork
VerifiedFinance
Payroll & Benefits
Needs reviewIT Operations · Before day one
IT Account Setup & System Access
- Owner
John Smith- Dependencies
- 2
Systems
OktaGoogle WorkspaceSlackRACI coverage
- John SmithAR
Jordan LeeC
Linked SOPs
New-hire IT setup
Incoming · Outgoing
Offer & Contract → this process → First-Day Orientation
Edit process details
Inside the tool
End-to-end · Stage · Department
Read the flow left to right, or sort processes into stage or department lanes.
Process card
A process with its department, its systems and its review status. Select it for its hub.
Process hub
The selected process’s owner, systems, responsibilities, SOPs and handoffs.
Review connections
Connections found in your sources wait for an editor to approve them.
Scenario
Test a future-state flow on a copy. The live model doesn’t change.
Three ways to read it. One model underneath.
Switching views changes the layout, never the model. Lanes hide the connections by default, so the layout stays readable.
- End-to-end
Processes in the order work moves, laid out left to right.
- Stage
Lanes for the stages you set up, like Intake, Qualify, Execute, Review and Close.
A process without a stage sits in Unassigned.
- Department
Lanes by department.
A process without a department sits in Other.
- Needs mapping
A process with no handoff in or out yet.
What you can do.
See the whole flow
Every process on one map, end to end, or in lanes by stage or department. Export it as an image or a PDF.
Draw handoffs and decisions
Connect processes in the order work moves, and add a decision point with its question and each named outcome.
Approve what’s suggested
Connections Jumpstart finds in your sources arrive as proposals. Nothing joins the map until an editor approves it.
See what needs attention
Each card shows its process’s review status, so the processes that need a look stand out across the whole business. The mapping queue lists those with no handoff yet.
Test a change first
Build a future-state flow as a scenario. Preflight checks catch gaps, loops and decisions without outcomes, and Meridi AI analyzes it when you ask. The live model stays as it is.
Know your systems
List every system with its owner, status and spend, and see the processes, departments and people each one touches.
How it connects.
- BaseProcessesEach card is a process. A process shows its upstream and downstream from the map, with a link to open it.Explore Processes
- BaseJumpstartAdds the processes it publishes, and proposes how they connect, for you to approve.Explore Jumpstart
- BaseStakeholdersThe hub shows each process’s owner and who is responsible, accountable, consulted and informed.Explore Stakeholders
- BaseSOPs and documentsThe hub lists each process’s SOPs, and flags a process with no documented steps.Explore SOPs and documents
- BaseMeridi AIAnalyzes a scenario when you ask, and proposes connections and systems for you to apply.Explore Meridi AI
- DeliveryProjects and plansOn Delivery, each project gets its own model, with more export formats.Explore Projects and plans
Put it to work.
Explore the workflows that use this tool.
| Feature | Free$0 | Base$29/month | Discovery$79/month | Delivery$149/month |
|---|---|---|---|---|
| Operating model and systems | Included | Included | Included | Included |