How to Avoid Proximity Bias During Performance Reviews

Here’s what happens.

You walk past someone’s desk every day. You see them working. You chat by the coffee machine. You assume they’re productive because they’re visible.

Your VA in Manila? You don’t see them working. You just see the finished work.

Same output. Different perception.

That’s proximity bias in a nutshell.

You favor the people you’re physically closer to. Not because they’re better. Just because you see them more.

It shows up everywhere:

• You give the best projects to people you run into on Zoom calls
• You assume your VA is less committed because they work while you sleep
• You rate people on responsiveness during YOUR hours, not on actual results
• You forget to mention your VA’s wins in team meetings

And your VAs notice.

What Remote Workers Say About Unfair Performance Reviews

Go read remote work forums for five minutes.

You’ll see the same stories over and over.

“I hit all my targets but got a lower raise than the office team.”

“My manager forgot I existed until review time.”

“They promoted someone who literally delivers less than me, but he’s in the office.”

“I found out there’s a career cap for remote workers at my company.”

These aren’t rare situations.

This is the default experience for most remote workers unless their manager actively works against it.

The people who do well in remote reviews? They don’t just do good work.

They document everything. They send weekly updates with numbers. They schedule regular check-ins to show what they’ve done.

They make themselves visible because they know “out of sight, out of mind” is real.

But that’s exhausting.

And it shouldn’t be necessary if your review system is designed right.

Habits That Reduce Bias in Remote Performance Reviews

The system helps. But your daily habits matter more.

Make Remote Work Visible

Your VA does great work that nobody else sees.

Fix that.

Ask them to share updates in public channels. Short videos walking through what they shipped. Written recaps everyone can read.

When the whole team sees contributions, you’re not the only one forming opinions.

Also, rotate who presents in team meetings.

If it’s always the same people (the ones in your timezone), remote workers stay invisible.

Give Everyone the Same Opportunities

When a cool project comes up, who do you think of first?

Probably the people you talk to most.

Catch yourself doing this.

That high-profile client project? Your VA might be perfect for it.

But if you never offer it because “they’re remote,” they never get the wins that drive strong reviews.

Post opportunities where everyone can see them. With clear criteria for who should apply.

Stop Punishing Time Zones

Your VA works overnight relative to you. Don’t penalize them for it.

Set clear response time expectations. “Respond to urgent issues within 2 hours during your business hours” is fair.

“Be available when I’m online” is not fair if you agreed to async work.

Use async tools heavily. Task boards. Recorded updates. Written briefs.

Work quality should be obvious even when you’re never online at the same time.

Notice Your Own Bias

You have proximity bias. Everyone does.

The trick is catching it.

During review season, ask yourself:

“Am I rating face time or results?”

“Would I score this differently if I saw this person every day?”

“Am I assuming office workers are more committed just because they’re visible?”

Just asking these questions helps.

What to Say in the Actual Review

The conversation itself matters.

Start With the Goals You Both Agreed On

Pull up the document where you wrote down expectations.

“Here’s what we said we’d accomplish. Let’s go through each one.”

This keeps you honest.

You’re not rating based on feelings. You’re comparing actual performance to agreed standards.

Use Real Examples

Don’t say vague things like “You’re doing well” or “You need to improve.”

Say “You closed 47 support tickets last quarter with a 4.8 rating. Our target was 45 tickets at 4.5 or above. You beat it.”

Or say “Three projects missed deadlines by more than two days. Walk me through what happened.”

Specific is always better.

Ask About Stuff You Can’t See

You’re not there. You might be missing obstacles.

“What’s blocking you that I don’t know about?”

“What would make it easier to hit these numbers next quarter?”

Remote workers work around problems all the time without telling you.

Ask directly.

Talk About What’s Next

Reviews aren’t just looking backward.

“What do you want to learn this year?”

“What kind of work do you want more of?”

“How can I help you get there?”

When remote workers see a development path that doesn’t require being in an office, they stick around longer.

Send a Written Summary

Within 24 hours, send them a document.

Ratings you gave. Examples you discussed. Goals for next period. Development plans.

Written records keep everyone aligned.

And they prevent “I thought you said X” conversations six months later.

Red Flags You’re Doing It Wrong

Watch for these:

Remote workers always score lower than office staff, even with the same metrics.

You can’t name specific examples when someone asks why they got a certain rating.

Your VAs are never mentioned when you’re recognizing good work.

Promotion criteria feel fuzzy, especially for remote roles.

You evaluate VAs differently on “soft skills” without defining what those skills mean in a remote context.

Your VAs get feedback less often than office staff, and annual reviews surprise them.

If you’re seeing these patterns?

Fix your system. Not your VAs.

Building Performance Reviews That Work

Avoiding proximity bias isn’t complicated.

You write down clear expectations. You track actual outcomes.

You gather input from multiple people. You have regular conversations with specific examples.

You check your rating patterns.

You design it so performance shows up whether someone’s across your office or across the world.

Your VAs in Manila are doing the work.

Make sure your review process actually sees it.