Requirements · AI for data and analytics

Data readiness requirements before adopting AI analytics

Last updated 25 October 2026 · 2 sources listed · Reading time about 3 minutes

Short answer

Readiness means data that is findable, documented, access-controlled, reasonably clean and owned. Before adopting AI tools, inventory sources, classify sensitivity, fix permissions, define key metrics, document tables, set quality checks and agree ownership. Skipping these steps turns every AI feature into a faster way to surface existing mess.

Who this is for: A data or IT leader assessing whether company data is ready for AI-powered analytics, search or forecasting projects.

What to evaluate

Inventory and ownership
Unknown sources and unowned tables produce unaccountable answers.
How to check: Maintain a catalog with owners, purposes and update schedules.
Sensitivity classification
Tools must treat personal and confidential data appropriately.
How to check: Classify datasets and apply handling rules including masking where needed.
Access control hygiene
AI search amplifies oversharing.
How to check: Review who can read each source and remove stale or broad access.
Documentation and definitions
Tools and people need to know what data means.
How to check: Provide descriptions for tables and columns and a glossary of metrics.
Quality monitoring
Silent errors undermine every downstream answer.
How to check: Implement checks for completeness, duplicates, ranges and freshness with alerts.
Lawful use and purpose
Using personal data for new purposes can breach data protection rules.
How to check: Confirm lawful basis and purpose limits with privacy staff for each use.
Retention and lineage
You must know where data came from and when it should be deleted.
How to check: Record lineage for key datasets and apply retention schedules.

Comparison

Readiness levels and next steps
Level	Description	Next step
Ad hoc	Spreadsheets and unmanaged exports	Create inventory and choose authoritative sources
Managed	Central store with some documentation	Add definitions, quality checks and access review
Governed	Catalog, owners, classification and monitoring	Pilot AI tools on a curated domain
Optimised	Semantic layer, lineage and automated testing	Expand use and measure outcomes

Decision worksheet

Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.

1. Have you checked each criterion?

Inventory and ownership — Maintain a catalog with owners, purposes and update schedules.
Sensitivity classification — Classify datasets and apply handling rules including masking where needed.
Access control hygiene — Review who can read each source and remove stale or broad access.
Documentation and definitions — Provide descriptions for tables and columns and a glossary of metrics.
Quality monitoring — Implement checks for completeness, duplicates, ranges and freshness with alerts.
Lawful use and purpose — Confirm lawful basis and purpose limits with privacy staff for each use.
Retention and lineage — Record lineage for key datasets and apply retention schedules.

0 of 7 criteria checked.

2. Compare options (0 = fails or unknown, 3 = meets it well)

Criterion	Option 1 name	Option 2 name	Option 3 name
Inventory and ownership	Inventory and ownership score for Option A	Inventory and ownership score for Option B	Inventory and ownership score for Option C
Sensitivity classification	Sensitivity classification score for Option A	Sensitivity classification score for Option B	Sensitivity classification score for Option C
Access control hygiene	Access control hygiene score for Option A	Access control hygiene score for Option B	Access control hygiene score for Option C
Documentation and definitions	Documentation and definitions score for Option A	Documentation and definitions score for Option B	Documentation and definitions score for Option C
Quality monitoring	Quality monitoring score for Option A	Quality monitoring score for Option B	Quality monitoring score for Option C
Lawful use and purpose	Lawful use and purpose score for Option A	Lawful use and purpose score for Option B	Lawful use and purpose score for Option C
Retention and lineage	Retention and lineage score for Option A	Retention and lineage score for Option B	Retention and lineage score for Option C
Total (max 21)	0	0	0

Questions to ask before you commit

Do we have a catalog and owners for the datasets in scope?
Which datasets contain personal or confidential information?
Who can access each dataset today and is that appropriate?
Are metric definitions documented and agreed?
What quality checks run and who responds to alerts?
What is the lawful basis and purpose for using personal data in these tools?
How long do we retain data and logs?
Can we trace lineage for the most important reports?

Typical trade-offs

Clean first versus pilot in parallel

Upside: Cleaning first avoids poor early impressions.
Downside: Can delay value; a narrow pilot on a good dataset provides lessons sooner.

Centralised data team versus domain ownership

Upside: Consistency under central teams.
Downside: Domain teams know the data best; hybrid models need clear responsibilities.

Masking sensitive fields versus excluding them

Upside: Masking keeps analytical utility.
Downside: Weak masking can leak through combinations of fields.

Common mistakes

Treating data readiness as a technology purchase. It is mostly ownership and process.
Connecting everything at once. Start with one curated domain.
Ignoring permissions because the pilot group is trusted. Fix them before scale.
Assuming privacy review is unnecessary for internal analytics.

Sources and further reading

These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.

Guidance for organisations — Information Commissioner's Office, retrieved 27 October 2026
Artificial intelligence — National Institute of Standards and Technology, retrieved 27 October 2026

How to choose · AI for data and analytics

How to choose AI tools for analysing and searching company data

Look past demonstrations to three questions: can it reach the right data with the right permissions, can you verify how an answer was produced, and does it understand your business definitions. Evaluate connectors, semantic layer support, query transparency, access control inheritance, data movement and retention, and accuracy on your own hard questions.

Comparison · AI for data and analytics

AI forecasting versus traditional statistical forecasting

Established statistical methods are transparent, cheap and often strong when history is stable and data is limited. Machine learning helps when there are many related series, rich drivers and enough clean history. General-purpose chat tools are not forecasting engines. Compare methods on your own backtests, forecast interpretability, maintenance effort and how decisions will use the results.

Problems & fixes · AI for data and analytics

Why AI analytics tools give wrong answers and how to prevent it

Wrong answers usually trace to ambiguous definitions, messy or undocumented tables, wrong joins and filters, stale data, permission gaps, or questions the data cannot answer. Prevent them with a governed semantic layer, documented data, visible queries, curated question sets for testing, and a culture that checks surprising numbers before they spread.

Requirements · AI agents

Requirements before giving an AI agent access to company systems

Before granting access, you need a defined task and owner, dedicated low-privilege credentials, a data classification of everything reachable, approval rules, logging with retention, a tested stop procedure, and agreement on who answers for outcomes. Without these, the agent inherits the access of whoever set it up, and nobody can reconstruct what it did.

Requirements · Workflow automation

Security and governance requirements for workflow automation

Treat the platform as a privileged system. Require single sign-on and role separation, scoped service connections instead of personal logins, secret storage you can audit, restrictions on which data may flow through it, run-log retention limits, change review for important flows, and an inventory with named owners. Without these, automations become unmanaged paths around your normal controls.

Comparison · B2B software

Buy off-the-shelf software or build a custom tool

Buy when the process is common across companies, a mature product covers most of it, and speed matters. Build when the process is a source of competitive difference, existing products force awkward workarounds, and you can sustain engineering ownership over years. Hidden costs on both sides, integration and customisation for bought tools, maintenance and security for built ones, usually decide the outcome.

Requirements · Professional services

What to require in a marketing agency contract and reporting

Require clear deliverables, ownership of accounts and creative assets, transparency on media spend and agency margins, compliance with advertising and data protection rules, defined reporting with raw data access, approval workflows and a workable exit. Agencies act in your name, so you carry legal responsibility for much of what they publish.

All AI for data and analytics guides · All Artificial intelligence