CELPIP Reading Part 4 Practice Test: When The Workday

At global consultancy Meridian Bridge, a Toronto employee can end the day just as a Singapore colleague begins it. Messages therefore continue around the clock, but no individual can. A proposed right-to-disconnect policy would protect workers from having to read routine messages after scheduled hours. Opponents say global service makes such a right unrealistic; supporters reply that constant technical reach has been mistaken for permanent personal availability.

Senior analyst Camille Roy supports the policy after ordinary evening messages became implied tests of commitment. Most senders did not demand an immediate answer, yet staff could not know which silence would later be judged negatively. Roy wants delayed delivery as the default and no performance credit for routine after-hours replies. She accepts that the company may contact a designated on-call worker, because a shared right need not mean that nobody ever covers emergencies.

Regional director Sanjay Patel says a blanket ban on cross-time-zone messages would force colleagues to remember every recipient’s local schedule and could delay work by a full day. He distinguishes sending from expecting: staff should be able to leave a message when information is ready, while the recipient should be free to answer during local hours. Patel would support software that displays time zones and asks senders to mark the rare message requiring urgent action.

Team manager Laura Chen worries that an urgency label will spread until every deadline appears exceptional. She proposes rotating on-call schedules, a narrow list of qualifying events, and a second manager’s approval when someone outside the rotation must be contacted. If a supposed emergency recurs, the team must fix staffing or planning rather than preserve it as an exception. Chen’s boundary treats urgency as an operational failure to study, not a word that cancels protection.

Employment lawyer André Wilson says a policy will fail if employees carry the burden of proving that each message was unreasonable. Meridian should publish response expectations, keep aggregate records of after-hours contact, and review teams with repeated patterns. Occasional receipt would not itself trigger discipline; retaliation for waiting until scheduled hours would. The practical right is thus not a silent global network, but predictable freedom from consequences when a worker is not assigned to respond.

As a distributed-team lead, I prefer Patel’s distinction to a sending ban: a colleague should record information without creating 6. Choose…a technical messagean immediate dutyrepeated future delayChen's approval in another. Time-zone displays and delayed delivery make that boundary visible. Roy adds that culture pressures people without the word ‘urgent,’ so routine night replies shouldn’t earn 7. Choose…a formal on-call rolemanagerial punishmentformal legal compliancea career advantage. Otherwise willingness becomes a hidden promotion test. Chen’s narrow emergency list helps too, since repeated ‘exceptions’ reveal 8. Choose…chronic planning weaknesssuccessful urgent serviceemployee silencerare personal choice, not bad luck. A second manager’s approval slows casual escalation without blocking on-call contact. Wilson’s aggregate records then shift attention from one disputed message to 9. Choose…a message's exact wordingcontact before expectationsa repeated team patterna formal worker complaint. That’s fairer than making the least powerful employee prove every interruption unreasonable. I’d define the right as freedom from retaliation for waiting, while keeping a clearly assigned 10. Choose…emergency coverage rolefixed evening shiftgeneral message banresponse after review. Global work needs continuity, but that continuity should be a designed role, not something pulled from everyone’s private time.