OperixHow to use the checklist
Have operational staff and managers answer separately, then discuss differences. Assess a clearly bounded task such as “combine supplier CSV files into the monthly report,” not an entire department.
A score is not an automatic approval. Lower areas show preparation work such as standardization, data cleanup, or access design.
Five areas for setting priority
Use the same five areas as the free Automation Readiness Assessment to compare candidates and identify follow-up questions.
| Area | What to review |
|---|---|
| Repetition and volume | Frequency, case count, peak concentration |
| Time and impact | Active work, waiting, rework, customer or control impact |
| Rule clarity | Decision conditions, exceptions, and owners |
| Data readiness | Format, completeness, consistency, and system of record |
| Integration readiness | APIs, files, access, licensing, and operating constraints |
Areas 1 and 2: Repetition, volume, time, and impact
Separate monthly volume, peak periods, time per case, waiting, and rework. A short task may still be valuable when many employees repeat it daily.
For high-impact errors, prioritize reconciliation, approval, audit logs, and recovery alongside savings. The question is often where human control should remain.
Areas 3 and 4: Rules and data
Even a documented procedure may contain frequent judgment. Record conditions, reference information, decision owners, and evidence before automating.
Paper, images, free text, inconsistent names, and missing values may make input improvement or master-data work the first priority.
Area 5: Integration and operating constraints
Confirm whether each system offers APIs, files, email, or only screen interaction. Screen-dependent automation needs monitoring and recovery for layout changes.
Terms of use, permissions, concurrency, licensing, maintenance windows, and personal information affect feasibility.
Ten questions for each candidate
Use the same questions for every candidate and attach evidence such as counts, procedures, error records, and sample files.
- How often is the work performed?
- How many cases are processed?
- How much active and waiting time is involved?
- What is the impact of an error?
- How clear are the decision rules?
- How many exceptions occur?
- Are inputs structured and consistent?
- Is there a reliable system of record?
- How can systems exchange data?
- Who will own operation and changes?
What the priority meeting must decide
For leading candidates, agree the scope, owner, evaluation period, success and stop conditions, required data, and how cost will be estimated. Leave room to compare implementation methods through a prototype.
The assessment does not guarantee return or feasibility. Confirm system behavior, exceptions, information controls, operating responsibility, and cost before the final decision.
References
- Information-technology Promotion Agency, JapanCybersecurity guidelines for SMEs, version 4.0 ↗
- Ministry of Economy, Trade and IndustryDX guide for small and medium-sized enterprises ↗