Shared Lesson Planning: Make Resources Usable

Define the planning package and the class adaptation

Shared planning can reduce duplicate preparation only when the next teacher can use the material for the intended lesson. Agree what the team shares, what each teacher adapts and who keeps the current version usable. A folder full of plans does not by itself establish less work.

HSE’s school toolkit recommends making high-quality resources and curriculum plans accessible and finding time for collaborative planning. DfE’s current England service recommends reviewing actual examples of planning with staff and discussing which expectations create unnecessary burdens. These support a conversation about the work, not a universal lesson-plan format.

Sources: [1] [2] [3]

Choose a manageable unit: one lesson, a sequence or a defined planning period. State the curriculum purpose, prior knowledge assumed and intended pupil task. Specify what belongs in the shared package and what belongs to the teacher using it with their own class. This guide is an original work-planning method; it does not determine current inspection or contractual requirements.

Check four conditions before reuse

Ask the receiving teacher to check the package before relying on it. Shared access, curriculum suitability and class adaptation are different questions. A file can be easy to open but unsuitable for the intended lesson, or well designed but dependent on equipment that is unavailable.

On a small screen, swipe inside this table. Keyboard users can focus it and use the arrow keys.

Use separate statuses for separate conditions: confirmed, proposed or still unknown, with the evidence beside them. An account login is not proof of every permission. A promised equipment slot is not a confirmed booking. The demands-and-resources worksheet gives the broader availability check.

The package need not become a large new document. Use enough information for the actual teaching need and the agreed requirements. Adding another detailed form for every shared file could recreate the duplication the team hoped to remove.

Work through a fictional shared lesson

Fictional example: three teachers plan a lesson in which pupils explain the link between a claim and its evidence. The shared package contains the purpose, two original model paragraphs, a pupil task and prompts for checking explanations. It identifies the intended place in the sequence.

The receiving teachers review it. One class needs a brief recap of the prior idea. Another needs clearer wording in the task instructions. Both teachers record those adaptations instead of treating the shared plan as ready for every class. They retain the common purpose while making the task usable.

The plan also calls for a displayed example. The file is available, but access to the relevant room equipment has not been confirmed. The team asks the resource owner before relying on it and considers an approved alternative. Having shared the file does not resolve that dependency.

After the lesson, the team records a confusing instruction and agrees an updated shared version. A local adaptation remains with its class context; the general correction becomes visible to all users. Nobody needs to guess whether a colleague’s emailed copy is now the authoritative version.

This is an original hypothetical scenario, not a real classroom trial or evidence of improved learning. Its purpose is to reveal the decisions and work that a shared package can otherwise hide.

Count creation, adaptation and maintenance separately

Compare the whole team’s work for the same planning scope. Include producing the shared material, reviewing it, adapting it, locating resources, resolving questions and keeping the version current. A local reduction for two teachers may be offset by substantial preparation assigned to the third.

Fictional comparison: separate planning is estimated at 45 minutes for each of three teachers: 3 × 45 = 135 minutes. A shared approach is estimated at 65 minutes to create the common package, 15 minutes of class adaptation for each teacher and 15 minutes of joint review: 65 + (3 × 15) + 15 = 125 minutes.

The proposed difference is 135 − 125 = 10 minutes across the team, under the assumption that the output and required quality are comparable. The creator also has their own adaptation time in that total. Do not count their entire work as the 65-minute common package and silently omit their class preparation.

If the shared package then needs 20 minutes of corrections or access work, the illustrative total becomes 145 minutes. That is 10 minutes more than the separate-planning estimate. This does not prove sharing is ineffective; it shows why omitted work changes the comparison.

These are round hypothetical estimates, not teacher time benchmarks or measured savings. Observe actual preparation and use before reporting a result. The same figures cannot establish better teaching or a health outcome.

Keep version decisions and staff feedback workable

Agree where the current package lives, who may change the shared core and how users see a revision. Name the scope of an update: general correction, new resource requirement or one class’s adaptation. Avoid turning every local copy into another competing “final” version.

Give the planning and maintenance work actual capacity. HSE’s school toolkit identifies blocks of time for collaborative planning; a meeting invitation alone does not free staff from overlapping duties. Resolve the work arrangement with the relevant owner before promising a shared deadline.

Use a concise handoff: “This is the current shared package for [purpose and sequence]. The common core is [items]. Check [adaptations and resources] before use. [Owner] will confirm general updates; local class adaptations remain labelled. [Unresolved item] is still awaiting [decision].” This is a fictional wording draft to adapt to confirmed arrangements.

Download the original shared-resource handoff (TXT). Review whether staff could actually use the package and whether work shifted to another colleague. Keep needed personal support separate from the success or completion of a planning process.

Check three shared-planning decisions

These fictional checks concern usability, the current version and the scope of a time comparison.