Guide

How to ask for a raise with evidence of your work

Updated November 2026 · by Jerry Liu, Dayflow's founder

Build the case before the meeting. Keep a wins file of dated notes on what you did and what changed because of it. Rebuild older months from your calendar, sent mail and tickets. Turn tasks into outcomes and fit them on one page. A notebook or plain document is enough for most people. Dayflow helps on a Mac if you can't remember your days.

You know you have done good work this year. You can feel it in how tired you are on Fridays and in the number of people who message you first when something breaks. But when you open a blank document to write the email asking for a raise, very little comes out. The big launch in the spring, sure. The weekend you spent fixing the billing bug. After that, a fog of ordinary Tuesdays.

Then there is the meeting. Your manager asks, kindly, “What would you point to?” You hear yourself say “honestly, a lot,” and you can tell how thin that sounds. You leave knowing you deserved more than you asked for.

This guide covers why the evidence is so hard to gather, six things to try that mostly need nothing more than a notebook and your calendar, and how to turn a pile of notes into a single page your manager can forward. Up front: Dayflow, the Mac app that publishes this blog, is our product. It shows up in one section near the end, along with where it is the wrong choice.

The short version

Why can’t I remember what I did all year?

It isn’t a character flaw. Memory keeps headlines and drops the middle. A launch, a crisis or an awkward meeting sticks. The forty small fixes, reviews and favors that kept the team moving do not, even when they added up to most of your year.

Recent weeks also crowd out older ones. Whatever you did last month feels like the whole story, so a strong first half can disappear behind a slow autumn.

Some of the most valuable work leaves no trace at all. If you prevented an outage, caught a bad contract clause or onboarded a new hire so well they never needed help, nothing visible happened. That is the point of the work, and it is also why it gets overlooked.

Your manager sees only a slice too. They were in some of your meetings and none of your heads-down afternoons. They may genuinely like your work and still be unable to list it.

Then there is the discomfort. Many people find describing their own work feels like bragging, so they round down. “I helped with the migration” replaces “I planned the migration and ran the cutover.”

Finally, a raise is usually decided by more than one person. Your manager often has to argue for you to someone who has never met you. What they need from you is something written, specific and easy to pass along. Feeling deserving is not enough on its own, and that is not a judgment on you. It is how these decisions tend to get made.

If the bigger problem is that whole days blur together, not only the year, where did my day go looks at that side of it.

Six things to try

1. Start a wins file today

What to do: Open a notebook, a notes file or a shared document and title it something boring. Once a week, on the same day, write three to five lines. Each line gets a date, what you did, and what changed because of it. If nothing changed yet, write what you expect to change and come back later. A weekly work log template gives you columns if a blank page feels hard.

Illustration: A Friday entry might read: “Oct 10. Rewrote the onboarding checklist after two new hires got stuck on access requests. Sam (started Monday) had everything by Tuesday noon. Shared with the other two team leads.” That took ninety seconds and will be worth far more in March than it feels like now.

After a week: You have one entry. That is the win. The test is whether writing it was easy enough to do again next Friday. If it felt like homework, cut it to one line. For more on keeping this kind of record going, see what a work journal is and how to keep one.

2. Rebuild the past year from what already exists

What to do: Your memory is the weakest source you have. Your calendar, sent mail, finished tickets, shared documents and chat history are much stronger. Block one hour. Go month by month, starting a year back. For each month, skim the meeting titles and your sent folder, and write one line for anything you led, fixed, shipped, taught or rescued. Don’t judge yet. Just list.

Illustration: You scroll to February and see a recurring meeting called “Vendor cutover sync” that you had forgotten existed. Your sent mail from that week has a plan you wrote. That becomes a line: “Feb: wrote and ran the vendor cutover plan, three-week project, finished one week early.” Then you find a thank-you in chat from the finance lead and paste it underneath.

After a week: You should have a list noticeably longer than the one you could produce from memory, with at least a few items from the first half of the year. If the list still feels thin, try other sources: the shared drive sorted by “last modified by me,” or the code or document review history. There are more ideas in how to remember what you worked on.

3. Turn tasks into outcomes

What to do: A task says what you did. An outcome says what was different afterward. For each item on your list, ask three questions: What was the situation before? What changed after? Who noticed or benefited? Use numbers you can point to, and plain description where you can’t. If you estimate, say so. A modest claim you can back up holds up better than a big one you can’t.

Illustration: “Updated the monthly report” becomes “The monthly report used to take two people most of the first week of the month. After I rebuilt the spreadsheet, one person finishes it in an afternoon. Finance now gets it four days earlier.” If you want a rough sense of what that freed-up time is worth, the real hourly rate calculator can help you think it through, as long as you label the result as your own estimate.

After a week: Pick your five strongest items and read them to yourself. If each one answers “so what?” without you adding anything out loud, it’s working. If you keep wanting to explain, the outcome isn’t on the page yet.

4. Line your work up against the next level

What to do: Raises and promotions are easier to justify when your work matches something the company already says it values. Ask your manager or HR whether there is a written description of your role and the one above it. If there isn’t, write your own short version: what does someone one step up actually do that you are expected to grow into? Then sort your outcomes under those headings.

Illustration: Suppose the next level mentions “owns projects across teams” and “mentors others.” Under the first heading you put the vendor cutover. Under the second you put the onboarding checklist and the two new hires you paired with. A gap shows up under “sets technical direction,” and that’s useful too. You now know what to say when asked where you want to grow.

After a week: You should be able to say, in one sentence, which parts of the next level you already do. If most headings are empty, that is information, not failure. It may mean the ask is about scope first and pay second, which is a different and still worthwhile conversation.

5. Borrow other people’s words

What to do: Your own description of your work is easy to wave off. Someone else’s thanks is harder to dismiss. Search your mail and chat for “thank you,” “thanks for,” “saved us” and “couldn’t have.” Copy the best few, with the person’s name and date, into a section of your wins file. If there is a colleague whose opinion carries weight, you can also simply ask: “I’m putting together notes for a pay conversation. Would you be willing to tell my manager about the cutover if it comes up?”

Illustration: You find a message from a sales lead in June: “The pricing sheet you rebuilt is the only one the team trusts now.” You paste it under the matching outcome. Separately, you ask a peer on another team for two lines, and they send them by Thursday.

After a week: You should have three to five pieces of written thanks attached to specific outcomes. If you found almost none, it doesn’t mean your work wasn’t valued. Many people thank each other out loud, not in writing. Start noting verbal thanks in your wins file from now on.

6. Write one page and say it out loud

What to do: Put everything on one page, in this order: the specific ask (a number or range, and what it’s based on), three to five outcomes, how your work lines up with the next level, a couple of quotes, and what you plan to take on next. For the number, look at what your company publishes about pay bands if it does, and at job postings for similar roles. Then set a kitchen timer for five minutes and explain the page to a friend or partner. Do it twice. Send the page to your manager a day or two before the meeting.

Illustration: Your friend listens and says, “You buried the best thing. Lead with the cutover.” You move it to the top. On the second run you notice you apologize before saying the number, so you practice saying it plainly: “I’m asking for an increase to X, based on the scope I’ve taken on this year.” The timer goes off with a minute to spare.

After a week: The page exists, you have said the ask out loud without hedging, and the meeting is on the calendar. If you keep rewriting instead of booking the meeting, that is a sign the page is already good enough. For the review side of this conversation, how to prepare for a performance review covers the steps around it.

Where seeing your actual day helps

Steps 1 and 2 depend on remembering or reconstructing what you did. Some people find their calendar and sent mail miss most of their real work, because the work happened in a code editor, a design file or a spreadsheet, not in meetings or messages. For them, an automatic record removes the need to remember to start a timer or rebuild a day from fragments.

Dayflow is one option on a Mac. It records your screen and has AI write the day into a readable timeline. Recordings and the timeline are stored on your Mac. With local AI, screenshot analysis stays on-device. You can instead send selected screenshots to your own cloud provider or to Dayflow Pro, which deletes screenshots after processing under its privacy policy. The local and cloud processing page explains the difference. You can export a date range as Markdown from Settings → Export and pull the useful lines into your wins file.

It costs $0 and is MIT licensed, with an optional Pro plan at $20 a month (see pricing). It needs macOS 14 or later. AI summaries can miss or misinterpret work, so check anything before it goes into your case. The details here come from Dayflow’s own published documentation for version 2.2.0.

Dayflow publishes this article, and it is our product.

Where Dayflow is the wrong pick

For most people preparing for a raise, a plain notebook or document wins. The hard part of this whole process is writing down outcomes and context, and no screen recording knows that your spreadsheet fix saved finance four days.

It is also the wrong pick if:

The bottom line

Asking for a raise goes better when the evidence exists before the meeting, written down, specific and short. Start a wins file this week, even if it is one line. Rebuild the forgotten months from your calendar and sent mail. Turn tasks into outcomes, line them up against the next level, and borrow a few words of thanks from the people who saw your work. Then fit it on one page, say it out loud twice, and send it ahead.

None of this needs software. If your days are a blur and your calendar doesn’t help, an automatic record on your Mac can fill the gaps. Either way, the page you write is what makes the case.

Frequently asked questions

What evidence should I bring when asking for a raise?

Bring a one-page summary of outcomes, not a task list. For each item, say what you did, what changed because of it, and who noticed. Add work that matches the next level's expectations, a few written thanks from colleagues, and the specific ask. Keep supporting detail, like dated notes or links to shipped work, ready but off the main page so the summary stays easy to forward.

How do I remember what I did over the past year?

Rebuild it from records that already exist. Scroll back through your calendar month by month, skim your sent mail, and check closed tickets, merged work, shared documents and chat threads where you were thanked. Write one line per item with a rough date. Most people find the forgotten middle months come back quickly once they see the meeting titles and threads from that period.

What is a brag document or wins file?

It is a running list of your work and its results, written as things happen instead of at review time. Each entry has a date, what you did, and what changed. It can live in a notebook, a notes app or a shared document. Its value comes from being kept up, so short weekly entries usually beat long ones you stop writing after a month.

Do I need an app to track my work for a raise?

No. For most people a plain document or paper notebook beats Dayflow or any other app for this, because the hard part is writing down results and context, which no recording captures. An automatic record helps only if you regularly can't remember what filled your days. Start with a five-minute weekly note and add software only if that note keeps coming up empty.

How far in advance should I start preparing to ask for a raise?

Start the wins file now, whatever the date. For the conversation itself, a few weeks of preparation is usually enough to rebuild past months, write the one-page case and rehearse it. Ask your manager when pay decisions are made, because budgets are often set before review season. Raising it before that point gives your manager time to argue for you.

How do I turn tasks into measurable results without making up numbers?

Use numbers you can point to, and use plain description where you can't. Before and after works well: a report that took two days now takes an afternoon, or a handoff that used to bounce back now goes through. Name who benefited. If you estimate, say it is an estimate. A modest claim you can back up holds up better than a big one you can't.

Can I use Dayflow to prove my hours to my employer?

Dayflow is a personal record, not a proof-of-hours system. It has no team reports, payroll approvals or invoices, and its AI summaries can miss or misread work, so check them before sharing. It is better used to jog your own memory, then write your case in your own words. Sharing raw screen recordings with an employer is rarely a good idea.

What if my manager says there is no budget for a raise?

Ask what would need to be true for a raise at the next cycle, and when that cycle is. Ask whether other things are on the table, such as a title change, scope or training. Write down what you agreed and send a short follow-up note. Your evidence is not wasted. It becomes the starting point for the next conversation, and you can keep adding to it.

Should I give my manager my evidence before the meeting?

Often, yes. Sending the one-page case a day or two ahead lets your manager read it calmly and think about who else needs to see it. Many managers have to make the case to someone above them, and a clear page they can forward helps. Keep the page short and factual, and save the longer notes for questions.

See where your day actually went

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