Tribunal Defence Documentation PPM Services for Landlords – Section 27A Evidence Packs

A tribunal-ready pack should trace each PPM charge from lease authority to final demand without inference.

That is the standard to aim for. Under section 27A of the Landlord and Tenant Act 1985, the tribunal is deciding whether a service charge is payable, by whom, to whom, in what amount, and when. A large bundle does not answer that on its own. A clear chain does.

If a disputed charge cannot be followed from lease wording to operational record to accounting treatment, the weakness is usually not presentation. It is recoverability. The risk is not just losing a point in the hearing. The bigger problem is that competent management can start to look improvised when the route into the demand has to be rebuilt from memory.

A sound pack usually has four layers. First comes authority: the lease, the service charge provisions, repairing obligations, and any consultation material where section 20 is engaged. Second comes operational proof: the asset reference, PPM schedule, work order, attendance note, service sheet, and any readings, logs, or photos. Third comes financial traceability: the invoice, ledger entry, budget line, apportionment schedule, and demand. Fourth comes navigation: chronology, exhibit index, and one cost-trace table that lets a tribunal see the route without detective work.

A charge becomes easier to defend when the route into the demand is visible, dated, and ordinary.

What should the bundle order look like if you want the logic to hold?

Start with the lease, not the invoice.

If you begin with spend, you are asking the tribunal to accept cost before it has seen legal basis. A safer sequence is:

• Lease clauses and service charge wording
• Management obligations and any consultation records
• Asset register and PPM schedule
• Work orders and attendance records
• Service sheets, logs, photos, and certificates
• Invoices, ledger postings, and apportionment
• Demand, summary, and chronology
• Cross-reference table for each disputed item

That order mirrors the real test. Can the lease support recovery? Was the task part of a planned regime? Did it happen? Did the cost reach the correct service charge head? Can the respondent follow that route without oral repair work from your team?

If your file runs in reverse, with invoices first and explanation later, the tribunal may test reasonableness more aggressively under section 19 of the Landlord and Tenant Act 1985.

Which records usually matter most when recoverability is challenged?

The strongest records connect legal basis, operational action, and accounting treatment in real time.

A practical minimum set often includes:

• Relevant lease clause and service charge schedule
• PPM schedule with asset or location reference
• Work order with task description and date
• Contractor service sheet or attendance log
• Dated photos or readings where relevant
• Compliance certificate where the task is technical or regulated
• Invoice matching the visit
• Ledger posting and nominal code
• Apportionment support and demand reference

A simple comparison helps show why some documents do more work than others.

The aim is not volume. It is continuity.

Where do these packs usually break down?

Most failures come from broken links, not one missing exhibit.

A common example is a fire alarm service line. The lease permits recovery for common system maintenance. The budget includes alarm servicing. The contractor attended. The invoice exists. But the service sheet uses one label, the ledger another, and the demand a third. You may know they all refer to the same visit. The tribunal may not.

Inherited records create the same risk. A prior managing agent may have left invoices and contractor folders, but not the bridge between them. You can still rely on inherited material, but you need to show provenance, explain checks, and avoid overstating certainty.

A straightforward charge such as communal plant servicing should be defensible in minutes. You should be able to show lease authority, asset identity, scheduled task, instructed visit, service sheet, matching invoice, ledger entry, and apportionment into the respondent’s demand. If you cannot, the issue is no longer just file tidiness.

If you need your board to see that exposure clearly before directions tighten, a bundle-readiness review or cost-trace diagnostic is usually the most practical next step. It gives you a cleaner answer than waiting for counsel to do document archaeology at hearing speed.

You should document PPM by proving why the task existed, why it applied to that asset, and how it was delivered.

That matters because recurring spend is often attacked as routine but unexplained. A charge can look operationally sensible inside your team and still look thin in tribunal if the file cannot show why the regime existed before the dispute began. Under section 19 of the Landlord and Tenant Act 1985, reasonableness is easier to defend when the record shows a recognisable maintenance logic rather than a budget habit.

For a property manager, that is an operational discipline issue. For an RTM chair or board member, it is a governance issue. For a finance lead, it is the difference between a recurring line that reads as managed and one that reads as inherited.

A stronger PPM record starts with an identifiable asset, system, or common area. It also records why the task exists. That reason may come from SFG20, an OEM recommendation, a statutory duty, a risk assessment, or a condition-based review. What matters is that the task was there for a reason before anyone challenged the charge.

Routine spend becomes vulnerable when it cannot explain itself.

What does good PPM documentation actually show?

Good PPM documentation shows intention, execution, review, and recharge.

That means your records should answer four basic questions:

• Why was this task in the programme?
• What exactly was meant to happen?
• What happened on site?
• How did the cost enter the service charge?

A reliable PPM record usually includes:

• Asset register entry or location reference
• PPM task and frequency basis
• Standard or duty supporting that interval where relevant
• Work order with contractor instruction and date
• Service sheet or attendance record
• Readings, observations, or defects found
• Follow-on note if remedials arose
• Invoice linked to the same task and period
• Ledger coding aligned to the service charge heading

A compact comparison makes the logic easier to test.

The biggest avoidable weakness is inconsistent naming. If the schedule says “communal extract fan service,” the invoice says “ventilation maintenance,” and the ledger says “misc mechanical servicing,” you are making the tribunal do reconciliation work that should have been done in your file.

Why do recurring tasks become harder to defend over time?

Because repetition without review can look like convenience.

An annual cost does not prove itself just because it has appeared for three years. In fact, the longer it sits in the budget without explanation, the more exposed it can become. A tribunal may ask why it was annual, what asset it covered, whether that asset was still in place, and whether the frequency was ever reviewed.

Roof gutter clearance is a good example. A robust file would show roof zones, planned frequency, storm-related follow-ups where relevant, contractor attendance, dated photos, and invoice coding that matches the same service line. A weak file would show generic invoices across several years with no location references and no evidence that the visits align with a programme.

One reads like a regime. The other reads like a custom.

How should you record changes, repeats, and failed visits?

Record the reason, not just the event.

This is where many otherwise decent files start to weaken. A contractor attends and cannot gain access. A second visit is needed because a part had to be sourced. A frequency changes after repeated defects. A plant item is replaced but the old schedule still appears in finance. None of that is unusual. It becomes risky only when no one records why the pattern changed.

A stronger PPM history records:

• Access failures and cause
• Repeat attendances and reason
• Changed frequencies and operational basis
• Inspection-to-remedial progression
• Removed, dormant, or replaced assets

That protects you in two ways. It helps prevent duplication arguments, and it stops your legal team from having to infer intent from scattered records.

If your current programme sits across spreadsheets, contractor portals, and finance exports, a PPM documentation audit is often the most useful low-friction next move. It tells you whether your recurring service charge lines read as justified maintenance or recurring spend that now needs a story.

The records that carry most weight are contemporaneous, specific, linked to an asset, and consistent with the accounting trail.

That is why polished summaries should support the file, not carry it. A chronology is useful. A cost schedule is useful. An index is useful. But if there is tension between a later reconstruction and a site record created at the time, the site record usually carries more evidential force.

An invoice alone is often weak. It proves cost, not necessarily scope, necessity, or location. A certificate can be stronger, but only if it links clearly to the exact service line in dispute. A photo can help, but only if it is dated, identifiable, and tied to a visit. Contractor service sheets and attendance logs often do the heaviest lifting because they show the practical detail that invoices rarely capture.

That distinction matters in contested PPM. The real question is not whether you have many records. It is whether your best records can show a third party what happened without guesswork.

Volume rarely wins. Alignment does.

What usually counts as high-weight evidence?

High-weight evidence tends to be contemporaneous, attributable, and exact.

That usually puts the following near the top:

• Work orders with date, location, and task
• Engineer service sheets
• Attendance logs showing arrival, duration, and outcome
• Site readings, measurements, or test results
• Dated before-and-after photos tied to the visit
• Compliance certificates where relevant
• Defect notes and follow-on recommendations
• Close-out notes with asset reference

A quick hierarchy helps show the difference.

Where the work is technical or regulated, recognised formats matter. Records built around BS 5839, BS 5266, ACoP L8, or gas safety documentation often carry more confidence because the tribunal can see they were not invented for the dispute.

How should you handle photos and certificates so they carry real weight?

Use them as linked proof, not loose decoration.

A photo with no location marker, no date context, and no work order link may help your internal team, but it is weak evidence in dispute. A stronger method is to tie each image to the work order, the asset or zone, the attendance date, and a short explanation of what the image shows.

Certificates work the same way. They matter most when they are clearly tied to the service line challenged. If the certificate sits in one folder and the charge appears in another with no obvious bridge, you are asking the tribunal to infer a link that your file should make explicit.

For example, a disputed communal emergency lighting charge is easier to defend when the file shows the planned test cycle, the work order, the test logs, any remedial note, the invoice, and the ledger line under the same service head. A lone annual certificate and a generic electrical maintenance line do much less work.

Why do contractor logs so often decide whether a repeat charge looks reasonable?

Because they explain what the invoice leaves out.

A good contractor log can show:

• Arrival and departure times
• Access delays
• Readings taken
• Parts used
• Defects identified
• Safety concerns
• Need for follow-on visits
• Scope boundaries on site

That becomes decisive where a respondent argues that multiple charges were duplicative. Three invoices may look excessive on paper. Three attendance records that explain inspection, delayed access, and final repair look very different.

This is also where fragmented storage does damage. If operations hold the service sheets, contractors hold the attendance logs, and finance holds the invoices, you may have the records but still fail to present the strongest ones first.

If a challenge has already narrowed to a particular cost head or accounting year, an evidential weight review is usually worth more than a bigger bundle. It helps you see which records should carry the argument and which ones are too generic to rely on heavily.

You map them by giving each disputed line one route from authority to task to cost to demand.

That is the practical difference between a category-based archive and a tribunal-ready bundle. A folder full of schedules, certificates, and invoices may all be correct. It can still be hard to use. The tribunal needs to see how one exact charge moved from lease permission through maintenance activity into the sum demanded.

The safest method is usually a line-by-line cost trace. Each disputed item gets one row. Each row is then mapped across the same fields. That forces consistency and exposes weak spots before the hearing does.

For a managing agent, this makes operations and finance speak the same language. For a board, it gives a clearer risk picture. For a solicitor, it replaces document chase with structured fact. For a tribunal, it saves time.

What should each cost-trace row contain?

Each row should answer the same practical questions.

A useful structure usually includes:

• Disputed charge description
• Lease clause or service charge authority
• Building area or asset reference
• PPM task or compliance duty
• Work order number and date
• Contractor attendance evidence
• Service sheet, log, or certificate reference
• Invoice number and date
• Ledger code and nominal description
• Apportionment basis
• Demand reference

This works because it turns vague assertions into a fixed test. If one field cannot be completed without assumption, you have found the weak point in the evidence chain.

Take water hygiene monitoring as an example. A robust row would show lease authority for communal water systems, the outlet group or system reference, the ACoP L8 or HSG274-linked regime, the relevant attendance dates, the temperature or flushing logs, the matching invoice, the ledger posting under the water hygiene head, and the apportionment into the respondent’s demand.

That is a very different position from simply saying the charge was part of compliance.

Why is this especially important for statutory and technical tasks?

Because compliance records and service charge records often live apart.

Tasks such as fire alarm servicing, emergency lighting tests, lift inspections, gas safety work, and water hygiene checks often generate strong operational proof. But a good certificate does not automatically prove recoverability. You still need to show how the corresponding spend entered the service charge and why the lease supports that route.

That split is where many files weaken. Sometimes the compliance evidence is good and the accounting route is poor. Sometimes finance is tidy and the operational proof is generic. A tribunal-ready file needs both.

A short comparison makes the point.

One side without the other creates room for challenge.

How do you keep the map credible rather than turning it into another spreadsheet no one trusts?

Use it as a control document, not a parallel narrative.

The map should direct the reader into the underlying evidence. Each row should point to source material. Each source document should be named consistently enough that the row can be checked in moments. That makes the map a navigation tool, not a substitute file.

Naming discipline matters here. If the work order, invoice, and ledger all describe the same task differently, standardise that in the map and explain the equivalence. Do not leave the reconciliation to the hearing.

If your current records exist but still do not read as one joined-up route from PPM schedule to service charge demand, a cost-trace diagnostic is usually the cleanest next step. It saves time because it tells you quickly which charges are structurally sound and which ones still depend on explanation.

Section 27A defences usually weaken because the file can show documents but not the relationship between them.

That is the point worth fixing early. Most challenged service charge files do not fail because nothing exists. They fail because the route from authority to activity to recharge is interrupted. The lease is present. The invoice exists. The work order is somewhere. The photos are somewhere else. But the tribunal cannot see one coherent line.

When that happens, a reasonable charge can start to look uncertain. A lawful cost can begin to look reconstructed. The issue is not always legal weakness. Often it is file weakness. That still matters because the tribunal only sees what the file allows it to see.

A busy bundle can therefore be less persuasive than a smaller, cleaner one. It creates effort for the tribunal, cost for your legal team, and stress for the people trying to defend ordinary property management decisions months or years later.

A messy bundle can turn a reasonable cost into an avoidable argument.

Which breaks in the chain usually do the most damage?

The most common break points usually fall into five groups.

First, authority breaks. The lease clause is included, but not tied to the exact service head challenged.

Second, operational breaks. The invoice exists, but there is no matching work order, attendance note, or service sheet.

Third, naming breaks. The schedule, invoice, and ledger all describe the same task differently.

Fourth, timing breaks. The file does not show when work happened, when it was invoiced, and when it reached the demand.

Fifth, rationale breaks. The frequency changed, a repeat visit occurred, or inspection led to remedial work, but no one recorded why.

The most common red flags are familiar:

• Generic invoice descriptions with no asset reference
• Missing work orders behind recurring charges
• Undated or unlabeled photos
• Summaries built later with little original support
• Ledger labels that do not match operational records
• No explanation for changed inspection frequency
• Inherited files with unclear provenance
• Certificates not linked to the disputed charge head

Each issue can look minor on its own. In combination, they make a charge look speculative.

Why is retrospective neatness less persuasive than contemporaneous proof?

Because a tribunal will usually trust the record made at the time.

A clean chronology is helpful. A summary table is helpful. A cross-reference schedule is helpful. But if the best-looking part of your file was created after the dispute began and the site records beneath it are sparse, the respondent may argue that the reasoning was assembled later. Sometimes that criticism is unfair. Sometimes it lands because the original records are genuinely thin.

Inherited files are a common example. A neat retrospective summary may be needed, but it should not pretend to be original operational evidence. If records come from a previous agent or contractor, say so. Explain the checks made. Keep certainty where certainty exists.

How do over-servicing and coding drift create avoidable tribunal risk?

Because they make ordinary spending patterns look arbitrary.

Over-servicing happens when frequency increases without a recorded reason. Coding drift happens when generic nominal headings absorb different tasks over time. Both are common in live portfolios. Both become harder to explain in dispute.

If roof inspections moved from annual to quarterly because repeated ingress was found, the change may be defensible. If no one recorded the reason, the respondent may argue that uncontrolled frequency drove uncontrolled cost. If “general repairs” begins to absorb inspections, servicing, and minor remedials, the service charge route loses clarity.

The practical fix is not theatrical. It is disciplined. Test the file at the point where the challenge narrows. Can each item be tied to lease authority? Can each recurring charge be tied to a regime? Can each invoice be matched to a site record? Can changed frequencies be explained without oral reconstruction?

If the answer is uncertain, an evidence-chain review is usually the right intervention before hearing preparation becomes expensive document archaeology.

The best bundles are usually built by combining internal building knowledge with specialist bundle structuring and testing.

That division works because most organisations already know where the records are, at least broadly. The problem is not usually awareness. It is conversion. Work orders, compliance logs, contractor folders, and finance exports do not turn themselves into a tribunal-ready pack. Someone has to structure them, map them, test them, and expose the weak points.

That is a different job from day-to-day management. When left too late, it lands on people who know the building but do not have the time or discipline to convert raw material into a hearing-ready record. The result is familiar: document movement without decision clarity.

For a property team, that means operational hours disappear into historic reconstruction. For a board, it creates a false sense of progress. For solicitors, it pushes factual filing work into legal time. That is usually where specialist support earns its keep.

Legal spend rises fastest when lawyers are asked to do filing work under pressure.

Who should own which part of the work?

A practical split usually looks like this.

• Property or FM team: asset history, tasks, and operational sequence
• Compliance team: statutory and technical validation
• Finance team: invoices, coding, apportionment, and demand route
• Board or client lead: approvals, authority, and risk decisions
• Specialist bundle support: mapping, indexing, chronology, and gap testing
• Solicitor or counsel: legal analysis once the factual file is stable

That division keeps people in the right lane. Your legal adviser should not be hunting for the correct roof survey. Your maintenance coordinator should not be inventing tribunal narrative structure late at night. Your board should not be trying to reconcile nominal codes with service sheets.

When is specialist support most likely to pay for itself?

It usually makes the most difference when one or more pressure points are already present:

• Directions are live
• More than one year is disputed
• Records sit across several agents or contractors
• The challenge focuses on recurring PPM lines
• Naming is inconsistent across systems
• The board needs a clear risk picture fast
• The same records may later be needed for insurer or lender review

A simple decision view helps.

The gain is not just tidiness. It is decision quality. A proper review often shows that some items are strong, some need repair, and some should not be defended aggressively at all.

What is the most useful next step for a high-intent team?

Choose the next step by file condition, not by anxiety level.

If the records exist but are poorly mapped, a cost-trace diagnostic may be enough. If the core documents are there but the bundle logic is weak, a stress-test can often show what to fix. If records are fragmented across former agents, contractors, and finance teams, a fuller evidence-pack build is usually safer. If your board needs a quicker view, a board-ready risk summary can show which charge heads are defensible, which need repair, and which may be better narrowed.

That is the practical threshold. You do not need a grander bundle. You need a file that proves enough, clearly enough, in the right order. If you are the person who will have to explain those charge lines under scrutiny, the calmest next move is usually the one that reduces reconstruction before it starts.