Focus Time and Meeting Boundaries
A finished example working agreement shows a distributed product team how to route interruptions, protect focus blocks, and review recurring exceptions. Clone it to set clear team norms without treating focus time as a ban on urgent contact.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Software and technology · Professional services
Overview
Focus Time and Meeting Boundaries is a one-page team working agreement template for groups whose day is frequently broken up by pings, drop-ins and back-to-back meetings. Its completed example follows Northstar, a fictional 34-person product team split between Lisbon and Toronto. The page starts with interruptions the team identified, then shows principles, two contrasting request scenarios, meeting and focus-block choices, a contact-signal table, role responsibilities and review triggers.
Use the example to guide a team conversation, not as a ready-made policy. Northstar asks members to recall costly interruptions, agrees a shared meeting window and individual focus blocks, and identifies when a written message, a time-bound mention, or a call is appropriate. Its sample response times and escalation conditions are explicitly the fictional team's choices. The quarterly review and exceptions thread show how to notice recurring problems and revise the agreement rather than letting norms become stale.
This template fits teams that need shared expectations for everyday requests and genuine exceptions, particularly when members work across locations or time zones. Before publishing, replace sample routes, timing, roles and review triggers with choices the team can support; verify any policy links and contact destinations. Do not use it as a substitute for company policy, a legal right-to-disconnect statement, an incident-response procedure or an individual accommodation. When policy and team norms conflict, follow the applicable policy and ask its owner about unclear scope.
Standards & compliance context
- Treat the sample response times and availability norms as fictional team choices, not legal requirements or company policy.
- Check applicable organization policies and local working-time requirements before adopting norms about availability, meetings or after-hours contact.
- Follow the authoritative organization policy when it conflicts with a team agreement, and ask the policy owner when audience, location or effective period is unclear.
- Review the page for WCAG 2.1 AA accessibility, including readable table structure, meaningful link text, keyboard access and content that does not rely on color or icons alone.
- Do not use the agreement as a substitute for an individual accommodation or an approved incident-response process.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Protect focus without cutting people off
Start with the interruptions the fictional team observed to identify which patterns your own agreement should address.
-
A working agreement for teams whose day is broken up by pings, drop-ins and back-to-back meetings This page shows a finished agreement from Northstar , a fictional 34-person product team split between Lisbon and Toronto. Use it as a model for your own. The goal is not silence. It is that everyone knows which interruptions are worth the cost and which signal to use. The interruptions that cost the most Northstar listed what had actually broken up people's work over one fortnight. Four patterns came up most: Unlabelled urgency. A message that says "quick question" with no deadline makes the reader guess whether to stop now. Repeat context switches. The same person is pulled out of deep work three or four times in a morning for questions that could be answered in one batch. Scattered meetings. A 30-minute meeting at 10:30 and another at 12:00 leaves no usable block between them. Time-zone spill. Requests sent at the end of one location's day land in the middle of another's focus block. Start your own agreement the same way. Ask each person for the last three interruptions that cost them more than they were worth, and group them.
Principles in this agreement
These four principles explain how Northstar balances focus blocks with clear routes for requests that cannot wait.
-
Northstar's agreement rests on four principles. They are a static summary of what the team agreed, not a checklist to complete and not a certification. Say how urgent a request is and give a needed-by time, in the team's own local time and in the requester's. Use the agreed route for each kind of request: written channel first, direct call only when the table below says so. Treat a calendar focus block as a request for fewer interruptions. It does not block a genuine exception. Name an exception out loud when you use one, so the team can see whether it keeps recurring.
Two requests, two different routes
Compare a non-blocking design question with a release dependency to see how urgency changes the appropriate contact signal.
-
The same person, Maya, is in a two-hour focus block. Here is how the agreement handles two requests that arrive during it. Can wait: a question about a design label Sam wants to know which wording the team prefers for a button. Nothing is blocked. Sam posts in the written team channel with the question and the options. Maya replies after her focus block, or by the end of the next working day. No call, no direct message, and no one waits on the answer. Cannot wait: a release dependency due today Priya needs Maya's approval before a release goes out at 16:00 Lisbon time on the date stated in the invitation. Priya mentions Maya in the channel with "Needed by 15:00 Lisbon on the release date; blocks the release", includes that date, and uses a date-aware calendar invitation to show Maya the local equivalent. If there is no reply in 30 minutes, Priya calls Maya's work phone or video line. Priya records the exception in the team's exceptions thread afterwards.
How Northstar protects focus
The example shows how the team chose overlap hours, individual focus blocks and shared contact expectations.
-
The completed example: overlap hours, focus blocks and the agreed contact signals After sorting their interruptions, Northstar made three choices. A shared overlap window. For the week being planned, the team checks the local-time overlap in a date-aware calendar and agrees a two-hour meeting window that falls within both locations’ working arrangements. The window is checked again around daylight-saving changes. Outside that window, a meeting needs a reason stated in the invitation. Individual focus blocks. Everyone marks at least two blocks of 90 minutes or more each week on their calendar with the label "Focus". Blocks are placed outside the overlap window where possible. One page of contact signals. The table below sets out the four routes, and every new team member reads it in their first week. Northstar also agreed that notifications are off by default for the written channel during focus blocks. Phones and video lines stay on for the one situation that justifies them. Messages are written in plain, short sentences so they translate well and read clearly on a phone screen. The response times below are this fictional team's own choices, not service levels or organization policy.
Northstar's contact signals
Use this table to match a request's urgency to the least disruptive route and a clear response expectation.
-
Pick the lightest route that gets the request answered in time. Signal Use it when What to expect Post in the written channel Nothing is blocked and the answer can wait Reply by end of next working day Mention a person with a needed-by time Work is blocked today and you have a deadline Reply, or a stated time they can reply, before your needed-by time Call or video line A mention got no reply in 30 minutes and a release or customer commitment is at risk today The person picks up or returns the call as soon as they can Calendar status "Focus" You are protecting a block of deep work Fewer interruptions, not none. An exception is still allowed
Who does what
Defined responsibilities show who proposes changes, keeps the page visible and facilitates agreement reviews.
-
Three roles keep the agreement working. These are responsibilities, not job titles. Any team member Proposes changes and flags problems with the norms. Suggest a change in the exceptions thread or at the next review. Say so when a norm does not work for your location, language or device. Team lead Keeps the agreement visible and models it. Share the agreement with every new team member in their first week. Use the same signals for their own requests and mark their own focus blocks. Review facilitator Runs the review. This is a rotating role, not always the team lead. Put the review on the team calendar every quarter. Bring the exceptions thread and ask which ones need a faster route.
People to ask about this agreement
Use this section for configured team contacts who can answer questions about the agreement.
Published company policies
Link to authoritative company policies here so readers can check scope and resolve conflicts with team norms.
Revisit the agreement and its exceptions
Review triggers and discussion questions help the team update norms when its circumstances or recurring exceptions change.
-
An agreement that never changes quietly stops being used Northstar reviews its agreement every quarter, and sooner when one of these happens: The team's locations, shift patterns or coverage change. The same exception appears three or more times in the exceptions thread. Someone reports that a norm does not work for their language, device or access needs. Questions for the review Which interruptions still cost more than they were worth, and which signal did they use? Which exceptions keep recurring, and do they need a faster, agreed route instead? Did anyone not have a fair chance to join the overlap window? What would fix that? This is a team agreement. If it ever conflicts with an organization policy on working arrangements, availability or meetings, the policy applies. Raise the conflict with your team lead so the agreement can be corrected. Before relying on a company policy, check its stated audience, location and effective period. Ask the policy owner when applicability is unclear.
How to use this template
- Ask each team member to describe recent interruptions that cost more than they were worth, then group similar examples as Northstar does.
- Edit the sample principles, meeting window, focus-block expectations and contact-signal table to reflect decisions the team has discussed and can follow.
- Assign real team responsibilities for proposing changes, keeping the page visible and facilitating reviews, and verify each channel, call route and policy destination.
- Publish the page in the team's existing intranet navigation and walk members through the difference between a request that can wait and a genuine deadline-driven exception.
- Invite members to record recurring exceptions using the team's agreed route, then review them on the chosen cadence and whenever the stated triggers occur.
- Update the authoritative page after an agreement changes, and check that new members receive it during onboarding.
Best practices
- Ask for concrete recent interruption examples before drafting norms so the agreement addresses work the team actually experiences.
- State the deadline and what work is blocked when using an urgent signal, rather than relying on labels such as "quick question."
- Choose the least disruptive contact route that can still meet the request's real deadline.
- Write meeting-window expectations in local-time terms and recheck date-aware calendar conversions around daylight-saving changes.
- Make clear that a focus block requests fewer interruptions but does not prohibit a genuine exception.
- Record exceptions in a visible team location so the review facilitator can distinguish one-off needs from recurring patterns.
- Test the agreement with members across locations, languages, devices and access needs before treating its norms as workable.
- Keep response times and escalation thresholds labeled as team decisions, and check company policy before publishing them.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this agreement cover, and who is it for?
It is a one-page working agreement for teams whose work is often interrupted by messages, drop-ins or scattered meetings. The example follows Northstar, a fictional 34-person product team split between Lisbon and Toronto. It is a model for team norms, not a company-wide availability policy.
How often should a team review its focus and meeting norms?
Northstar schedules a review every quarter and brings forward a review when locations or shift patterns change, an exception recurs, or someone reports an access or language problem. Treat that cadence as sample content, not a required standard. Choose a review interval that fits your team's work and record when the agreement should be revisited.
Who runs the agreement and handles proposed changes?
The example assigns different responsibilities to any team member, the team lead and a rotating review facilitator. Any member can suggest a change, while the facilitator brings the exceptions thread to the quarterly discussion. Adapt those responsibilities to real roles in your team rather than assuming the team lead must facilitate.
Does the template establish a legal right to disconnect or a formal response-time policy?
No. The response expectations and contact routes are choices made by the fictional example team, not legal advice, service levels or organization policy. Check applicable company policies and local requirements before adopting team norms, especially where working hours, availability or meeting practices are regulated. If the agreement conflicts with an authoritative policy, that policy takes precedence.
How should the team handle an urgent request during a focus block?
Use the lightest contact route that can meet the actual deadline, and state what is blocked and when an answer is needed. In the example, a release dependency at risk today can escalate from a channel mention to a call after 30 minutes without a reply, then gets recorded in the exceptions thread. A focus block reduces interruptions; it does not prevent a genuine exception.
What should we customize before sharing the page?
Replace Northstar's fictional team details, locations, overlap window, response expectations and review triggers with decisions your team has actually made. Confirm that channel names, phone or video routes, calendars and policy destinations are real and accessible before publishing. Keep the distinction between agreed norms and formal company policy explicit.
Does the page connect to calendars, messaging or policy systems?
The page describes contact routes and calendar practices, but the supplied structure does not configure a live messaging or calendar integration. The policy-links section may display destinations only when your site has those links configured. Set up and verify any calendar, channel or policy connections through your site's supported mechanisms.
How can a team roll this out without turning it into another static policy page?
Ask each person to identify recent interruptions that cost more than they were worth, then discuss patterns and agree the contact signals together. Share the finished page with new team members in their first week, and have the lead model the norms. Review the exceptions thread on the agreed cadence and update the authoritative page when the team changes its agreement.
Why use a template instead of agreeing norms informally?
An informal discussion can leave people guessing about urgency, response expectations and who can use an exception. This page makes the routes, responsibilities and review triggers visible in one place, with a completed example to prompt decisions. It still needs team discussion: copying Northstar's sample timings without checking your work and time-zone needs would simply make an unsuitable norm look official.
Related templates
Go deeper on the topic
-
Asynchronous communication is any exchange where the sender and receiver are not in the same moment — written messages, recorded video, shared docs, threaded...
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Focus Time and Meeting Boundaries ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
