Personal SOP & Automation Library

You are a process optimization specialist who helps professionals systematize their work through documentation and automation. Build a personal SOP and automation library based on:

Role: [YOUR JOB TITLE]
Recurring Tasks: [LIST 5-10 TASKS YOU DO REPEATEDLY]
Time Spent on Repetitive Work: [ESTIMATED HOURS PER WEEK]
Technical Comfort Level: [LOW/MODERATE/HIGH]
Tools Used Daily: [LIST PRIMARY TOOLS]
Automation Budget: [FREE/MODERATE/FLEXIBLE]

## Section 1: Process Inventory and Prioritization
Conduct a comprehensive inventory of all recurring processes in your work and personal life. For each recurring task document the frequency (daily, weekly, monthly, quarterly), time required per occurrence, current number of steps, error rate or quality issues, dependencies on other people or systems, and the value of the output. Calculate total annual time invested in each process. Prioritize processes for documentation and automation using a scoring matrix that weighs time savings potential, error reduction value, frequency of execution, and ease of systematization. Identify the top 10 processes that would benefit most from formal SOPs and the top 5 candidates for partial or full automation.

## Section 2: SOP Writing Framework
Create a standardized template and methodology for writing effective SOPs. Build a universal SOP template that includes the process name and purpose, trigger event that initiates the process, prerequisites and required materials, step-by-step instructions with specific actions at each step, decision points with criteria for each path, quality checkpoints and verification steps, expected output and completion criteria, common errors and troubleshooting guidance, and the date of last review and update. Provide guidelines for the optimal level of detail: enough that someone unfamiliar with the process could follow it successfully but not so granular that it becomes tedious to maintain. Include screenshot and screen recording recommendations for visual processes. Create a style guide for consistent SOP writing.

## Section 3: SOP Library Organization
Design an organizational structure for your growing SOP library. Create a categorization system based on functional area, frequency, and complexity. Define naming conventions that make SOPs searchable and immediately identifiable. Build a SOP index or table of contents that provides a quick reference to the entire library. Establish a version control system that tracks changes and maintains a history of updates. Design access and sharing protocols for SOPs that involve team members or collaborators. Include tagging and cross-referencing methods that connect related SOPs. Create a new SOP creation workflow that ensures every process documented meets quality standards before entering the library.

## Section 4: Automation Opportunity Assessment
Evaluate each prioritized process for automation potential. Create an automation readiness assessment that scores each process on rule-based predictability (can the steps be expressed as if-then logic), data structure (is the information in a consistent, machine-readable format), tool integration availability (do the tools involved have APIs or automation connectors), error tolerance (what happens if the automation makes a mistake), and volume justification (is the process frequent enough to justify automation setup time). For each automation candidate, define what can be fully automated, what can be semi-automated with human checkpoints, and what should remain manual. Calculate the ROI for each automation: setup time versus ongoing time saved.

## Section 5: Automation Implementation Guides
Provide step-by-step implementation guides for the highest-priority automations. For each automation create a detailed blueprint covering the trigger event, each automated step with specific tool configurations, data mapping between systems, error handling and notification settings, testing procedures before going live, and monitoring requirements after deployment. Cover common automation platforms appropriate to the technical comfort level: native app automations for beginners, Zapier or Make for intermediate users, and scripts or APIs for advanced users. Include three starter automation recipes that can be implemented in under an hour each and immediately save time: an email-to-task automation, a recurring report generation, and a file organization routine.

## Section 6: Maintenance and Continuous Improvement
Establish the practices that keep SOPs current and automations running smoothly. Create a quarterly SOP review schedule that assigns each SOP a review date and owner. Define triggers for immediate SOP updates: process changes, new tool adoption, error pattern identification, or team feedback. Build an automation monitoring dashboard that tracks execution success rates, error frequencies, and time saved. Design a continuous improvement cycle where process execution data identifies optimization opportunities. Include a process improvement suggestion system where anyone who follows an SOP can flag improvements. Create an annual process audit that evaluates whether documented processes are still necessary, whether new recurring tasks need documentation, and whether automation technology has advanced enough to automate previously manual processes.