You prevented a project from going off the rails because you caught a data inconsistency no one else noticed. You mentored three junior team members who are now running their own workstreams. You created documentation that cut onboarding time in half. None of that shows up in your quarterly metrics dashboard.

When performance reviews focus on output volume, ticket closure rates, or sales numbers, employees with disabilities often face a documentation gap. The contributions that matter most (crisis prevention, knowledge transfer, process improvement) don't fit into standard KPIs. And if it's not documented, it doesn't exist when promotion decisions get made.

You need a portfolio system that captures what you do, not just what the metrics track.

Why Standard Metrics Miss Disability-Related Contributions

Most performance tracking systems measure individual output: tasks completed, deals closed, code shipped. They don't capture collaborative work, institutional knowledge creation, or the invisible labor that keeps teams functioning.

Employees with disabilities often contribute in ways that fall outside these metrics. You might spend time creating accessible workflows that benefit the entire team. You might prevent problems before they escalate, which means there's no crisis to point to as evidence of your impact. You might do the cognitive work of translating between departments, smoothing communication gaps that would otherwise derail projects.

Standard metrics reward visible crisis response. They don't reward the person who made sure the crisis never happened. The goal isn't to lower standards but to document the full scope of what you deliver when the system only measures a fraction of it.

Start a Contributions Log You Control

You can't wait for your manager to notice. You need a documentation system that runs parallel to official performance tracking.

Create a contributions log: a running record of work that matters but doesn't show up in dashboards. It's a searchable, categorized record you'll mine when building a promotion case, not a reflective diary.

What to track:

• Problem prevention: Caught a process gap before it caused a missed deadline. Flagged a data error that would've affected client reporting.
• Knowledge transfer: Created onboarding documentation. Mentored a colleague through a system they'd never used. Fielded questions that prevented repeat mistakes.
• Process improvement: Built a template that standardized team workflows. Automated a manual task that was eating hours each week.
• Cross-functional work: Connected two departments that weren't communicating. Translated technical requirements into language stakeholders could act on.
• Team stability: De-escalated a conflict between team members. Stepped in when someone was out sick to keep a project moving.

Log entries don't need to be long. Date, what you did, impact if known. "March 12: Created Slack automation that routes bug reports to the right team. Reduced response time from 48 hours to 6 hours." That's enough.

Keep this log in a format you control: Google Doc, Notion, plain text file. Don't rely on company systems that might change or disappear.

Translate Contributions Into Business Impact

A log is raw material. A promotion case requires translation.

Your manager doesn't care that you created documentation. They care that new hires are productive three weeks faster because of it. They don't care that you caught a data error. They care that the client didn't see incorrect numbers in their quarterly report.

For each logged contribution, ask: what would've happened if I hadn't done this? The answer is your impact statement.

Translation examples:

• "Created onboarding guide for CRM system" becomes "Reduced new team member ramp-up time from 6 weeks to 3 weeks, allowing faster assignment to client work."
• "Flagged duplicate records in vendor database" becomes "Prevented $15,000 in duplicate payments flagged during quarterly audit."
• "Answered 20+ Slack questions from junior analysts" becomes "Enabled junior staff to complete projects independently, reducing manager bottleneck time by estimated 5 hours per week."

Quantify when possible. Estimate when you can't quantify precisely. Your manager is estimating impact all the time when they make decisions. You're allowed to do the same.

If you don't know the downstream impact, ask. "Hey, did that template I built save you time?" The answer goes in your log.

Build a Promotion Portfolio That Tells the Full Story

When you're ready to make a case for advancement, you're not handing your manager a list of tasks. You're building a portfolio that shows the scope of what you deliver.

Pull from your contributions log and organize by impact category:

• Efficiency gains: Process improvements, automation, tools you built or improved
• Risk mitigation: Problems you prevented, errors you caught, gaps you filled
• Team development: Mentoring, knowledge transfer, documentation that made others more effective
• Strategic contributions: Cross-functional work, insights that shaped decisions, initiatives you drove

Each category gets 3-5 concrete examples with measurable or observable impact. You're not listing everything you did. You're curating the strongest evidence.

This portfolio is a living document. Update it quarterly so you're never scrambling to remember what you did eight months ago when a promotion conversation comes up.

Present Your Case Without Waiting for Permission

Don't wait for your annual review to surface contributions your manager hasn't seen. Schedule a mid-cycle check-in and bring your portfolio.

Frame it as a career development conversation, not a complaint. "I want to make sure you have visibility into the full scope of what I'm contributing, especially work that doesn't show up in our standard metrics. I've been tracking some key areas where I've had impact this quarter."

Walk through your portfolio. Give your manager time to absorb it. They may not have realized the scope of what you're doing because they're looking at the same dashboards you are.

If your manager dismisses contributions as "not part of your core role," that's information. It tells you they're measuring you against a narrow job description, and you need to explicitly connect your work to business priorities they care about. Ask what metrics they use to evaluate readiness for the next level. Then map your portfolio to those metrics.

If they still don't engage, you're documenting for the next conversation: with their manager, with HR, or with a future employer who will recognize the value.

When Accommodation Needs Complicate Metrics

If you use accommodations that affect how you work, standard metrics may penalize you for differences that aren't performance deficits.

You might work fewer hours due to a reduced schedule accommodation, which means your raw output numbers are lower. You might take longer on certain tasks because you use assistive technology or need processing time. You might avoid high-travel roles that would boost visibility but aren't sustainable with your disability.

Your portfolio makes the case that performance isn't measured by hours logged or speed. It's measured by impact delivered.

If your manager raises concerns about metrics that are directly affected by your accommodation, you're in legal territory. Accommodations are protected, and performance standards must be applied to the essential functions of your role, not arbitrary measures. Document that conversation. If you need support framing the issue, consult your HR business partner or an employment attorney.

Make This a Routine, Not a One-Time Project

The difference between employees who advance and employees who get passed over often comes down to who controls the narrative about their work.

Set a recurring calendar reminder to update your contributions log. Every Friday, add the week's wins. Every quarter, build out your portfolio. Every six months, schedule a check-in with your manager to surface what you've documented.

This isn't extra work on top of your job. It's making visible the work you're already doing.

Your contributions have value whether or not they're captured in a KPI. But they only influence promotion decisions if there's a record someone can act on. You're the person who builds that record.