An AI company wants to record your team's workflows: what to consider

What workflow recording requests usually involve#

Workflow recording requests ask to capture how your people actually do their jobs, usually so a developer can train or test AI agents that operate business software or follow procedures. The capture method determines most of the risk.

Requests sometimes arrive informally, through a vendor whose tool your team already uses or a startup offering to pay staff directly. Treat each one as a company decision rather than an individual one, because the recordings will show company systems and company information.

Employee consent and notice come first#

Employee consent for workflow recording should be informed, voluntary and documented, because the recordings are new records about identifiable people. Employees should know what is captured, who receives it, what it will be used for, how long it is kept and that declining carries no penalty.

Workplace monitoring and recording laws vary by state, and some require notice before electronic monitoring or consent before audio is recorded. Which of these may apply depends on where employees work and what is captured, so review the plan with employment counsel before anyone is recorded. Existing handbooks and acceptable-use policies were usually written for internal monitoring, so check whether they say anything about a third party receiving the footage.

Consent terms should also cover what happens when an employee later withdraws or leaves the company: whether recordings already made stay in the licensed package, or are removed before delivery if they have not yet been released.

Screens show far more than the task#

Screen recordings capture whatever is on the display, so customer names, inboxes, chat pop-ups, billing records and calendar entries appear unless the environment is built to prevent them. Redacting video after the fact is slow and imperfect, so prevention beats cleanup.

Capture software deserves its own security review. An agent installed on employee laptops can see whatever those laptops can, so IT should approve the tool, confine it to the designated workspace and confirm it is fully removed when the sessions end.

• 1Record in a sandbox or training environment populated with past, de-identified records, not in live production systems.
• 2Use dedicated test accounts with no access to real email, chat or payment tools.
• 3Limit capture to an allowlist of applications and block password managers and personal browsers.
• 4Give employees a visible pause control and a way to flag and delete a segment.
• 5Review a sample of recordings internally before anything leaves the company.

Trade secrets and know-how ride along#

Recordings of skilled work expose the judgment that makes your team good: how an estimator prices a difficult job, how a dispatcher reorders a day, how a support lead decides to escalate. That know-how is what makes recordings valuable to a developer, and it may also be information you protect as a trade secret.

Decide which workflows you are willing to show at all, and keep pricing logic, supplier terms and proprietary methods out of scope unless the license addresses them. Permitted use, confidentiality, limits on sharing with third parties and any exclusivity should be written down before capture begins, not negotiated after the footage exists.

Who gets paid, and for which hours?#

Compensation for workflow recording should flow through the company and its normal payroll, not through side arrangements between employees and the AI company. Direct payments to staff can create conflicts of interest, confusion about who owns the recordings and tension with employees' confidentiality and invention assignment agreements.

Time spent recording at the company's request is generally work time. For non-exempt employees, wage-and-hour rules may apply to that time, and sessions that run after hours may count toward overtime like any other work. Agree in advance whether participating employees receive anything extra and how that is decided, so nobody feels pressured to volunteer.

A checklist before you say yes#

A workflow recording request is ready for a decision only when every item below has a named owner and a written answer.

• 1Purpose: what the AI company will build, and whether recordings will be used only for that.
• 2Scope: which roles, tasks and applications are in, and which are out.
• 3Consent: written, voluntary employee consent with a no-penalty opt-out.
• 4Environment: a sandbox or de-identified data instead of live customer records.
• 5Capture software: who installs it, what it can access and how it is removed.
• 6Ownership: the company licenses the recordings rather than handing over ownership.
• 7Retention: how long the buyer keeps raw footage and how deletion is certified.
• 8Pay: how participating employees are compensated through payroll.
• 9Approval: who signs for the company and who reviews recordings before release.

Illustrative: a roofing contractor weighs an estimating capture request#

Illustrative: a fictional commercial roofing contractor is approached by an AI developer that wants to record its estimators using aerial measurement software, spreadsheets and the company's job management system to price reroof projects. The developer offers to pay estimators directly for each recorded session.

The COO declines direct payment and live capture. Instead, the company builds a training workspace loaded with closed jobs from earlier years, with customer names and addresses removed, and invites estimators to volunteer for sessions paid through regular payroll. Pricing multipliers and supplier price lists stay out of scope.

The company also offers to license its historical estimates, change orders and job outcomes, which show the same decisions without any new recording. The developer takes both packages, and the contractor keeps control of what each one contains.

How SourceX looks at recorded workflows#

SourceX focuses on records companies already hold, such as job histories, support conversations and engineering workflows, because they show real decisions and outcomes without asking employees to perform for a camera. If a buyer's interest turns to new capture, the same SourceX five-step transaction applies, and new recordings would need their own rights and consent review before anything is agreed. The supplier approves every step before anything is delivered.

The questions are the same in either case: what the records show, who appears in them, what rights the company holds and who approves release. Whatever proceeds is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization.