SW-IMS-FRM-006
Management Review Action Tracker
Version
1.0
Owner
IMS Coordinator
Effective Date
TBD
Review Date
TBD
Management Review Action Tracker
Purpose
This tracker captures and monitors actions assigned during Management Review meetings. It ensures that decisions made by senior management are implemented, tracked to completion, and reviewed for effectiveness.
Instructions
- Create at each Management Review: Start a new tracker for each management review meeting
- Assign actions: Clearly define each action with owner, due date, and success criteria
- Track progress: Owners update status regularly; IMS Coordinator monitors overall progress
- Review at next meeting: Report on previous actions as input to next management review
- Archive completed trackers: Maintain as records of management review outputs
Management Review Information
| Field | Details |
|---|---|
| Review Meeting Date | [YYYY-MM-DD] |
| Review Period Covered | [e.g., Q1 2025, January-March 2025] |
| Meeting Attendees | |
| Chair | [Typically CEO] |
| Minutes Reference | [Link/reference to full meeting minutes] |
| Tracker Created By | [IMS Coordinator] |
| Tracker Created Date | [YYYY-MM-DD] |
Action Items
Action Entry Template
Complete for each action assigned during the management review:
Action #1
| Field | Details |
|---|---|
| Action ID | [Format: MRA-YYYY-MM-NNN] |
| Source | [ ] Strategic review [ ] Performance metrics [ ] Audit finding [ ] Risk assessment [ ] Customer feedback [ ] Improvement opportunity [ ] Compliance requirement [ ] Other: _______ |
| Priority | [ ] Critical [ ] High [ ] Medium [ ] Low |
Action Description:
[Clear, specific description of what needs to be done]
Background/Context:
[Why is this action needed? What issue or opportunity does it address?]
Expected Outcome:
[What will success look like? What should be different when this action is complete?]
| Field | Details |
|---|---|
| Action Owner | [Person accountable for delivery] |
| Support/Contributors | [Others involved in delivery] |
| Due Date | [YYYY-MM-DD] |
| Resources Required | [Budget, staff time, tools, external support] |
| Dependencies | [What else needs to happen first? Links to other actions?] |
Progress Updates:
| Date | Status | Progress Summary | Issues/Blockers | Updated By |
|---|---|---|---|---|
| [ ] Not Started [ ] In Progress [ ] Complete [ ] On Hold [ ] Cancelled |
||||
| [ ] Not Started [ ] In Progress [ ] Complete [ ] On Hold [ ] Cancelled |
||||
| [ ] Not Started [ ] In Progress [ ] Complete [ ] On Hold [ ] Cancelled |
Completion:
| Field | Details |
|---|---|
| Completion Date | |
| Outcome Achieved? | [ ] Yes - Fully [ ] Yes - Partially [ ] No |
| Effectiveness Verified? | [ ] Yes [ ] No [ ] Pending |
| Evidence | [Reference to deliverables, reports, measurements] |
| Lessons Learned |
Action #2
| Field | Details |
|---|---|
| Action ID | [Format: MRA-YYYY-MM-NNN] |
| Source | [ ] Strategic review [ ] Performance metrics [ ] Audit finding [ ] Risk assessment [ ] Customer feedback [ ] Improvement opportunity [ ] Compliance requirement [ ] Other: _______ |
| Priority | [ ] Critical [ ] High [ ] Medium [ ] Low |
Action Description:
Background/Context:
Expected Outcome:
| Field | Details |
|---|---|
| Action Owner | |
| Support/Contributors | |
| Due Date | [YYYY-MM-DD] |
| Resources Required | |
| Dependencies |
Progress Updates:
| Date | Status | Progress Summary | Issues/Blockers | Updated By |
|---|---|---|---|---|
| [ ] Not Started [ ] In Progress [ ] Complete [ ] On Hold [ ] Cancelled |
Completion:
| Field | Details |
|---|---|
| Completion Date | |
| Outcome Achieved? | [ ] Yes - Fully [ ] Yes - Partially [ ] No |
| Effectiveness Verified? | [ ] Yes [ ] No [ ] Pending |
| Evidence | |
| Lessons Learned |
Action #3
| Field | Details |
|---|---|
| Action ID | [Format: MRA-YYYY-MM-NNN] |
| Source | [ ] Strategic review [ ] Performance metrics [ ] Audit finding [ ] Risk assessment [ ] Customer feedback [ ] Improvement opportunity [ ] Compliance requirement [ ] Other: _______ |
| Priority | [ ] Critical [ ] High [ ] Medium [ ] Low |
Action Description:
Background/Context:
Expected Outcome:
| Field | Details |
|---|---|
| Action Owner | |
| Support/Contributors | |
| Due Date | [YYYY-MM-DD] |
| Resources Required | |
| Dependencies |
Progress Updates:
| Date | Status | Progress Summary | Issues/Blockers | Updated By |
|---|---|---|---|---|
| [ ] Not Started [ ] In Progress [ ] Complete [ ] On Hold [ ] Cancelled |
Completion:
| Field | Details |
|---|---|
| Completion Date | |
| Outcome Achieved? | [ ] Yes - Fully [ ] Yes - Partially [ ] No |
| Effectiveness Verified? | [ ] Yes [ ] No [ ] Pending |
| Evidence | |
| Lessons Learned |
[Continue adding action entries as needed. Copy the action template for each additional action.]
Tracker Summary
Completion Date: [YYYY-MM-DD]
Overall Status:
| Status | Count | Percentage |
|---|---|---|
| Not Started | ||
| In Progress | ||
| Complete | ||
| On Hold | ||
| Cancelled | ||
| Total Actions | 100% |
By Priority:
| Priority | Total | Complete | In Progress | Not Started | On Hold | Cancelled |
|---|---|---|---|---|---|---|
| Critical | ||||||
| High | ||||||
| Medium | ||||||
| Low | ||||||
| Total |
Overdue Actions:
| Action ID | Description | Owner | Original Due Date | Days Overdue |
|---|---|---|---|---|
Actions Requiring Escalation:
[List any actions that are blocked, significantly delayed, or require senior management intervention]
Review at Next Management Review
Status Report Date: [YYYY-MM-DD]
Prepared By: [IMS Coordinator]
Key Highlights:
- Actions Completed Since Last Review: [Number and percentage]
- On-Track Actions: [Number and percentage]
- At-Risk Actions: [Number and brief description]
- Significant Achievements: [Notable outcomes or successes]
- Challenges/Barriers: [Systemic issues preventing action completion]
Recommendations for Management:
- [e.g., Additional resources needed for Action #5]
- [e.g., Extend deadline for Action #3 due to vendor delay]
- [e.g., Escalate Action #2 blocker to CEO]
Actions Carried Forward to Next Review:
| Action ID | Description | Reason for Carry-Forward | Revised Due Date |
|---|---|---|---|
Notes for Users
Action Assignment Best Practices
SMART Actions:
- Specific: Clearly defined, unambiguous
- Measurable: Success can be objectively verified
- Achievable: Realistic given resources and constraints
- Relevant: Aligned with IMS objectives and strategic goals
- Time-bound: Clear deadline
Good Example:
"Implement automated monitoring for SaaS platform uptime with SMS alerts for downtime >5 minutes. Owner: Operations Manager. Due: 2025-03-31. Success: 24/7 automated monitoring operational with alert log."
Poor Example:
"Improve monitoring." (Too vague; unclear who, what, when, how)
Ownership and Accountability
- One Owner Per Action: Multiple contributors OK, but one person accountable
- Authority and Resources: Owners must have authority and resources to deliver
- Senior Ownership: Critical/strategic actions should have Management Team ownership
- Clear Expectations: Owners should understand the action, context, and expected outcome
Progress Tracking
Update Frequency:
- Critical/High Priority: Weekly updates
- Medium Priority: Bi-weekly updates
- Low Priority: Monthly updates
Status Definitions:
- Not Started: Action assigned but work hasn't begun
- In Progress: Active work underway; on track or minor delays
- Complete: Action delivered; awaiting effectiveness verification
- On Hold: Paused due to dependencies, resource constraints, or strategic decision
- Cancelled: No longer required or superseded by other actions
Effectiveness Verification
Actions should not be marked "complete" until effectiveness is verified:
- Immediate Verification: Quick check that deliverable meets requirements
- Deferred Verification: Monitor over time to ensure sustained improvement (e.g., 30/90 days)
- Evidence Required: Tangible proof (reports, metrics, test results, records)
Integration with Other Processes
Management Review actions may trigger:
- Corrective Actions (SW-IMS-FRM-003): If action addresses a nonconformity
- Risk Treatment Plans (SW-IMS-FRM-004): If action treats a risk
- Change Requests (SW-IMS-FRM-011): If action requires significant system/process changes
- Training Requests (SW-IMS-FRM-007): If action requires competence development
Cross-reference these forms to avoid duplication and ensure alignment.
Escalation Triggers
Escalate to CEO/Management Team when:
- Action is >30 days overdue without acceptable justification
- Action owner requests escalation due to barriers beyond their control
- Action requires strategic decision or significant resource reallocation
- Action impacts regulatory compliance or certification
- Multiple dependent actions are blocked
Record Retention
- Active Trackers: Maintain until all actions closed and verified
- Completed Trackers: Retain for minimum [TBD - e.g., 5 years] as evidence of management review outputs
- Archive Location: [TBD - document management system, shared drive, etc.]
Document Control
| Version | Date | Author | Changes | Approved By |
|---|---|---|---|---|
| 1.0 | [TBD] | IMS Coordinator | Initial template creation | [TBD] |
Next Review Date: [TBD]
Document Classification: Internal
Document Owner: IMS Coordinator