Downloading & Exporting

All generated deliverables can be reviewed, edited, and exported directly from the platform.

Where editing happens. A deliverable is edited on its process's page in the Library, on the process's latest version — a wording fix updates that version in place, a change to the process becomes the next version to review (see The process page in the Processes section). The documents on a Scout session — As recorded in this interview — are the record of that one recording and open read-only, for the owner too; they are the evidence the process was built from, not the document to change. The session's Deliverables tab leads with the process's own documents, labelled with their version, and opens them on the process page; when the version an interview produced is no longer the newest it is marked Stale, says which version replaced it and why, and the cards open the latest instead.

Downloading the SOP

From the SOP preview you can download as PDF, Word (.docx), or Markdown (.md):

• PDF — looks exactly like the branded, styled preview on screen (your organization's template, logo, and layout). Clicking PDF generates the file and downloads it directly (it may take a few seconds). It's only offered when the SOP has a branded template applied — otherwise download Word instead, or apply a template (Regenerate → choose a template) first.
• Word — an editable document with generic formatting rather than the branded template.
• Markdown — the wording alone, plain text with no styling.

Screenshots come through in the PDF and Word downloads (in Word with their captions beneath them). The Markdown file is text only — each screenshot is replaced by a line naming its caption, like "[Screenshot: Approve the invoice]".

Process flows — the process map drawn into a template's map slot, and the flow fragments an SOP places after its steps — come through the same way: drawn in the PDF, embedded as images in Word, and noted in Markdown ("[Process flow: Tick the claim → Validate receipts — shown in the template view]"). On a library process's page, PDF, Word, and Markdown sit in the Download menu on the Document tab and export the version shown — the PDF there doesn't need a branded template; without one you get a plain layout. Pictures carried in from the document a library process was imported from (step screenshots, an "As documented in …" map) export like screenshots: in the PDF and Word downloads, and as a caption line in Markdown.

In the PDF, the whole process map gets a landscape page of its own. When the map is too large to read at that size, that page is an overview and is followed by numbered detail pages, each a readable stretch of the map with its lane names. A flow fragment under a step is drawn to fit the text column at a readable size; one that would be too small is shown as two or three consecutive parts ("Process flow (part 1 of 2)"). Lane names always appear inside a fragment, and no figure is split across pages.

Downloading the BPMN diagram

The process map can be downloaded on its own, without the SOP, for people who receive it by email rather than in the app:

• PDF, one sheet (the default) — the whole map on a single page cut to the drawing's own size, the way an engineering drawing or an ARIS export ships. Nothing is split or shrunk: the PDF viewer opens it zoomed to fit and you zoom in to read any part. Best for sharing on screen and filing. (A small map gets an A4 landscape page; a very large one is scaled to the biggest page PDF readers open, still one sheet.)
• PDF, A4 pages — the same map pages the SOP PDF carries, for printing: the whole map on an A4 landscape page when it is readable at that size, otherwise an overview page followed by numbered detail pages, each a readable stretch of the map with its lane names, and no figure split across pages. Its file name ends in "A4" so the two exports of one version sit side by side.
• BPMN XML (.bpmn) — the diagram itself, for UiPath, Camunda and other BPMN tools.

In both PDFs the diagram's own formatting — box sizes, colours and the text size chosen in the editor — comes through, and each page carries the process name, the version (for a library process) and the date at the top, and "Linc AI, Page X of Y" at the bottom.

Where to find them: on a library process's page, the BPMN tab's Download menu offers PDF, one sheet, PDF, A4 pages and the XML; the Outputs tab's BPMN row has PDF, PDF, A4 and BPMN 2.0; and the Document tab's Download menu adds BPMN diagram (PDF, one sheet) and BPMN diagram (PDF, A4 pages) under the SOP formats. Inside the BPMN editor, the toolbar's download buttons export the diagram as it is on the canvas — unsaved changes included — as XML or, from the PDF button's menu, as either PDF, so you can print a layout before deciding whether to save it.

Flowcharts have no PDF export (PNG/SVG/.mmd).

Regenerating outputs

A session's as-recorded documents are written once, when the interview completes. There is no Regenerate for them: they are the record of that recording, and once the interview has been filed against a process a rewrite would change the record without reaching the process. If a run fails, the failure banner on the session offers Try again, which re-runs the generation.

To change the process itself (a step is wrong, missing, or out of order), edit the SOP or the BPMN diagram on the process page and save it as a new version; the other documents are updated to match on that version. To rebuild a process's deliverable from its interviews and documents, use Regenerate in the ⋯ menu on the process page, which writes a new version rather than overwriting the one you curated. If the interview itself is wrong, tell the interviewer in the session chat — a session marked Needs update by a later answer is taken into the process from its page, not by rewriting the recording's documents.

Version history

Every time an SOP is written, Linc snapshots a new version. On a process's page you can view any version, see what changed and which interview it came from, edit the latest one, and publish a specific version as the official one (see the Processes section). Older versions are read-only — the toolbar says Superseded by vN with an Open latest shortcut. Where your organization runs a controlled-document process, SOPs carry an allocated document ID.

Finding SOPs in the Library and Chat

There is nothing to save by hand. Every interview feeds a process in the Library, and a process's published SOP is what the rest of your team finds through Chat — searchable the moment it is published, and kept current as versions are published over it. An interview's own SOP stays on its session in Scout (and on the process's Interviews tab) as the record of that one recording; it is not listed as a separate document in the Library and is not quoted by chat (see What chat reads in the Processes section).