SFG20 PPM Schedule Explained – Standard Maintenance Frequencies UK

An SFG20 PPM schedule is a structured, evidence‑ready maintenance plan that tells you exactly what to do, how often, and why. It replaces guesswork and inherited spreadsheets with task lists and frequencies you can defend to a board, insurer, regulator or resident when something goes wrong.

The difference between “a list of visits” and a defendable maintenance regime

Most PPM calendars start life as a copy‑and‑paste job: “service plant – monthly”, “inspect roof – annually”, with no clear link to any standard, law or risk. That feels harmless until you are sat in a room after a fire, leak or injury and somebody calmly asks, “Why that frequency? Where is that written down?”

An SFG20 PPM schedule flips that. Each maintainable item – boilers, AHUs, distribution boards, pumps – is mapped to:

• a recognised SFG20 task set
• a baseline interval linked to British Standards or manufacturer guidance
• a role, competence level and evidence expectation

You move from “we’ve always done it like this” to “this asset follows SFG20 task set X at Y interval, signed off by this role, with this log and photo here.” That is the language auditors, insurers and lenders instinctively trust.

If you want to be the person who can open a laptop, pull up a clean schedule and walk a risk surveyor through exactly how your estate is being maintained, this is the kind of PPM you need.

How a duty‑holder can start using SFG20 without rebuilding everything at once

You do not have to re‑platform your CAFM or spend six months cleaning data to get started. A sensible route is to choose one pilot: a single tower, a plantroom, or a critical system like fire alarm and smoke control.

For that pilot, you:

• assign a unique ID and clear location to each maintainable asset
• write a plain‑English description a new engineer can understand
• map each asset to the relevant SFG20 task set and manufacturer tasks
• decide which tasks and frequencies to adopt or tighten based on risk

From there you turn those into job plans engineers actually rate: step‑by‑step checks, safety notes, required readings, pass/fail criteria and mandatory photos. Once that one area runs smoothly, you replicate the pattern across the portfolio instead of trying to “boil the ocean” in one hit.

If you would rather keep your time for board packs and lender calls, you can send All Services 4U your asset export and existing calendar. We can do the first mapping pass, propose a criticality model, and hand back SFG20‑aligned job plans for your sign‑off so you stay in control of the risk decisions, not buried in spreadsheets.

Standard maintenance frequencies come from a mix of UK law, British Standards, industry guidance and real‑world engineering practice. Regulations set the duty to keep systems safe; documents like SFG20, BS 5839, BS 5266 and ACoP L8 translate that duty into weekly, monthly, quarterly or annual tasks you can put in a diary.

Why baseline frequencies exist before you apply your own risk judgement

The Fire Safety Order, Gas Safety (Installation and Use) Regulations and the Electricity at Work Regulations rarely hand you a neat calendar. They tell you to maintain plant and systems so they are safe; they expect a “suitable system” of maintenance, not box‑ticking.

Baselines exist so you are not inventing that system from scratch on every site. For example:

• BS 5839 expects weekly fire alarm tests with six‑ or twelve‑monthly service.
• BS 5266 expects monthly emergency lighting checks plus annual full‑duration tests.
• ACoP L8 and HSG 274 expect regular Legionella temperature checks and flushing.

SFG20 pulls these strands together into task lists and suggested intervals for common systems. Your job is then to deviate deliberately, not randomly. High‑load plant, vulnerable residents, ageing switchgear or critical data rooms justify tightening. Low‑risk spaces, light usage or duplicated resilience sometimes justify stretching within the guidance. Either way, you write the reasoning down and log who signed it off.

That simple gear change – from “we guessed” to “we started from this recognised baseline and adjusted because…” – is what lets you speak calmly when everyone else is back‑filling answers in real time.

How to explain frequency decisions to boards, auditors and finance

Boards, auditors and FDs are not asking for a lecture on BS numbers; they want to know your regime is not guesswork. A simple way to talk about frequencies is with a three‑column view:

• Law or standard: – e.g. Fire Safety Order + BS 5839
• Baseline: – weekly user tests + annual service
• Your regime: – weekly as standard; additional monthly panel checks for higher‑risk blocks

You can do the same for pumps, distribution boards, calorifiers or fire doors. When you can say, “The baseline for these pumps in SFG20 is quarterly, but because they run continuously in a dirty sump we have moved critical checks to monthly,” people relax. You look like the person making conscious trade‑offs, not hiding behind a contractor.

If you want that storey packaged in board‑safe language, you can lean on All Services 4U to turn technical decisions into one‑page matrices and short briefings. You stay accountable for the risk calls; we help you show your thinking in a way non‑technical stakeholders understand and support.

SFG20 task sets give you a consistent starting point, but the right frequencies for HVAC, electrical, fire and water hygiene change with building use, occupancy, vulnerability and consequence of failure. A high‑rise with sleeping risk, a 24/7 care block and a low‑occupancy office should never share the same tolerance.

What “good tailoring” looks like on real systems

When you tailor SFG20 intelligently, the pattern starts to look like this:

• HVAC and ventilation: – Air handling units running continuously in dusty, polluted or kitchen environments deserve more frequent philtre changes and inspections than units feeding a lightly used office. Cooling serving a server room or critical plant has a very different risk profile to comfort cooling in a meeting room.

• Electrical distribution: – Main switchgear and heavily loaded boards feeding lifts, life‑safety systems or data rooms justify more frequent thermal imaging and torque checks than a small consumer unit on corridor lighting. SFG20 and BS 7671 give you the baseline; the load, age and consequence of failure tell you where to tighten.

• Fire alarms and emergency lighting: – In sleeping risk or higher‑risk buildings, trying to argue away weekly tests or monthly checks is usually not worth the regulatory or insurer fight. In low‑risk, low‑occupancy commercial, you might consolidate user checks in a controlled way, but you still keep the annual engineer visits rock‑solid.

• Water hygiene: – Your Legionella risk assessment under ACoP L8 and HSG 274 leads. Void units, long dead legs, stored water, showers and vulnerable occupants all pull you towards more frequent temperatures, flushing and inspections. A single sheltered block with older residents will often justify a tighter regime than a small, modern office.

As soon as you start thinking this way, you stop being “the person with an SFG20 licence” and become the person who can explain, asset by asset, why each system is treated the way it is.

How to stop responsibilities and checks quietly falling through the gaps

The smartest frequency decisions mean nothing if nobody is actually doing the tasks. As soon as you introduce landlord/tenant splits, head‑tenant sub‑lets or mixed‑use blocks, gaps appear: landlord thinks the tenant is flushing; tenant thinks the landlord is handling plant; neither side has logs.

A practical safeguard is to build a simple ownership map at the same time as you tailor SFG20:

• list the key systems (fire, gas, electrical, water, roof, lifts)
• mark who owns each task (landlord, managing agent, tenant, specialist)
• decide where evidence lives and how both parties can see it

When All Services 4U is asked to review or rebuild a schedule, we surface those interfaces early. We sit with your leases, risk assessments and asset lists and agree, in plain language, who does what, where records sit, and how you will spot drift before a regulator, insurer or resident points it out for you.

You overlay statutory compliance by starting from the law and guidance, not from SFG20, and then tying each duty to specific tasks, intervals, competencies and records inside your SFG20‑aligned PPM. SFG20 helps you structure and resource the work; it does not replace your responsibilities under the Fire Safety Order, Gas Safety Regulations, Electrical Safety rules, ACoP L8 or the Building Safety Act.

Turning fire, gas, electrical and water duties into visible controls

A good overlay looks like a map from law to calendar, not just a dense schedule. For example:

• Fire safety: – Your fire risk assessment under the Fire Safety Order, and any Building Safety Act duties for higher‑risk buildings, drive recurring checks on alarms, emergency lighting, fire doors, compartmentation and smoke control. In SFG20 terms, that means specific task sets tagged to BS 5839 and BS 5266, plus regular fire door inspections (BS 8214/EN 1634) and compartmentation surveys, all with clear logbooks and certificates.

• Water hygiene: – Your Legionella risk assessment and written scheme convert into weekly or monthly temperature checks, flushing programmes, tank inspections and TMV servicing. Each of those becomes a named task with a set interval, log field and competence requirement, rather than living in a separate “water hygiene” world no one in property can see.

• Gas safety: – Landlord gas safety checks under the Gas Safety (Installation and Use) Regulations are non‑negotiable diary entries: every appliance has a CP12 due date; any C1/C2 defects flow straight into remedial work orders.

• Electrical safety: – Electrical Installation Condition Reports under BS 7671 and PRS regulations have planned cycles; remedial codes C1/C2 and significant C3s are tracked as actions until closed, not left as a pdf in an inbox.

With that structure in place, when someone points to a duty – “show me how you comply with ACoP L8 in this block” – you can point to distinct tasks, intervals and records rather than shrugging at a long PPM list.

A fast way to test your existing regime is to put your statutory register and your PPM schedule side by side and build a one‑page matrix. Across the top, list the core items: Fire Safety Order, BS 5839, BS 5266, Gas Safety, BS 7671, ACoP L8, Building Safety Act. Down the side, list columns for “task”, “interval”, “competence” and “evidence”.

Anywhere you cannot fill those four boxes from your PPM data, you have a blind spot. Some common ones we see:

• emergency lighting only checked ad‑hoc, not monthly and annually
• water temperatures done by a contractor with no visibility to the property team
• fire doors inspected informally with no record of which doors, when or by whom

Fixing those gaps before your next enforcement visit, insurer survey or lender review is a very different experience to arguing about them afterwards.

If you prefer a second pair of eyes, you can share a redacted PPM export and statutory register with All Services 4U. We can run a quick overlay review, mark clear passes, highlight grey areas, and show you exactly where to tighten so that “statutory compliance” is clearly wired into your SFG20 PPM rather than assumed.

The best way to build an SFG20‑aligned PPM schedule from an asset register is to make the minimum data fixes you need, map each asset type to the right task templates, and then turn those into job plans and work orders that engineers can execute and auditors can trust. You are aiming for a schedule that is credible, operable and provable, not theoretically perfect.

From messy asset list to something your engineers and auditors both respect

Almost every inherited asset register has the same problems: vague descriptions (“pump”), inconsistent naming, missing locations, no criticality. You do not need a six‑month cleanse to move; you need enough clarity that a new engineer could find and service each item.

A pragmatic sequence looks like this:

• give each maintainable item a unique ID
• record a clear, on‑the‑ground location (“Roof level 3 – North plantroom – Panel DB‑03”)
• write a description that would still make sense to a new joiner

Then you group assets by type – boilers, AHUs, DBs, pumps, calorifiers, fans – and pick the relevant SFG20 task sets and manufacturer routines. You adopt the tasks that make sense, park those that do not fit your systems, and add any risk‑specific checks your FRA or Legionella RA demands. For each task, you choose a sensible baseline interval and then adjust where use, load or vulnerability justify it.

Finally, you convert those decisions into job plans:

• numbered steps with safety notes
• readings and tolerances that make pass/fail objective
• mandatory photos or attachments where proof matters
• realistic durations that do not force bad behaviour

Those job plans become the templates in CAFM, so your engineers see the same clear expectations on every similar job instead of “do a service” and guess.

If you need a partner to get that lift done while you focus on governance and stakeholders, All Services 4U can take a copy of your asset register, propose a criticality model and SFG20 mapping, build the first wave of job plans and walk you through them. You retain the final say; we handle the grind of turning a messy register into a PPM schedule you can stand in front of.

How to pilot and scale without burning out your team

Trying to repoint an entire estate in one go is how good intentions stall. A smarter pattern is:

1. Choose one building or system with enough complexity to be a good test.
2. Build and load the SFG20‑aligned job plans there first.
3. Run them for one cycle – a quarter, for example.
4. Listen to your engineers, coordinators and residents about what worked and what did not.

You fix what the pilot reveals – access assumptions, durations, sequencing – then scale the proven pattern across similar assets or buildings. By the time you get to portfolio‑wide rollout, your SFG20‑aligned regime already reflects how your places actually operate, not just what a spreadsheet or standard imagined.

You prove SFG20 PPM completion by designing “proof” into every job up front, so done always includes documented. Each task should answer, for a specific asset: what was done, when, by whom, to which standard, and where the record now lives. When you bake that into work orders and CAFM close‑out, audit packs become exports, not archaeology.

What “good” evidence looks like for common SFG20 tasks

Think of evidence in categories your stakeholders recognise:

• Fire systems (BS 5839 / BS 5266): – weekly alarm tests logged with date, zone or call point, result and fault actions; monthly and annual emergency lighting tests with pass/fail and duration; six‑ or twelve‑monthly engineer certificates.

• Electrical safety (BS 7671): – full EICRs with coded observations; a remedial tracker showing C1/C2 items closed; test sheets and any commissioning data attached to major works.

• Water hygiene (ACoP L8 / HSG 274): – temperature logs with locations and dates; flushing records for low‑use outlets; TMV service sheets; evidence of corrective action where readings drift.

• Gas safety: – CP12 certificates for all relevant appliances; service sheets showing safety device checks and combustion readings.

• Roof and fabric: – dated, location‑labelled photo sets for inspections and repairs; short written condition summaries and clear links to any follow‑on works.

When you define, in advance, “this is what complete looks like” for each SFG20 task type, your teams know the bar. You stop arguing at year‑end about whether a tick on a worksheet is enough and start rejecting incomplete evidence in real time.

All Services 4U can help you calibrate that bar by sampling a subset of your current jobs and logs, showing you where you are already strong, where critical evidence is missing, and what “audit‑proof” would look like in your context.

How to make evidence part of the job, not a second job

If evidence sits on a separate to‑do list, it will always lose to the next emergency call. The trick is to make it part of the workflow:

• configure your CAFM so key fields – photos, readings, log attachments – are mandatory for close‑out on specific job types
• write job plans so evidence is captured as you go (e.g. “Step 5: record L/N/E readings and attach panel photo”)
• use simple naming conventions (“Site‑Block‑AssetID‑YYYYMMDD”) so retrieval is painless for anyone building a pack

Once that wiring is in place, pulling proof together for an audit, pre‑renewal review or refinance check is just a matter of filtering by asset, date range and job type. Being able to answer, in under a minute, “show me three years of roof inspections on this block” is exactly the kind of calm confidence that shifts how insurers, lenders and boards see your estate.

If you want support putting that wiring in without overwhelming your own team, you can ask All Services 4U to design or tune those standards with you. We already think in terms of “job → standard → evidence”, so you get the benefit of that discipline while you focus on being the person stakeholders trust to keep the buildings – and the paper trail – under control.