How It’s Done

Process and knowledge management

Capture how work really gets done

Interview, verify and document each process. Start simple, then refine it with evidence, walkthroughs, and reviewed updates.

Start an interview View current SOPs

Workspace overview

2 Active employees2 Approved master maps2 Current SOPs

How the Process Works

How to use it well

First interview: discover operations, not every detail

Ask what starts the process, the main sequence, major handoffs and what finishes the task. Avoid detailed software field-by-field questioning until the process scope is clear.

Master maps: compare without inventing agreement

Keep each employee's account separate. Different interviews from the same employee do not represent independent agreement. Mark conflicts for a reviewer; never resolve silently.

Knowledge Discovery: investigate what matters

Use the approved master to ask broad ownership and decision questions first. Record tools, explanations and exceptions only when relevant; let employees correct prior answers.

Walkthroughs: optional, not mandatory

For computer work, employees can narrate a demonstration. A reviewer should confirm which screenshots illustrate which SOP step before adding them.

Quality and updates

An SOP can be useful before every edge case is documented. Flag consequential gaps, revise only supported statements, and keep earlier approved versions available.

Manage employee and role records

Under More → Record management, you can archive employees, remove unreferenced interviews or request permanent deletion of a role workspace. Permanent deletion includes linked documents and is not reversible through the interface.

Planned: Existing SOP intake

A future workflow could import a company’s existing SOPs, extract current steps, identify gaps and ambiguous claims, and use interviews to verify rather than recreate them. This is not implemented yet.