Plan and review collective worship

Keep future planning, reviewed material and the record of an actual act of worship separate. A plan published to the worship schedule is not evidence that it was delivered or that pupils experienced the intended outcome.

1. Add a straightforward schedule entry

Open Leadership → Faith inspection → SIAMS → Collective worship. Where forward planning is enabled, choose Plan worship. Complete Planned date, Led by, Worship theme, optional Scripture reference and Liturgical season, then Add to plan.

Check the returned date/theme and planned state. Use the offered Mark delivered action only after the activity actually happened; this records plan status and is distinct from writing the delivered worship log. Expand the list with its show-all control where needed rather than assuming the first eight entries are the full plan.

2. Create and review a sequence where the planner is available

The series shelf offers Build from scratch or, for eligible leaders, Generate a series. A manual series remains authored school material; choosing manual creation does not require a generated draft.

For generation, complete Theme, Number of weeks, Year groups and the offered inclusion/content choices, then Generate draft. Select the actual served year groups and wait for their options to load. A generated sequence is a starting point needing review for theological accuracy, age, inclusion, safeguarding and the school’s context.

Open the resulting series. Check its Series title, Theme and every session’s Session title, Big idea, scripture references/editions and Summary. Use the offered edit action and Save details for session details; series-heading changes use their own Save.

Open each age-appropriate content block. Check Introduction, Bible notes, You will need (one per line), activity titles/steps, prayers and safeguarding notes. Use Save block and wait for confirmation. A prayer title without text or activity steps without a usable title are incomplete material, not a finished session.

Save deliberate edits before navigating away. Changing/regenerating content can replace reviewed wording; read the confirmation and recheck the regenerated block. A failed save retains text with an error, while controls lock during the submitted save. Do not read a closed form or an old thumbnail as proof a later revision was retained.

3. Publish the reviewed plan to the intended dates

When every session is ready, inspect Review before use, choose Date of the first week for weeks without their own dates and review the sequence. The offered Publish [number]-week plan writes to the worship schedule; check the resulting dates and linked entries.

Publishing is an authorised planning action, not an email to families, a statutory approval or a delivery record. A blank/failed/still-generating sequence must be resolved before use. If generation stalls, use the offered return/recovery controls rather than launching repeated duplicates. A failed series may retain its failure label even after individual parts are regenerated, so inspect the actual saved content and state.

Use Delete series only after reading its confirmation and checking whether it already has delivered schedule entries. Deletion can remove connected schedule entries, including delivered entries; do not use it merely to tidy the shelf when that history must remain.

4. Record what actually happened

Use Log worship for delivered evidence. Enter Date, a recognisable Theme, optional Scripture reference, Pupil leadership role, What pupils said, What pupils did and What was offered for reflection, then Save worship log.

The date must be on or before today. Keep attendance/leadership and observed responses factual; a plan for pupil leadership is not an observed pupil role, and one quotation is not every pupil’s experience.

Check the saved log and the associated evidence in the appropriate SIAMS question. Use the evidence’s current/pre-vision context and actual sample when interpreting it. Expand the log list where needed; deleting a mistaken log requires confirmation and can remove the evidence tagged from it.

5. Review the next question

Return to Self-evaluation and distinguish what was offered, what was observed and what remains untested. Create any agreed owned follow-up in the appropriate task workflow rather than assuming a line in a log assigns someone work.

For vision setup, evidence tags, pupil/adult lenses, wider records, exports and access limits, see Use SIAMS. A failed source/material read is not “no worship”; resolve the failure before reporting totals or sharing the output.