Guide
Write a promotion case by matching specific, dated examples to your company's criteria for the next level. Keep a weekly work log or a running brag document so the evidence exists before review season. Pull in outcomes, artifacts and other people's words. On a Mac, Dayflow can show what you actually worked on when memory has gaps, but you still write the story.
Your manager says promotion packets are due in three weeks. You open a blank document, type your name and the level you want, and then stall. You know you worked hard this year. You can picture the late nights in March and the launch that went sideways in June. But when you try to write down what you actually did, the specifics slide away, and what comes out is “led several cross-functional initiatives.”
Then the doubt creeps in. Maybe the year wasn’t that impressive. Maybe the colleague who talks about their work more often will look stronger on paper. Usually the work was there. What is missing is the record of it, and the shape of an argument someone else can follow.
This guide covers how to build that argument: finding what the decision is really based on, collecting evidence while it is still fresh, rebuilding the parts you have already forgotten, and writing examples a reviewer can check. Most of it needs nothing more than a document and a calendar.
Memory is not a log. It keeps the vivid moments, like the outage, the tense meeting, the launch, and drops the steady work that filled most weeks. The careful review you did that prevented a bad decision leaves no strong memory precisely because nothing went wrong.
Recent work also crowds out older work. Many people find that when they sit down to write a case, the last six weeks feel enormous and January feels like a different job. That is how a whole year gets summarized by one quarter.
There is also a mismatch in what you notice. Day to day, you think about tasks: the bug, the deck, the hiring loop. A promotion committee thinks in terms of scope, judgment, influence and independence. Translating one into the other is hard when you are doing it all at once, from memory, under a deadline.
Finally, a lot of people find writing about their own work uncomfortable. It can feel like bragging. So they write vaguely, which feels safer and reads weaker. None of this means you are bad at your job. It means the record and the framing need some help.
What to do: Find the written expectations for the level above yours. That might be a career ladder, a leveling guide or a list your manager keeps. Copy each criterion into a two-column table: the criterion on the left, your examples on the right. Leave the right column empty for now.
If there is no written ladder, ask your manager: “What would someone at the next level be doing that I’m not doing yet?” Write their answer down word for word and use it as your criteria.
An illustration: Say the next level lists “owns projects end to end”, “improves how the team works” and “mentors others.” Your table now has three rows. When you remember the onboarding guide you rewrote, you know it goes under “improves how the team works,” not in a general pile.
How to tell after a week: You can look at your table and point to which rows are thin. If every row looks equally full or equally empty, the criteria are probably too vague. Go back and ask for more detail.
What to do: Every Friday, before you close the laptop, write three or four lines. What did you do this week that mattered? What changed because of it? Where is the proof, such as a doc, a ticket, a thread or a meeting note? Date each entry. A paper notebook works. So does a single running document, or the weekly work log template if you want structure.
Keep the bar low. This is not a status report and nobody else reads it. If you want a deeper look at the habit, there is a guide to keeping a work journal.
An illustration: “Oct 9. Found that the weekly export was double-counting refunds. Wrote up the fix, finance confirmed numbers now match. Thread in #finance-data.” That took under a minute and is already a promotion example.
How to tell after a week: You wrote the entry without it feeling like homework. After a month, read the entries back. If they only describe activity (“worked on export”), add the “what changed” line. If they include outcomes, the habit is working.
What to do: Turn your raw notes into short, structured examples. Each one has four parts:
Aim for three to six sentences per example. Reviewers are often reading many cases. Clear examples they can verify do more than long ones they have to decode.
An illustration:
| Part | Example |
|---|---|
| Situation | New hires were taking a long time to ship their first change because setup steps lived in scattered docs. |
| What you did | I collected the steps into one guide, tested it with two new hires and fixed what tripped them up. |
| What changed | The last two new hires shipped a change in their first week without needing a setup call. |
| Proof | Onboarding guide link, and a note from their manager in the team channel. |
How to tell after a week: Hand one example to a friend outside your team. If they can tell you what you did and why it mattered without asking questions, it works. If they ask “so what happened?”, the “what changed” line is missing.
What to do: When someone thanks you, praises your work or says your doc helped, save it. Screenshot it, copy it into your log or forward it to yourself with a clear subject line. When a project ends, ask the people you worked with for one or two sentences about your part. Most people are happy to help when the request is small and specific.
Other people’s words carry weight because they are not your own framing. They also cover things you would never think to mention.
An illustration: “Could you write two sentences about how the migration went from your side? I’m collecting notes for my review.” A week later you have a quote from another team’s lead saying your plan was the reason the cutover went quietly.
How to tell after a week: You have at least one saved message or quote. If you have none, you are probably not noticing the praise when it happens. Try searching your chat history for “thank you” and “thanks for” and see what turns up.
If you are reading this two weeks before a deadline with no notes, the habits above will not help this cycle. Rebuilding will.
What to do: Block an hour. Open your calendar and walk back month by month, writing one line for anything that looks like real work: project kickoffs, design reviews, launches, interviews you ran. Then do the same with your sent mail, chat threads where you wrote long messages, document edit history, tickets you closed and reviews you gave. Write a rough timeline first and judge it later.
Treat anything uncertain as a question, not a fact. Mark it and confirm with a teammate. The guide on where did my day go goes into more ways to reconstruct time from traces you already have, and remembering what you worked on covers the shorter-term version.
An illustration: Your calendar for April shows four meetings titled “Vendor eval.” You had forgotten them entirely. Your sent mail shows you wrote the comparison doc that led to the decision. That becomes an example under “drives decisions across teams.”
How to tell after a week: Your timeline has something in every month. If a month is still blank, it is worth asking a teammate what you worked on together then.
What to do: Write a rough draft with your criteria table and your best examples, then show it to your manager well before the deadline. Ask three questions: Which criteria am I not yet meeting? Which examples are weakest? Who else will read this, and what will they look for?
Then show it to a friend or peer who will be honest. Ask them to read it as a skeptic. If you want help structuring the conversation with your manager, the guide on preparing for a performance review covers it.
An illustration: Your manager reads the draft and says the “mentors others” row is thin. You remember you have been reviewing a newer teammate’s work every week for months. You ask that teammate for two sentences, and the gap is closed.
How to tell after a week: You have specific feedback, not just “looks good.” If everyone says “looks good,” ask a narrower question, such as “Which example would you cut?”
The rebuild step is the slow one, and it depends on traces you happened to leave behind. Work that happened in a doc you never shared, a debugging session or a long research afternoon often leaves nothing in your calendar or inbox. A record that builds itself means you do not have to remember to log anything.
Dayflow is a Mac app that records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Recordings and the timeline are stored on your Mac. You choose how screenshots are analyzed: Local AI keeps analysis on-device, your own cloud provider processes selected screenshots under its own terms, or Dayflow Pro handles cloud analysis. The local and cloud processing page explains the differences. You can export a date range as Markdown from Settings → Export, which gives you raw material to search when filling in a month, as described in exporting your work history.
The app is free and MIT licensed, with an optional Pro plan at $20 a month. It needs macOS 14 or later. Its AI summaries can miss or misinterpret work, so check anything before it goes into a case. On a work computer, check your employer’s policy before recording your screen.
Dayflow publishes this article. Product details here come from Dayflow’s own documentation for version 2.2.0, reviewed on 2026-09-06.
If you are not on a Mac. Dayflow is Mac only. A running document you update every Friday works on any device and is the better choice.
If your work happens away from the screen. It sees only what is on your screen. Whiteboard sessions, hallway conversations, phone calls and the judgment calls you made in a meeting never show up. For many senior roles, that is where the promotion evidence lives. A notebook catches it.
If your employer restricts screen recording. Many company devices are managed, and recording may not be allowed. A plain written log needs no approval.
If you need someone else to see your work. Dayflow has no team reports. It is a private record, not a way to show your manager anything. Your case still has to be written and shared by you.
If you need hours for billing. It does not create invoices or payroll approvals. A dedicated time tracker for Mac built for billing is the better fit.
If you already keep a good log. If your Friday notes are working, you may not need anything else. A record of activity is not a judgment of impact, and impact is what the case has to argue.
A promotion case is an argument, not a diary. Start from the criteria, find two or three checkable examples for each, and let other people’s words back you up. Most of the evidence comes from a habit that takes five minutes a week and a willingness to dig through your calendar and sent mail when the habit lapses.
If you have weeks left, rebuild the year from traces and get your manager’s eyes on a draft soon. If you have months, start the Friday log today. Either way, the work you did this year happened. The job now is to make it visible enough that someone else can see it too.
A good promotion case names the level you are going for, lists that level's criteria, and gives two or three concrete examples under each one. Each example says what the situation was, what you did, what changed because of it, and where the proof lives: a doc, a ticket, a message or a metric your team already tracks. A short summary at the top ties it together.
Long enough to cover every criterion with real examples, short enough that a busy reviewer finishes it. For many people that means one to three pages plus links. If your company has a template or a word limit, follow it exactly. Cut examples that repeat the same skill and keep the ones that show range, scope and growth over time.
Describe the before and after in plain terms, even without a number. What was slow, confusing or risky, and what is different now? Point to artifacts: the process doc people now follow, the decision that got made because of your write-up, the teammate who ramped up faster. Other people's words also count. A short note from a peer often carries more weight than a vague metric.
Rebuild the year from what already exists. Walk through your calendar month by month, then your sent email, chat threads, document edit history, tickets and code reviews. Write a rough timeline first, then pick the strongest examples from it. Expect gaps. Mark anything you are unsure of and check it with a teammate or your manager before it goes into the final case.
Yes, and early. Ask which criteria they think you already meet, which ones are missing, and who else weighs in on the decision. That conversation tells you where to spend your writing effort. It also turns your manager into a collaborator rather than a reviewer who sees the document cold. Share a rough draft well before any deadline so there is time to fill gaps.
Name the team result, then say exactly which part was yours. Use phrases like 'I owned', 'I proposed', 'I wrote' or 'I unblocked', and credit others by name for their parts. Reviewers usually know who did what, so precise ownership reads as confident and honest. Vague 'we' language undersells you, and broad 'I' language on shared work can cost trust.
A brag document is a running list of your wins, kept as they happen rather than reconstructed later. Each entry has a date, what you did, why it mattered and a link to proof. It does not need polish. Its job is to make sure that when promotion or review season arrives, you are choosing from a full list instead of trying to remember a year from scratch.
No. Dayflow records your Mac screen at one frame every 10 seconds and has AI write a timeline of your day, which you can export as Markdown. That gives you raw material about what you worked on. It does not know your company's criteria, judge impact or write the argument. Its summaries can also miss or misinterpret work, so check anything before it goes into a case.
No. Dayflow is Mac only and needs macOS 14 or later, and many employers restrict what can record a work screen. In that situation a plain shared document or notebook you update every Friday beats it. It works on any device, needs no approval, and captures meetings, conversations and decisions that never appear on a screen at all.
Start the evidence habit now, regardless of when the next cycle is. Start writing the actual case a few months before the decision, so you have time to talk with your manager, spot a missing criterion and still do work that covers it. Starting the week before a deadline usually means writing from memory, which tends to favor recent work and miss the rest.
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