
Who Gets the Final Say? A Practical AI Workflow Approval Plan
A practical approval plan for an AI business workflow
“Let the system handle it” is easier to evaluate when you decide what “handle it” means for one specific task. Before enabling a workflow, draw a clear line between what the system may prepare, what it may do within your chosen permissions, and what should wait for your approval.
Here’s a practical way to set that line for a customer-support inquiry. This is a planning example—not a claim that every step is available in every setup.
Start with one ordinary request
Imagine a customer asks a question through a connected support channel. The goal is to get the inquiry to an appropriate response while keeping the conversation’s relevant context together.
Write down the outcome you want: for example, “Prepare a response using the available business context, and let a person review it before it is sent.” That gives you a specific starting boundary rather than a broad instruction such as “automate support.”
Divide the workflow into three decisions
| Workflow step | A useful boundary to define | What to check | |—|—|—| | Understand the inquiry | May the system use the connected conversation and relevant business context to prepare work? | Which channel and information are connected, and what context is available? | | Prepare a response | May it draft or organize a possible reply? | Is the requested work supported in your configured setup? What should happen when the answer is unclear? | | Send or escalate | Should a person review the response, or may an authorized action proceed? | Which actions are eligible under your permissions, and which should wait for approval? |
The point is to set each boundary deliberately. Permission to prepare a response does not automatically mean permission to send it. Likewise, a workflow that needs information or an authorization it does not have should not be treated as ready to proceed.
Choose a starting level of autonomy
Foreshadow describes an autonomous business system spanning marketing and growth, sales support, customer service, bookkeeping, controller work, and CFO intelligence. Its website’s autonomy experience illustrates choices such as “Review first” and “Not running,” as well as operating modes labeled “Balanced,” “Guided,” and “Autonomous” where authorized. The site identifies that experience as an illustration, not live account settings.
For the example inquiry, a business might begin by requiring review before a customer-facing response is sent. The useful question is not whether one mode is universally best; it is whether the chosen boundary matches the work, the connected tools, and the permissions actually configured for that workflow.
Write down the approval rule
A concise rule makes expectations easier to discuss and test. For example:
> Prepare a response from the available customer conversation and business context. Hold it for review before sending. If the needed context is missing or the appropriate response is unclear, bring the question back for a person to decide.
This is a sample policy for a buyer to adapt—not a description of a default Foreshadow rule. Make the boundary explicit before enabling any customer-facing action.
Test the boundary with a few cases
Use a normal inquiry, one with missing context, and one that needs a judgment call. For each case, decide what a good outcome looks like: prepared work, a request for review, or no action until the necessary information or permission is available. Then check whether the configured workflow behaves as intended before expanding its scope.
Keep the first measure close to the workflow: for example, whether the intended review step occurred. That helps you evaluate the approval process itself without confusing it with broader outcomes such as revenue or customer growth.
Bring this plan to your setup
You can start with one workflow and the approval rule that matters most to your business. Foreshadow offers a free business growth audit and a 7-day free trial of its autonomous business system. Use the audit to discuss where coordinated work could fit; explore the trial when you’re ready to configure the system around your goals and permissions.
