Action plan & roadmap

From score to action plan

A score is a nice thing to have. A score that tells you what to do on Monday morning is worth paying for. So every factor that lands below the top band becomes a short list of tasks. Each task gets a priority, somebody's name, and a date, and the list is ordered so the first few items take the most risk off the table for the least effort.

How gaps become tasks

The factor score sets the priority. Under 5.0 and the tasks come out marked High. Between 5.0 and 7.9 they're Medium. At 8.0 or better they're Low, which in practice means keep doing what you're doing and check it quarterly. When two tasks share a priority, the identity and permissions ones go first. They carry the most weight in the score, and more to the point, every AI assistant you switch on inherits whatever state they happen to be in that morning.

Nothing goes on the list without a person's name and a date beside it; unowned tasks are how plans quietly die. On the guided evaluation, your technical account manager drafts the plan from the scan results and sits with your leadership team to go through it. If you're doing this yourself, the recommendations on your results page are the raw material, and the roadmap template further down this page is where you write them up.

Rule of thumb: fix the lowest-scoring factor first. The weighting makes this pay: taking a 20% factor from 4 to 7 lifts the overall score by 0.6, while the same jump on a 10% factor only moves it 0.3.
Sample taskFactorPriorityTarget
Enforce MFA for every admin and disable legacy authenticationIdentityHighQ1
Run a tenant-wide permissions audit and remove broad accessPermissionsHighQ1
Approve the AI acceptable use policy and collect acknowledgmentsGovernanceHighQ1
Create DLP policies for customer PII and financial dataMonitoringMediumQ2
Apply retention to the main document librariesData qualityMediumQ2
Train the leadership team; pick the first two use casesPeopleMediumQ2
Evaluate Copilot-eligible licensing for the pilot groupTechnologyLowQ3

The six-step path from assessment to governed AI

This is the route we run with clients, in order. The assessment is step one. Everything after it is optional and sized to what the score says you actually need, so a company that scores well on data might skip step three entirely.

Step 1

AI Readiness Assessment

The seven-factor assessment described on this site. The guided version adds three scans of your tenant (identity posture, permissions, and data security posture) and comes back as a scored rubric, a maturity rating, and the first draft of this very plan.

Step 2

Remediation roadmap

The plan itself. Governance gaps, identity exposure, over-shared data and ROT cleanup, written up in the order that gets the most risk off the table soonest.

Step 3

Data governance onboarding

This is the heavy lifting, and it's for companies whose permissions scored badly. We rebuild or migrate SharePoint, redo the permissions around roles instead of individual names, switch DLP on, and add automated archiving if the ROT numbers say it's worth it.

Step 4

Data governance as a service

The monthly service that stops step three from quietly undoing itself. Workspace management, security monitoring, Microsoft Purview DLP, and a technical account manager whose job includes noticing when the permissions have drifted back to where they started.

Step 5

Copilot enablement

Only once the environment has earned it. A structured Copilot deployment, AI literacy training for the people who'll use it, and use cases rolled out one at a time with a number attached to each. See Copilot readiness.

Step 6

Continuous governance

A quarterly re-score, permission audits, access reviews, and updates to the AI policy whenever the regulators or the attackers change the rules.

A three-phase roadmap

Most organizations end up following roughly this shape over three years. Your action plan supplies the specifics, and the AI Strategy & Roadmap template gives you a document to write them into.

Phase 1 · Months 1 to 6

Foundation

  • Complete the readiness assessment and set the baseline
  • Approve the AI acceptable use policy and name an AI owner
  • Close the identity gaps: MFA everywhere, legacy auth off, admin roles minimized
  • Audit permissions and external sharing; assign data owners
  • Deliver AI awareness training to everyone
  • Select the first pilot use case and a pilot group
Phase 2 · Months 7 to 18

Expansion

  • Enforce DLP across endpoints and cloud; monitor AI activity
  • Apply retention and clean up ROT in the main repositories
  • Run the pilot, measure results, expand to the next two or three use cases
  • Role-based training for managers and power users
  • Re-assess; compare against the baseline
Phase 3 · Months 19 to 36

Optimization

  • Automate permission governance and access reviews
  • AI-aware DLP and automated incident response
  • AI embedded in core processes with ROI tracked per use case
  • Quarterly re-score as part of ongoing governance
  • Annual strategy refresh

Implementation tracker

A readiness score is a trend line, not a photograph. Tracking is how you watch it move while the plan gets worked through, and, just as useful, how you notice when it has stopped moving.

Action plan progress

Sample: 13 of 21 tasks complete62%
13 done5 in progress3 to do

On the guided and full programs, every task sits in the plan with its current status. The leadership team can see how far along things are without sending IT an email and waiting until Thursday for an answer.

Before and after

Baseline
5.4
AI Vulnerable
→
After remediation
7.6
AI Capable

The full program re-scores the environment after remediation and writes up a progress validation report. If you're doing it yourself, the assessment page keeps your history on your own device, so a retake each quarter gives you the same before-and-after picture, just without the engineer.

Start with the score

The recommendations on your results page are the first draft of this plan, so that's the place to begin.