01
Collect repeated work from real sources
You pull recurring work from the places where it currently hides, including calendars, reminders, sent messages, shared folders, checklists, and memory.
Made for Administrators
Build Your Recurring Admin Task System
Also useful for: people in Government
120 min
Advanced
Government
Administrator
Get Organized
Career outcome:
Improve Productivity
Build a working register for daily, weekly, monthly, quarterly, and annual admin tasks so recurring work doesn't depend on memory or one person's availability.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
You can see what must happen, when it starts, when it's due, who owns it, and who covers it.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Separate recurring tasks from one-time work
You remove projects and isolated requests so the system only tracks work that repeats or follows a repeatable trigger.
03
Define the trigger and due rule
You replace loose timing with a clear start signal and deadline rule for each task.
04
Set priority by missed-task impact
You rank recurring work by what happens if it is late, skipped, or completed incorrectly.
05
Assign ownership and backup coverage
You make responsibility clear and prepare for leave, illness, schedule changes, or staff turnover.
06
Define completion evidence
You decide how you can tell that each task is actually finished rather than merely started.
07
Check workload collisions
You find periods where several deadlines compete for the same time, information, or approval.
08
Build the master task register
You place approved task details into one source that can be sorted, filtered, and maintained.
09
Test the system against disruptions
You check whether the system still works during a holiday, a busy deadline period, and an unexpected absence.
10
Launch reviews and maintain the system
You create a light routine that keeps the register accurate instead of letting it become another stale document.
Make Your Play
Build Your Recurring Admin Task System
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
List repeated work from calendars, reminders, inboxes, checklists, notes, and memory. Include frequency or timing when you know it.
0/10000
Provide your working days, time zone, holidays, cutoff times, month-end rules, and any business-day conventions that affect deadlines.
0/10000
List the people or functions that may own, approve, receive, or cover recurring work. Include known access limits without sharing credentials.
0/10000
Choose where you'll maintain reminders, assignments, and status updates.
Explain when you must escalate a delay, request approval, or notify someone that a deadline may be missed.
0/10000
State when you can run your weekly and monthly maintenance reviews.
0/10000
Note policies, access limits, record rules, or privacy requirements the system must respect.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Collect repeated work from real sources
You pull recurring work from the places where it currently hides, including calendars, reminders, sent messages, shared folders, checklists, and memory.
02
Separate recurring tasks from one-time work
You remove projects and isolated requests so the system only tracks work that repeats or follows a repeatable trigger.
03
Define the trigger and due rule
You replace loose timing with a clear start signal and deadline rule for each task.
04
Set priority by missed-task impact
You rank recurring work by what happens if it is late, skipped, or completed incorrectly.
05
Assign ownership and backup coverage
You make responsibility clear and prepare for leave, illness, schedule changes, or staff turnover.
06
Define completion evidence
You decide how you can tell that each task is actually finished rather than merely started.
07
Check workload collisions
You find periods where several deadlines compete for the same time, information, or approval.
08
Build the master task register
You place approved task details into one source that can be sorted, filtered, and maintained.
09
Test the system against disruptions
You check whether the system still works during a holiday, a busy deadline period, and an unexpected absence.
10
Launch reviews and maintain the system
You create a light routine that keeps the register accurate instead of letting it become another stale document.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
You can start with a rough list copied from your calendar, reminders, notes, and recent sent messages. Include imperfect task names. The AI will help you sort them, but you should confirm every deadline, owner, and backup before using the system.
Advanced instructions
You can include business-day rules, service targets, blackout dates, dependencies, evidence requirements, approval paths, and access limits. After the first draft, test the system against a month-end, a holiday week, and an unexpected absence before you publish it.
Use this when
Use this when recurring work lives across calendars, inboxes, notes, spreadsheets, or memory, especially before a handoff, staffing change, busy period, or extended absence.
You'll need
- Recurring task dump
- Work schedule and timing rules
- Owners and backup coverage
- Tracking tool
- Escalation and approval rules
- Review preference
- Constraints and sensitive-data rules
You'll get
- One approved register covering each recurring task's frequency, trigger, due rule, owner, backup, evidence, and escalation point
- You can identify deadline collisions, cover critical work during an absence, run weekly and monthly reviews, and answer or assign every unresolved decision.
By the end of this playbook
You will have:
- One approved register covering each recurring task's frequency, trigger, due rule, owner, backup, evidence, and escalation point
- You can identify deadline collisions, cover critical work during an absence, run weekly and monthly reviews, and answer or assign every unresolved decision.
Examples
Progress 1 of 10