Action Plan Examples: 5 Real Templates You Can Copy
Five completed SOP examples covering the most requested operational functions: employee onboarding (HR), bank reconciliation (Finance), refund escalation (Customer Support), equipment calibration (Manufacturing), and software deployment (Engineering). Each example includes every component a production SOP needs, formatted the way an operations team would actually use it.
When You Would Build This
You are building an SOP program from scratch or replacing informal process notes with structured documentation. You need to see what a finished SOP looks like before you write your own. Your team spans multiple departments and each department needs a different type of procedure: some are linear (step by step), some involve escalation decisions, and some require regulatory compliance formatting.
These five examples were selected because they represent the five most common SOP categories that operations teams document first: people processes, financial processes, customer facing processes, equipment processes, and technical processes.
Why Examples Matter More Than Blank Templates
A blank action plan template tells you the structure. An example shows you how to fill it in. The five examples below cover the most common action plan types: a business goal (launching a new product feature), a personal development goal (earning a certification), a corrective action plan (addressing a performance gap), a project launch plan (organizing a company event), and a strategic plan (entering a new market). Each example includes a complete, filled out template with realistic steps, owners, deadlines, and success criteria.
Every example follows the same six column format from the Action Plan Template: step number, action, owner, deadline, resources, and status. The goal statement and success criteria are included at the top. Use these as starting points. Copy the structure, replace the specifics with your own goal, and adjust the number of steps to match your situation.
The Example
Example 1: New Employee Onboarding SOP
SOP ID: SOP-HR-001 | Revision: 3.2 | Effective: January 2025 | Owner: HR Operations Manager
Purpose: Standardize the onboarding process for all new hires from offer acceptance through the end of their first 90 days, ensuring consistent setup across departments.
Scope: All full time and contract employees at US offices. Does not cover internship programs (see SOP-HR-009).
| Step | Action | Owner | Timeline | Completion Criteria |
|---|---|---|---|---|
| 1 | Send offer letter and collect signed documents (NDA, tax forms, direct deposit authorization) | HR Coordinator | Within 24 hours of verbal acceptance | All documents returned with valid signatures |
| 2 | Submit IT provisioning request: laptop, email account, software licenses, badge access | HR Coordinator | 5 business days before start date | IT confirms all accounts are active and equipment is shipped or staged |
| 3 | Schedule orientation sessions: company overview (60 min), benefits enrollment (45 min), security training (30 min) | HR Coordinator | Calendar invites sent 3 days before start | All three sessions appear on the new hire's calendar |
| 4 | Assign onboarding buddy from the same department and notify the buddy's manager | Hiring Manager | 2 business days before start date | Buddy confirms availability for first week |
| 5 | Conduct Day 1 welcome: office tour, team introductions, workspace setup verification | Hiring Manager | First 2 hours of Day 1 | New hire confirms equipment works and can access all required systems |
| 6 | Complete 30/60/90 day check in meetings with documented progress notes | Hiring Manager | Day 30, 60, and 90 | Check in form completed and filed in HR system with goals for next period |
Quality Control: If any step is incomplete by its deadline, the HR Coordinator escalates to the HR Manager within one business day. The 90 day retention review uses the completed check in forms as evidence of onboarding quality.
Example 2: Monthly Bank Reconciliation SOP
SOP ID: SOP-FIN-003 | Revision: 5.1 | Effective: March 2025 | Owner: Finance Manager
Purpose: Reconcile all company bank accounts with the general ledger within 5 business days of month end to identify discrepancies before financial statements are finalized.
Scope: All operating bank accounts (currently 4 accounts across 2 banks). Does not cover petty cash or credit card reconciliation (see SOP-FIN-007).
| Step | Action | Owner | Timeline | Completion Criteria |
|---|---|---|---|---|
| 1 | Download bank statements for the closed month from each bank's online portal. Save as PDF in the monthly close folder. | AP Specialist | Business day 1 after month end | PDF statements saved for all 4 accounts |
| 2 | Export general ledger transactions for each bank account from the accounting system. Filter by the reporting period. | AP Specialist | Business day 1 | GL export matches the date range of the bank statement |
| 3 | Match bank transactions to GL entries line by line. Flag unmatched items in the reconciliation worksheet with a reason code (timing, error, missing entry). | AP Specialist | Business days 2 to 3 | Every bank transaction is either matched or flagged with a reason code |
| 4 | Investigate variances. For each unmatched item, determine if it requires a journal entry, a void, or is a timing difference that will clear next month. | AP Specialist | Business days 3 to 4 | Every variance has a documented resolution or is classified as a timing difference |
| 5 | Submit completed reconciliation worksheet to Finance Manager for review and approval. Attach supporting documentation for any journal entries posted. | AP Specialist | Business day 5 | Finance Manager signs off. Final variance is zero or consists only of documented timing differences. |
Quality Control: If the net unexplained variance exceeds $500 on any account, the AP Specialist must escalate to the Controller before the Finance Manager review. All reconciliation worksheets are retained for 7 years per the company's document retention policy.
Example 3: Customer Refund Escalation SOP
SOP ID: SOP-CS-012 | Revision: 2.4 | Effective: February 2025 | Owner: Customer Support Director
Purpose: Define the escalation path for refund requests that exceed front line agent authority ($100 limit), ensuring consistent handling and response times.
Scope: All refund requests above $100. Requests at or below $100 are processed by the front line agent without escalation (see SOP-CS-001).
| Step | Action | Owner | Timeline | Completion Criteria |
|---|---|---|---|---|
| 1 | Verify the refund request: confirm the original purchase, check refund eligibility against the return policy, and document the customer's stated reason in the ticket. | Support Agent | During the initial customer interaction | Ticket updated with order number, purchase date, refund amount, reason code, and eligibility status |
| 2 | Escalate the ticket to the Support Lead queue with all documentation attached. Set the ticket priority based on refund amount: $101 to $500 (normal), $501 to $2,000 (high), above $2,000 (urgent). | Support Agent | Within 1 hour of the initial interaction | Ticket appears in the Support Lead queue with correct priority level |
| 3 | Review the escalated ticket. Approve, deny, or request additional information. For denials, draft the customer communication with a clear explanation referencing the specific policy clause. | Support Lead | Within 4 business hours for normal and high priority. Within 1 hour for urgent. | Decision recorded in the ticket with reasoning documented |
| 4 | Process the approved refund through the payment system. Select the original payment method. If the original method is unavailable, issue a company credit and note the exception. | Billing Specialist | Within 1 business day of approval | Refund confirmation number recorded in the ticket |
| 5 | Send the customer a confirmation email with the refund amount, expected processing time (3 to 5 business days for card refunds, 1 business day for credits), and a satisfaction survey link. | Support Agent | Within 2 hours of refund processing | Confirmation email sent and logged in the ticket |
Quality Control: Any refund above $2,000 requires a second approval from the Customer Support Director before processing. The Support Lead reviews a weekly report of all escalated refunds to identify patterns that may indicate policy gaps or product issues.
Example 4: Equipment Calibration SOP
SOP ID: SOP-OPS-042 | Revision: 4.0 | Effective: January 2025 | Owner: Quality Assurance Manager
Purpose: Ensure all measurement instruments used in production are calibrated to manufacturer specifications on a scheduled basis, maintaining traceability to national standards.
Scope: All measurement instruments on the calibration register (currently 47 instruments across 3 production lines). Does not cover laboratory instruments (see SOP-LAB-003).
| Step | Action | Owner | Timeline | Completion Criteria |
|---|---|---|---|---|
| 1 | Check the calibration schedule. Identify all instruments due for calibration within the next 7 days. Pull each instrument from service and place an "Out for Calibration" tag on the workstation. | Calibration Technician | Every Monday morning | All due instruments are tagged and removed from active use |
| 2 | Perform the calibration using the instrument manufacturer's procedure and the certified reference standard. Record all measurements in the calibration log: nominal value, measured value, tolerance, and pass/fail for each test point. | Calibration Technician | Within 3 business days of removal from service | All test points recorded with pass/fail status |
| 3 | For instruments that pass: apply a new calibration sticker showing the calibration date, next due date, and technician initials. Return the instrument to service. | Calibration Technician | Same day as calibration | Sticker applied, instrument returned to workstation, calibration log updated |
| 4 | For instruments that fail: quarantine the instrument with a red "Do Not Use" tag. Notify the production supervisor and the QA Manager. Initiate an out of tolerance investigation to assess whether any products measured with this instrument since the last calibration need to be reinspected. | Calibration Technician and QA Manager | Within 4 hours of discovering the failure | Quarantine tag applied, investigation form initiated, production supervisor notified |
| 5 | Complete the out of tolerance investigation. Document the affected date range, product lots, risk assessment, and corrective action (reinspection, rework, or disposition). Close the investigation with the QA Manager's signature. | QA Manager | Within 5 business days of the failure notification | Investigation report completed and signed. Affected lots dispositioned. |
Quality Control: The QA Manager reviews the calibration compliance rate monthly. Target is 100% on schedule. Any instrument overdue by more than 7 days triggers an immediate audit of the calibration program. All calibration records are retained for the life of the instrument plus 3 years.
Example 5: Software Deployment SOP
SOP ID: SOP-ENG-017 | Revision: 6.3 | Effective: April 2025 | Owner: Engineering Manager
Purpose: Define the steps for deploying application code from staging to production, ensuring every release is tested, approved, monitored, and reversible.
Scope: All production deployments for the primary web application. Does not cover infrastructure changes (see SOP-ENG-022) or database migrations (see SOP-ENG-019).
| Step | Action | Owner | Timeline | Completion Criteria |
|---|---|---|---|---|
| 1 | Verify all CI checks pass on the release branch. Confirm that QA has signed off on the staging environment. Check the deployment calendar for conflicts with other teams. | Release Engineer | At least 2 hours before the deployment window | CI green, QA sign off recorded in the release ticket, no calendar conflicts |
| 2 | Create a deployment ticket in the project tracker with: release version, changelog summary, rollback plan, and the names of the deployer and the on call engineer. | Release Engineer | Before the deployment window opens | Ticket created with all required fields populated |
| 3 | Execute the deployment using the automated deployment pipeline. Monitor the pipeline output for errors. Do not proceed past any failed step. | Release Engineer | During the scheduled deployment window | Pipeline completes without errors. Health check endpoint returns 200. |
| 4 | Run the post deployment smoke test suite against production. Verify core user flows: login, dashboard load, data submission, and payment processing. | Release Engineer | Within 15 minutes of deployment completion | All smoke tests pass. Error rate on the monitoring dashboard is at or below the pre deployment baseline. |
| 5 | Monitor production for 60 minutes after deployment. Watch error rates, latency percentiles (p50, p95, p99), and user reported issues in the support channel. If any metric exceeds the rollback threshold, execute the rollback procedure documented in the deployment ticket. | On Call Engineer | 60 minutes post deployment | All metrics within normal range for the full monitoring period, or rollback executed and confirmed |
Quality Control: Deployments are only permitted during the approved deployment window (Tuesday through Thursday, 10:00 AM to 2:00 PM local time). Emergency deployments outside this window require Engineering Manager approval and a post incident review within 48 hours. The rollback threshold is defined per service: API error rate above 1%, p95 latency above 500ms, or any payment processing failure.
Three structural decisions make these SOPs effective rather than decorative.
What Makes This Example Work
Three structural decisions make these SOPs effective rather than decorative.
Every step has a single owner. Notice that no step says "the team" or "relevant stakeholders." Each action is assigned to one role. The onboarding SOP splits responsibility between the HR Coordinator (administrative setup) and the Hiring Manager (relationship and integration tasks). The refund SOP routes through three distinct roles in sequence. When a step has two owners (Example 4, Step 4), it is because two people must act simultaneously on different parts of the same event. Ambiguous ownership is the most common reason SOPs get ignored.
Quality controls define what triggers escalation, not just what "good" looks like. The bank reconciliation SOP does not say "ensure accuracy." It says "if the variance exceeds $500, escalate to the Controller." The deployment SOP does not say "monitor for issues." It defines the exact thresholds (1% error rate, 500ms p95 latency) that trigger a rollback. Vague quality controls produce vague compliance.
Scope exclusions prevent the SOP from becoming a catch all document. Every example explicitly names what it does not cover and references the SOP that does. The calibration SOP excludes laboratory instruments and points to SOP-LAB-003. The deployment SOP excludes infrastructure changes and database migrations. Without scope boundaries, SOPs grow until they become unwieldy reference manuals that nobody reads.
One thing you may want to adapt: these examples use a table format for procedure steps. If your process has frequent decision points ("if X, do Y; if Z, do W"), consider the flowchart SOP format instead. The refund escalation SOP (Example 3) is close to the threshold where a visual flowchart would improve clarity, especially if you add more refund tiers or exception paths.
Common Questions About Action Plan Examples: 5 Real Templates You Can Copy
How many steps should an SOP have?
Most effective SOPs contain 5 to 15 steps. Fewer than 5 usually means the process is too simple to need an SOP. More than 15 suggests the procedure should be broken into subprocedures or the steps are too granular. Each step should represent one meaningful action performed by one person.
Can I use these SOP examples in regulated industries?
These examples demonstrate the structural pattern that regulated industries require, but you will need to add industry specific compliance elements. Healthcare SOPs may need HIPAA references. Manufacturing SOPs may need ISO 9001 document control formatting. Use these as the structural foundation, then layer in your regulatory requirements.
What is the difference between an SOP example and an SOP template?
An SOP template gives you the blank structure with placeholder labels. An SOP example shows you a completed document with realistic content filled in. Start with the examples on this page to understand what good looks like, then use the SOP templates to build your own from scratch.