02/Processes as data
Process maps you can query, not just look at.
Every step carries its owner, timing, inputs and handoffs.
Each workflow is a model rather than a drawing, so the same process can be searched, updated, exported and analyzed without anyone redrawing it.
Levels of detail
One map for the summary and the operational detail
A step can contain a whole sub-process, so the same map serves an executive summary and the team actually doing the work.
- Hierarchical breakdowns with drill-down detail
- Swim-lanes by role, team or department
Finding problems
Find the steps with no owner before they cost you
Because ownership, timing and handoffs are modeled rather than drawn, gaps are findable instead of something you hope somebody notices.
- Rich node data: owners, inputs, outputs, SLAs
- Branching, convergence and cross-functional handoffs
Exports and API
Take the process out as a file or through the API
The same model drives comparison, analysis, exports and the API, none of which is possible against an image.
- Editable maps generated in seconds
- Linked knowledge across maps and documents
"We stopped maintaining a separate process catalog. The Sapeum map is our process catalog now."
One process catalog to maintain, not two
The map is the catalog.
Ready to analyze, not just to read
Structure is what analysis runs against.
Cheap to keep current as work changes
Editing a model is cheap. Redrawing is not.
Related features
All featuresProcess telemetry
Compare live run data against the documented process, and see where the two have drifted apart.
Simulation
Test a process design against realistic volumes and timings before anyone has to work that way.
Common questions
How is this different from a diagramming tool?
A diagramming tool stores shapes and lines. Sapeum stores steps, roles, decisions, handoffs and their attributes, and renders a diagram from them. That difference is what makes version comparison, analysis and API access possible at all.
Can one process contain another?
Yes. Process breakdowns are hierarchical, so a single step can expand into a full sub-process. The same map serves an executive summary view and the operational detail underneath it.
Can we get the underlying data out?
Yes. Processes and their change history are available through the REST API, alongside document, image and spreadsheet exports. See data integration.
Can we get a map into a board pack or an SOP?
Yes. Processes export to PNG, SVG, PDF, DOCX and XLSX, so the same model serves a procedure document or a spreadsheet analysis without being redrawn. See data integration.
Who can see and edit a given process?
Access is governed by role-based access controls, and every edit is attributed. Sapeum has completed an independent SOC 2 Type 2 examination; trust.sapeum.com carries the current detail.