Guide
Collect evidence before you write. Go through your sent mail, calendar, tickets and documents, and turn each find into a bullet that names the problem, what you did and what changed. Use only numbers you can explain. To make the next update easier, keep a five-line weekly work log on paper. On a Mac, Dayflow can add an automatic record of what was on your screen.
You open your resume to update it. Under your current job sit the three bullets you wrote the week you started. Since then you have shipped things, fixed things, trained people and lived through at least one reorg. But the cursor is blinking, and the only line that comes to mind is “Collaborated cross-functionally with stakeholders.” You honestly can’t say what you were doing last March.
So you scroll back through old chat threads and your calendar, trying to work out which quarter that migration happened. An hour later you have a few half-memories and a creeping sense that you did less than you thought. You probably didn’t. Your record is just scattered across a dozen places.
This guide is about getting from scattered to specific. It covers where to find evidence of work you’ve already done, how to turn a task into a bullet that says what changed, how to handle numbers honestly, and how to keep a light record going so the next update takes an evening, not a weekend. Most of it needs only a notebook and the tools you already use at work. Dayflow, the Mac app that publishes this blog, comes up once near the end, along with the cases where it doesn’t fit. Anything said about Dayflow here comes from its own documentation as reviewed on 2026-09-06. Everything else is general, practical advice.
Mostly because memory isn’t built to work like an archive. Many people find that a few things stand out, like the launch, the outage, the presentation that went badly, while the steady work in between blurs together. The months that made up most of the job leave the least behind.
Routine work also stops feeling like work. If you rebuilt the onboarding checklist and then ran it every week for a year, it can feel like “just what I do” rather than something worth a bullet. Familiarity makes your own contributions invisible to you.
Some of the most valuable work leaves almost no trace. Unblocking a teammate, talking a manager out of a bad plan, or answering the same question patiently for the fifth time rarely ends up in a document with your name on it.
Your job description gets in the way too. When you sit down to write, you tend to remember your duties, because that’s what the role is called, rather than what changed because you were there. That’s how bullets turn into “Responsible for…”
Finally, finished work drops off your to-do list, and the to-do list is where your attention lives. Once something is done, nothing reminds you of it. None of this means your memory is bad. It means memory alone is the wrong tool for this job, and you need a record.
Before writing any bullets, spend one sitting collecting raw material. Set a kitchen timer for 45 minutes and go through your sources in order:
Write each find as one rough line in a notebook, with an approximate date. Don’t polish anything yet. You’re collecting, not writing.
Illustration: “Feb - wrote the vendor comparison doc, team picked option B.” “Apr - ran 3 onboarding sessions for new support hires.” “Jun - fixed the export bug customers kept emailing about.” Three lines like these, ugly and specific, are worth more than any polished sentence you could write from memory.
How to tell it’s working after a week: you have more raw lines than you’d ever fit on a resume, and at least a few of them are things you’d completely forgotten. If the list is still thin, go back to sent mail and slow down. That’s usually where the most turns up.
Take each raw line and answer three questions: What was wrong or needed? What did you do? What was different afterward? Then compress the answers into one line that starts with a specific verb.
The third question matters most. “Ran onboarding sessions” is a task. “Ran onboarding sessions that let new support hires take tickets in their first week instead of their third” is an accomplishment, as long as it’s true.
Illustration:
| Raw note | Weak bullet | Stronger bullet |
|---|---|---|
| Fixed export bug customers kept emailing about | Fixed bugs in export feature | Found and fixed the export bug behind a recurring stream of support emails, which then stopped |
| Wrote vendor comparison doc | Researched vendors | Compared four vendors on cost and migration risk; the team adopted my recommendation |
| Rebuilt weekly report | Responsible for reporting | Replaced a manual weekly report with an automated one, freeing half a day each week for the analyst who owned it |
If you can’t answer “what changed?”, say so honestly in your head and look at the result from another angle. Who used the thing? What would have happened without it? Sometimes the answer is that nothing much changed, and that’s a sign the line belongs in your notebook, not on your resume.
How to tell it’s working after a week: read each draft bullet aloud and ask “so what?” If every bullet already answers that question, you’re done with this step. If several still end in a duty, they need another pass.
Resume advice often says to quantify everything. That’s useful advice taken too far. A number helps when it’s real and you can explain where it came from. A guessed one is a liability, because interviewers ask.
Here’s what you can usually measure honestly without a dashboard:
If a real metric exists but you don’t know it, ask the person who owns it. A short message, “Do you remember roughly how support volume on exports changed after the fix?”, often gets you a usable answer.
Illustration: someone who reorganized a shared drive might not know how many hours it saved anyone. They do know they moved files for three teams, wrote the naming guide everyone now follows, and that new hires stopped asking where things were. That’s a strong bullet with no invented figure in it.
How to tell it’s working after a week: pick any number in your draft and explain, in one sentence, where it came from. If you can do that for every number, keep them. If you hesitate on one, rewrite that bullet as a count, a scope or a before-and-after instead.
Other people often remember your contributions better than you do, because they saw the effect and you only saw the effort. Ask a current or former colleague, or a friend you worked with, for twenty minutes over coffee or a call.
Useful questions:
Take notes on their exact words. Don’t argue or play it down. Add anything new to your raw list.
Illustration: you ask a former teammate about the year you both worked on the billing project. They say, “You were the one who wrote down how the old system actually worked. Nobody could have migrated it without that.” You’d filed that under “made some notes.” It becomes a bullet about documenting a legacy system ahead of its migration.
How to tell it’s working after a week: you’ve had at least one of these conversations, and it gave you a bullet or a framing you wouldn’t have come up with alone. If the person struggled to answer, try someone who depended on your work, not someone senior to you.
The reason this job is hard is that nobody was writing anything down. The fix is to start, lightly. Once a week, at a fixed time, write five lines:
Paper, a notes file or the weekly work log template all work. Ten minutes is plenty. If you want to know more about why this habit tends to stick, the guide to keeping a work journal covers it in more detail. The same log also makes preparing for a performance review far less painful.
Illustration: “Finished: Q3 pricing page copy. Fixed: broken signup email link. Helped: walked Sam through the analytics setup. Learned: legal needs two weeks for any pricing change. Outcome: signup errors stopped after the link fix.” In a year that’s fifty entries, and resume bullets are sitting in most of them.
If Friday comes and the week is a blur, that’s normal. A short reflection like where did my day go can help you look back before writing your five lines.
How to tell it’s working after a week: you actually wrote one entry. That’s the whole test at this stage. If you skipped it, the timing is wrong, not you. Attach it to something you already do every week, like the last meeting on Friday or your first coffee on Monday.
You’ll end up with more good bullets than space. That’s the goal. Keep a master list with every bullet you’ve written, then choose from it for each application.
For each role, rank bullets by how closely they match the job you’re applying for, not by how hard the work felt at the time. Put the closest match first. Three to six bullets per recent role is plenty, and older roles can get fewer.
Run the stranger test on every survivor: could someone with your job title at a different company have written this line without knowing you? If yes, it describes the role, not you. Cut it or make it specific.
Illustration: someone applying for an operations role has twelve bullets from a support job. The ones about building processes and reducing repeat tickets go to the top. The one about winning the team’s holiday quiz, however much fun it was, stays in the master list.
How to tell it’s working after a week: you can tailor a resume for a new posting in under an hour by picking from your master list, without writing from scratch. If you’re still rewriting everything each time, your master list needs more raw material, so go back to the evidence step.
Every step above depends on having a record. The weak point is that a record usually needs you to remember to keep it, and the weeks you most need it are the weeks you’re too busy to write anything down.
Dayflow takes a different route on a Mac. It records the screen at one frame every 10 seconds and has AI write the day into a readable timeline, so there’s no timer to start and no blank page at the end of the week. Full screen recordings and the timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis stays on-device. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. The details are on the local and cloud processing page.
For resume work, the useful part is export. You can export a date range as Markdown from Settings → Export, then read it as raw material for your evidence list or weekly log. The export work history workflow walks through it. Treat the summaries as prompts, not as facts. AI summaries can miss or misinterpret work, so check outcomes before anything goes on a resume.
Dayflow is $0 and MIT licensed, runs on macOS 14 or later, and has an optional Pro plan at $20 a month.
Dayflow publishes this article.
For most people updating a resume this month, the winning tool is a notebook and an afternoon with their sent mail. Dayflow is optional help for the record going forward.
Writing resume bullets is hard because you’re asking memory to do an archive’s job. Start with evidence, not a blank page. Turn each find into a line that says what changed, keep numbers honest, and ask someone who watched you work. Then start a five-line weekly log so next time you’re copying, not reconstructing. If you’re on a Mac and want a record that keeps itself, Dayflow can add one from today onward. The bullets themselves are still yours to write.
Don't rely on memory alone. Go through the places your work left traces: sent mail, your calendar, tickets, shared documents, file or code history, and any old review notes. Write each find as one rough line with a date. Once you have more raw lines than bullet slots, start writing. Memory works much better when it has something concrete to react to.
A good bullet says what was wrong or needed, what you did about it, and what was different afterward. It starts with a specific verb and names something a reader can picture. A useful test: could a stranger with the same job title have written it without knowing you? If yes, it is a duty, not an accomplishment. Rewrite it or cut it.
No. Numbers help when they are true and you can explain where they came from. A plain before-and-after description, like a report that used to take two days and now runs automatically, is often stronger than a guessed percentage. If an interviewer asks how you measured something, you should be able to answer in one sentence. If you can't, rephrase the bullet without the number.
Count what you can count: people trained, requests handled, documents written, systems moved. Describe scope, such as which teams relied on the work. Describe the change in state, like going from manual to automatic or from weekly to daily. You can also ask whoever owns the relevant metric what moved. Don't invent figures to fill the gap.
For most roles, three to six bullets is enough. Recent and relevant jobs get more, and older ones get fewer. Rank bullets by how closely they match the job you are applying for, not by how hard the work felt. If you have ten strong candidates, that is a good problem. Keep a longer master list and choose from it for each application.
Keep a short weekly log. Once a week, write five lines: what you shipped or finished, what you fixed, who you helped, what you learned, and any outcome you noticed. Paper or a notes file both work. Ten minutes a week is enough. The point is that a year from now you'll be copying from a record instead of trying to reconstruct one.
No. Dayflow keeps a timeline of what was on your Mac screen and has AI summarize it, which can remind you what you worked on. It doesn't know what your work changed for the business, and its summaries can miss or misread things. The bullets still come from you, ideally checked against your other evidence.
For past years, your own archives beat Dayflow. Dayflow only records from the day you install it, so it has nothing from before then. Old sent mail, calendar history, project folders, tickets, shared documents and past review notes are where that work lives. Former colleagues are also a good source. Start with whichever archive you still have access to.
Check your employer's policy first. Some companies restrict recording software on work machines, especially where customer or confidential data appears on screen. If you use Dayflow, local AI keeps screenshot analysis on your Mac, while a cloud provider or Dayflow Pro sends selected screenshots off-device. Pick the mode your policy allows, or keep your log on paper instead.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required