Business Operations SOP
Action Item & Follow-Up Management SOP #
This SOP defines how PrecisionTech records, assigns, tracks, escalates, and closes action items created from internal business reviews, KPI reviews, client issues, bookkeeping workflows, IT support, cybersecurity activity, vendor matters, and operational improvement work.
Purpose #
To make sure every important operational issue has a clear owner, due date, priority, follow-up path, and closure record so actions do not get lost between reviews or client work.
Scope #
Applies to action items from Business Operations reviews, KPI tracking, client service, Business Care plans, bookkeeping, IT support, cybersecurity, backup continuity, documentation, training, vendors, and internal improvement activities.
Core Follow-Up Principle #
An action item is not complete because it was discussed. It is only complete when the required work is done, the outcome is documented, any client or internal communication is completed, and the record is marked closed.
When to Create an Action Item #
Client Service #
Unresolved ticket, client escalation, recurring issue, onboarding blocker, offboarding task, or client communication concern.
Bookkeeping #
Missing documents, BAS readiness issue, reconciliation blocker, payroll review item, AP/AR concern, or accountant follow-up.
IT Support #
Microsoft 365 issue, access request, endpoint problem, recurring fault, backup concern, or service improvement task.
Cybersecurity #
MFA gap, phishing concern, access control exception, incident follow-up, security baseline gap, or remediation task.
Documentation #
Missing SOP, outdated process, template issue, uncategorised document, knowledge base update, or client record gap.
Business Operations #
Operational risk, vendor issue, subscription concern, training gap, capacity issue, or improvement item from a review.
Action Item Management Procedure #
- Identify the issue or task: Confirm the action is specific enough to be assigned, tracked, and closed.
- Create the action item: Record the action in the approved action item register, tracker, ticketing system, or Business Operations record.
- Assign an owner: Every action item must have one responsible owner. Shared responsibility is allowed, but only one person owns completion.
- Set priority: Assign Low, Normal, High, or Critical based on business impact, client impact, security risk, deadline sensitivity, or operational urgency.
- Set a due date: Use a realistic due date based on urgency, dependency, workload, and client or compliance deadlines.
- Add context: Include background, source review, affected client or system, expected outcome, and any supporting notes.
- Track progress: Update the status during weekly, monthly, or event-based reviews until the item is closed or formally deferred.
- Escalate blocked or high-risk items: Escalate if the action affects client delivery, cybersecurity, bookkeeping deadlines, business continuity, or owner-level decision-making.
- Document completion: Record what was done, when it was completed, who completed it, and any follow-up required.
- Close the action item: Mark the item closed only when the outcome is verified and the closure note is complete.
- Archive or retain the record: Keep completed action records with the relevant business review, client file, risk register, or operations documentation.
Action Item Review Rhythm #
- Daily / As Needed: Review critical, client-impacting, security-related, or deadline-sensitive actions.
- Weekly: Review overdue items, blocked items, high-priority actions, bookkeeping blockers, and urgent client follow-ups.
- Monthly: Review all open actions created from KPI reviews, internal business reviews, Business Care client reviews, and service reviews.
- Quarterly: Review recurring action themes, repeatedly overdue items, risk-linked actions, vendor issues, and process improvement trends.
- After Major Events: Create and track post-incident, post-escalation, missed deadline, or service failure actions until closure.
Required Fields #
- Action item title
- Category
- Source or trigger
- Owner
- Priority
- Due date
- Status
- Business impact
- Expected outcome
- Completion notes
Priority Guide #
- Critical: Active client impact, security risk, missed deadline risk, data issue, or continuity concern.
- High: Important risk, blocked workflow, recurring issue, or upcoming deadline.
- Normal: Standard operational task that should be completed in the normal review cycle.
- Low: Improvement item, cleanup task, or non-urgent documentation update.
Status Definitions #
- Open: Created but not yet started.
- In Progress: Work has started and is being tracked.
- Waiting: Waiting on client, vendor, staff member, or external dependency.
- Blocked: Cannot continue without escalation, decision, access, or resource.
- Deferred: Approved to move to a later review period.
- Closed: Completed and verified with closure notes.
Escalation Conditions #
- Critical item is not progressing.
- Due date will be missed.
- Client service or Business Care delivery is affected.
- BAS, payroll, month-end, or reporting deadline is at risk.
- Cybersecurity, backup, or access risk remains unresolved.
- Vendor delay affects client or internal operations.
- Repeated overdue items show a capacity or process problem.
Action Item Register Template #
Action ID: [AUTO / Manual Reference]
Action Item Title: [Short title]
Category: [Client Service / Bookkeeping / IT Support / Cybersecurity / Backup / Documentation / Training / Vendor / Risk / Other]
Source / Trigger: [KPI Review / Internal Business Review / Client Issue / Incident / Service Review / Vendor Issue / Other]
Description: [What needs to be done]
Business Impact: [Impact summary]
Expected Outcome: [What good completion looks like]
Owner: [Name]
Priority: [Low / Normal / High / Critical]
Status: [Open / In Progress / Waiting / Blocked / Deferred / Closed]
Created Date: [Date]
Due Date: [Date]
Last Updated: [Date]
Escalation Required: [Yes / No]
Completion Date: [Date / N/A]
Completion Notes: [Outcome, evidence, or follow-up]
Follow-Up Rules #
- Every action item must have one clear owner.
- Every action item must have a due date unless formally deferred.
- Critical and High items must be reviewed until resolved or escalated.
- Blocked items must include the blocker and the escalation path.
- Waiting items must identify who or what the item is waiting on.
- Deferred items must include the reason and next review date.
- Closed items must include completion notes.
- Recurring action items should trigger a process, capacity, client, or vendor review.
Related SOPs and Records #
- Business Operations Master SOP
- Internal Business Review SOP
- KPI & Metrics Tracking SOP
- Operational Risk Register SOP
- Client Health Review SOP
- Vendor & Subscription Review SOP
- Service Review SOP
- Incident Response SOP
- Backup Verification SOP
- End-of-Month Close SOP
Escalation Triggers #
- Critical action item is overdue or blocked.
- Client-impacting action has no owner or no due date.
- Bookkeeping, BAS, payroll, or reporting deadline may be missed.
- Security, access, MFA, backup, or continuity action remains unresolved.
- Vendor delay creates client delivery or operational risk.
- Repeated overdue actions indicate a capacity, process, or ownership issue.
- Action item requires owner-level decision, risk acceptance, or resource approval.
Completion Checklist #
- Action item clearly described
- Category selected
- Source or trigger recorded
- Business impact documented
- Expected outcome defined
- Owner assigned
- Priority assigned
- Due date set
- Status updated
- Blockers or dependencies recorded
- Escalation raised where required
- Completion notes added
- Action item closed only after verification
- Record archived or retained
Document Control #
Owner: PrecisionTech
Applies To: Business Operations, Client Service, Business Care Plans, Bookkeeping, IT Support, Cybersecurity, Vendor Management, Documentation, Training, Risk Management
Review Frequency: Quarterly, or after major operational, staffing, service, client, security, bookkeeping, vendor, or process changes
Last Reviewed: [Insert Date]
Version: 1.0
