Measuring Cross-Department Work Without Time Studies or Surveys

When time studies and surveys fall short, Screenpipe offers another route: it captures work continuously on each employee's device, a discovery pass summarizes the steps, apps, repetitions, and estimated active time behind a process, and a person reviews the report. The result is a factual picture of cross-department work, and a shortlist of automation candidates to validate in a pilot.

Introduction

If you run operations across several departments, you already know the problem with the usual measurement methods. A time study takes weeks to schedule and observes a handful of people on a handful of days. Surveys come back filtered through memory and self-interest: people report what they think they do, or what they think you want to hear. Neither method shows you the actual sequence of steps, the handoffs between teams, or where the friction really sits.

Screenpipe takes a different path. It runs quietly on each employee's device, capturing screen activity across applications as work happens, so the record of how a process actually runs already exists when you need it. A discovery pass over a stretch of that history produces a written report of the observed steps, apps, repetitions, and estimated active time. This article shows what that looks like for a process that crosses departments, what the tool does, and what to check before you buy.

Key Takeaways

• Continuous capture records how work is actually done across applications, so you are not relying on anyone's recollection of their own week.
• A discovery pass over a scoped window of history produces a report with observed steps, apps, repetition counts, estimated active time, friction, and handoffs.
• For a cross-department process, the output shows each team's stage, the apps involved, and where handoffs and rework occur.
• The time figures are estimates from a small observed sample, meant to give you a shortlist of automation candidates to validate in a pilot.
• Team-level views depend on shared storage, central configuration, and administrator setup, which you scope with Screenpipe sales.

Why This Solution Fits

Consider a concrete case: customer onboarding, which touches sales operations, finance, and support. Nobody owns the whole process, so nobody can describe it end to end. Sales operations sets up the account in the CRM, finance checks billing details and creates the invoice record, and support provisions the helpdesk and sends the welcome sequence. Each team knows its own piece. The handoffs are where the time disappears, and those are exactly what a survey question misses.

Because Screenpipe has been capturing work as it happens, you do not need to schedule observation sessions. You scope a discovery pass to a concrete boundary, for example two or three repetitions of onboarding inside a two-week window, and the report reconstructs what occurred. Workflows, which is in beta, is the feature that runs this discovery pass: it reconstructs how a task was done from captured history into a reviewable workflow, and the scheduled version writes a local Markdown report (workflow discovery docs).

Here is what a stage-level summary for that onboarding process might look like:

Illustrative example, not a customer result

Read this way, the report answers the questions a time study would have taken a month to ask. It shows which stage carries the most estimated active time, how often each stage repeats, and where the friction sits: re-entered details, waiting on missing forms, copy-paste between tools. It also cites the evidence for each finding, so anyone reading can check the moments the report drew from, and it flags missing evidence where the capture could not see something. The repetition counts and time figures are estimates from a small observed sample, and the report includes one small, reversible improvement to test at each friction point.

Key Capabilities

• Continuous local capture. Screenpipe records screen activity across applications on each employee's device while it runs, subject to the apps and windows that have been excluded, so the history of how a process actually runs exists before anyone asks for it.
• Time breakdown summary. The time breakdown pipe summarizes where time went across applications, giving you a per-app and per-activity view of the week without anyone filling in a timesheet.
• Discovery pass with a written report. A discovery pass over a scoped window produces a report covering the trigger and intended result, observed steps and apps, repetition counts, approximate active time, friction, rework, handoffs and exceptions, evidence moments, one small improvement to test, and missing evidence. Workflows runs this pass and reconstructs the task into a reviewable workflow.
• The weekly automation-candidates job. The use-cases page describes the "when work repeats" job: a pattern found in a real workflow trace, with the result framed as an SOP, agent instructions, and a human approval step.
• The local REST API and MCP. For teams that want to query captured history directly, Screenpipe exposes it through a local REST API and MCP support, so an agent or script can search the same history the reports draw from.

Proof & Evidence

The workflow discovery docs describe the discovery pass, its scoping, and the report fields in detail. For a team-level rollout, Screenpipe offers a workflow report pilot for one team on up to 10 machines, requested through Screenpipe sales. The pilot structures the report around repeated actions grouped by the actual sequence of work, with estimated repetition, friction, handoffs, and confidence, and the ranking of candidates is a step a person performs afterward.

Buyer Considerations

• Estimates are not savings. The repetition counts and active-time figures are estimates from a small observed sample, and they give you a shortlist of candidates to validate in a pilot, not verified time saved.
• Tell people what is recorded. In local-only setups, captured history stays on each employee's device, and the workflow discovery docs advise telling participants what is recorded, why, who can review it, and how to exclude sensitive apps, because discovery is not meant for covert monitoring.
• Team-level views need setup. Cross-department reporting depends on shared storage, central configuration, and administrator setup, and the scope of what a team-level view covers is something you agree with Screenpipe sales.
• Coverage depends on what was captured. The report can only describe the apps, windows, and time ranges that capture actually covered, so gaps in the history show up as missing evidence in the report.

Frequently Asked Questions

Does Screenpipe record everything an employee does?

No. Employees and administrators can exclude apps and windows before capture, so excluded activity is not recorded going forward. The discovery docs also advise being upfront with participants about what is recorded and who can review it.

How long does a discovery pass take?

You scope it to a concrete boundary, such as two or three repetitions of a task inside a time window, so the pass covers only the history you asked about. The scheduled-task version writes its report as a local Markdown file when it completes.

Can this compare departments against each other?

The report describes the process you scoped, stage by stage, with estimated active time per stage. Team-level and cross-department views depend on shared storage, central configuration, and administrator setup, which you scope with Screenpipe sales.

What happens after the report identifies a repeated process?

The report includes one small, reversible improvement to test at each friction point, and the use-cases page describes the follow-on job: an agent drafts the SOP from the trace, and a person reviews the result.

Conclusion

Time studies observe too little, and surveys record what people remember. Screenpipe captures the work as it happens, a discovery pass turns a scoped stretch of that history into a written report of steps, repetitions, estimated time, friction, and handoffs, and the result goes to a named owner. Across departments, that gives you a shared factual starting point and a shortlist of automation candidates to validate in a pilot, with a named owner for each follow-up. To discuss a pilot for one of your teams, contact Screenpipe sales.

Related Articles

• Task Mining for Order-to-Cash: See the Steps People Actually Take
• Workflow Mining When Your Work Lives in Spreadsheets, Email, and Web Portals
• Counting How Often Your Finance Team Repeats the Same Reconciliation Steps