Skip to content
Need the decision, not the software? Start the Trail Map assessment →
ProcessScoutSoftware
How it works Capture Capabilities Practitioners Teams Integrations Trust Log in Get started
Capture · where the evidence starts

The evidence starts with what people actually do.

Every finding ProcessScout produces traces back to captured evidence, not a workshop retelling. Browser recordings, WooCommerce and WordPress operations, and reviewed walkthroughs all feed the same governed record that analysis, design and outcome tracking run from.

Why capture is different

Most tools map from memory. ProcessScout maps from what happened.

A workshop produces someone's best account of a process, recalled under time pressure, months after the fact. Capture produces the process itself — recorded, timestamped and reviewable — so the first version of the map is built from evidence, not from good intentions.

The common approach

Interview, then diagram

A stakeholder describes the process from memory in a workshop. The resulting map reflects how the process is supposed to work — not necessarily how it runs on a bad Tuesday.

How ProcessScout starts

Capture, then analyze

Browser sessions, system operations and narrated walkthroughs are captured directly. The first map is built from what a person or a system actually did, with a citation back to the source.

How evidence gets captured

Four ways reality reaches the evidence base.

01

Browser capture

ProcessScout — Screen Recorder is a Chrome extension that captures what happens in the browser as evidence — the pages visited, the actions taken, and the order they happened in. It's a public extension on the Chrome Web Store, installed the same way as any other.

Host permissions are scoped to *.processscout.com and *.betterwrk.com by default. Recording any other site is requested per-site, at the moment you start, and only proceeds if you grant it — there is no blanket permission to read every site a person visits.

ProcessScout — Screen Recorder, on the Chrome Web Store.

Generally available
02

WooCommerce & WordPress

The WordPress connector reads directly from a WooCommerce store: the order lifecycle, the fulfilment steps, and the admin actions staff take to move an order along. That operational history carries the same source, confidence and review state as any other capture.

Requires WordPress 6.0+, PHP 7.4+ and WooCommerce 7.0+.

Available by scope
03

Walkthroughs & recordings

The safest place to start — no install, no credentials. A stakeholder narrates the task as they do it. The recording is transcribed, timestamped and reviewable, and a reviewer can pin a note to the exact moment a finding comes from. Every walkthrough lands in the Evidence Ledger with the same lineage as a browser recording or a system operation — though the unified Evidence Ledger view is limited availability.

Generally available
04

Field & mobile

Voice, photo and field-work capture for evidence gathered away from a desk is in pilot. It exists in the product today, but reliability, support and pricing are still being proven before it becomes a standard entitlement. Ask about the pilot when you request access.

Pilot
What capture feeds

Every capture becomes one link in the same evidence chain.

A browser recording, a WooCommerce order history and a reviewed walkthrough all land in the same place — the Evidence Ledger, whose unified view is limited availability — carrying source, confidence and review state through analysis, design, launch and outcome tracking.