Companies are demanding proof of productivity: Here's how to write yours
In January 2026, Amazon began requiring all 350,000 corporate employees to submit 3 to 5 specific accomplishments as part of its revised "Forte" performance review system. The internal guideline asks for "specific projects, goals, initiatives, or process improvements that show the impact of your work."
Source: Fortune, January 8, 2026.
Amazon is not the first and will not be the last. Musk used the same playbook at Twitter in 2022 and again at federal agencies in 2025 with the "what did you get done this week" weekly email. RTO mandates have moved from suggestion to enforcement, and tech layoffs hit 142,000 in 2026. The common thread: companies want defensible documentation of who delivered what.
This guide covers what is happening, what companies are actually asking for, and how to build the record before your employer demands it.
TL;DR: Document 2 to 3 specific accomplishments per week with metrics and named scope. Use the X-Y-Z formula: accomplished X, measured by Y, by doing Z. When your company asks for a list, you copy and paste instead of scrambling. BragBook auto-imports your work from GitHub, Jira, Linear, Asana, and Dovetail so the record builds itself.
Why companies are demanding proof of productivity now
This is not a coincidence. Three trends collided in 2025 and 2026 to make documented accomplishments a workplace requirement rather than a personal habit.
RTO mandates moved from policy to enforcement. 54% of Fortune 100 employees are now subject to five-day office requirements, up from 11% the year prior. 32% of companies factor in-office attendance into performance evaluations, and 29% consider it for promotions and pay. The proportion of companies tracking attendance jumped from 45% to 69% year over year. Once your physical presence is being tracked, demands for your output tend to follow.
AI compressed expectations of individual output. Developers using AI coding tools produce 40 to 55% more code per sprint at comparable quality. New software engineering job postings declined 15% in the first two months of 2026 versus 2025. When the bar for what one person can ship has moved, the bar for proving you cleared it moves with it.
Layoffs forced documentation. Tech layoffs hit 142,000 in 2026, with 55% explicitly citing AI or automation as a factor. When companies are deciding who stays, leaders want defensible records of who delivered. Performance reviews became the audit trail. See our tech layoffs and career security report for the full breakdown.
Sources: JLL Q2 2025 Office Market Dynamics report. Visual Capitalist, biggest tech layoffs 2025 to 2026.
What companies are actually asking for
The formats look different on the surface but ask for the same thing underneath. Specific work, named scope, measurable outcome, your role in delivering it.
Amazon Forte (350,000 corporate employees)
Submit 3 to 5 accomplishments per review cycle. Internal guidance defines them as "specific projects, goals, initiatives, or process improvements that show the impact of your work." Reviews now feed an Overall Value rating that drives compensation, with weight on accomplishments, peer feedback, and Leadership Principles compliance.
Musk weekly accomplishments (Twitter/X and federal agencies)
Send 5 bullet points each week listing what was accomplished. First deployed at Twitter in 2022, then re-used in 2025 across federal agencies. Estimated time per submission: "less than five minutes." Non-response was treated as voluntary resignation in some implementations.
Standard performance review formats
Most large companies now ask for a self-review with 5 to 10 accomplishments, each tied to a metric or outcome. The format is consistent across Google, Meta, Microsoft, and most public tech companies. See self-review examples for what each role should produce.
Sources: The HR Digest, Amazon performance evaluations require proof of productivity. Axios, Musk federal employees weekly email.
What documented impact actually looks like
The difference between a strong accomplishment entry and a weak one is not effort. It is specificity. Same week of work, two different framings, two very different reads.
Vague
Helped the team improve onboarding. Worked on a few projects. Contributed to cross-functional initiatives.
Documented
Reduced week-one activation drop-off from 41% to 12%
Led the onboarding redesign across product, design, and engineering. Recovered 40 hours of weekly support time and lifted activation by 22 points.
The X-Y-Z formula works for almost any role: accomplished X, measured by Y, by doing Z. Lead with the outcome, attach the number, end with how you made it happen. Quantifying accomplishments walks through the formula in depth.
What good entries look like for each role
The format is the same. The work and the metrics change by role. Here is what a single strong entry looks like for engineers, product managers, designers, and UX researchers.
Software engineer
"Led the migration of the payments service to a new queue architecture. Cut p95 latency 38% and prevented an estimated 2 outages per quarter based on the prior 12-month incident history. Mentored 2 engineers through the migration plan and rollback drills."
Product manager
"Owned the pricing experiment that grew net revenue retention by 8 points over Q2. Aligned product, design, finance, and customer success around three pricing variants, shipped to 20% of accounts, and rolled the winner to 100% by end of quarter."
Product designer
"Redesigned the onboarding flow that lifted week-one activation 22%. Ran 8 usability tests, shipped 3 design system components reused by 4 other teams, and reduced support tickets for first-time setup by 40 hours per week."
UX researcher
"Ran the discovery research that shaped the Q3 retention roadmap. Synthesized 22 customer interviews into 3 prioritized opportunities, presented findings to leadership, and the team shipped 2 of the 3 within the same quarter. The third lifted day-7 retention 11 points."
Notice the pattern. Each entry names the work, attaches a measurable result, and clarifies the writer's role. None of them say "contributed to cross-functional initiatives."
How to build the record before your company asks
The easiest version of this list to write is one you have already written. Build the habit before the demand lands, and the demand becomes a copy-paste.
Log 2 to 3 wins per week. Friday afternoon, 5 minutes. Write down what you shipped, what changed because of it, and the metric tied to it. Keep entries to two or three sentences. See how to document your work for the full system.
Tag entries by skill and project. When your company asks for a list, you filter for relevance and pull the top 5 in seconds. Without tags, you scroll through 6 months of notes hoping you flagged the right ones.
Save evidence as you go. Screenshot positive Slack feedback. Copy the dashboard showing the metric you moved. Save the email thread where leadership approved your proposal. Specifics fade. Artifacts do not.
Auto-import wherever you can. Manual logging fails for most people within a month. Auto-importing from GitHub, Jira, Linear, Asana, and Dovetail means the record populates itself from work you are already doing.
Take a quarterly snapshot. At quarter end, distill your top 3 to 5 wins into a one-page highlight reel. You always have a current version ready for a Forte-style request, a recruiter ping, or a 1:1 with your manager.
BragBook handles the weekly logging, tagging, and auto-import in one place. The AI turns your logged entries into resume-ready and review-ready content so the writing part is done before the request lands.
What to do if your company asks tomorrow and you have nothing
Most people are here. Do not panic and do not try to recall everything from memory. Reconstruct from the artifacts your work already produced.
Start with your calendar. Scan the last 6 months of meetings. Look for launch reviews, retro meetings, project kickoffs, and 1:1s. Each one points to a project you can write about.
Search Slack and email. Search your own messages for words like "shipped," "launched," "migrated," "deployed," "wrote," "led." Search for project codenames. Search for "thanks" and "great job" to find feedback artifacts you forgot you received.
Pull closed tickets and merged PRs. Engineers, look at merged GitHub PRs in the last 6 months and group them by feature. PMs and designers, look at closed Jira or Linear tickets, shipped Figma files, and the deck library. Each artifact is one bullet you can rewrite as an accomplishment.
Read your last self-review. Whatever you wrote in your last review is a strong starting list. Update each entry with what happened since.
Rewrite each entry with X-Y-Z. Once you have raw material, rewrite each item as accomplished X, measured by Y, by doing Z. If you cannot attach a number, look for one. Most work has measurable signals if you look.
A 6-month backfill takes 2 to 4 hours if you start with the artifacts and rewrite at the end. Going forward, weekly logging keeps the cost at 5 minutes.
Common mistakes people make on accomplishment lists
Listing job duties instead of accomplishments. "Responsible for the analytics service" is a job description. "Rebuilt the analytics service to handle 4x traffic on the same hardware" is an accomplishment. Every entry should name what changed because of you.
Burying the metric. Numbers should be visible in the first half of the sentence. A bullet that hides "38% improvement" in the third clause reads weaker than one that opens with it.
Using "helped with" or "contributed to." These phrases hide your role. Replace them with verbs that name what you actually did. Led, designed, shipped, migrated, automated, recovered, owned.
Only listing the biggest project. A single major launch reads as one win. Three to five accomplishments with range reads as consistent impact. Reviewers and managers are looking for the second.
Skipping qualitative wins. Mentoring, hiring, and process improvements rarely have a clean metric but matter at promotion time. Include them with whatever measurable signal you can attach (hires landed, mentees promoted, hours saved by a process change).
Reconstructing from memory at the last minute. You will forget half of what you did and soften the metrics on the half you remember. Weekly logging fixes this. The cost is 5 minutes a week.
Why this matters even if your company has not asked yet
Amazon, Twitter, and federal agencies are the loud examples. The quieter version of the same shift is happening at hundreds of other companies under different names. Quarterly check-ins, Workday goals, OKR retros, calibration packets, 1:1 prep templates. The format varies. The underlying ask is the same. Show your work.
The leverage of a documented record extends beyond review season. It powers job search and offer negotiation, builds the foundation for a promotion case, and gives you concrete evidence when asking for a raise. The single habit pays into every career conversation you will have.
The people who treat documentation as a quarterly scramble lose every time. The people who treat it as a weekly habit win every time. The window to build the habit is between requests, not during them.
Start the record before the request lands
The companies asking employees for accomplishment lists are not going to stop, and the list is going to keep getting harder to fake. Start documenting your work weekly and you will not be scrambling when the next Forte-style email lands in your inbox.
BragBook auto-imports from the tools you already use, tags entries by project and skill so your accomplishment list is one filter away, and uses AI to turn each entry into review-ready and resume-ready content. When the request comes, your evidence is already compiled.
Frequently asked questions
What does proof of productivity mean at work?
Proof of productivity is concrete, documented evidence of the work you have completed and the impact it had. It usually takes the form of a list of specific accomplishments with metrics, dates, and outcomes. Amazon's Forte review system requires 3 to 5 such accomplishments per employee. Musk popularized the format with the 'what did you get done this week' weekly email at Twitter and later in federal agencies.
Why are companies suddenly asking for accomplishment lists?
Three overlapping trends. First, return-to-office mandates moved from suggestion to enforcement, with 32% of companies now factoring office attendance into performance evaluations. Second, AI has compressed expectations of individual output, making it harder to justify roles without visible results. Third, tech layoffs hit 142,000 in 2026 alone, and leaders want defensible documentation when deciding who stays.
What format do most companies use for accomplishment lists?
Amazon's Forte asks for 3 to 5 accomplishments framed as specific projects, goals, initiatives, or process improvements that show impact. Musk's federal email format asked for 5 bullet points of what was accomplished in the last week. Common elements across formats: specific scope, named project, measurable outcome, and your role in delivering it.
What should I write if my work does not have obvious metrics?
Almost every role has measurable signals if you look. Count things (PRs reviewed, interviews conducted, customers contacted). Measure time saved (hours per week recovered, days cut from a process). Estimate scope (teams affected, users reached, decisions influenced). Cite feedback (quote a Slack message, reference a 1:1 comment). The goal is specificity, not perfection.
How far back should my accomplishments list go?
Most companies ask for the last performance cycle, which is typically 6 to 12 months. Amazon's Forte covers the last review period. For job searches, the last 2 to 3 years is the sweet spot. Older entries are useful as context but should not be your headline material because hiring managers care about recent impact.
What if I have not been tracking my work and my company just asked?
Backfill from artifacts. Check your calendar for big meetings and launches. Search Slack for project names and feedback. Look at closed Jira or Linear tickets, merged GitHub PRs, shipped designs. Skim old 1:1 docs. You can rebuild a reasonable list in a few hours. Going forward, log weekly so you never have to scramble again.
Should I share my accomplishment list with my manager outside of reviews?
Yes, and most people do not. Sharing a short list of recent wins in your 1:1 or in a weekly update keeps your impact top of mind for the person making promotion and retention decisions. You do not have to wait for a formal request. A monthly summary in your manager's inbox is one of the highest-leverage habits you can build.
Can AI help me turn my work history into a polished accomplishment list?
Yes, but only if you have the raw material. AI tools can take rough notes and turn them into structured impact statements with strong verbs and clean formatting. BragBook combines accomplishment tracking with AI that generates polished review-ready content from your logged entries. The AI is not the magic, the consistent logging is. The AI just removes the writing friction at the end.
