How to Use the AI Workflow Suitability Check
Use actual task frequency, staff time, document volume, review requirement, systems and compliance sensitivity. The result is conservative screening guidance; AI Workflow Production still requires qualification.
Definition
Use actual task frequency, staff time, document volume, review requirement, systems and compliance sensitivity. The result is conservative screening guidance; AI Workflow Production still requires qualification.
Why it matters to the business
A diagnostic is useful when it makes the current operating condition more explicit before a buyer enters preflight or checkout.
How it works
Enter current-state information, read the result as decision support, and continue only to the package route the tool names.
Where it appears in real systems
The tools run locally in the current static site build and do not create a hidden production-system scan.
Common failure modes
- Optimistic target values are entered instead of current-state values.
- The output is treated as a guarantee.
- A tool result is used to bypass package preflight or qualification.
Implementation considerations
- Use current inputs.
- Keep arithmetic and heuristics transparent.
- Treat uncertainty as a reason for review or discovery.
When it is appropriate
Use the guide before the corresponding package preflight when the buyer wants to quantify or structure the problem.
When it is not appropriate
Do not use a self-reported diagnostic as a substitute for technical access, audit evidence or acceptance testing.
Relationship to BYFORCE
The guide supports the ai-workflow-suitability diagnostic and routes toward the ai-workflow-production package where appropriate.
Source basis
- website/data/diagnostics.json
- docs/website/BYFORCE_WEBSITE_EVOLUTION_ROADMAP_2026-09-24.md