A thorough list of accomplishments cannot determine your promotion raise percentage. You may still need that list to explain why your work supports a promotion and to have a grounded compensation conversation. The choice is when to assemble it. A weekly log takes small amounts of time while the work is fresh; review-time recall saves that effort until you urgently need the details. Compare the two on effort, accuracy, and how well they reveal growth in your scope. Compensation decisions also depend on factors your record does not control, so neither method promises a particular figure.
What a promotion raise percentage can and cannot tell you
A promotion raise percentage describes the increase relative to your previous pay. To calculate it, subtract your old pay from your new pay, divide by your old pay, and multiply by 100. Use like-for-like figures, such as base salary before and after the change, rather than mixing base pay with a bonus or another component.
That calculation tells you the size of a change, not how your employer decided on it. Pay ranges, the new role, local practices, and compensation rules vary. Your evidence can help establish what you took on and achieved. It cannot turn a desired percentage into a guaranteed outcome, and a well-supported promotion case may still involve a separate compensation process.
Weekly logs versus review-time recall on effort
Review-time recall appears cheaper because you write nothing during the year. The cost arrives when you search old messages, reconstruct decisions, and ask colleagues which results followed from your work. You may also spend time sorting meaningful contributions from a long list of tasks.
A weekly log shifts that work into a short, recurring appointment. Record only items with a plausible review use: a decision you owned, an improvement you made, a complex problem you resolved, or a result you can later verify. For an analyst, that could be a corrected metric definition that changed a team's interpretation of performance. A brief note at the time is enough to preserve the question, your contribution, and where to check the outcome.
Weekly capture does have a cost. If your work is highly repetitive, forcing an entry every week may produce noise. Skip weeks without a meaningful change rather than manufacturing achievements.
Which method preserves stronger evidence?
Recall works reasonably well for recent, visible projects. It is weaker for contributions whose value becomes apparent later, especially prevention, careful judgment, and work that helps another team make a decision. By review time, you may remember the successful recommendation but not the conflicting inputs you reconciled to make it credible.
A weekly entry preserves those details close to the decision. Add an outcome later instead of predicting one. For example, record that you challenged an assumption in a recurring analysis and identified the shared document or discussion where the team agreed on a revision. If the revised approach is adopted, update the entry with that fact. Do not store restricted reports or customer-level data in a personal tool; a plain-language account and a safe pointer to proof are enough.
The advantage is particularly clear when your manager was not present for the work. A specific account of your ownership is easier to discuss than a retrospective claim that you “improved reporting.”
How each method supports a promotion discussion
A review assembled from memory may show your biggest wins, but it can miss the pattern connecting them. A record built over time lets you look across projects for evidence that your responsibility expanded. Perhaps you began by fixing individual analyses, then started defining shared measurement standards and explaining tradeoffs to cross-functional partners. That progression is more informative than the number of entries you collected.
Use the record to prepare a concise case. Choose examples that show the role you are already performing, name your distinct contribution, and distinguish the result from the effort involved. Then ask how promotion and compensation decisions are made in your workplace, and which salary band applies to the new role. Those questions give you more actionable information than assuming a strong case maps to a standard raise percentage.
If you are unsure when to raise the pay question, this guide to deciding when to ask for a raise considers scope, evidence, and decision timing.
Choose a cadence that matches your work
Use weekly capture if decisions happen across many small pieces of work or outcomes surface long after the task ends. A short note after each substantial project may be more efficient if your work has clear handoffs and few parallel commitments. Reserve review-time recall as a backup, not your only source, when your contributions are spread across months.
For your next promotion conversation, start with one recent decision whose context you can still reconstruct. Record what you owned, what changed, and how you would substantiate it. Keep that promotion evidence in ImpactLogr so you can update the result when it becomes clear.