How to Prepare for an AI Readiness Assessment

Prepare for an AI readiness assessment by defining the next decision, locating the evidence that could change it and making the right people available to explain that evidence. Preparation should make the organisation understandable without pretending that unresolved problems have already been fixed. A polished presentation is less useful than a clear account of the proposed task, current work, uncertain sources and decisions that need an owner.

This guide is for Saudi project sponsors and operational coordinators arranging an assessment. Its illustrative case is a research consultancy considering an internal expert-profile assistant. The proposed assistant would assemble a reviewable profile from authorised records for a project manager. It would not invent credentials, decide employment eligibility, disclose confidential assignments or contact experts automatically. The preparation process keeps those boundaries visible from the first meeting.

Write the decision sentence before collecting documents

State what the assessment should enable someone to decide. For the consultancy, the question might be whether a restricted trial can assemble supported expert profiles for internal project planning, and which conditions must be resolved first. That is more useful than asking whether the firm is ready for AI in general. It identifies the workflow, audience and proposed next step.

Add the decisions outside scope. The assistant will not select the best expert, infer availability from old assignments or treat a published biography as permission to reuse every underlying project detail. These exclusions help the assessor request relevant evidence. They also prevent an attractive demonstration from expanding the task without an explicit business decision.

Use the meaning of an AI readiness assessment if stakeholders are expecting a certification or completed implementation. Agree the intended deliverable: a supported next-step conclusion, its evidence and limitations, and the work needed to resolve material gaps. Preparation is easier when everyone understands what the assessment can reasonably establish.

Describe the current work through one real sequence

Choose a recent internal request and explain how the team currently handles it. Who receives the project brief? Where do they look for relevant expertise? Who checks whether a biography is current? How are restricted assignments excluded? Who accepts the final profile? The walkthrough should describe actual practice, including informal handoffs, rather than an ideal process that no one follows.

Use an authorised, suitably minimised example. The assessor needs enough context to understand the work, not unrestricted access to every expert record. If a real example cannot be shared, prepare a clearly labelled synthetic sequence and explain which operational details it preserves. Do not present synthetic material as evidence that the real sources already meet the same conditions.

Record where the current process relies on a person's memory. A coordinator may know that an old assignment cannot be mentioned externally or that two similar names refer to different experts. These are important dependencies. The assessment should determine how that knowledge becomes a usable rule or source decision, rather than assume that an AI system will infer it safely.

Create a short evidence index instead of a document dump

An evidence index helps the assessor understand what exists before any sensitive material is shared. List the source, owner, relevant date or revision, intended use, access status and known limitation. A link to an inaccessible folder is not equivalent to usable evidence. An available file is not automatically authorised for the proposed purpose.

Illustrative preparation index for an expert-profile assistant

Material	Why it matters	Preparation note
Approved biography	Defines currently supported public profile statements	Identify owner, revision and permitted use
Internal expertise catalogue	Shows task-relevant categories and identity fields	Record duplicate names and uncertain definitions
Assignment records	May support experience claims	Mark confidentiality and reuse questions without assuming permission
Profile request example	Shows the project manager's actual information need	Remove unrelated personal and commercial details
Accepted profile example	Shows current review expectations	Explain who accepted it and under which conditions
Rejected or disputed example	Reveals a boundary the assistant must respect	Preserve the reason, not just the corrected final version

The index can be short. Its value is traceability, not volume. Use data catalogue and lineage readiness when the assessment needs deeper relationships among sources. For preparation, it is enough to identify where a claim originates, who can explain it and what remains uncertain.

Select examples that expose meaningful differences

Do not provide only the cleanest biographies. For an illustrative diagnostic selection, prepare eight profile examples: two current approved records, two older records, two containing restricted assignment references and two with bilingual name variants. These categories are deliberately chosen to expose different conditions. They are not a representative statistical sample or a claim about the proportion of problems in the consultancy.

Explain the selection rationale and any exclusions. If the proposed trial includes Arabic and English profiles, show how identity and material claims appear in both languages. If some source systems cannot yet be accessed, record that limitation instead of filling the gap with a more convenient source that may have different authority.

Ask the assessor to confirm whether the selection can support the proposed conclusion or needs adjustment. Sample quality and representativeness can guide that discussion. The preparation team's job is to make relevant variation visible; it should not quietly decide that every difficult case is outside scope simply to improve the appearance of readiness.

Keep original evidence separate from preparatory corrections

Preparation may reveal obvious errors, such as a duplicate name or an outdated role description. Correcting them can be useful, but preserve what changed and why. If the assessor only sees the cleaned version, they may miss an operational dependency that will recur after the assessment. A one-time cleanup does not establish a maintained process for keeping profiles current.

For the consultancy, record whether an updated biography came from the expert, the responsible manager or an informal assumption. Keep the earlier source revision available through an appropriate controlled route when it is relevant to the assessment. The purpose is to explain source history, not to create unnecessary copies of sensitive material.

Do not pre-resolve genuine disagreements just to simplify the meeting. If an internal record claims a capability that the approved biography omits, show the conflict and identify who can decide its permitted use. Source authority and freshness addresses that question directly. A visible uncertainty gives the assessor something concrete to evaluate.

Agree information handling before sharing the evidence

Decide which materials can be shared, with whom, through which environment and for what purpose. Start with the minimum detail needed to assess the question. A profile-readiness exercise may not need personal contact details, compensation information or complete confidential project files. Record material that cannot be shared and consider whether a controlled view, metadata or a synthetic example can answer the initial question.

The NIST Privacy Framework is a voluntary resource for organising privacy-risk work. It does not approve a particular data transfer or establish Saudi compliance. For this assessment, the practical preparation task is to make the proposed information use and unresolved permissions visible to the organisation's responsible reviewers.

Confirm the actual sharing route rather than assuming an assessor's preferred tool is suitable. Do not send credentials, unrestricted exports or unrelated personal records to make access easier. If evidence requires restricted access, agree a proportionate review arrangement. Preparation can proceed with an index and explicit limitations while the relevant permission questions are resolved.

Make the people who can answer the questions available

Invite people according to the decisions they can explain, not only their seniority. The project manager understands the profile's intended use. The catalogue owner understands identity and source conventions. The person responsible for approved biographies can explain current claims. A privacy or legal reviewer may be needed for specific reuse questions, while IT can explain the intended access environment.

One person may cover several roles. Identify the questions each participant can settle and the questions they must refer elsewhere. An interview with a helpful employee should not be mistaken for an authorised decision about confidential assignments. Record unresolved questions and the role that can close them rather than relying on informal consensus in the meeting.

Use ownership and evaluation readiness to check that owners have both authority and availability. If a key person cannot attend, arrange a focused follow-up or provide their approved written position. Do not allow the assessment schedule to convert absence into assumed agreement.

Prepare a workshop that follows the decision

A meeting agenda should move from purpose to evidence to unresolved conditions. An illustrative ninety-minute session could allocate five minutes to the decision, fifteen to the current workflow, twenty-five to source examples, twenty to acceptance and authority, fifteen to gaps and ten to next actions. The allocation totals ninety minutes and is a planning example, not a promised assessment duration.

Send the decision sentence, evidence index and specific questions beforehand. Participants should know which source or decision they are expected to explain. Avoid spending the whole session on general AI education if the purpose is to inspect readiness evidence. A brief orientation can be arranged separately when it is needed to make the discussion productive.

Leave room for an inconvenient finding. If a key source cannot be interpreted, the meeting may need to narrow the next step rather than complete every agenda item. The useful output is an agreed record of what the evidence supports and what must happen next, not proof that every scheduled slide was presented.

Use an evidence request that explains why the item is needed

A request such as “send all your data” creates unnecessary work and may create avoidable information-handling problems. Ask for a specific item linked to a decision. State the minimum content, intended reviewer, sharing route and acceptable alternative if the material cannot be provided. This makes the request easier for the source owner to assess and fulfil.

Question: Can an internal profile state this experience claim?
Requested evidence: One authorised record supporting the claim and its permitted use.
Owner: The role responsible for the relevant biography or assignment record.
Minimum content: Identity match, supported statement, revision and use limitation.
Sharing arrangement: The agreed restricted review environment.
If unavailable: Record the gap and propose a controlled explanation or synthetic example.

This illustrative request is not a legal permission form. It helps the team identify the evidence and the appropriate decision owner. If the source owner says the material cannot be used for the proposed purpose, retain that restriction. The assessment should not treat difficulty obtaining evidence as permission to use a less controlled route.

Document a baseline without turning estimates into benefits

Describe how the current task is performed and which observations are available. The consultancy may know the number of profile requests, the usual review steps and common clarification reasons. If handling time is only estimated, label it as an estimate and record who supplied it. Do not turn a guessed current duration into a precise future savings claim.

Separate waiting time from active work. A profile may take several days to complete because an owner is unavailable, even if drafting takes a short time. An AI drafting assistant may not remove that waiting dependency. The assessment needs the distinction so that the proposed workflow addresses the actual constraint rather than the most visible step.

Prepare the criteria for a useful later comparison: comparable requests, accepted quality, source preparation, review and corrections. The readiness assessment can establish what should be measured and whether the baseline evidence is usable. Demonstrated productivity or commercial return requires a subsequent evaluation, not merely a well-prepared workshop.

Bring open questions in a form that can be resolved

Turn broad concerns into decision questions. “Our data is messy” becomes “which source governs when an approved biography and an internal assignment record disagree?” “Staff may resist” becomes “who will review the profile and how much time is available?” “Arabic could be difficult” becomes “who can verify the source and output conditions in both languages?”

For each question, record why it matters, the evidence already available, the owner and the consequence of leaving it unresolved. The assessment can then distinguish a prerequisite from a useful improvement. Some questions may be outside its scope and require specialist review. Record that boundary rather than expecting one engagement to settle every technical, commercial and legal issue.

Preserve disagreement in the notes. Two owners may have different but legitimate objectives for the profile. One wants a concise project-planning summary; another expects a public marketing biography. Those uses require different permissions and acceptance criteria. The preparation process should surface the difference before the assessor evaluates an imaginary compromise that neither owner will use.

Agree deliverable acceptance and the handover

Before the assessment starts, define how the customer will recognise a useful result. Ask for the stated decision, evidence examined, limitations, material findings and a conclusion linked to the proposed next step. For remaining work, request an owner, intended evidence and acceptance condition. Avoid making acceptance dependent on a positive readiness score.

Agree who will review factual accuracy and who will accept the decision pack. A source owner can correct a misdescribed record without being able to approve a wider trial. Keep those reviews distinct. Ensure that a condition appearing in detailed findings is also visible in the executive conclusion, so a shortened handover does not erase the limitation.

Use the readiness decision pack to structure the expected output and a remediation backlog for the follow-up. Preparing the handover early reduces the chance that the organisation receives a report but has no owner able to act on it. The assessment should end with a usable decision and an explicit route for resolving what remains.

Check that prepared evidence is actually reviewable

Assign one coordinator to maintain the preparation status. Separate an item requested from an item received, and an item received from one that the intended assessor can review. A file may arrive without its relevant attachment, a link may require an unavailable account or the supplied revision may not match the example discussed. These are practical preparation findings, not reasons to mark the source as complete.

For the expert-profile case, the coordinator can perform a short handover check with the source owner. Confirm the identity of the record, the included pages, the relevant revision and the allowed review route. Check that any masking preserves the condition the assessor needs to understand. Removing a date or restriction may protect information while also making a particular readiness question impossible to answer; record both effects.

Keep a visible distinction between what is ready for review and what remains pending. A source owner should be able to correct the status without rewriting the entire assessment brief. When the evidence changes, tell the assessor which item changed and whether earlier observations may need reconsideration. This avoids several people working from different versions while believing they share the same evidence.

The coordinator's role is to make the handover reliable, not to certify the contents. Subject owners still confirm meaning and permission. A small, accurate preparation register is sufficient if it lets the team locate the right material and understand the remaining limitation.

Know when to stop preparing and let the assessment examine the gaps

Preparation is complete enough when the decision is understandable, relevant evidence can be located, sharing conditions are clear and the right owners can explain the unresolved questions. It does not require perfect data, complete remediation or a working prototype. Continuing to polish the evidence can delay the very assessment intended to identify what matters.

Send a concise readiness-for-assessment note: confirmed purpose, available material, known restrictions, participants and open dependencies. Make any timing assumption explicit. If the key source is unavailable, the assessor may still review the decision and evidence needs, but should not claim to have examined that source. A narrower honest start is more useful than pretending access is complete.

For a coordinated engagement, use Enterprise Data & AI Readiness. A readiness enquiry can begin with the decision sentence and a short evidence index, even when some items remain uncertain. These materials help establish a proportionate scope and make the first discussion concrete without requiring an unrestricted data transfer.