HROUS

UK Office Owners: Lift Traffic Analysis Requirements Before Upgrades

Advertisement

Set the study requirements before discussing equipment

Before choosing an office lift upgrade, commission documented occupancy scenarios, justified survey coverage, separate service measures and comparable equipment options. Put these in the study brief rather than starting with a preferred replacement package.

Advertisement
Open elevator in a modern airport terminal, showcasing sleek design and signage.

Use the active CIBSE Guide D: Transportation Systems in Buildings as the relevant guidance. Its scope includes traffic planning, surveys, simulation, performance optimisation and modernisation.[2] CIBSE’s archived 2015 Guide D is marked “Superseded” and identified as reference-only, not for use on current projects.[3]

Advertisement

Keep the status of the checklist clear:

  • Status of this checklist: the survey coverage and service criteria below are recommended commissioning inputs to be agreed for the project, not prescribed numerical requirements. The cited CIBSE pages and ORR’s railway-specific station-lift report do not establish compulsory office survey periods or numerical acceptable-service targets.[1][2][3]
  • Recommended commissioning inputs: request demand assumptions, survey evidence, defined service measures and option comparisons.
  • Project-agreed requirements: record which scenarios, deliverables and performance criteria the consultant is to assess.

Agree the project requirements before fieldwork and modelling begin.

If purchasing the guidance, the listed standard PDF price is £220 plus VAT for the active Guide D and £150 plus VAT for the superseded edition. These are publication prices, not lift-study quotations.[2][3]

Advertisement

Define tenant and occupancy scenarios

Ask for a scenario register separating the observed position from the occupancy the building is intended to accommodate. Guide D covers data gathering, traffic descriptions, car loading, mixed traffic and multiple entrance floors.[2]

Specify the following as project choices, not prescribed CIBSE scenarios:

  • Current observed position: record the population and attendance associated with the surveyed conditions, identifying assumptions separately from observations.
  • Intended change: describe the proposed tenancy or occupancy arrangement, including which floors and areas would become occupied or vacant.
  • Higher-demand case: agree the additional demand to test and document its basis, rather than accepting an unexplained uplift.
Advertisement

For each case, request floor-by-floor population assumptions, expected attendance, occupied and vacant areas, entrance use and relevant shared destinations. Decide explicitly whether phased occupation, hybrid attendance or tenant turnover needs a separate case. Leave no default percentage or headcount implicit.

Ask the consultant to define the project’s tenant-change cases and numerical occupancy and attendance assumptions alongside the traffic descriptions covered by Guide D.[2] Require the consultant to explain and justify the values selected for the project.

Request passenger counts, origins and destinations, movement direction and car-loading observations, alongside an explanation of how these become model demand. This is a recommended specification drawing on Guide D’s coverage of traffic surveys and traffic descriptions, not a prescribed register.[2]

Use consistent fields for each input:

  • Input: what the value describes.
  • Source: where it came from.
  • Status: measured or assumed.
  • Scenario: which case uses it.
  • Owner confirmation: accepted, amended or awaiting agreement.
Advertisement

Agree representative survey coverage

Turn the input register into a survey plan before fieldwork. Ask which passenger movements need observing and how the proposed coverage will capture them. Guide D covers traffic surveys, data logging and monitoring, alongside mixed traffic, car loading and multiple entrance floors.[2]

Include these requirements in the brief:

  • Movements: identify relevant arrival, departure, lunchtime and inter-floor movements, with reasons for exclusions.
  • Days and observation windows: request proposed dates and times, with a justification for how they represent the office’s attendance patterns.
  • Physical coverage and method: identify entrances and floors to be observed, how passengers and their origins and destinations will be counted, and how missing observations will be handled.
  • Context: request attendance information, unusual tenant activity and lift availability during each observation window, so the report explains what the counts represent.
  • Coverage gaps: identify conditions the survey will not observe, distinguishing proposed additional measurement from assumptions used to fill gaps.

Agree the survey-day count and time-of-day sampling windows against the study’s questions rather than accepting an unexplained standard survey package. Use Guide D’s traffic-survey coverage as the relevant guidance.[2]

Advertisement

Separate interval, actual waiting time and queues

Request separate report entries for interval, actual waiting time and queue length, rather than accepting one headline indicator as evidence that passenger waits meet the project requirements.

Guide D covers quality of service, performance time and measurement of lift kinematics.[2] Ask the consultant to specify the definitions and acceptable numerical thresholds needed to complete that reporting schedule. Make the definitions and assessment criteria part of the commission.

  • Define each measure: specify the event being measured, start and end points where relevant, observation location, units and aggregation period.
  • Account for unfinished journeys: explain how passengers still waiting or otherwise not served within the reporting window are treated.
  • Label the evidence: distinguish measured passenger observations, calculated indicators and simulated results. Reserve “observed actual waiting time” for passenger observations; label modelled waiting times as simulated.
  • Show variation: request a distribution or range alongside the selected summary, rather than an unexplained average.

These are proposed reporting requirements for work drawing on Guide D’s coverage of surveys, monitoring, simulation and performance measurement.[2] Agree which measures determine suitability and how each will be assessed before comparing options.

Require simulated waiting-time results to be presented with their assumptions and limitations, not as guaranteed passenger waits.

Advertisement

Compare retained equipment with modernisation

Request a retained-equipment baseline before assessing changes. Make this an owner-selected requirement alongside Guide D’s coverage of modernisation and lifecycle planning.[2]

Ask which control changes, performance improvements, component replacements or broader modernisation options merit investigation, without assuming every option is technically feasible. These categories reflect Guide D’s coverage of legacy and destination-control algorithms, performance improvement, minor replacement of major components, modernisation and lifecycle planning.[2]

Specify the same agreed occupancy scenarios, passenger-demand inputs and service definitions for each option. Require differences to be disclosed and explained, rather than allowing an equipment change to be assessed against more favourable demand assumptions.

Advertisement

Request a consistent comparison entry for each option:

  • Scope: identify the retained-equipment baseline or proposed intervention, stating what stays and what changes.
  • Model assumptions: show demand inputs, control behaviour and equipment-performance assumptions, highlighting departures from the baseline.
  • Service results: assess each agreed measure against the project criteria.
  • Limitations: identify feasibility questions and unresolved dependencies.
  • Recommendation: explain the reasons to progress or reject the option.

For each predicted improvement, ask what drives it and what technical verification remains before equipment selection. Require the recommendation to explain how the change addresses the stated demand problem.

Advertisement

Test sensitivity to changing demand

Ask which uncertain assumptions could change the ranking of the options, then agree sensitivity tests around them. As project-selected tests, vary attendance levels, arrival concentration, entrance use and inter-floor demand where relevant. Guide D covers mixed traffic, multiple entrance floors and simulation applied to modernisation.[2]

Request a short explanation of the methods. Guide D includes Monte Carlo simulation, CIBSE and ISO simulation templates, and the relationship between calculation and simulation.[2] Ask the consultant to address:

  • Method comparison: where calculation and simulation are both used, explain differences between their results and how these have been investigated.
  • Run variability: where simulations are repeated, explain how variation between runs is represented rather than presenting a single run as definitive.
  • Decision sensitivity: identify which options meet the project criteria across the tested scenarios and where the recommendation depends on an unresolved assumption.

For modelling drawing on Guide D’s simulation methods, ask the consultant to specify sensitivity increments, scenario probabilities and simulation-run counts.[2] Request a project-specific justification for those choices and show the limitations alongside the recommendation.

Advertisement

Require a report with a traceable recommendation

Specify a report that links the recommendation to observations and assumptions, not just a preferred equipment option. The following is a recommended deliverables schedule, drawing on Guide D’s coverage of data gathering, surveys, simulation templates, modernisation, and tests and records—not a prescribed reporting template.[2]

  • Survey evidence: coverage records, passenger-count summaries, origin–destination information and car-loading observations.
  • Inputs: the scenario register and equipment assumptions, showing how observations were translated into modelling inputs.
  • Assessment basis: service definitions and project-agreed performance criteria.
  • Results: measured, calculated and simulated findings in separate, clearly labelled sections.
  • Option comparison: retained-equipment and modernisation results assessed on consistent terms.
  • Decision trail: sensitivity findings, data gaps, limitations and reasons for the recommendation.

Ask the conclusion to state whether the evidence supports an equipment decision. If not, request the specific unresolved input, why it matters and what further investigation is proposed—not a general statement that more information is needed.

Check the study before authorising expenditure

Use this final check against the agreed commission:

  • Occupancy scenarios include the proposed tenant changes.
  • Survey coverage is justified and gaps are identified.
  • Passenger movements, origins, destinations and car loading are documented.
  • Measured inputs are separated from assumptions.
  • Interval, actual waiting time and queue reporting are defined separately.
  • Performance criteria were agreed before option assessment.
  • Retained-equipment and modernisation options use consistent assumptions.
  • Sensitivity findings and modelling limitations are disclosed.

Return the report for clarification if the preferred option rests on unexplained occupancy assumptions, incomplete survey coverage or simulated performance presented as guaranteed. Base equipment selection on how the option addresses the agreed demand scenarios, not merely an improved headline simulation result.

References

  1. Passenger Lifts at Stations Performance and Information 15 March 2024 (orr.gov.uk, 2024)
  2. CIBSE Guide D: Transportation systems in buildings (2025) (cibse.org)
  3. Transportation systems in buildings: Guide D | CIBSE (cibse.org)
Advertisement

Similar reads