Workflow Audit Cheatsheet

The Predictability Test

Before auditing anything, apply this test to every task:

If the structure repeats even when the content changes, it's a workflow candidate.

Weekly reports follow the same structure every week even though the numbers change. That's a high-predictability task. A brainstorming session where the output changes completely each time is low-predictability. Focus on high and medium tasks first.

The Right Question

Most people ask: "Can AI do this?" That's the wrong question.

The right question is: "Is this task predictable enough that I can write a template for it?"

If you can describe the expected output format in one sentence, the task passes. If the output format varies wildly, it might need human judgment more than automation.

The 15-Minute Audit Process

Run this once a month. Open your calendar, go through last week, list every repeating task.

Step 1 List

Write Down Every Repeating Task

From your calendar, not your memory. Memory misses the small stuff.

For each task, write four fields: Task: [e.g. Weekly status report] Frequency: [Daily / 3x per week / Weekly / Monthly] Time per occurrence: [5 min / 15 min / 30 min / 2 hours] Predictability: [High / Medium / Low] Be honest about time. Most people underestimate how long repetitive tasks take because they've always done them manually.

Step 2 Score

Rank by Automation Potential

Not all repeating tasks are equal. Prioritize the ones with the highest return.

Score each task on two axes: 1. Predictability: How consistent is the output format? (High = 3, Medium = 2, Low = 1) 2. Time per occurrence: How long does it take? (More time = higher priority) Multiply the two scores. Sort descending. Top 5 tasks are your candidates. Example: - Weekly status report: 3 x 2 hours = 6 - Meeting notes: 3 x 30 min = 1.5 - Email triage: 2 x 20 min = 0.67 - Sprint planning: 2 x 1 hour = 2

Step 3 Select

Pick Three, Not Ten

This is the most important step. Volume kills adoption.

From your ranked list, pick the top 3. Why three? - Three is small enough to test in one week - Three is small enough to refine without decision fatigue - Three is enough to prove the concept and build the habit Do NOT try to automate everything at once. That's the #1 reason people quit. If a task is partially automatable, include it. You can always drop it later if the template doesn't work well.

Step 4 Build

Write One Template Per Task

Use the 4-part prompt structure: Role, Context, Task, Format

For each of your 3 tasks, write a prompt template with four parts: 1. Role: Who should the AI act as? ("You are a [role] with [X] years of experience") 2. Context: What information does it need? (Paste your raw input here) 3. Task: What should it produce? ("Generate a [output type] with [specific sections]") 4. Format: How should the output look? ("Under [word count], structured as [format]") Write the template. Test it with real input. Refine if the output needs adjustment. Time: ~10-15 minutes per template. Faster if you use AI to help draft the initial version.

Step 5 Test

Use the Templates for One Full Week

Don't fall back to manual. If a template doesn't work, note the issue and fix it at the end of the week.

For one full week, use every template whenever the task comes up. At the end of the week, evaluate each template: - Did I use it consistently? (If not, the template isn't solving the right problem) - Was the output good enough? (If you edit less than 20% of the output, it's working) - Did it save measurable time? (Compare with your pre-template time) Templates that pass all three: save them. Templates that fail: refine or replace.

Common Workflow Categories

These are the most frequently automatable task types across roles. Check which match your work.

Category Reporting

Weekly status reports, monthly metrics, quarterly reviews, performance write-ups

High predictability. Same format every time. The content changes but the structure doesn't. These are usually the easiest wins.

Category Communication

Meeting notes, follow-up emails, stakeholder updates, team announcements, client summaries

High frequency (often daily). Structured input, structured output. Strong candidates for templates.

Category Development

Code review summaries, PR descriptions, technical documentation, sprint planning prep

Can connect to GitHub/GitLab for automated input. Output needs to be specific enough to be actionable.

Category Education

Lesson plans, flashcard generation, reading summaries, study guides, grading rubrics, homework assignments

Particularly strong for flashcard generation. Claude can produce interactive flashcards with analogies and discussion questions.

Category Content

Blog outlines, social media posts, newsletter drafts, video scripts, content calendars

Good for outlines and first drafts. Always requires human editing before publishing.

Category Operations

Email triage, invoice processing, scheduling, onboarding checklists, expense reports

High frequency, low creative requirement. Strong automation candidates. Often overlooked because they feel too small to bother with.

Monthly Cadence

Set a calendar reminder for the first week of every month:

Day 1: 15-minute audit. List repeating tasks, score predictability, rank by potential.

Day 2-3: Build or refine templates for your top 3 picks. About 10-15 minutes per template.

Day 4-30: Use the workflows. Save what works, refine what doesn't.

Total investment: 25-45 minutes per month. Ongoing savings: 5-15 hours per week, growing as your library expands.

What This Rules Out

Don't automate tasks that require significant creative judgment (brainstorming, strategic planning, complex decision-making). Don't build more than 3 templates at once. Don't skip the testing phase. Don't try to automate someone else's work before automating your own.

Get the audit framework