Clarity

​

Introduction

Clarity is Duvo’s process documentation and analysis system. It helps you capture how work actually gets done — through video recordings, AI voice interviews, phone interviews, and documents — then uses AI to turn those captures into structured documentation with cost-benefit insights. Whether you’re onboarding new team members, evaluating automation opportunities, or standardizing operations, Clarity gives you a clear picture of your processes.

​

Key Capabilities

• Capture processes via screen recordings, AI voice agent interviews, phone interviews, and uploaded documents
• AI-powered video analysis that extracts steps, systems used, and decision points
• Automated documentation generation with cost-benefit analysis
• Industry-specific benchmarks for retail, grocery, and CPG workflows
• Sharing and collaboration through public links or shareable invite links for people outside your team

​

Quick Start: End-to-End in 5 Steps

​

Capture a Process

Clarity supports four capture methods. Pick the one that fits how the knowledge lives today — or combine several on the same process.

​

How to Invite People

You can invite subject matter experts to add their own captures to a process — even if they do not have a Duvo account yet.

​

How to Create a Client Invite Link

A client invite link lets you share a specific process with an external stakeholder — such as a client or vendor — without sending an individual email invitation or adding them to your team. Anyone with the link can open the process and contribute a voice interview. People who open the invite link see a focused interview view where they can start a voice interview and contribute to the process. They do not gain access to the rest of your team workspace.

​

How to Generate and Review Documentation

Once you have added at least one capture and configured your team settings, you can generate the process documentation.

​

Generate

​

Navigate the output

The process view uses an immersive layout: the BPMN process diagram fills the full canvas, with a floating tab switcher overlaid on top. Select a tab to open a side panel alongside the diagram. The diagram supports interactive navigation: use the controls overlaid on the canvas to zoom in, zoom out, fit the entire diagram to the view, or download the diagram as an SVG file. You can also pan by clicking and dragging the canvas.

​

Share

The shared view uses the same immersive layout as the private view.

---

​

How Clarity Handles Conflicting Inputs

When you add several captures to a process, they will not always agree. Two interviewees may describe the same workflow differently, or an uploaded AOP may not match what someone explains in an interview. Clarity does not pick a winner automatically — there is no fixed priority order that ranks one source above another. Instead, Clarity treats every capture as evidence:

• Inputs are evidence, not authority. Clarity does not assume an AOP outranks an interview, or that one interviewee is more correct than another. It weighs what each capture describes rather than deferring to a single source.
• Conflicting versions are surfaced with attribution. When two captures describe a step differently, Clarity shows both versions and where each one came from, so you can see who said what rather than silently merging them into one account.
• Conflicts in decision logic are flagged. Disagreements that affect decision points, branching, or escalation paths are flagged as high-priority, because that is where an unresolved conflict has the largest impact on how the process actually runs.
• The team is prompted to align. Rather than auto-resolving a conflict, Clarity prompts your team to agree on a single standard for the process, so the documented version reflects a real decision instead of a guess.
• Extra capture clarifies missing detail. When a step lacks enough detail to automate — often because the captures conflict or leave a gap — Clarity asks for an extra capture to clarify it. See Fill in missing information below and the capture requests in Organize processes.

This keeps the generated documentation honest about where the source material disagrees, and puts the decision about the single correct version in your team’s hands.

---

​

Edit and Ask with Clarity Chat

Clarity Chat lets you ask questions about a process and make changes to it through a simple chat — without editing anything by hand. It works on both the Current Process and the Transformation Proposal.

​

What you can do

• Ask about the process — for example, “Why is this step a risk?”, “Where are we leaking margin?”, or “What would change if we automated this?”
• Edit the process — add, reword, or remove steps, or refine the Transformation Proposal, just by describing what you want.
• Fill in missing information — when a step is flagged as needing more detail, Duvo asks you one focused question at a time and updates the process from your answers.
• Review before you accept — every change appears as a preview, with added text highlighted and removed text struck through, so you see exactly what will change before applying it.

​

How to use it

​

Fill in missing information

When the Transformation Proposal has steps that need more detail, those steps are flagged. To provide what’s missing:

​

Organize the Process Library

The team library has three views, switchable from the toolbar:

• Folders (default) — collapsible folders your team owns, plus an Unfiled section holding every process without a folder.
• Ungrouped — one flat grid of all processes.
• Organization — a read-only view grouping your team’s processes by their Process Landscape areas, with an Unclassified section for processes the landscape has not placed yet.

​

Key Capabilities

• Team-owned folders — create, rename, reorder, and delete folders (team managers and above). Deleting a folder never deletes processes; they return to Unfiled. Any team member can move processes between folders.
• Set up from landscape — one click creates a folder for each landscape area that contains your team’s processes. These folders follow the area’s name until you rename them; renaming makes the name permanently yours. Folder changes never modify the landscape itself.
• Suggestions — an unfiled process that the landscape has classified shows a Suggested chip on its card. Click the chip to file it, or use File all suggested on the Unfiled section header to file every suggested process at once.
• Focused browsing — search, status filters, and My processes always show flat results across all folders; clear them to return to your folder view.

​

How to use it

​

Organize processes

The Clarity library follows the same hierarchy shown in Process Landscape. Open a folder to review the processes grouped under that part of your operating model. For organizations where Process Landscape is enabled, access works as follows:

• Open and understand the landscape — All organization members can open Process Landscape. Folders and capabilities form the visible organization skeleton. Inaccessible processes appear as Restricted process; only granted processes render in full.
• Maintain process nodes — Managers can maintain process nodes for teams they manage. Organization Executives, Owners, and Admins can maintain the skeleton and all process nodes.
• Generate the landscape — Only organization Executives and Owners can generate Process Landscape.
• Assign ownership — Process ownership assignment remains limited to organization Admins, Owners, and Executives.

Process Landscape generation organizes your team’s existing processes into a company landscape. Captures add optional context for grouping and summaries, but existing processes are the source of truth.

​

Key Capabilities

• See the full hierarchy on the map — the map view draws each area as an outlined region with its folders nested inside, split into value chain and support rows, so the map matches the tree structure. Deeper folders appear as section labels above their processes.
• Maintain the organization skeleton — organization Admins, Owners, and Executives can move areas and folders, change their order, and add sub-areas.
• Maintain team processes — managers can add, edit, move, and remove process nodes for teams they manage. Organization Admins, Owners, and Executives can maintain process nodes across all teams.
• Review proposed processes on the map — proposed processes appear as dashed cards. Click one to open its details. Organization Admins, Owners, and Executives can assign its owning team or remove it.
• Review ownership suggestions — managers can review team assignment suggestions for processes owned by teams they manage. Organization Admins, Owners, and Executives can review suggestions across the organization.
• Add processes manually — managers can add a missing process for a team they manage and describe it. Organization Admins, Owners, and Executives can also assign the team that owns it.
• Track process people — add real people by email or placeholders by name, with an optional role tag for each process.
• Accept or dismiss suggestions — managers can review capture and team assignment suggestions for teams they manage. Organization Admins, Owners, and Executives can review suggestions across the organization.
• Assign capture requests — choose the teammate who should provide the missing interview or capture.
• Notify the assignee — accepted capture suggestions become open capture requests, and the assigned teammate receives the same notification used for extra capture.
• Select multiple processes — tick the checkbox on each process, or the checkbox in the toolbar to select all, to act on several at once.
• Assign or remove in bulk — organization Admins, Owners, and Executives can assign selected processes to one team. Managers can remove selected process nodes for teams they manage.
• Reorganize together — drag any selected process to move the whole selection into another area at once.

​

How to use it

​

Process tags

Process tags help your organization mark and find related processes in the Landscape. Tags are shared across the whole organization, so the same tags are available to every team.

• Tags appear on process nodes in the Landscape.
• Managers and above (and organization admins) create, edit, and delete tags; everyone in your organization can see them.
• Tags are managed by people: add or remove them directly on a process, or ask Duvo in chat to do it for you. Duvo never adds or removes tags on its own.

​

When to use it

Use Process Landscape suggestions after sorting new captures, importing process material, or reviewing an L1-L4 area where ownership or missing context is still unclear.

​

Inspect Processes from the CLI

Use the Duvo CLI when you need terminal access to a Clarity process. The CLI can find processes, compare generated versions, review evidence citations, list gaps and extra capture requests, import Miro exports, create interview invite links, export Markdown briefs, and produce structured JSON for scripts or AI assistants. The Clarity CLI also exposes public write commands for generating, promoting, reverting, postprocessing, and building automations from Clarity process context.

​

How to Regenerate Documentation

If you add new captures, want to incorporate feedback, or need a more thorough analysis, you can regenerate the documentation at any time.

​

Duplicating a Process

You can create a copy of any existing process using the duplicate action. This is useful when you want to start a new process based on an existing one, or when you need to make a variant without modifying the original. To duplicate a process: Duvo creates a new process named “Copy of [original name]” with:

• All captures from the original process (voice interviews, videos, and documents that were fully processed — any captures still recording or processing are skipped)
• The full message and generation history
• The same analysis, transformation guidance, and process breakdown

​

Process Diagram Version History

The process diagram view includes a version history timeline in the bottom-right corner of the diagram canvas. This timeline lets you navigate between previously generated versions of the diagram and revert to an earlier one if needed. Version history is only visible to:

• The team member who created the process
• Users with the Manager role or above (Manager, Administrator, Owner)

Members, Builders, and Clarity Members who did not create the process cannot view or navigate its version history.

​

Configure Team Settings

Before generating documentation, set up your team context so Clarity can provide accurate cost-benefit analysis. These settings apply to all processes in the team and are used to calculate financial impact in the generated documentation. The Language setting is preselected for every new interview and is the language Clarity writes the generated current process, transformation proposal, and chat edits in — English, Czech, French, German, Polish, Portuguese, or Spanish.

​

Process Statuses

Each process moves through the following stages:

​

Clarity Member Role

Team members with the Clarity Member role have a focused, interview-only experience. When a Clarity Member opens a process:

• Only the voice interview option is shown — video upload and document upload are not available
• They can see and manage captures they have personally added
• Their captures are visible to process owners and admins alongside other contributions

This role is designed for subject matter experts who contribute process knowledge through interviews without needing full Clarity access. Admins can invite Clarity Members from team settings — enter one or more email addresses at once to send bulk invitations in a single step.

​

Key Takeaway

Clarity turns informal knowledge — videos, voice interviews, and documents — into structured, actionable process documentation. Use it to understand how work gets done today and identify where automation can save time and cost.

​

Next steps