The 4 admin jobs Claude runs without you

Each job assumes Claude already knows who you are. Load these five facts into the Admin Project instructions before you build job 1, and every instruction after that gets shorter and more accurate. Skip this and you will spend the month pasting the same context into four separate jobs.

Paste this block into the Project instructions and fill the brackets:

Who I am: [your role], working in [your industry]. My week is mostly [the three things you actually do].

The topics that count as my industry news: [three or four, be specific. Not "technology"].

My writing style: short sentences, no corporate filler, no exclamation marks. Match the style guide saved in this Project, built from my own sent emails.

My expense categories: [software, travel, meals, hardware, subscriptions, other].

My content baseline: [your number]. Above it is a win, half of it or lower is a loss.

How you behave in this Project:
Never send anything on my behalf. Drafts only, always.
If you cannot read a file or a thread, say so and skip it. Never guess a number, a name or an amount.
If a section has nothing in it, write NOTHING HERE. Do not pad.

Then build in this order: job 1 (triage, highest daily payback, and it is the one that proves the connectors work), job 3 (the brief, it reuses the topics you just defined), job 2 (receipts, the folder habit has to exist first), job 4 (the recap, it needs a baseline number and so a few weeks of data).

It reads everything that arrived since you closed the laptop, and splits it into three: what needs your brain, what needs a reply you can approve, and what needs nothing. For the middle group it writes the reply in your voice and leaves it in drafts. It never sends.

Connect: Gmail or Outlook, with read access plus draft creation. Do not grant send permission. There is no version of this where a machine sends mail in your name unreviewed, and the drafts folder costs you four seconds per email to approve. It is the withheld send permission, not a technical limit, that keeps you safe.

The standing instruction:

Every morning at 6am, read everything that arrived in my inbox since 6pm yesterday.

Sort it into three groups:
NEEDS ME: decisions, bad news, anything with money or a relationship at stake. List these with one line on why.
I CAN APPROVE: routine replies, scheduling, acknowledgements, simple questions. Write the reply in my voice and save it as a draft.
NOISE: newsletters, notifications, automated mail. Count them, do not list them.

Match my writing style from my sent folder: short sentences, no corporate filler, no exclamation marks.
Never send anything. Drafts only.
End with a one line summary: how many in each group.

You drop every receipt into one folder as it happens, photo or PDF, no renaming. Claude reads the new files, pulls the date, supplier, amount, tax and category, and adds one row per receipt to your sheet. Then it tells you which ones it could not read.

Connect: Google Drive or OneDrive, with access to one folder and one spreadsheet. Nothing wider. Create the folder now, name it Receipts, and make a sheet with these columns: Date, Supplier, Amount, Tax, Category, Notes, Source file.

The standing instruction:

Every Friday, check the Receipts folder for files added since the last run.

For each new file, read it and pull: date, supplier, total amount, tax amount, and a category from this list: [software, travel, meals, hardware, subscriptions, other].
Add one row per receipt to my expense sheet. Put the file name in the Source file column so I can trace any row back.

If a receipt is unreadable, blurry, or missing the total, do not guess. Skip it and list it at the end under CHECK THESE.
If the same supplier and amount appears twice on the same date, flag it as a possible duplicate instead of adding both.

Finish with: how many rows added, the total, and the CHECK THESE list.

It runs before you are up and leaves one page: the news in your industry worth knowing, what is on your calendar, what you said you would do yesterday and did not, and what is still waiting on a reply from you.

Connect: your Calendar connector, web search, and read access to your inbox if you want the waiting-on-you section. Tell the Project which three or four topics count as your industry, otherwise the news section fills up with generic tech headlines.

The standing instruction:

Every day at 7am, write me a one page brief with these four sections in this order:

NEWS: up to five items from the last 24 hours in [your topics]. One line each on what happened and why it matters to me. Skip anything that is only a funding announcement or a rumour.
TODAY: my calendar, in order, with the one thing I need to have ready for each meeting.
CARRIED OVER: what I said I would do yesterday and have not marked done.
WAITING ON ME: threads where someone is expecting a reply and has not had one for more than two days.

No preamble, no summary of the summary. If a section is empty, write NOTHING HERE and move on.
Hard limit: one page.

Every Monday it looks at what you shipped last week and how it performed, tells you what beat your baseline and what died, what those two groups have in common, and gives you exactly one recommendation for the week ahead.

Connect: usually no connector here, and that is fine. Paste your numbers in, or point Claude at the sheet where you log them. The important part is that your baseline lives in the Project so the comparison is consistent every week.

The standing instruction:

Every Monday, review what I shipped last week against the numbers I give you.

My baseline is [your number]. Anything above it beat baseline, anything at half of it or lower died.
For the winners and the losers, tell me what they have in common. Look at format, topic, hook and timing, not just the numbers.
Then give me exactly ONE recommendation for this week. Not a list. One.

If last week's data is too thin to draw a conclusion, say so plainly instead of inventing a pattern.
Keep a running note of past recommendations and tell me whether the last one worked.