Guide
Prepare an AI workflow for production.
Check approved actions, test results, human handoffs and release responsibilities. Record gaps and decide the scope of an AI pilot.
Review what the agent may do, whether tests support those actions and who handles failures. FieldSignal prepares the workflow evidence, rules and draft tests for this review. Your engineering and operations owners must also complete their technical release checks.
Download the production-readiness checklist. Record evidence and an owner for each check. The template requires no FieldSignal account.
Bring the implementation and its evidence.
Identify the agent version, proposed release scope, approved policy, connected systems and test results. Include routine cases, exceptions and previous failures. If tests have not run, record that as a gap.
Check five things before release.
- Permission to act. Have the process owner approve the actions, limits and required approvals. Confirm the permissions in each connected system.
- Evidence from tests. Run cases where the agent may proceed and where it must stop. Inspect tool actions and saved system changes as well as the response. Keep some cases out of development and use them only for testing.
- Failure handling. Test missing information, conflicting records, unavailable tools and uncertain action results. Check who receives requests for help and how they resume the work.
- Technical release checks. Assign owners for security, data handling, access controls, capacity, cost, monitoring and recovery. Record their evidence and decisions alongside the workflow tests.
- A controlled first release. Define the pilot users, permitted actions, success criteria and stop conditions. Name who monitors it, can disable actions and handles work after a stop.
Record the release decision.
List the evidence reviewed, failed or unrun tests, untested case types and unresolved decisions. Name the owner and required action for each gap.
The responsible owners decide whether to proceed within the stated scope, narrow it or resolve gaps first. Passing a workflow test suite does not establish that every production risk is covered.
Use the acceptance-testing guide to define checks. See the replacement example for approvals, failed actions and pilot criteria.
Resolve the missing workflow evidence.
If the rules or expected actions are unclear, ask FieldSignal to review the workflow. If you already have approved records and rules, use the task brief and examples to draft tests.
Implementation, system connections and ongoing operation require a separate agreement when FieldSignal does that work.