A small team needs four clear agreements for hybrid work: when people are available, which meetings require shared time, how work is handed over and when on-site presence is necessary.
For each area, define three things:
- The default: What normally happens?
- Reasonable exceptions: When can a different arrangement apply?
- Communication: How, when and to whom should someone report a change?
The goal is predictable cooperation. It is not continuous visibility into where people are or what they are doing.
Manage agreed outcomes, not visible activity
Hybrid work becomes difficult when colleagues have to guess. They may not know when someone will reply, whether a meeting requires attendance, who owns the next step or why they need to come on site.
More monitoring does not necessarily solve this. Online status, time at a desk and physical presence show activity. They do not reliably show whether important work is moving forward.
Managers still need to coordinate work, address missed commitments and make decisions. The useful distinction is between checking agreed outcomes and watching activity throughout the day.
A short working agreement supports this distinction. It gives people a shared default while allowing for customer needs, focused work, travel, personal circumstances and differences between roles.
Define response expectations without requiring constant availability
Availability should tell colleagues when they can reasonably expect contact and a response. It should not imply that everyone must reply immediately throughout the day.
Agree on four points:
- The hours when team members generally overlap.
- The normal response time for routine messages.
- The route for genuinely urgent matters.
- How someone indicates that they are unavailable.
For example:
Team members are normally reachable between 10:00 and 15:00 on working days. Routine messages should receive a response by the next working day. Urgent operational issues should be raised by phone. Planned absence and focused work should be added to the shared calendar.
The exact arrangement should reflect the role. Customer support may need defined coverage. A developer, designer or analyst may need uninterrupted blocks of time. If coverage matters, assign it explicitly instead of expecting everyone to monitor every channel.
Define urgency as well. A service interruption or a customer waiting for a same-day decision may be urgent. A colleague wanting a quick update usually is not.
Decide which work needs a meeting
A hybrid team should distinguish between work that needs live discussion and work that can happen asynchronously.
Use a live meeting when people need to resolve disagreement, make a joint decision, run an interactive workshop or discuss a sensitive issue. Status updates, routine approvals and information sharing can often be handled in writing.
A practical meeting agreement can state that:
- Recurring meetings are scheduled in advance and have a clear purpose.
- Every meeting has an owner and identifies any decision required.
- Participants receive relevant material beforehand.
- Decisions and assigned actions are recorded afterwards.
- An in-person meeting needs a practical reason that remote participation cannot serve equally well.
Unplanned calls will still happen. A customer issue may need an immediate decision, or a complex problem may be easier to settle live. In those cases, the organiser should explain the urgency, invite only the people needed and record the outcome for anyone affected.
Make handovers complete enough for the next person to act
A handover is complete when the next person can continue without reconstructing the situation from messages, personal notes and memory.
Every handover should record five things:
- Current state: What has been completed?
- Next action: What needs to happen now?
- Owner: Who is responsible?
- Timing: What is the deadline or next decision point?
- Obstacle: What is blocking progress or creating risk?
For example:
The customer approved the revised scope. Marta will update the delivery plan by Thursday at 14:00. Pricing for the additional integration is still waiting for supplier confirmation.
This is more useful than saying, "Marta has the latest information." It shows what changed, what happens next and what remains unresolved.
The team should also agree where handovers are recorded. The specific tool matters less than having one current place that everyone knows to check.
Require on-site presence for a practical reason
On-site presence should be connected to the work. It should not be treated as automatic evidence of commitment.
Practical reasons may include:
- Access to a location, physical document or piece of equipment.
- Onboarding that involves demonstrations or several colleagues.
- A workshop that depends on intensive live collaboration.
- A customer or operational obligation tied to a location.
- Work that has not been handled effectively at a distance.
The agreement should also define notice. For example:
On-site attendance is required when the work needs physical access or when the organiser explains why in-person collaboration is necessary. Planned sessions should be added to the calendar at least two weeks ahead where possible. Shorter notice is reserved for operational needs that could not reasonably have been predicted.
Some roles will require more physical presence than others. Consistency does not mean giving every role the same schedule. It means applying clear criteria and explaining why arrangements differ.
Keep the agreement to one page
A hybrid working agreement does not need to read like a formal policy. A one-page table is enough if it covers the default, reasonable exceptions and communication method for each area.
| Area | Default | Reasonable exceptions | Communication |
|---|---|---|---|
| Availability | Expected overlap and routine response time | Focus time, appointments, travel and role-specific coverage | Shared calendar or agreed team channel |
| Meetings | Which discussions are live, remote or in person | Urgent decisions and unusual customer needs | Invitation stating the purpose and required participants |
| Handovers | Required information and where it is recorded | Incidents where immediate action must come first | Update the agreed record as soon as practical |
| On-site presence | Situations that normally require attendance | Individual circumstances or an effective remote alternative | Advance notice from the organiser or manager |
Test the agreement against recent problems. If a decision was delayed because nobody owned the next step, strengthen the handover rule. If people attended an office day without understanding why, clarify the criteria for on-site presence.
Review the agreement after the team has used it in real work. Keep rules that remove recurring uncertainty. Change or remove rules that no longer fit the roles, customer obligations or type of work.
Frequently asked questions
Does every hybrid team need fixed office days?
No. Fixed office days can help when a team has recurring work that benefits from being done together. They are not a universal requirement. A small company can instead define which situations require on-site attendance and schedule them with reasonable notice.
Should working hours be the same for every role?
Not necessarily. Customer support, operations, sales and focused project roles may need different coverage. Each role's availability should be clear, and the arrangement should cover necessary collaboration and customer obligations.
How should a team handle repeated exceptions?
First check whether the default still fits the work. A repeated exception may show that the agreement needs revision. If the agreement remains appropriate, address the missed commitment directly instead of adding restrictions for the whole team.
Where should the agreement be stored?
Store it somewhere every team member can access without creating competing versions. The specific tool matters less than having one current version, a named owner and a clear way to announce changes.