What Federal Telework Agreements Say About Communication Boundaries

"Be available during work hours" sounds clear until you are actually at home, trying to figure out whether a Slack message at 6:40pm needs an answer tonight. The US Office of Personnel Management (OPM), which issues official telework policy for federal agencies, solves this problem a specific way: by requiring communication expectations to be written into the telework agreement itself, not left as an unstated assumption.

Why this applies beyond federal employees

OPM's Guide states that telework participation requires a signed written agreement between a manager and employee, and that this agreement must outline the specific work arrangement both sides agreed to. The guide is written for federal agencies, but the structure it requires, putting communication expectations in writing rather than leaving them implied, works the same way in any remote or hybrid job, even without a formal government-style agreement.

OPM's main telework page backs this up from a different angle: it offers separate online training tracks, "Telework Fundamentals for Employees" and "Telework Fundamentals for Managers," treating communication and expectation-setting as a skill both sides of the arrangement need to practice, not something that is simply assumed to work itself out.

What the agreement is required to specify

According to OPM's Guide, the "Expectations" section of a telework agreement must specify:

• The location of the approved alternative worksite and the employee's official worksite for pay and other purposes
• The duties that must be performed
• Work or productivity reporting and oversight requirements
• Expected work hours and schedule
• Frequency and modes of communication, including specific items: email versus telephone, core hours for contact, speed for returning calls, and participation in video conferencing and other meetings

That last bullet is the part most informal remote work arrangements skip entirely. Most people agree on a schedule and maybe a tool (email, chat, calls), but rarely write down an explicit answer to "how fast is someone expected to reply" or "which hours am I actually reachable."

The four specific decisions worth copying

Based on OPM's own breakdown, four decisions turn a vague "stay available" expectation into something enforceable and much less stressful to live with:

1. Which channel for which purpose. OPM's guide separates "email vs. telephone" as a decision point, which implies these are not interchangeable by default. A practical version: pick one channel for anything urgent (so people know where to look when something is time sensitive) and a separate channel for everything else, rather than letting urgency get signaled by which app a message happens to arrive in.

2. Core hours for contact. This is the window during which someone is expected to be reachable, distinct from their full working hours. Defining this explicitly answers the "can I message them right now" question before it comes up, instead of leaving each person to guess based on how quickly others usually reply.

3. Speed for returning calls or messages. OPM's guide treats this as something to specify, not assume. "I'll get back to you" means something different to different people; a stated expectation like "same business day" or "within 2 hours during core hours" removes the ambiguity that otherwise causes people to either over-check their phone or feel guilty for not replying instantly.

4. Participation in meetings. The guide separately calls out video conferencing and other meeting participation as its own expectation to define, rather than folding it into general availability. This matters because meeting attendance and general reachability are not the same commitment, someone can be "available" without being expected to be on camera for every call.

Why writing it down changes the outcome

OPM's guide also makes a point about accountability that applies regardless of employer: expectations related to performance do not differ based on whether someone is working in-person, teleworking, or working remotely, and evaluation should be based on accountability for results and quality of work, not on where someone happened to be sitting. The guide adds that managers should maintain open communication and give objective feedback on performance expectations.

Put together, the logic is: if communication expectations are vague, "availability" quietly becomes the metric people get judged on, because it is the only thing anyone can actually observe in real time. Writing down specific core hours, response speed, and channel-per-purpose takes availability off the table as a stand-in for performance, which is exactly the problem an unwritten "just be reachable" expectation tends to create.

A simple way to set this up without a formal HR process

You do not need an official agreement to borrow this structure. A short written note to your manager or team, covering the same four points, accomplishes the same thing:

1. State your core hours (for example, 9am to 5pm local time) as the window you are reliably reachable, separate from when you might also work.
2. Name one channel for anything genuinely urgent, and state what counts as urgent.
3. Give a concrete response-time expectation for non-urgent messages (for example, same business day) rather than leaving it open-ended.
4. Clarify which recurring meetings require being on camera versus just available by chat.

Key takeaways

• OPM's official telework guidance requires communication expectations to be written into a telework agreement, specifically naming channel choice, core hours, response speed, and meeting participation as separate items to define.
• Leaving these expectations unwritten tends to make constant availability the default measure of performance, since it is the easiest thing to observe.
• OPM's guide states that performance evaluation should be based on accountability for results and quality of work, not on where or how visibly someone is working.
• The same four-part structure (channel, core hours, response speed, meeting participation) works for any remote arrangement, with or without a formal written agreement.