Knowledge base
The UK lift reference, in short entries
2 entries across 4 categories
Reach-for-it definitions and one-page explainers for lift owners, managers and residents. Deeper reading lives in the guides and fault-first walkthroughs in the symptoms hub.
Use arrow keys to move between results, Escape to return to the search box.
Fundamentals
1 entryHow lifts work — the vocabulary, components and lift types you will meet.
- How a passenger lift worksUpdated 2026-07-16
The car, counterweight, motor room, controller and safety gear explained in plain English for UK building owners and managers.
Compliance & standards
1 entryUK duties, LOLER, PUWER, EN 81 and the paperwork that proves them.
- LOLER in one pageUpdated 2026-07-16
The Lifting Operations and Lifting Equipment Regulations 1998 explained on a single page for UK building owners and managers.
Operations & maintenance
0 entriesService intervals, contracts, spares and the day-to-day of running a lift.
Entries coming soon.
Safety & emergencies
0 entriesWhat to do when something goes wrong — for users, managers and duty holders.
Entries coming soon.
How to use the knowledge base
The knowledge base is the reference layer of the site: definitions, component explanations, safety background and the vocabulary that turns up in service reports and quotes.
Where the symptom pages start from what a lift is doing. These entries start from what something is.
Search matches entry titles and body text. The category and lift-area filters narrow results to the kind of equipment you have. If a search returns nothing useful, the hub pages for brands.
Symptoms and guides are usually a faster route in than a second search.
Why the terminology matters
Most frustration between lift owners and service companies is vocabulary. A landing door is not a car door. A governor is not a brake.
A thorough examination is not a maintenance visit — but quotes and reports use all of those terms as though everybody already knows them.
Getting them right lets you read a report, question a line item. Describe a fault in language an engineer can act on.
It also protects you commercially. Knowing that maintenance and LOLER thorough examination are separate duties, or that a controller fault and a drive fault mean different parts.
Makes it much harder to be sold work you do not need.
Where the safety line sits
Every entry stops at observation. Nothing here asks you to force a door, move a stuck car, remove a panel, or enter a pit or shaft. Those are engineer tasks under controlled conditions.
The risk to an untrained person is severe.
What you can safely do is look, listen, note and report from the landing: car position, door state, indicators and displays, sounds, and when the behaviour started.
That handful of details is what makes a callout useful.
How an entry is built and checked
Each entry starts from a question people actually ask, not from a keyword.
Someone wants to know what a governor does, why a lift needs a pit, what a door operator is, or why a report mentions a competent person.
The entry then answers that in the order an owner needs it: what the thing is. Here, it sits in the lift, what it looks or sounds like when it is behaving normally.
What an engineer usually checks when it is not.
Sources come first. Component and terminology entries follow manufacturer paperwork and published industry references. Safety entries follow the wording of the regulation itself and official guidance, rather than a summary of a summary.
Where a detail could not be confirmed against something published. The entry says so plainly instead of filling the gap with a plausible guess.
Entries are then rewritten for readability: short sentences. No jargon left undefined on first use. No instruction that would put a reader inside the equipment.
Anything that changes — a revised regulation, a manufacturer updating its manual, a reader pointing out an error. Sends the entry back through the same pass rather than getting patched in place.
Using the knowledge base alongside the rest of the site
The knowledge base works best as the second page you open, not the first. If your lift has stopped, start from the symptom index.
Because that is organised by behaviour: doors that will not close. A car that will not level, a display showing something unfamiliar, a repeating beep. Once the symptom page has narrowed things down.
The knowledge base explains the parts and terms that page mentions.
If you already know the make, the brand pages are the faster route.
They carry the faults most commonly reported against that manufacturer in the UK, the questions a service company will ask about it, and — where a manufacturer or documented service reference confirms them.
The meanings of that brand's error codes.
The guides sit between the two. They cover the processes around a lift rather than the hardware inside it: who pays for a repair, what a LOLER thorough examination involves.
How to read a quote, what to expect on a first callout. Reading a guide before a phone call usually saves more time than reading three component entries.
What to write down before you call anyone
The single biggest difference between a short callout and a long one is the quality of the note you make before picking up the phone.
All of it can be gathered standing at the landing, without touching anything that is not a normal control.
Note the lift type and roughly its age, the manufacturer and model, and any unit or job number printed on the plate or sticker by the landing.
Then record the state: where the car is sitting. Whether the doors are fully open, fully closed or part-open.
Exactly what any display or indicator shows including symbols and colours, and any repeating sound and how often it repeats.
Finally, record the history. When did it start, is it constant or intermittent.
Did anything change beforehand — a power cut, water ingress, building works, a recent service visit, or a key switch or fire-service switch being operated.
Add who holds the maintenance contract and when the last thorough examination was done. Then take the lift out of service, keep people away from it, and report it.
Get help by email
Can't find what you need?
Describe the term, fault or scenario in plain words — we'll route it to the editor or an engineer reviewer.