Run your weekly service owner review
Review new and changed items, approaching deadlines and outstanding actions for your service.
Applies to: Dataverse-based ChangePilot Enterprise. Dashboard pages require an installed release that includes them and access to the underlying items.
Who this is for: service and product owners. Reserve a regular review slot; the time needed depends on your service and workload.
1. Check what Microsoft has changed
Open What’s Changed under Dashboards & Reports. Choose your categories and a timeframe that covers the period since your last review. A longer window helps after an absence.
Start with Already reviewed: check again, then check dates brought forward, dates delayed and rewritten posts. Open relevant MCIDs and reconsider any assessment, action or communications plan affected by the update. This page surfaces updates; it does not decide whether your organisation’s earlier response remains sufficient.
2. Assess new items for your service
Use Product Insights or your item list view to focus on your product areas. Check new items, their impact and rollout dates. Confirm ownership and record an assessment. Do not rely only on automated assignment: also check relevant unassigned items and cross-product dependencies.
Follow the item review walkthrough for the assessment, notes, actions and status.
3. Look ahead to deadlines
Use Deadlines & Retirements and the relevant product view to check approaching changes. Agree action owners and realistic due dates before the rollout window.
The Landing Page’s At Risk counter means an open item has a Standard Start between today and seven days ahead. It is a prompt to check readiness, not proof that no work has happened.
4. Review outstanding actions
Open Actions Report or your action list. Check overdue work, confirm who owns each action and record progress. If work is blocked, record the dependency and agree the next step. Close items only when the agreed response is complete or no further action is needed, with a clear reason.
5. Prepare discussion and user communications
Set items needing a shared decision to To Discuss so they appear in Change Call Agenda. Explain the decision needed in a note.
Apply the End User Communication tag where users need information or training, then review the relevant window in Change Readiness.
Check that the review is complete
- New relevant items have a recorded assessment and accountable owner.
- Microsoft updates have been checked against previous decisions.
- Approaching changes have actions or a recorded no-action decision.
- Blocked decisions are ready for the internal change meeting.
- Communications needs have been passed to the right lead.
Refresh dashboards after changing items. Counts reflect the page’s filters, access and calculation rules, so compare the underlying MCIDs before treating different totals as a data issue.
Review after a longer absence
What’s Changed offers a maximum lookback of 60 days. If your last review was earlier, review older changes on the underlying items as well. A dashboard’s seven-day At Risk counter is a different window from the 14-day at-risk definition described in the weekly email reference; compare the same dates and MCIDs when checking totals.
Documentation reviewed: 12 November 2026.