Product updates · 6 min read
The Flowchart view: process documentation that finally updates itself
Starting with FlowSharp 0.85, every process automatically produces its own official document: three layouts, completeness checks, an audit-ready PDF, and a guided conversion into an ActiveSOP procedure.
The problem every SME knows: two versions of the truth
Almost every company has a process modeled in some software, and then a separate procedures manual, a Word file for ISO 9001, a slide deck used for onboarding new hires. Two different artifacts, maintained by different people, updated at different times. Sooner or later the outcome is always the same: the process evolves, and the documentation falls behind.
This isn't a discipline problem, it's an architecture problem: if documentation lives in a separate document, somebody has to remember to update it every single time. With the Flowchart view, FlowSharp removes that second artifact altogether: documentation is no longer a separate file, it's a live view of the process itself.
Three layouts, one single source of truth
The Flowchart view takes the same stages, activities and rules already modeled in the process designer and lays them out like the pages of a readable document: no diagram to redraw by hand, no manual syncing to remember. Add a stage, and the document includes it. Change an owner, and the document reflects it on the next refresh.
You can pick from three layouts depending on who's going to read it: Sequence, for anyone who wants to follow the flow step by step; Swimlanes by owner, which instantly clarifies who does what across roles; and Sequence with owners, a middle ground that keeps the chronological order while still surfacing responsibilities. Same process, three ways to tell its story to different audiences — an auditor, a new hire, or an owner who just wants the big picture.
Expected outcome and the amber flag: documentation you can actually measure
Every activity now has a new field: expected outcome. It's not extra bureaucracy, it's the exact question anyone reading a procedure would ask: 'okay, and what should I have in hand once this step is done?'. You can fill it in yourself, or let the AI draft a suggestion based on the process context — activity name, stage, role involved — which you then review and keep.
The real safety net, though, is the amber flag. FlowSharp automatically highlights where documentation is still incomplete: a missing output, no operating guidance, an owner written as free text instead of linked to a real user in the system. It's not a cosmetic detail — these are exactly the gaps an ISO auditor or a new colleague would spot first. Turning every amber flag green means, in practice, getting the process to an audit-ready state.
One click, one audit-ready PDF
Once the documentation is ready, the Flowchart view turns it into a printable PDF with a single click: a cover page with your company branding, a paginated banded diagram with numbered connectors linking pages together, a symbol legend, and a 'Who does what' sheet for every stage, with roles, activities and expected outcomes clearly laid out.
This is the document you bring to an ISO inspection, attach to an internal audit, or hand a new colleague on day one instead of improvising a verbal explanation. And because it's generated from the same live process you use every day, it can never quietly become 'the old version' someone printed two years ago and nobody ever updated.
Convert to Procedure: from diagram to written know-how, chapter by chapter
The most ambitious feature in this release is 'Convert to Procedure'. An AI-guided wizard reads the Flowchart and drafts an actual operating procedure, one chapter per stage — including automatic stages, which are usually the least documented simply because 'the system handles it'. You review the proposed text, edit what needs editing, and save it.
From that point on, the procedure isn't an isolated file sitting in a shared folder: it's directly linked to the stages and activities inside ActiveSOP. Whoever is working on a case finds contextual guidance exactly at the current state of that item, with no need to hunt for the right manual among ten versions. It's also the most concrete way to protect company know-how: knowledge of how things are actually done no longer lives only in one key person's head — it becomes a company asset, always current and always within reach.
In short: measure first, then automate — even the paperwork
FlowSharp's guiding principle hasn't changed: measure first, then automate. The Flowchart view applies that same logic to documentation itself: it no longer has to be something you chase every time the process changes, but something that follows it automatically, always one step behind the designer and yet always in sync with it.
Whether the goal is sailing through an ISO audit without sleepless nights, getting a new colleague up to speed without flooding managers with questions, or simply not depending on one person's memory for 'how things are done here', the Flowchart view turns a well-designed process into a document that's always ready — without anyone having to remember to update it.