ITF Digital

Where AI earns its place in your operation

A short assessment that ranks the tasks in your operation where AI earns its place, names the ones to keep with a person, and drafts rules for the AI tools your staff already use.

Duration
One to two weeks for a single entity
Output
Use-case register · keep-human list · AI use policy draft · pilot specification
Interviews
On site across Saudi Arabia, or remote
Pilot specification
Written for any competent supplier to build

AI readiness is a one to two week assessment of your work, not a presentation about AI. We list the repeated tasks, score each on frequency, rule clarity, cost of an error and data sensitivity, then hand you a ranked register, a keep-human list, a staff AI use policy and one pilot specification.

A two-axis chart. Cost of an error runs from low on the left to high on the right, and how often a task runs rises from monthly at the bottom to daily at the top. The upper left corner, frequent and cheap to get wrong, is marked as the place to pilot. A band on the right, where an error is costly, is marked keep human. Five illustrative tasks are plotted as numbered points, and a key at the edge marks with a lock the tasks whose data cannot leave.PILOT HEREFREQUENT, LOW COSTKEEP HUMANHIGH COST OF ERRORDAILYWEEKLYMONTHLYHOW OFTEN IT RUNSLOWHIGHCOST OF AN ERROR12345TASKS, ILLUSTRATIVE1RETYPING DELIVERY NOTES2REPORT NARRATIVE3PROCEDURE QUESTIONS4SUPPLIER APPROVAL5GRADING A FINDINGDATA CANNOT LEAVETHE RULETHE VERDICT COMES FROM THE SCORE
Where each task landsIllustrative tasks. Yours come from interviews.Swipe to pan
  1. 01 Enquiry
  2. 02 Systems audit
  3. 03 Specification
  4. 04 Build
  5. 05 Pilot
  6. 06 Deploy
  7. 07 Handover
  8. 08 Support

Where AI earns its place in your operation sits at step 3 of the build cycle. You receive a written specification and scope.

01

Your staff are already using AI

If nobody has written rules for AI tools, somebody has probably pasted a client document into a public chat tool to write a report faster.

Nobody told them what may go in. The first job of the assessment is finding out what is being used, by whom, for what, and what data is going into it.

The point is to write rules people can follow, not to discipline anyone.

02

Four questions for every task

Each repeated task is scored the same way: how often it runs, whether its rules are written down, what an error costs, and whether its data can leave your environment. The rows below are illustrative. Yours are built from interviews with the people who do the work.

TaskHow it scoresVerdict
Retyping supplier delivery notesDaily. Rules written. An error is cheap and caught at invoicing. Data can leave.Pilot candidate
Drafting the narrative in a monthly client reportMonthly. Rules partly written. Medium cost, and a person reviews. Data can leave.Candidate, with review
Answering staff questions about proceduresDaily. Rules written if documents are controlled. Medium cost. Data depends on hosting.Candidate after document control
Deciding whether a supplier is approvedWeekly. Rules written. High cost. Data stays in.Keep human
Grading an internal audit findingMonthly. Rules written. High cost, because it is a conformity call. Data stays in.Keep human
03

The assessment pack

01

The tool inventory

What is in use now, by whom, and with what data.

02

The use-case register

Every repeated task scored on the four questions and ranked.

03

The keep-human list

The tasks to keep with a person, with the reason against each line.

04

The AI use policy draft

Two pages, ready for your own approval route.

05

The pilot specification

The top candidate, specified so any competent supplier could build it.

06

The management walk-through

A session with your management that goes through the register line by line.

04

How the one to two weeks run

  1. 01

    Inventory the tools

    Which AI tools are in use, by whom, for what, and what data goes into them.

  2. 02

    Interview the functions

    The people who do the work list the tasks they repeat and the rules they follow.

  3. 03

    Score every task

    Frequency, rule clarity, cost of an error and data sensitivity, scored the same way for each.

  4. 04

    Rank and draw the line

    The register is ranked, and the keep-human list is written with the reason against each line.

  5. 05

    Draft the policy

    Two pages your staff can follow, drafted for your approval route.

  6. 06

    Specify one pilot

    The top candidate written up as a specification any competent supplier could build.

  7. 07

    Walk through it

    A session with your management on the register, the keep-human list and the pilot.

05

An AI plan, due within the quarter

An engineering services company with its office in Khobar and crews on client sites is asked by its head office for an AI plan within the quarter.

The assessment starts with interviews across its main functions and an inventory of the tools already in use. It finds engineers pasting client drawings into a public chat tool to draft daily site reports.

Tasks are listed and scored. The top candidate is drafting daily site report narratives from the structured site data the crews already capture, with the site engineer approving each report. Approving timesheets and signing off inspection results go on the keep-human list, and the policy draft names which client documents stay out of unapproved tools.

The company holds the tool inventory, a ranked register, the keep-human list, a policy draft ready for approval and a pilot specification it can take to any supplier.

06

Inside the pack

The tasks your people should keep

This is often the most useful page in the pack. It names the tasks where the work should stay with a person and says why. A board that has seen this list trusts the rest of the register more.

  • Conformity decisions
  • Approvals of money
  • Disciplinary decisions
  • Safety-critical instructions
  • Anything a regulation assigns to a competent person
  • Any output nobody will read before it is used
07

What a board usually asks

Q01

Is this the same as ISO/IEC 42001?

It is a practical assessment of your tasks and tools. An AI management system to ISO/IEC 42001 is management-system work, and ITF Consult covers it on its own page.

Q02

Will you then try to sell us a build?

We will offer to build the pilot. The specification is written so you can take it elsewhere, and a readiness assessment that only ever recommends its author is worth little.

Q03

Do we need our data ready first?

No. The assessment is about tasks and rules. Data questions are part of what it finds.

Q04

Can you train our staff on safe use?

ITF Training runs a course on AI and digital tools in operations, built around drafting, checking and approving. It pairs well with the policy.

Q05

What drives the cost?

The number of functions interviewed, the number of sites, and whether the policy must be bilingual.

Answer the board with a register

Book the assessment and take your board a ranked register, a keep-human list and one pilot it can approve.

Book an AI readiness assessment