The Friday reset
Once a week, on Friday, I hand my system the week's raw stuff and it rebuilds everything from it. It takes me a few minutes. It used to be my whole Sunday.
Tabled for now. Built, not on the homepage, still true.
The job I gave away
The catch-up. Sunday nights, going back through the week's messages, orders, photos, and half-finished lists to figure out what the coming week actually needed. I did it because if I didn't, Monday was chaos. I hated every minute of it.
What runs now
Friday, I download this week's messages, export two reports, and drop the week's photos in one folder. That's all I do.
Then my system runs a chain. It reads the messages and rebuilds who is waiting on me. It reads the orders and settles which promises are done. It updates every list from the fresh data and stages next week. Each step checks its own result before the next one starts, and if one fails, the chain stops and tells me which step, instead of quietly building the week on top of a broken piece. That rule came from two real weeks. One check said all clear every morning while skipping the exact emails I needed, and I found out from a missed deadline. A separate Tuesday step never ran at all for three weeks and nothing said a word. Now every step reports what it looked at, not just that it finished.
The free version, thirty minutes on Friday
Pick your week's raw stuff
For most people that's your calendar for next week, the texts and emails that still need an answer, and a photo of the fridge or the family whiteboard. Gather them, don't sort them.
Paste it all into your chat app with this:
This is my week's raw material. Build me next week in three parts. One: who I owe a reply, and a one-line draft for each. Two: what is on the calendar and what it needs from me before it happens. Three: anything I promised or started that is not finished. Tell me how many messages and events you read, so I know you saw all of it.
Read it Friday afternoon, not Sunday night
The point is that the week is built while you still have a weekend.
What it hands back
I read 7 calendar entries and 4 messages.
One: Replies owed
Erin — "Yes, count us in for after the game Saturday, see you there!"
Karen — "Wednesday's actually open for us, happy to cover carpool."
Priya — "Not yet, but I'll dig through my folder this week and send it over."
Dave — "Honestly, just more sleep — but surprise me with something small."
Two: Calendar prep
Mon: Dentist for Maya 3:30 — confirm insurance card is in the bag.
Tue: Soccer 5:15 — cleats and water bottle.
Wed: Open, but Karen wants carpool coverage — reply first, then it's settled.
Thu: Parent-teacher conference 6 PM — pull the reading log now so it's not a scramble.
Fri: Pizza night — no prep, just show up hungry.
7 more lines follow.
Where this goes wrong
Success that means nothing. A step that prints done whether it worked or not. Every step now reports what it read, thirty-two emails, three inside the window, because a healthy line and a broken line must never look the same, and for two weeks mine did.
The rule underneath
Do the same small thing on the same day and let the rebuild be automatic. The reset is never having to remember what state things are in.
Numbers on this page come from my own system, computed 2026-09-10: 43 distinct mornings the 6 AM job ran, 2026-07-28 to 2026-09-10.