Hybrid Work Pilot Plan: Template and Success Criteria

A hybrid work pilot plan should state what will change, who will take part, how the team will work, what evidence will be collected, and who will decide whether to continue. Set the success criteria before the trial begins, then compare the results with a documented baseline.

Use the copyable brief, weekly evidence record, and decision memo below to test one practical change, such as a shared office day or a new weekly planning routine. This is an operational planning template for an already authorised arrangement. It does not replace your organisation's employment policies or approval process.

What a hybrid work pilot should test

Start with a problem you can observe: a handoff waits for the right colleague, a shared office day lacks the people needed for a review, or plans change too late to coordinate a visit. Write the proposed change beside that problem.

For example: “We will test a shared Wednesday review session to see whether design decisions can be completed during the session, while keeping customer coverage and focused work workable.” That is a clearer test than “We will see whether hybrid work is successful.”

CIPD's practical guidance, published in November 2021 for the Flexible Working Taskforce, recommends setting criteria for measuring success when introducing a pilot or trial. It also asks managers to agree communication and knowledge-sharing practices with their teams. These are useful process principles, not evidence that a particular schedule will work for your organisation.

Keep these three documents distinct:

• The team agreement describes the operating rules during the trial.
• The pilot plan describes the question, evidence, and decision criteria.
• The weekly location plan shows the current intention for each date.

If the operating rules are still unclear, complete the relevant parts of the team agreement template first. A pilot needs something specific to test.

Copy-and-use hybrid work pilot plan template

Copy the following fields into a shared document. Replace the brackets before launch. Keep the brief short enough for participants to read, with detailed evidence in a separate record.

1. Decision and scope

• Pilot name: [plain description of the change].
• Problem: [observable coordination or service problem].
• Proposed change: [one schedule or planning change].
• Decision at the end: [continue, expand, change and retest, or stop].
• Participants and location: [teams, roles, site, and key partner teams].
• Out of scope: [changes this pilot will not test].
• Start, end, and review dates: [dates].
• Decision owner and operational contact: [names or roles].

2. Working arrangement

• Office-day purpose: [work that benefits from being together].
• Usual pattern and shared session: [days, location, and relevant hours].
• Service coverage: [required coverage and the owner of the rota].
• Weekly planning deadline: [day, time, and time zone].
• Current location plan: [one shared destination].
• Change process: [how to correct the plan and notify affected people].
• Remote participation: [how someone joins, contributes, and receives decisions].
• Space and equipment: [what must be available, with a support contact].

3. Evidence and decision rules

• Baseline period: [comparable work cycles before the change].
• Primary success measure: [one outcome tied to the problem].
• Measure definition: [what counts, source, owner, and collection frequency].
• Success threshold: [a result agreed before launch].
• Guardrails: [service, workload, space, or participation conditions to protect].
• Feedback route: [shared operational feedback and a private route for personal concerns].
• Stop or pause condition: [specific problem that needs an immediate response].
• Evidence limitations: [missing records, unusual demand, or untested situations].
• Data handling: [who can see records, how corrections work, and when records are reviewed for deletion under existing policy].

Choose participants for the work being tested. Include the people who supply or receive its main handoffs, even if they only contribute feedback. Avoid presenting a willing team's result as proof that every role can use the same arrangement.

The Notre Dame pilot announcement from June 2021 illustrates a context-specific selection process. It considered service recipients, the role of in-person interaction, collaboration, seasonal responsibilities, and work requiring a campus presence. It describes that university's historical pilot, not a current eligibility rule for other employers.

Choose success criteria that answer the question

Use one primary outcome and a small set of guardrails. Write the numerator, denominator, and exclusion rules when using a rate. For a small team, show the underlying counts alongside any percentage.

Primary outcome: did the intended work improve?

For a review-session pilot, record the number of reviews ready for a decision, the number completed during the session, and the reason each remaining review was delayed. Decide what “ready” and “completed” mean before collecting the baseline.

For a service-coverage pilot, use the team's established service measure. For a planning-routine pilot, count avoidable rescheduling caused by missing or stale location information. Choose a measure already close to the work rather than creating a general productivity score.

Coordination: could the right people participate?

Record whether the required contributors were available and whether the necessary discussion happened. Separate a planned office day from a confirmed interaction. Someone's name on a location calendar does not establish that a review took place.

Use the work location calendar guide to define recurring patterns and date-specific changes. Keep work outcomes in the pilot record, where their meaning can be explained.

Guardrails: what must stay workable?

Check service coverage, access to a suitable workspace, remote participation, and the effect on focused work. Ask participants what became easier, what became harder, and which concrete incident explains their answer.

RISD's pilot assessment tool separates operational effectiveness, role suitability, team effectiveness, and equipment considerations. Borrow that separation when reviewing your pilot. Its institution-specific suitability checklist is not a universal assessment of employees.

Use the same short feedback questions at baseline and review. The hybrid work survey questions provide options if you need a starting point. Report how many people answered, and distinguish missing responses from positive feedback.

How long should a hybrid work pilot run?

Choose a duration that includes the work cycle you need to observe. A weekly planning habit can be reviewed sooner than a pattern whose main test is a monthly close or a seasonal service peak. Put both an end date and a decision date in the brief.

As an adjustable example, collect two representative baseline weeks, run the new arrangement for six weeks, and hold the final review immediately afterwards. These timings are suggested planning defaults, not a researched optimum. Extend the evidence window if the relevant work did not occur, and explain the reason.

Historical programmes used different time horizons. Notre Dame announced a one-year pilot. RISD's 2021 pilot agreement called for ongoing dialogue and a review at the three-month point. Neither duration is a benchmark for your team.

Do not use a short coordination pilot to claim a lasting effect on retention or promotion. Define a later follow-up if those are separate questions the organisation wants to investigate.

Run the pilot without changing the test every week

Before launch: capture the baseline

Use the same definitions and collection method you intend to use during the trial. Record workload, team membership, missing data, and exceptional events. If the baseline is incomplete, mark it as incomplete. Do not reconstruct precise figures from memory.

Read the brief with participants. Confirm the shared session, current planning destination, support contact, feedback routes, and decision date. Check that the necessary room, equipment, and remote participation method work before the first session.

During the pilot: keep a weekly evidence record

Copy this record for each week. Link to the work evidence where appropriate and keep personal explanations out of the shared version.

• Week and arrangement version: [dates and current test].
• Work in scope: [reviews, cases, handoffs, or other units].
• Primary outcome: [count or rate, including its denominator].
• Missed opportunity: [what did not happen and the operational reason].
• Guardrails: [met, not met, or unknown, with evidence].
• Participant feedback: [response count and specific themes].
• Context: [leave, workload changes, outages, or unusual events].
• Correction or adjustment: [what changed, why, owner, and effective date].
• Next action: [action and owner].

Resolve immediate operational problems promptly. If you change the shared day, meeting format, or main workflow, date the new version. Keep its results separate so the final review does not silently combine different arrangements.

A before-and-after comparison can guide a local decision, but it cannot by itself establish that the schedule caused every change. Record alternative explanations, such as a lighter workload or a new project lead. If a comparison team is available, document differences in work and staffing before treating it as a meaningful comparison.

Make an expand, change, or stop decision

Read the primary outcome and every guardrail separately. Avoid a combined score that lets a favourable attendance count hide a service or participation problem.

• Continue or expand: the agreed outcome is supported, guardrails are met, and the work observed is relevant to the proposed next step. Define the next review date.
• Change and retest: the underlying idea remains plausible, but a specific workflow problem needs correction. Name the change and the new evidence window.
• Stop: a stop condition is met, or the arrangement does not meet the agreed criteria. Record the operational fallback and how it will be communicated.
• Inconclusive: the relevant work did not occur or evidence is missing. Specify what is still needed and a bounded extension, rather than calling the pilot successful.

Worked example: a shared review session

This is a fictional example, not an Officedays customer result or benchmark. A team tests a Wednesday review session. It defines success as completing at least six of eight decision-ready reviews during the trial, while keeping all agreed service-coverage windows staffed.

The team completes seven of eight reviews, but one service window is left uncovered. Its decision is “change and retest”, because the coverage guardrail failed. The next version staggers participation and names a coverage owner. The team does not describe seven completed reviews as sufficient evidence to expand.

Copyable final decision memo

• Question tested: [problem and proposed change].
• Evidence window: [baseline and pilot dates, including arrangement versions].
• Outcome against threshold: [result and supporting evidence].
• Guardrail results: [each condition and its status].
• Participant and partner feedback: [themes and response counts].
• Limitations: [missing evidence and alternative explanations].
• Decision and reason: [continue, expand, change, stop, or inconclusive].
• Next arrangement: [what happens, owner, and effective date].
• Communication and follow-up: [who needs to know and next review date].

Keep the weekly plan visible

If your pilot needs a shared view of intended office days, Officedays in Slack lets people share their plans and supports scheduled weekly prompts. Keep the outcome measures and decision memo alongside the team's work records. Check current Officedays plans if recurring usual office days are part of your setup; that feature is listed on Pro.

Sources and methodology

Sources were checked on 9 September 2026. This article is an Officedays operational synthesis with newly written planning templates. It is not original empirical research. The example counts, timing suggestions, and decision rules are illustrative and should be adapted before use.

• Hybrid Working Practical Guidance, November 2021, commissioned by CIPD on behalf of the Flexible Working Taskforce. UK practice guidance; not government guidance or a statistical sample. Used for explicit pilot criteria and team communication principles.
• Notre Dame pilot announcement, University of Notre Dame Human Resources, 15 June 2021. A US university's historical programme announcement, with no study sample. Used for scope selection and its stated duration.
• RISD pilot assessment tool, Rhode Island School of Design. Document date not stated; filename references August 2021. Historical US institutional planning tool, not a survey. Used for distinct feasibility checks.
• RISD pilot agreement, revised 1 August 2021. Historical US institutional agreement. Used only for its review timing; its employment terms and technical requirements are not recommendations here.

These sources establish practical approaches to planning and review. They do not validate the suggested pilot length, supply universal success thresholds, or prove that any particular office schedule improves performance.