AI for recurring work tasks

The problem, in your words

I copy the same information between documents every week and cannot see where to start.

Using AI for recurring work tasks starts with describing the part you are actually trying to draft. You do not need a clever instruction or a complete life story. You need enough detail for the answer to refer to your situation instead of an imagined average person. Start with one piece of work, then read it before asking for anything else.

For this guide, the useful input is the inputs, output, repeated steps, exception cases and approved tools. You can leave out anything you do not want to share. An unknown detail should remain unknown: ask the AI to name the gap, not fill it with a convincing guess.

What to tell an AI

Give the request a clear boundary. Say what you want to make, what information it can use and what you will check yourself. For recurring work tasks, that means a draft you can read and change, not an instruction to achieve a result on your behalf.

Here is a fictional starting situation: “I spend an hour assembling a status report from three approved sources every Monday. I can test with made-up records.” Add the time you can actually spend and when you want the first draft. A two-hour weekly budget should not become a daily two-hour schedule. If the answer uses a detail you never supplied, remove it or ask where it came from.

Three example prompts

These prompts are fictional drafts to adapt, not claims about what will happen. Use them one at a time. Read the first answer, correct any mistaken detail, then move to the next request. The facts and the limits matter more than polished wording.

1. I spend an hour assembling a status report from three approved sources every Monday. I can test with made-up records. Map these steps into a checklist and mark which ones still need a person to check them.
2. I spend an hour assembling a status report from three approved sources every Monday. I can test with made-up records. Draft a prompt that turns my fictional status notes into the required headings without adding facts.
3. I spend an hour assembling a status report from three approved sources every Monday. I can test with made-up records. Give me a small test case, including a missing input, before I use the workflow on an approved document.

Read the draft before using it

Start with a description of the task rather than a tool purchase. A suggested workflow is not an installed integration. Check your employer’s rules before sending work material to an AI service. Use made-up inputs first, compare the output with the source and keep a manual route for exceptions.

Check whether the draft for recurring work tasks contains a visible next action. You should be able to tell what you would open, write, compare or ask first. If it only says to “make a plan”, request the first small piece of that plan. Give a real time limit and ask it to leave later work for another session.

Where people get stuck

Common sticking points here are: starting with the tool rather than the task; using confidential records for a test; removing the final human check. Each changes the usefulness of the draft before you even start using it. Narrowing the request is usually a better next move than asking for a longer answer.

For recurring work tasks, return to the actual task when the conversation becomes broad. Ask for the relevant section, checklist or wording, and stop once you have enough to read. You can skip a question, pause or keep a private note instead of sharing more.

Start with your own answers

Axiomative has standard plans across every area, free and without a card. You choose the topic and answer what you want to answer. The standard draft uses those answers; you can skip anything and choose Plain English. Voice options depend on the browser you are using.

The fictional example below is rendered with the same deterministic template builder used for standard plans. It shows the structure, not a person’s result. Your own wording and constraints change the draft. Start with one topic rather than adding detail simply to complete every box.

Fictional example · standard template

Made-up goal: Describe a repeatable process for a weekly status report. Obstacle: The inputs arrive in different formats and contain work information. Time: 1–2 hours a week. Timing: Within a month. This is not a real person’s result.

Repeated tasks ranked by time saved

Situation: your goal is "Describe a repeatable process for a weekly status report"; what gets in the way: the inputs arrive in different formats and contain work information; about 60 minutes a week.
Options: (a) start small with repeated tasks ranked by time saved this month; (b) get outside help first; (c) wait and review in a month.
Recommendation: option (a) — one 20-minute session, then decide.