Guidance/Guidance

WSTCF management process

From the EM RE(S) Autumn Working Guidance 2026 v1.1 — report → FMS / MYIM → classification → response → sign-back, with the Appendix C scenarios and Appendix D sign-back levels.

Process flow

1 — Report received
WSTCF reported by a signaller (train on TC showing clear) or by an RCM alarm (RADAR / Centrix). Log time, TC, line and reporting train.
2 — FMS fault raised
Raise the failure on FMS and record all relevant information in MYIM — a separate MYIM file per track circuit, linked together (2026 guidance §9). Record on the daily CCIL 'Autumn Suspect WSTCF' log (created 00:01 for 24h); confirmed failures transfer to the per-DU WSTCF CCIL Master Log, open all season.
3 — Classify
Classify High / Low / Negligible using the hazard index (NR/L3/SIG/10047 Mod 03 §10.1) and the Appendix A flow chart (NR/L3/SIG/11231 Part 05 Module S04). RCM trace evidence drives classification — a blip under 300ms is Negligible, a sub-1 s boundary transition with the abutting TC occupied is not a WSF; no RCM at site means treat as High.
4 — Operational response
Apply the Appendix C scenario response: Reg 3.5 / double block / TS11 as required, liaising with the Level 3 SFI so special working prevents a recurrence; arrange a wheelset check of the train involved within 30 minutes of the SCWO. Ops Managers keep the live special working register up to date.
5 — Treatment before attendance
Where RCM is fitted and traces indicate railhead contamination there is no immediate requirement to send MOM / S&T to site, nor to wait for them before the railhead is treated by RHTT / MPV — but the Level 3 SFI must give permission before treatment starts. The L2/L3 SFI may still call staff to site where there is doubt or treatment is not effective.
6 — Sign back
Sign back at the Appendix D level for the classification (FF/NFF). The L2/L3 SFI can sign a TC back using RCM information exclusively and advise the Operations Manager to instruct the signaller to remove special working. L2/L3 closure needs the SFI report/statement, II RCM traces and an interlocking logger / technician's terminal extract.
7 — Report to NOC
High-risk failures: Form A (first failure) / Form B (simplified, subsequent on same circuit) to the NOC by 18:00, otherwise by close of play. TS11 s15 / F3.17A form daily.
8 — Restore normal working
Remove special working per the restoration rules below (RHTT pass / 3 consecutive trains + good RCM traces), reinstating on red/black forecasts.
9 — Withdraw special working
Formal withdrawal with photographic evidence and the Withdrawal form to the NOC (see withdrawal procedure below).

Scenario guidance (Appendix C)

Ref	Situation	Actions	Sign-back
1.1	Signaller reports a TC blip under a train (RCM fitted)	Ops: alert Control of a potential High-risk TC (treated as High until evidence disproves it), apply Reg 3.5 working, create the MYIM report. TSE / IIT: check the TC boundary transition and SCWO timing on RADAR & Centrix; risk is determined at this point (SMTH Part 05 Module S04). (A) Proved High or Low: inform the incident controller, ask for wheelsets to be checked (within 30 min), escalate to SFI Level 2. (B) Negligible with improved traces confirmed by TSE / IIT: Control decides when to remove the special working.	High/Low: full sign-back per the TC table, L2 or L1 (App D). Negligible: Control, after discussion with L1 (or L2 in certain scenarios), may remove the working without further escalation.
1.2	Signaller report, no RCM fitted	Treat as High risk and escalate to SFI Level 1 or 2 for interlocking checks (section 4 of the guidance). Confirm RCM is genuinely not fitted.	Full sign-back required.
1.3	Driver reports a change of aspect (COA) on an approach-release signal	As 1.1: alert Control (High until disproved), apply Reg 3.5, create MYIM. TSE / IIT check the boundary transition and SCWO timing; (A) High/Low — wheelset check within 30 min and escalate to SFI Level 2; (B) Negligible — Control decides when to remove the working.	High/Low: full sign-back per the TC table, L2 or L1. Negligible: Control with L1 (or L2) may remove the working.
1.4	RCM alarm (SCWO) — blip on a single track circuit	Follow the Appendix A flow chart / SMTH Part 05 Module S04. TSE / IIT: (A) is the trace more or less than 300 ms? (B) apply the track-section boundary clause (§14); (C) escalate to SFI Level 1 / 2 / 3 according to the hazard level.	High/Low: full sign-back per the TC table, L2 or L1. Negligible: if Reg 3.5 was implemented, remove after 2 recent good traces confirmed with L1 and/or L2.
1.5	Late-reported RCM alarm — less than 8 hours ago	TSE / IIT check the latest 2 train traces; if there has been a white period, run Reg 3.5 for the next 2 trains and confirm both traces are normal before removing. Under 8 hours: follow the Appendix A flow chart.	High/Low: full sign-back per the TC table. Negligible: remove after 2 good traces with L1 and/or L2; if Reg 3.5 was never implemented there is no sign-back requirement.
1.6	Late-reported RCM alarm — 8 or more hours ago	With continuous train occupation since and traces normal for 2 occupations, record as Negligible and close (beware differing train characteristics — a light engine may fail where heavier trains behave). If traces are not normal, treat as a live RCM failure under scenario 1.4.	Special working not implemented — nothing to remove.
1.7	Wheelset checks	A request to check wheelsets must be made within 30 minutes of the SCWO. After that there is no need — any contamination has likely been removed.	n/a
1.8	First train of the day	Covered by operational procedures (first-train arrangements), not the WSTCF flow.	n/a
1.9	Overlay AHB track circuit (section 12 list)	Reg 3.5 / special working is not required; treatment suggested at the nearest convenience. Check via a data logger (e.g. Centrix) whether the crossing entered a failed state.	No special working implemented, so no removal requirement.
1.10	Rail contamination from rust	Follow Rule Book module TS11 (GERT8000-TS11 Issue 6, Dec 2023) — failure of, or work on, signalling equipment. Appendix E rusty-rail areas: Newstead loop, Wetmore, Cricklewood, Nadins GF, Leicester P4, Uttoxeter Loop, Leicester North Jct.	n/a — TS11 arrangements
1.11	TC SCWO where already protected by special working	No change to the special working; when removal becomes desirable follow the normal procedure. Negligible-risk fault as the TC is already under Reg 3.5 — a fault must still be created and closed (vital for monitoring).	Normal removal procedure when desired.

Sign-back levels (Appendix D)

Failure	Fault found	No fault found
High — signal / interlocking / level-crossing failure	L3	L3
High — railhead contamination, unprotected	L2	L3
Low — indication-only circuit	L2	L2
Low — RCM blip under 300ms	L1	L2
Negligible — sequencing controls effective	L1	L2
Negligible — special block in force	L1	L1

Where SFI Level 2 or 3 sign-back is required, closure needs (A) the SFI L2/L3 report or statement, (B) II RCM traces and (C) an extract from the interlocking loggers or technician's terminal. Sign-back at Level 2/3 may be granted on RCM evidence without site attendance. Where an event is considered NOT a wrong-side failure, the RCM traces are appended to the MYIM record (NR/SMTH Part 05 Module S04 §3.13).

Restoration of normal working

Remove Reg 3.5 after an RHTT pass — reinstate at the end of the day.
Remove special working after 3 consecutive trains operate the TC correctly with good RCM traces.
Re-implement Reg 3.5 when a red or black adhesion forecast is issued.
Where RCM is installed, removal may be considered once the contamination that caused the failure has been found and treated — RCM / Centrix evidence attached to the MYIM record and the S&TME satisfied the TCs are operating correctly.
Sites without RCM: at the end of the leaf-fall season the S&TME (or representative) and an Ops representative jointly inspect the railhead; the whole area must be free of contamination (allowing for leaves still on trees). A MOM photo to Control supports the decision; the fault is closed in MYIM when all parties agree.

Withdrawal of special working

Photographs of the railhead from 2–3 points plus a line-of-view shot.
Evidence sent to the Route Control Manager and DU S&T for agreement.
Withdrawal form submitted to the NOC.
Change circulated via the daily record of special working (Appendix K) and the 18:00 Autumn Log.

Grouping of TC failures

Failures may be grouped under one SFI pack when they share the same line, the same interlocking area and the same geographical area / section of line — e.g. 5 of 8 consecutive TCs between junctions A and B with similar site conditions; not two isolated TCs 5 miles apart.
A single SFI pack may be used for all failures in the same area in the same year.
If one TC fails in an area prone to leaf-fall WSTCF, additional TCs in that area may be tested proactively; on further failures the SFI Level 3 decides whether earlier proactive checks suffice or more testing is needed.

Retrospective RCM alarms (8-hour rule)

Reported less than 8 hours after occurrence: check the last 2 RCM traces; if unavailable apply Reg 3.5 for the next 2 trains.
Reported more than 8 hours after occurrence with continuous occupation since and 2 normal traces: classify Negligible and close.

Wheelset checks (30-minute rule)

Wheelset checks of the train involved must be carried out within 30 minutes of the SCWO.
Findings (wheelset contaminated yes/no, TCA fitted/working, sander fitted/working/used) are recorded on the WSTCF CCIL entry.