trionTalk to Trion
Skip to calculator

Workflow readiness

Use evidence from real work to answer each question. The checklist highlights preparation gaps; it cannot establish technical feasibility.

Local calculation · no sign-up

Your inputs

Illustrative inputs
Someone owns the operating rules and the outcome.
Review actual messages, documents and required fields.
An API, supported integration or approved workflow with the needed permissions.
Know who handles missing, conflicting or unusual information.
The steps and rough volume have been observed.
Use 0 if no recurring work has been recorded.

REVIEW THE ASSUMPTIONS

6 of 10 preparation points.

Checklist points
6 / 10
Observed items / month
300
Areas to investigate
3
An accountable process ownerYes · 2 points
Usable, consistent inputsPartly · 1 point
A permitted system access routePartly · 1 point
Documented exceptions and a review pathNo · 0 points
A repeatable process and measured volumeYes · 2 points
  • Next check: usable, consistent inputs.
  • Next check: a permitted system access route.
  • Next check: documented exceptions and a review path.
  • Equal weighting is a planning convention: Yes = 2, Partly = 1, No = 0. The points are not a feasibility probability or a promise that an integration can be built.
  • Even with 10 points, inspect real examples, system permissions, security requirements and operating exceptions before scoping a pilot.

The formula

Five checks, equally weighted. Yes = 2 points. Partly = 1 point. No = 0 points. Maximum = 10. Recorded volume provides context and does not add points.

How to choose a process to automate

Example PNGPlanning checklist. It does not measure a feasibility probability.