How to Request On-Call Pay Parity Across Timezones in English
Learn the English phrases for raising unequal on-call compensation between teammates in different timezones or regions.
On distributed teams, on-call compensation sometimes ends up uneven — one region’s engineers get paid on-call stipends while another’s don’t, or the same rotation pays differently depending on local pay bands. Raising this fairly, with data, keeps the conversation productive rather than adversarial.
Raising the Discrepancy Clearly
Start with a factual description of what you’ve observed.
- “I’ve noticed that on-call compensation differs between our timezone and the other region on the same rotation, and I wanted to understand why.”
- “We’re covering the same severity incidents and the same rotation schedule, but the stipend structure seems to differ by location — can you help me understand the reasoning?”
- “I want to raise this constructively: is the pay difference intentional, tied to local pay bands, or is this an oversight in how the policy was applied?”
Asking for the Underlying Policy
Understanding the rationale helps you respond appropriately.
- “Is there a documented on-call compensation policy that explains how stipends are calculated across regions?”
- “Could you walk me through how the on-call rate is set for each location, so I understand what’s driving the difference?”
Making the Case for Parity
If the work is genuinely equivalent, argue on that basis.
- “The severity, frequency, and disruption of on-call incidents are identical regardless of which region is covering them — I’d like us to consider aligning the compensation accordingly.”
- “If we’re expecting the same responsiveness and the same interruption to personal time, I think the compensation should reflect that equally.”
- “I understand cost-of-living adjustments apply to base salary, but on-call disruption doesn’t scale with cost of living the same way — could we treat it as a flat, equal stipend instead?”
Proposing a Concrete Fix
Suggest something specific rather than leaving it open-ended.
- “Would it make sense to standardize the on-call stipend as a flat rate globally, separate from base salary bands?”
- “Could we pilot equal on-call pay for this rotation specifically, and evaluate whether it should extend company-wide?”
Escalating If Nothing Changes
If raised informally without progress, involve the right people directly.
- “I’ve raised this with my manager without much movement — I’d like to bring this to HR or people ops to get a clearer answer on the policy.”
- “I want to be direct: this feels like an equity issue, not just a preference, and I think it’s worth a formal review.”
Vocabulary Reference
| Term | Meaning |
|---|---|
| Pay parity | Equal compensation for equivalent work, regardless of location or other non-relevant factors |
| Stipend | A fixed additional payment, often for on-call duty, separate from base salary |
| Cost-of-living adjustment | A salary adjustment based on regional living costs |
| Rotation | A recurring schedule assigning on-call responsibility among team members |
| Equity issue | A concern about fairness in how compensation or treatment is distributed |
Key Takeaways
- Describe the pay discrepancy factually and ask about the underlying policy before assuming intent.
- Distinguish between base-salary cost-of-living adjustments and on-call disruption, which doesn’t necessarily scale with location.
- Make the case for parity based on equivalent severity, frequency, and disruption of the on-call work itself.
- Propose a concrete fix, such as a flat global stipend, rather than leaving the request open-ended.
- If informal conversations don’t lead to change, escalate to HR or people ops and frame it explicitly as an equity concern.
Navigating Nuance: Refining Your Request with Precision
Previously, we’ve discussed the core principles of requesting on-call pay parity when working across multiple time zones – highlighting the inherent imbalances and advocating for a fair approach based on workload and impact. However, simply stating that you deserve equal compensation isn’t enough in professional settings, particularly when dealing with colleagues or managers who may not fully grasp the complexities involved. The key lies in crafting your request with precise language and demonstrating a clear understanding of the factors at play. This is especially crucial for developers learning to articulate their needs effectively in English – often a subtle but significant difference can make all the difference in achieving a positive outcome.
Let’s consider a scenario: You’re reviewing a pull request submitted by a teammate based in Japan. The PR addresses critical bug fixes, and you recognize that they’ve been consistently on-call during periods when your team is largely offline. During the code review discussion via Slack, instead of saying “This isn’t fair,” which can immediately trigger defensiveness, try something like: “Thanks for submitting this, Kenji – these are really important fixes! I wanted to flag that while my team has had significantly less on-call coverage recently, you’ve been consistently supporting the system during our off-hours. Considering the increased responsibility and potential impact of your extended availability – particularly given the timezone difference – it would be beneficial to discuss how we ensure equitable compensation for this level of commitment.” Notice the use of phrases like “flag,” “increased responsibility,” “potential impact,” and “equitable compensation” - these are more sophisticated terms that demonstrate you’ve thought through the situation strategically.
Another example might appear in a pull request description itself. Instead of a vague statement, you could write: “This PR addresses a high-priority incident impacting users globally. Given my team’s reduced on-call presence and your sustained support across multiple time zones, I would like to initiate a discussion regarding adjustments to our current on-call compensation structure to reflect the additional workload and associated risk mitigation.” Framing it as initiating a “discussion” rather than demanding a change encourages collaboration and demonstrates you’re open to finding a mutually agreeable solution. Remember, focusing on impact – the impact of their work, and the impact of differing coverage patterns – is consistently more persuasive than simply stating your personal feelings about fairness.
Finally, when speaking with your manager directly, avoid emotive language. A good approach would be: “I’d like to schedule some time to discuss our on-call compensation model in light of recent operational realities. As you know, we have team members covering critical systems across significant time zones. I want to ensure that the current arrangement accurately reflects the workload and risk associated with supporting the system during periods when other teams are unavailable. Could we explore ways to objectively assess and adjust compensation based on factors like response times, incident resolution rates, and timezone coverage?” This demonstrates professionalism, a focus on objective data, and a commitment to finding a productive solution.