Watching an Automated Workflow After Go-Live: Finding the Work People Still Do by Hand

Automating a workflow does not end the story, because parts of it usually keep running by hand. Screenpipe keeps capturing work on each machine while it runs, a discovery pass summarizes where time still goes, and the result is a shortlist of automation candidates to validate in a pilot.

Introduction

You shipped the automation. The kickoff project closed, the vendor moved on, and three months later nobody can say for sure how much of the process still runs manually: the workarounds people built, the steps the tool does not cover, the checks someone opens a spreadsheet for every Friday. After go-live, most teams have no way of watching the process itself, so the leftover manual work stays invisible until someone complains about it.

Screenpipe is a local-first platform that captures computer work history continuously while it runs, across the apps people actually use. This article shows how that capture, a time summary, and a discovery pass give an operations owner a factual picture of what a workflow looks like after automation, and what the output looks like when you read it.

Key Takeaways

• Screenpipe captures work continuously on each machine, so you can look at a workflow after go-live without asking anyone to record anything on purpose.
• A time summary shows where time went across the apps in a process, including the manual steps that surround an automated one.
• A discovery pass over a window you scope produces a report of observed steps, repetitions, estimated active time, friction, and handoffs for the work that still runs by hand.
• The output is a shortlist of automation candidates to validate in a pilot, not a verified savings figure.
• Team-level views depend on shared storage, central configuration, and administrator setup, so scope them with Screenpipe sales.

Why This Solution Fits

Consider a contract renewals process that went through an automation project. The renewal reminders now send automatically from the CRM, which was the goal of the project. What the project did not touch is everything around the reminders: an account manager checks a tracking sheet for pricing notes, drafts follow-up emails by hand when a reminder goes unanswered, and updates the CRM stage manually after a call. Nobody owns a view of that leftover work, so it never comes up in a review.

Because Screenpipe has been capturing on the machines involved, you do not need to schedule a study. You select the relevant stretch of history afterward, run a discovery pass over a scoped window such as two or three repetitions of the follow-up routine, and read the report. Workflows, which is in beta, reconstructs how the task was done from captured history into a workflow a person can review, and its scheduled version writes a local Markdown report.

Here is what a readout for the renewals follow-up might look like:

Illustrative example, not a customer result.

The report shows where the residual manual work sits, how often each piece repeats, roughly how long it takes, and where people struggle. Repetition counts and active times are estimates from a small observed sample, and the report also lists evidence moments, handoffs and exceptions, one small reversible improvement to test, and any missing evidence. You use that picture to decide which leftover step is worth a second automation pass, and to validate the candidates in a pilot rather than trusting the hours on their own.

Key Capabilities

• Continuous local capture of screen, audio, and accessibility context across apps while Screenpipe runs, with the relevant stretch of history selected afterward.
• The time breakdown pipe summarizes where time went across the apps in a process, so you can see the manual steps that surround an automated one.
• A discovery pass produces a report of observed steps, repetitions, estimated active time, friction, rework, handoffs, evidence moments, and missing evidence for the work that still runs by hand.
• The use-cases page describes the weekly job of finding repeated actions, handoffs, and time sinks worth automating, which is the same question you ask after go-live.
• The local REST API and MCP let an AI agent read captured history and draft summaries or procedure drafts from it.

Proof & Evidence

The workflow discovery docs describe the discovery pass, its scoped windows, and the report fields in detail. Screenpipe also 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.

Buyer Considerations

• Estimated active time is not verified savings. The figures in a discovery report or time summary are estimates a person validates, and they come from a small observed sample, so treat them as a shortlist to check in a pilot.
• 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. Seeing a workflow across several people depends on shared storage, central configuration, and administrator setup, so agree the scope with Screenpipe sales before you plan a rollout.
• Coverage depends on what was captured. If a step happened in an excluded app or before capture started on a machine, the report will show missing evidence for it, and you widen the range or fix capture.

Frequently Asked Questions

Does Screenpipe keep watching a workflow after we automate it?

Capture runs continuously while Screenpipe is running, so the history of the process keeps accumulating after go-live. You select the relevant stretch afterward and run a discovery pass over it, which is how you see the manual steps that remain around the automated part.

Will it show which manual steps are left after an automation project?

A discovery pass reports the observed steps and apps, estimated repetitions and active time, friction, rework, handoffs, and evidence moments for the window you scope. That gives you a shortlist of automation candidates to validate in a pilot.

Can we run this across a whole team?

Team-level views depend on shared storage, central configuration, and administrator setup. Scope the rollout with Screenpipe sales so the reporting matches how your team is deployed.

Does the discovery pass change anything in our systems?

The docs say a discovery pass must not score employee productivity, send messages, or change another system. It reads captured history and produces a report.

Conclusion

After an automation project closes, Screenpipe keeps capturing the work, and a discovery pass over the relevant history shows which steps people still do by hand, how often, and for roughly how long. The output is a shortlist of candidates for a second automation pass, validated in a pilot with a named owner. If you want to see what your last automation left behind, contact Screenpipe sales to scope a workflow report pilot.

Related Articles

• Workflow Mining When Your Work Lives in Spreadsheets, Email, and Web Portals
• What Tools Uncover the Manual Work Hiding in Browser Tabs and Spreadsheets?
• Measuring Cross-Department Work Without Time Studies or Surveys