Key takeaways

  • Start with the team’s tasks, not a national stereotype.
  • Check peak attendance rather than the weekly average.
  • Review the agreement with people working in different locations.

Start with the work, not a national stereotype

Mountain coast beneath low cloud
Kym Ellis / Unsplash, photograph from the historical FLYDESK article. Landscape illustration, not a workplace or customer reference.

Denmark, Finland, Iceland, Norway and Sweden offer useful material for thinking about distributed work. They do not provide a single attendance policy that another organisation can copy. A software team, a public-facing service and a workshop have different requirements, even when they share an address.

The Nordic Council of Ministers’ report on remote work and multilocality examines regional development and planning. Its emphasis on cooperation and learning across countries is a reason to compare contexts, rather than claim that every Nordic employer follows the same model. The practical suggestions below are a team-planning method, not a description of national law or a ranking of countries.

Write down the conditions for working together

The Finnish Institute of Occupational Health highlights trust, joint planning and support for independent work. It also recommends developing hybrid arrangements through trials and feedback. That is more useful to a manager than assuming trust removes the need for an agreement.

For your own team, record who needs to exchange information, which decisions require a discussion and where the result will be documented. Define the deadline for updating a planned office day and the contact to use when plans change. A shared calendar should help people coordinate; it should not become a substitute for discussing workload or judging completed work.

Start with a short flexible-work policy. Give each rule an owner and an example. “Tell the project lead before changing the workshop day” is easier to apply than “collaborate effectively”.

Give an office day a specific purpose

Before asking colleagues to travel, identify the activity they will do together. A design review might need the people who can decide, a usable room and a prepared document. Routine updates may be better shared before the meeting so that the session can focus on unresolved questions.

Check the practical sequence: confirm participants, agree a date, reserve the right space and publish the preparation. Leave a way for someone who cannot attend to contribute beforehand and read the decision afterwards. Do not assume that everyone in the building is available for the same meeting.

Prepare the shared day

  1. Purpose

    Name the decision or task and the people needed.

  2. Coordination

    Agree the date, space and preparation before travelling.

  3. Review

    Record the decision and ask what should change next time.

Suggested planning sequence, not a Nordic legal rule or product screenshot.

Test the busiest day before changing office capacity

Consider a fictional team of 12 people with eight usable desks. Its proposed attendance is six people on Monday, ten on Tuesday, eight on Wednesday, four on Thursday and two on Friday. That is 30 planned desk-days across five days, or an average of six people per day. Tuesday still exceeds capacity by two.

This example assumes each attending person needs one desk for the whole day; rooms and visitors are excluded. Moving two willing Tuesday attendees to Thursday would bring the peak down to eight, but only if it does not prevent the intended joint work. Adding up weekly attendance alone cannot answer that question.

Use the office size calculator to explore your assumptions, then check daily demand, suitable equipment and any seats that are unavailable. Planned attendance is not a measurement of actual occupation or productivity.

Review exceptions without creating a second-class team

Invite feedback from people whose work or circumstances do not fit the initial pattern. Ask whether information arrives in time, whether remote contributors can influence decisions and whether the chosen office day actually brings the necessary colleagues together. Separate these questions from a preference for one weekday.

Keep a short record of the problem, the change being tested and when it will be reviewed. For example, a team might move a decision meeting earlier while leaving individual attendance choices unchanged. This tests a coordination problem without treating every difficulty as a reason to impose more office days.

Keep the agreement visible in everyday planning

Publish the approved working pattern where people plan their week, with a clear route for exceptions. FLYDESK hybrid scheduling and desk booking address planned presence and shared spaces. They do not establish a national employment policy or prove that one working pattern produces better results.

Review a real team scenario in a demonstration: changing an office day, finding a suitable desk and informing the people affected. Keep the agreement small enough to use, and revise it when the work changes.

Continue reading