How to Use Claude Skills to Turn Handwritten Shift Notes Into a Clean Manager Handoff Report

Warning: If the notes include payroll issues, employee discipline, customer health information, or incident details, only use Claude in an approved environment and keep the file set narrow.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

Problem and who this is for

At close, people write fast. Shift notes are often incomplete, handwritten, and scattered across a prep sheet, a stock note, and a few texts. The next manager still needs one clean handoff that says what happened, what needs attention first, and what can wait.

This workflow is for local business owners, clinic admins, studio managers, front-desk leads, and service operators who inherit messy end-of-shift notes.

Prerequisites

• Claude Skills access.
• Photos of handwritten shift notes, closeout sheets, or whiteboard reminders.
• Any related text messages or quick typed notes you want included.
• A preferred handoff structure. Example: incidents, staffing, inventory, facilities, first-priority follow-ups.

How to gather the source material

1. Take clear photos in good light. Fill the frame with the note.
2. If there are multiple pages, number them in the file names.
3. Paste any related texts into one note file instead of giving Claude ten separate screenshots.
4. Make one file called location-context.txt with the site name, shift date, and next opening time.
5. If a shorthand term is unique to your business, add a small glossary at the bottom of location-context.txt.

Numbered workflow steps

1) Use the internal-comms skill pattern

This work is a straight internal communication task. The internal-comms skill pattern fits because it is built for concise internal updates and incident-style reporting.

2) Extract facts from the shift notes first

{
  "task": "Extract a clean manager handoff input from handwritten shift notes",
  "input": {
    "shift_note_images": "ATTACHED PHOTOS",
    "related_text_notes": "PASTE RELATED TEXT IF ANY",
    "location_context": "PASTE location-context.txt"
  },
  "rules": [
    "Preserve numbers, product names, and times exactly.",
    "Do not infer causes or blame.",
    "Group items into operational categories.",
    "Mark unreadable items [UNREADABLE].",
    "Keep unclear ownership visible."
  ],
  "output": {
    "incidents": "What happened that needs awareness",
    "staffing": "Callouts, gaps, swaps, or coverage notes",
    "inventory": "Stock issues, low items, orders needed",
    "facilities": "Equipment or maintenance notes",
    "first_priority_next_shift": "Top actions for the opening or next manager"
  }
}

3) Verify only the details that matter most

Check names, counts, timing, and any item that could trigger wasted money or a bad customer experience. Leave [UNREADABLE] in place instead of guessing.

4) Generate the final handoff report

{
  "task": "Write a clean manager handoff report from verified shift-note facts",
  "input": {
    "verified_handoff_input": "PASTE STEP 2 OUTPUT AFTER REVIEW",
    "tone": "plain, operational, calm"
  },
  "rules": [
    "Write for the next manager, not for headquarters.",
    "Keep headings short and scannable.",
    "Put time-sensitive items first.",
    "Do not invent next steps if they were not stated or obvious from the note."
  ],
  "output_format": {
    "type": "handoff_report",
    "sections": [
      "What happened this shift",
      "What the next manager needs first",
      "Staffing notes",
      "Inventory and supplies",
      "Facilities or equipment",
      "Open items"
    ]
  }
}

Tool-specific instructions

Claude Skills

• If the feature is new to you, read the Claude Skills explainer page in the site's Tools menu first.
• The internal-comms pattern is the right starting point because the repository examples explicitly include internal updates and incident-style communications.
• If your business wants a fixed handoff format every day, later you can upload a private custom skill with your exact headings and wording rules.

Quality checks

1. Every count, item name, and time matches the source note or remains marked uncertain.
2. The first-priority items are truly next-shift actions, not a full replay of the entire day.
3. Unreadable or unclear text remains visible instead of being guessed at.
4. The report is short enough that a manager could scan it in under two minutes.

Common failure modes and fixes

The report repeats trivial details

Fix: tell Claude to keep only items that affect the next shift, inventory, staffing, or customer service.

Handwriting causes bad extraction

Fix: retake the photo closer, crop tighter, or manually type only the unreadable line.

Claude sounds too formal for store ops

Fix: ask for plain operational language and one short paragraph or bullet block per section.

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: How to create custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-how-to-create-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: internal-comms skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/internal-comms

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.