---
name: adulting-day
description: Use when someone wants a recurring monthly or quarterly block that batches life admin such as appointments, renewals, forms, repairs, and returns, using one running list. Distinct from [[weekly-planning-meeting]] (planning work and priorities, not admin chores), [[home-reset-system]] (housework), [[calendar-control]] (managing the calendar itself), and [[emergent-task-planning]] (handling tasks that arise unplanned).
---

# Adulting Day

Life admin is small, dull, and spread everywhere: a form, a returned
parcel, a dentist booking, a lapsed renewal. Done as it arises, it
interrupts everything. An adulting day batches it. A running list
collects tasks all month, and one protected block clears most of them at
once. The system has three parts: the list, the date, and the session
routine.

## Input required

- **Current admin backlog**: whatever the user already knows is overdue.
- **Recurring obligations**: renewals, checkups, filings, memberships.
- **Time available**: how long a block and how often (monthly or
  quarterly).
- **Where the list will live**: notes app, paper, or task manager.
- **Constraints**: opening hours of offices, phone-only services, shared
  household tasks.

## Questions to ask first

Ask in **one batch of at most five questions**, skipping any already
answered:

1. What admin tasks are you putting off right now?
2. How often can you protect a block, and for how long?
3. Which obligations recur (insurance, registration, checkups, filings)
   and when do they fall due?
4. Where do you already keep to-dos, and will you add one more place?
5. Does anyone share these tasks with you?

## Method

1. **Create one capture list.** Name it plainly, such as "Adulting".
   Put it where the user already looks daily. The rule: any task that
   takes more than a couple of minutes and is not urgent goes on the
   list the moment it appears.
2. **Dump the backlog.** Spend ten minutes writing every pending admin
   item. Do not sort yet.
3. **Pick the cadence.** Monthly suits a busy admin load; quarterly
   suits a light one. Default to monthly for the first three months,
   then adjust. Put it on the calendar as a recurring event with a
   fixed day and a reminder a few days before.
4. **Add recurring items in advance.** For renewals and checkups,
   add the task a few weeks ahead of the due date so lead time is
   built in. The user checks the current due dates with the issuing
   body; do not state them.
5. **Prepare before the day.** A day or two before, review the list
   and note what each item needs: a phone number, a login, a
   document. Check opening hours for the day chosen, since many
   offices close at weekends.
6. **Run the session in passes.**
   - *Pass 1, calls and bookings*: appointments, quotes, repair
     visits.
   - *Pass 2, forms and renewals*: online or paper paperwork.
   - *Pass 3, returns and errands*: parcels to post, items to return,
     things to drop off. Group by location.
   - *Pass 4, money checks*: bills, subscriptions, anything odd.
   Cap each task at a short time; if it is bigger, schedule it as a
   project with the next step written.
7. **Close the loop.** Delete finished items, move unfinished ones
   with a new date and the reason, and file confirmations.
8. **Reward and reset.** End on a defined finish and put the next date
   on the calendar before closing the list.

### What belongs on the list

| Belongs | Does not belong |
|---|---|
| Bookings, renewals, forms | Anything urgent or time-critical this week |
| Returns, repairs to arrange | Big projects (give them their own plan) |
| Small purchases to research | Daily chores, which fit [[home-reset-system]] |

## Output format

- **Starter list**, grouped by the four passes.
- **Recurring renewal table**: item, due-date source, lead time, task
  date.
- **Session agenda** with time boxes.
- **Calendar entry** text and reminder timing.
- **A one-line review** after the first session: what worked, what to
  change.

## Ground rules

- **Do not state due dates, fees, or rules.** They vary by country and
  provider; tell the user to check the current official source.
- **Never ask the user to paste** passwords, account numbers, card
  numbers, or ID numbers.
- **Urgent things are not saved for the day.** Deadlines inside the
  next week are done now.
- **Keep it one list.** Several parallel lists defeat the batch.
- **Time-box.** If the session runs long, stop and carry over.

## Self-check before answering

- Is there one list, one date, and a recurring calendar entry?
- Are renewals entered with lead time?
- Do the passes group similar tasks?
- Is anything urgent wrongly deferred?
- Is there an end time and a next date?

## Common pitfalls

- **Skipping the day** because it feels dull; protect it like an
  appointment.
- **Dumping projects on the list** that need real planning.
- **Late renewals**: due dates are added on the due date.
- **No preparation**: the session is spent hunting for documents.
- **Offices closed**: the day is chosen without checking hours.
- **Endless carry-over**: the same item appears for six months, a
  sign it needs deleting or a decision.

## Example prompt

> I put off everything: the dentist, a returned jacket, renewing my
> insurance, a form for my landlord. Set me up an adulting day once a
> month with a running list, the order to do things in, and calendar
> reminders.

## Learn more

- [[weekly-planning-meeting]] for planning the week's priorities.
- [[calendar-control]] for keeping the recurring slot protected.
- [[important-docs-vault]] so documents for forms are easy to find.
- [[emergent-task-planning]] for tasks that arise in the middle of other work.