You know which AI subscriptions the business pays for. You may not know which spreadsheet sends information to an assistant, which employee-built workflow runs every morning, or which shared account still belongs to someone who changed roles.
The invoice list is a start. It is not an inventory of the work.
Before you write more AI rules, find out what exists. Record the job, the owner, the information involved, the action it can take, and how to pause it. A shared sheet can be enough to begin.
Count Workflows, Not Just Products
One tool can support several very different activities. Drafting a meeting agenda and publishing a customer response may use the same provider, but they have different consequences and review needs.
Give each recurring workflow its own row. Include manual use when information is routinely copied into an AI tool, as well as connected automations that run on a trigger or schedule.
Ask about small personal workarounds without assuming bad intent. Someone may have built a useful summary because the official process took too long. You need to understand that unmet need alongside the access or data problem.
If the first conversation sounds like a trap, you are likely to receive a very tidy and incomplete inventory.
Use the Recent Research Carefully
Pax8’s October 12 SMB AI Pulse release reports that 35% of AI-engaged respondents discovered unapproved AI tools, workflows, or agents in their operations during the preceding six months.
This is vendor-sponsored survey evidence, not a count of every small business. The report surveyed business leaders across the United States, United Kingdom, Germany, and Sweden. The finding is a reason to ask better inventory questions, not proof that the same percentage applies to your workplace.
Your own check may uncover nothing unexpected. It may uncover a useful workflow that needs a proper owner. Either result is more actionable than repeating an alarming headline in a team meeting.
Build the First Inventory
Use a location the responsible team can access. Do not store credentials or secret keys in the inventory. Record where approved access is managed instead.
| Field | Question to Answer |
|---|---|
| Workflow Name | What recurring job does this perform? |
| Owner and Backup | Who understands and maintains it? |
| Tool and Account | Which approved account or workspace runs it? |
| Trigger | Manual request, schedule, event, or another workflow? |
| Input | What information does it read, and from where? |
| Output or Action | Draft, analysis, record update, message, or publication? |
| Connected Systems | What else can it access or change? |
| Review Point | Who checks or approves the result? |
| Cost | Subscription, usage basis, and billing owner |
| Pause Method | How can an authorized person stop it? |
| Last Review | When was it tested, and what remains unresolved? |
If a field is unknown, write “unknown” and name the person investigating. An honest gap is useful. A guessed permission level is an invitation to learn something unpleasant during the next incident.
Ask People to Show One Run
A demonstration often reveals details a tool list misses. Ask the owner to walk through a normal run using fictional or approved sample data. Where does the information come from? What happens after the output appears? Who acts on it?
Look for copies and exports. A workflow might read an approved folder, create an intermediate file, and send a summary to a personal inbox. Each destination matters even if the final output looks harmless.
Ask about schedules and exceptions. Does it run while the owner is away? What happens when a connection expires? Does a retry create another message or another record?
The purpose is to document behavior, not to collect people’s passwords or rummage through private accounts. Use the business’s authorized access and review process for any deeper inspection.
Prioritize by Information and Consequence
Do not give every row the same urgency. Start with what information the workflow handles and what it can do without another person.
A draft made from public information differs from an automated update to a live customer record. A private note differs from a published statement. Both may use AI, but their review priorities should reflect the possible impact.
Mark the issues that need prompt attention under existing procedures: sensitive information in an unapproved place, unknown access, unattended consequential actions, or no authorized way to stop the workflow.
Then identify improvement work. A safe but undocumented draft process may need an owner, a source check, and a short instruction card. Do not turn every gap into an emergency or every useful workaround into a permanent exception.
Decide What Happens to Each Workflow
Use a small set of decisions: keep with an owner, improve before wider use, pause pending review, or retire through the approved process. Record the reason and next action.
For a useful employee-built workflow, ask what would make it supportable. That may include a business-owned account, a backup owner, clear inputs, an approval step, and a tested pause method.
For something being retired, check dependencies first. Another task may rely on its output. Do not delete access or switch off a production workflow casually because its name looks unfamiliar.
Document the replacement or fallback. The business problem will still exist after the automation stops, and somebody will still need to do the work.
Test Ownership Before the Owner Is Away
Ask the backup to explain the workflow, locate its approved instructions, and show how they would recognize a failed run. Use a controlled test that does not send live messages or alter records unexpectedly.
Check that pausing the trigger prevents new runs and understand what happens to work already in progress. Different tools handle that differently. Follow the provider’s current documentation and your authorization rules rather than assuming a stop button reverses completed actions.
Keep the manual fallback accessible. A workflow with one knowledgeable owner is a fragile dependency even when it has behaved perfectly so far.
Keep the Inventory Connected to Change
Add a row when a new recurring use begins. Update it when the owner, account, connected system, source information, or permitted action changes. Include it in the existing access and offboarding process where appropriate.
Choose a review cadence that matches the workflows’ impact and rate of change. Also review after an incident or meaningful change. A calendar reminder is helpful; it is not a substitute for responding to new information.
For instructions on making one task repeatable, see Your AI Needs Standard Work Too. The inventory tells you what exists. Standard work tells people how an approved task is performed.
Start with three workflows you know are running. Find the owner, the data path, the action boundary, and the pause method for each. You can write better rules once you can see the work those rules need to cover.























