Feature area
Documentation that comes from the process
Process documentation ages because it is written by hand in a separate file. Here it comes from the flow. The Process Chart reads the flow structure, the banded PDF makes it printable, the operating procedure is generated with AI and versioned. What the operator reads in a stage is the guide linked to that stage, not a document to hunt for in a shared folder.
Process documentation
- 1Process Chart in three automatic layouts
- 2Professional banded PDF
- 3Convert to Procedure (SOP) with AI
- 4Versioned procedures and stage guides
6 features
Three problems this area solves
Documents nobody updates
The separately written procedure diverges from the real process after the first change.
Operators without guidance at the right moment
Instructions sit in a folder, while the work happens in the case.
Audits chased at the last minute
Before a review, who does what and with which versions is rebuilt by hand.
Process Chart in three automatic layouts
The documentation view of the flow in three layouts, read from the same flow structure.
There is no second drawing to maintain: the Process Chart reads the flow structure, so it is always aligned. The three layouts are Sequence, Lanes by owner and Sequence with a "Who" column.
Technical details
- Every stage shows number, type, owner, time constraints, guidance, blocking tasks and human fallback.
- Seven task icons.
- An amber dot flags what is missing from the documentation.
- Operators and read-only users see owners, outcomes and guides, never URLs, scripts or prompts.
Professional banded PDF
A PDF that prints the way you see it: cover, diagram cut between stages, legend and "Who does what" cards.
The diagram is cut only between stages, with numbered connectors between pages. What you see is what you print.
Technical details
- Cover with branding and version.
- Legend and "Who does what" cards (Task, Who, Expected output, Constraints, Guidance).
- A4 portrait or landscape depending on the layout.
Convert to Procedure (SOP) with AI
A 3-step wizard generates an operating procedure from the flow in Italian or English.
The procedure comes from the process, not from a separately written document. Where the AI lacks information it says so: gaps are marked and counted.
Technical details
- Fixed structure: purpose and scope, roles, conventions, one chapter per stage, transitions and timings.
- Gaps are marked "[TO VERIFY]" with a counter.
- A single chapter can be regenerated.
- Each chapter links with one click as the guide of the matching stage.
Versioned procedures and stage guides
A procedure register with immutable versions, citable sections and guides operators find in the case.
Each version has an author, a note and a content fingerprint. Sections are linked to stages and tasks; when a new version comes out, links are flagged "to realign".
Technical details
- Immutable versions with author, note and content fingerprint.
- Procedure coverage per flow.
- The stage guide appears to the operator in the card of the current stage.
The features
Expected output for every task
A dedicated field up to 300 characters, with AI suggestion, that travels through all documentation.
Show detailsHide details
The expected output says what must exist when the task ends. It appears in the Process Chart, the PDF, the procedure and exports.
Technical details
- If not written by hand, it is derived automatically (e.g. "Outcome: A / B", "Field X filled").
Deep dive
One source, four documents
The Process Chart is the documentation view of the flow in three layouts: Sequence, Lanes by owner and Sequence with a Who column. Every stage shows number, type, owner, time constraints, guide, blocking tasks and human fallback. An amber dot flags what is missing. There is no second drawing to maintain, so it cannot diverge from the process.
The banded PDF prints the way you see it: cover with version, diagram cut only between stages with numbered connectors, legend and Who does what cards with task, owner, expected output, constraints and guide. From Automate, the Convert to Procedure wizard generates an SOP in Italian or English: where the AI has no information, it marks the gap as to verify and counts it.
Procedures live in a register with immutable versions, each with author, note and content fingerprint. Sections link to stages and tasks; when a new version comes out, links are flagged to realign. The operator finds the guide in the card of the current stage. To show a flow to a client, a temporary link cleaned of credentials is used, expiring from 30 minutes to 30 days.
In daily use, the process owner opens the Process Chart in a workshop, spots the amber dot on a stage without an owner and completes it on the spot. The next day the updated PDF is ready for review. The procedure, generated and then reviewed, is linked as a guide to the stages: the operator finds it where they work, and whoever audits finds a version with author and note.
Related use cases
Related areas
Frequently asked questions
Is the AI-generated procedure ready to use?
It is a structured draft. Gaps are marked and counted, and a single chapter can be regenerated. A person approves it.
Does the process chart need manual updates?
No, it reads the flow structure, so it stays aligned with every version.
What does the recipient of a share link see?
A snapshot of the flow cleaned of credentials, viewable without an account until expiry.
In which editions is it available?
Process chart and guides are included in Free too; the PDF from Optimize; procedure conversion from Automate.
Who can see a flow's scripts and prompts?
Only those who design. Operators and read-only users see owners, outcomes and guides, never URLs, scripts or prompts.