Free framework · Department
The best automations to set up in operations
The operations jobs to move to Claude or ChatGPT first, starting with your processes written down once from the people who do them.
For operations managers, office managers and owners who keep the business running from Microsoft 365 or Google Workspace, a job or project system, a shared drive and a lot of email. These are the jobs we would move to Claude or ChatGPT first, because they come round every week, they read from systems you already run, and someone already checks the result.
The 8 automations, in the order we would start them
Each one recurs every week or month, reads a system you already run, and has a person who already checks the result. That is why we start here: nothing goes out or gets posted on its own, and the check that keeps the work honest stays with your team.
- 01
Recorded walkthroughs into processes and skills
Takes a screen recording or a meeting where someone talks through how they do a job, and writes it up as a step-by-step process, then as a skill Claude can follow the same way every time.
- Reads
- Recordings and transcripts from Teams, Zoom or Loom; your existing process documents
- Who checks it
- The person who does the job checks every step before the process is published or the skill is used.
- 02
Operations inbox triage
Sorts the shared operations inbox each morning into what needs a reply, what needs a job raised, what is waiting on someone else and what can be filed, and drafts the routine replies.
- Reads
- The shared mailbox in Outlook or Gmail; your job or project system
- Who checks it
- A person reads and sends each reply and decides anything unusual. Nothing is sent automatically.
- 03
The weekly operations report
Writes the weekly report for the owner or leadership team: jobs opened and closed, what is late and why, open issues, and the three things worth deciding this week.
- Reads
- Your job or project system, the shared drive, and the week's notes and emails
- Who checks it
- The operations manager checks each item against its source before the report goes out.
- 04
Supplier and purchase order follow-ups
Reads open purchase orders and supplier emails, picks out what is late or unconfirmed, and drafts the follow-up for each supplier in your tone.
- Reads
- Purchase orders in your accounting or inventory system; supplier email threads
- Who checks it
- A person reads and sends each follow-up. Changes to an order stay with whoever approves orders now.
- 05
Meeting notes into actions
Turns the transcript of an operations or team meeting into decisions and actions, each with an owner and a due date, and drafts them as tasks in the system your team already works in.
- Reads
- Meeting transcripts from Teams, Zoom or Google Meet; Planner, Asana or your task system
- Who checks it
- The meeting owner confirms the actions before they are assigned.
- 06
Rostering notes and cover requests
Reads leave requests, availability notes and the current roster, flags the gaps and clashes, and drafts the message asking for cover.
- Reads
- Your rostering tool or roster spreadsheet; leave requests in email or your HR system
- Who checks it
- The manager who sets the roster makes every change. Claude only flags and drafts.
- 07
How we do things here
Answers the questions the team asks operations every day, like where a form lives or what the process is for a return to supplier, from your own processes rather than the internet.
- Reads
- Your processes and policies, kept in your second brain, SharePoint or Google Drive
- Who checks it
- Operations owns the process pages. Anything they do not cover goes to a person.
- 08
Shared drive tidy and document finder
Finds the latest version of a document on request and lists the duplicates, stale copies and misfiled documents worth sorting, folder by folder.
- Reads
- SharePoint, OneDrive or Google Drive
- Who checks it
- A person decides what is moved, renamed or archived. Claude never deletes.
What the full framework adds
The PDF is about ten pages and free. It takes each automation above and adds a worked example of one typical run, the unit to time it in, a 30-day plan to prove your first one, the policy points for this team, a worksheet to measure before and after, and the mistakes we see most often.
- Week 1Write one process down
- Week 2Pick one job and time it
- Week 3Build it and run it beside the old way
- Week 4Decide, then pick the next job
See it in practice: MacroActive. An international coaching-software team on Claude, with a skills library for six departments and scheduled weekly reports.
Want it set up for you?
The Operations AI Department is these automations set up with you in your own Claude or ChatGPT: the skills, the connections and the schedule, wired into your second brain. Start with one part of it:
Or see every AI Department and the Claude skills behind them.
More free frameworks