Audit your week

Build-along · ~15 min at your own keyboard

Before you hand any work to an assistant, look at your week as it is. Most owners guess wrong about where their hours go. The task that annoys you most is often not the one that costs you most. This lesson takes a calendar and fifteen minutes. List the ten tasks you repeat. Beside each one, write how many hours a week it takes and what happens if the AI gets it wrong. Then mark which level of Flint would take it on. Rank them, keep the top five, and write what done looks like for each. You do not change anything this week. You only look. The list comes back later: in Level 4 it is the starting point for picking the one job to automate.

Ladder · Level 0The long version: Getting started with an AI assistant ↗

Your starter: Week audit sheet

Template

Make it yours: Fill all ten rows from your own last week, in your own words. Then rank them and keep the five that come out on top.

MY TEN MOST REPEATED TASKS (from last week's calendar, sent mail and texts)
| Task, in my words | Hours per week | Risk if the AI gets it wrong (low, medium, high) | Flint level |
| 1. |  |  |  |
| 2. |  |  |  |
| 3. |  |  |  |
| 4. |  |  |  |
| 5. |  |  |  |
| 6. |  |  |  |
| 7. |  |  |  |
| 8. |  |  |  |
| 9. |  |  |  |
| 10. |  |  |  |

Levels: 1 Ask it well. 2 Give it your context. 3 Connect it. 4 Automate. 5 Build. 6 Run a personal OS.

RANKED FIVE (most hours first; a high-risk task goes below every low and medium one)
1. Task:          Hours:   Risk:   Level:   Done looks like:
2. Task:          Hours:   Risk:   Level:   Done looks like:
3. Task:          Hours:   Risk:   Level:   Done looks like:
4. Task:          Hours:   Risk:   Level:   Done looks like:
5. Task:          Hours:   Risk:   Level:   Done looks like:

LEFT OFF, AND WHY:

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/6

Checkpoints

▸You should now see ten tasks from your own week, each with hours per week and a risk rating.
▸You should now see a Flint level beside each task.
▸You should now see five tasks, ranked, each with one line on what done looks like.

The three ways this goes wrong

The list is in the order of what you hate most. — Annoyance is not cost. Re-rank by hours per week, then move high-risk tasks down. Keep the one you hate if it earns its place on hours.
Half the list is projects: the website, the new hire, the move. — A project happens once. Cross it out and look at last week's calendar again for the things that came back.
The tasks are too broad: 'email', 'admin', 'paperwork'. — Split each one into the kind of work it really is. 'Email' is usually three tasks: quote requests, scheduling, and chasing payment. Score each one.

Share what happened

Paste your ranked five. For each task give the hours per week, the risk (low, medium or high), the Flint level, and one line on what done looks like. Add one line on what you left off and why.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.