Claude writes your work log 🧾
From @techyai_cj. Every evening Claude writes down what I actually did that day: what I worked on, what got finished, and what quietly ate the time. By Friday I can point at exactly where the week went. Here is the whole setup, easiest version first, and the way mine actually runs at the bottom.
The easy path · two minutes, any plan
1. Open Claude and make a Project. Call it Work Log. Anything you drop in it stays there, so your logs build up in one place.
2. Set a repeating alarm on your phone for the end of your work day.
3. When it goes off, open the Project, paste this, and talk for thirty seconds:
It is the end of my work day. Write my work log from what I tell you. Three sections with these exact headings: Worked on, Finished, What quietly ate the time. Finished means something actually shipped, closed, or left my hands. Anything still open stays under Worked on. Be blunt in the last section, name the thing that took more time than it should have. Under 150 words, plain sentences, no tables. Here is my day: [three rough lines about your day, typed or dictated]
That is genuinely it. The magic is not the prompt, it is having the log exist at all. One month in you can ask the same Project "read my logs from this month, what keeps eating my time" and it answers from your own history.
The scheduled version
1. In the Claude app, look for scheduled tasks. It is still rolling out, so if you do not see it, stay on the easy path for now.
2. Create a task, point it at your Work Log Project, set it to daily at your quitting time.
3. Use this as the task prompt:
Write my end of day work log. Check my calendar for today and anything you can see from connected tools. Three sections with these exact headings: Worked on, Finished, What quietly ate the time. Only claim what you can actually see, do not invent tasks or numbers. If you cannot see enough to judge, ask me three quick questions instead of guessing. Under 150 words.
Connect Calendar and Gmail under Settings, then Connectors, and this version gets sharply better because it can see your meetings and what you sent.
How mine actually works
Mine does not wait for me to describe my day. A small script runs at 6pm on a schedule, gathers what actually happened on my machine, and Claude writes the log from the evidence: git commits, files I produced, which projects saw activity, even the same file being rewritten six times, which is what time sinks look like in the data.
I did not write the script by hand. I asked Claude Code to build the whole thing. If you have Claude Code, paste this and let it work:
Build me a daily work log automation on this machine. Make a script that gathers today's real activity: git commits across my repos, files I created or modified in my main work folders, and which projects saw activity today. Then have Claude summarize that data into a log file named by date, with three sections: Worked on, Finished, What quietly ate the time. It must only claim what the data shows, never invent tasks or times. Schedule it to run automatically every day at 6pm, then run it once now so I can see today's log.
Mine wrote its first log the day I set it up, and the first thing it caught was real: a full day of edits that never got committed. That is the kind of thing you feel at the end of a week but can never point at.
What a day looks like
What to do with the logs
Friday: paste the week's logs and ask for the three patterns worth changing.
Standups: your update is already written, out loud in ten seconds.
Freelancing: the log is a receipt for every billed day.
I'm a software developer and I post what I actually run.
Follow @techyai_cj on TikTok and Instagram 🚀
More free guides: see all of them
© 2026 CJ · free to use, send it to whoever cannot say where their week went