BUILDIT CONSULTANT PATHWAY
Vertical Transport Consultant
Understand the vertical transport consultant's role, the information and assumptions they control, the interfaces they influence and the points where decisions about lift and escalator performance, builder’s work and long-lead system integration intersect with procurement, construction, testing and approval.
Know their role, pressures and place within the team.
01The role in plain EnglishThey control defined lift and escalator performance, builder’s work and long-lead system integration outcomes within their appointment›
Understand the vertical transport consultant's role, the information and assumptions they control, the interfaces they influence and the points where decisions about lift and escalator performance, builder’s work and long-lead system integration intersect with procurement, construction, testing and approval.
Usually responsible within scope
Vertical transport performance specification and design advice within scope.
Coordinates but may not own
Building structure, electrical supply design, fire strategy, builder's works execution or supplier manufacturing design beyond review.
02Why the project needs themThey make lift and escalator performance, builder’s work and long-lead system integration explicit, coordinated and verifiable›
03When they matterTheir influence changes across the project lifecycle›
04What they own and do not ownResponsibility is not the same as coordination›
Usually responsible within scope
Vertical transport performance specification and design advice within scope.
Coordinates but may not own
Building structure, electrical supply design, fire strategy, builder's works execution or supplier manufacturing design beyond review.
Builder responsibilities remain
Construction methodology, sequencing, temporary conditions, site verification, procurement, trade coordination, identifying departures, controlling releases and complying with the contract remain builder responsibilities unless expressly reassigned.
Do not assume
A vertical transport consultant review does not automatically approve work outside the appointment, transfer trade design, close statutory requirements or authorise contractual change.
05What good looks likeA good Vertical Transport Consultant makes the whole team more effective›
Before the issue
Inputs, assumptions, responsibilities and release gates are visible in the lookahead before core concrete, lift order, factory manufacture, shaft handover or authority inspection.
When the issue appears
The exact condition is marked up, site facts are verified, affected interfaces are identified and workable options are presented.
After the decision
The answer is recorded in the correct design information, trade release, inspection or evidence record and downstream parties act on one position.
At handover
Installed work, testing, certificates, as built data and operating information tell the same story.
06Dependencies and pressuresTheir answer is shaped by people, inputs and obligations you may not see›
Understand how the consulting team actually works.
07The real consulting teamThe formal output is visible; coordination happens between people›
The Vertical Transport Consultant rarely closes a live interface alone. They test assumptions with Architect, Structural, Electrical, Fire, seek authority and negotiate who will change before a formal answer appears.
Encourage direct coordination
Let the actual technical people solve the shared condition early.
Control the outcome
Return material decisions, departures and consequences to the authorised project record.
08Existing working relationshipsWho has worked together before can matter more than the company logos›
Strong existing relationships can accelerate trust, candid challenge and coordination. Assess the named people, their recent comparable work, availability, continuity and how they resolved disagreement—not merely the firms on the organisation chart.
Upside
Known response styles, tested interfaces and quicker access to the right decision-makers.
Watchpoint
Groupthink, complacency, cliques, undocumented decisions and historical loyalty to an outdated client position.
09Engagement gaps that affect deliveryInterface conditions that make good performance possible›
10When to involve themGive them the right issue before options close›
Shaft concrete or steel release, lift manufacture, shaft handover, permanent-power issue, unsafe installation condition, failed emergency mode or authority-inspection blocker.
Cores, lobbies, pits, headrooms, loading lifts, destination control, fire and security integration or installation access shared by multiple disciplines.
Use a controlled written request where vertical transport design information conflicts, assumptions are missing, a departure needs review or the approval record must be preserved.
Escalate when the vertical transport design owner is clear but the consequence has become material and the last responsible release, inspection or approval time is approaching.
11Top 20 construction questionsThe recurring questions builders need the Vertical Transport Consultant to close›
Before acting on “What shaft size is required”, confirm the controlling value and basis, datum where relevant, operating or construction condition, tolerance and margin, actual site information, adjoining interfaces and source document.
Before acting on “What pit depth do we need”, confirm the controlling value and basis, datum where relevant, operating or construction condition, tolerance and margin, actual site information, adjoining interfaces and source document.
Before acting on “What headroom is required”, confirm the controlling value and basis, datum where relevant, operating or construction condition, tolerance and margin, actual site information, adjoining interfaces and source document.
Before acting on “Can the lift door move”, confirm the current design basis and reason for the change, test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, coordinate architecture and lobbies, structure and shafts, electrical and communications, fire and security, and identify work already released, approvals, testing and the smallest safe hold point.
For “What structural loads apply”, provide the exact location and current references, state the governing criterion and decision required, identify affected interfaces and irreversible work, give a genuine need date and record the answer in controlled project information.
Before acting on “What power supply is required”, confirm the controlling value and basis, datum where relevant, operating or construction condition, tolerance and margin, actual site information, adjoining interfaces and source document.
Before acting on “Can the lift type change”, confirm the current design basis and reason for the change, test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, coordinate architecture and lobbies, structure and shafts, electrical and communications, fire and security, and identify work already released, approvals, testing and the smallest safe hold point.
For “What builder's works are required”, provide the exact location and current references, state the governing criterion and decision required, identify affected interfaces and irreversible work, give a genuine need date and record the answer in controlled project information.
To resolve “When must the shaft be ready”, mark the exact location and geometry, confirm traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, access and tolerances, coordinate the condition with architecture and lobbies, structure and shafts, electrical and communications, fire and security, and close the installation and evidence requirements before release.
For “What installation access is needed”, provide the exact location and current references, state the governing criterion and decision required, identify affected interfaces and irreversible work, give a genuine need date and record the answer in controlled project information.
Before acting on “Can the pit detail change”, confirm the current design basis and reason for the change, test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, coordinate architecture and lobbies, structure and shafts, electrical and communications, fire and security, and identify work already released, approvals, testing and the smallest safe hold point.
To resolve “How does fire recall work”, map the operating modes, inputs, outputs, ownership and failure states across architecture and lobbies, structure and shafts, electrical and communications, fire and security; then define the coordinated drawing, programming and integrated test that closes the interface.
To answer “Can the landing level tolerance be accepted”, identify the governing requirement and authorised decision maker, then close the supporting design, specialist, evidence, inspection and contractual gates rather than relying on one review.
For “What communications are required”, provide the exact location and current references, state the governing criterion and decision required, identify affected interfaces and irreversible work, give a genuine need date and record the answer in controlled project information.
For “Can we stage lift handover”, confirm the temporary and permanent conditions, prerequisites, sequence, access, protection, hold points and evidence before the next activity removes options.
For “What temporary protection is required”, confirm the temporary and permanent conditions, prerequisites, sequence, access, protection, hold points and evidence before the next activity removes options.
Before accepting “Can the supplier use an alternative product”, compare traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, evidence, compatibility, warranty, lead time, maintainability, interfaces and every required approval.
To close “What testing is required”, define the acceptance criterion, evidence, sample or test condition, witness point, responsible signatory, defect response and the release or handover gate.
To close “What is blocking commissioning”, define the acceptance criterion, evidence, sample or test condition, witness point, responsible signatory, defect response and the release or handover gate.
To close “What is the final lift handover requirement”, identify the controlling document and responsible owner, list every design, client, statutory, contractual and evidence gate still open, then issue one position that construction and handover can rely on.
12Do not ask this. Ask this.Better framing produces faster, more useful answers›
13Interpret the responseReviewed is not the same as coordinated, authorised and ready for release›
14What slows them downThe visible delay may be a symptom of a different unresolved problem›
Know what to expect and recognise when information is breaking down.
15Typical outputsUnderstand the evidence without turning BUILDIT into a package scope›
16Stages and issue statusA stage label is not proof of design maturity›
Concept and strategy
Set lift quantity, type, traffic performance, cores, lobbies, fire strategy, accessibility, loading and maintenance or replacement approach.
Design development
Coordinate shafts, pits, headrooms, beams, doors, lobbies, power, cooling, communications, fire, security and access.
Documentation and coordination
Close the performance specification, builder’s work, openings, loads, interfaces, finishes, controls and supplier-design criteria.
Procurement and fabrication
Place the long-lead order only after type, performance, shaft geometry, interfaces and commercial options are sufficiently frozen.
17Critical informationWhat the builder must protect before work becomes irreversible›
18Document and revision disciplineIf the change is hard to find, it is not being managed›
19Common missing or unclear informationThe gaps that force the delivery team to infer the specialist outcome›
20Common performance issuesThe twenty builder gripes that surface most often›
These are recurring builder-side complaints, not claims about every Vertical Transport Consultant. Convert each into a maturity check, interface owner, hold point, evidence requirement or decision date.
The Vertical Transport Consultant package is labelled ready while key lift and escalator performance, builder’s work and long-lead system integration criteria, inputs or approvals remain open.
The project receives different answers and no controlled resolution identifies what governs.
Changes are not clearly marked, described, registered or summarised for affected packages.
The answer refers elsewhere, restates intent or omits the authorised action needed by the builder.
Site-critical answers wait on another person, client or discipline without a visible escalation route.
Standard content does not address the actual geometry, condition, exposure, duty or interface.
The builder or trade is expected to complete unresolved design without a clear brief, boundary or acceptance path.
Fabrication information becomes the first place unresolved design and cross-discipline clashes appear.
Access, sequence, temporary conditions, tolerances, procurement and trade constraints are not tested before release.
Inspections, tests, certificates, as-builts and close-out records are requested after access or rectification options disappear.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Treat this as an early warning that the Vertical Transport Consultant interface, not merely the technical task, is breaking down.
Shaft sizes, structural loads.
Pit depth, power.
Manage the interface, not the personality.
21Behind-the-scenes pinch pointsThe twenty tensions hidden behind a simple request for information›
A seemingly simple request can depend on several disciplines, the client, a certifier or a specialist trade.
They can provide a view but cannot commit the client, company, regulator or another designer.
Consultants test positions privately because the interface is shared or politically sensitive.
Trust can accelerate honest coordination; history and alliances can also distort the current decision.
The apparent delay may be an unresolved design-leadership issue rather than simple inaction.
A consultant may qualify a response instead of openly contradicting a peer.
No appointment clearly owns the missing design, coordination or evidence task.
Acceptance may extend beyond available information, competence, authority or fee.
Earlier briefs, approvals and conversations may still shape the consultant response after the delivery model changes.
Commercial pressure cannot remove duties around competence, safety, compliance and records.
A genuine site need still requires adequate facts, checking and the right signatory.
The consultant may be waiting on survey, selections, another design, client direction or trade data.
Redesign, unpaid work or changed scope can appear as a technical delay.
The people producing information may not know assumptions held by project leaders.
A small design response can disrupt sequence, fabrication, access, rework and programme.
Shafts, lobbies, doors and finishes.
Shaft sizes, structural loads.
Additional cars drive shafts, pits, lobbies, structure, power, controls, maintenance and large area opportunity cost.
Survey dimensions, plumb, openings, embeds, beams, waterproofing, drainage, access, cleanliness and tolerances before handover.
A practical change may affect vertical transport consultant performance, approvals and connected design assumptions and obligations beyond the immediate trade.
22Allegiance, authority and historyThe consultant may be working for today’s client while carrying yesterday’s project›
When the builder arrives, the Vertical Transport Consultant may already carry a long history of brief development, approvals, client conversations and prior design decisions. Novation or a changed delivery model can move the formal reporting line without instantly removing those relationships or assumptions.
The tension
They may be unsure whether a request changes the agreed outcome, conflicts with a prior commitment, falls outside the current appointment or asks them to accept a commercial compromise.
The control
Reset the current client, authority, final deal, governing criteria, approvals, departures, consultant scopes and decision route together.
23Required outcome versus methodologyThe Vertical Transport Consultant–builder boundary is frequently blurred›
The Vertical Transport Consultant controls the required lift and escalator performance, builder’s work and long-lead system integration outcome within their appointment. The builder controls sequencing, temporary works, access and construction methodology. The boundary must be tested wherever the method changes permanent performance or another designer’s assumptions.
Consultant position
“The required performance and constraints are defined. How you safely sequence and construct it is the builder’s responsibility.”
Builder position
“The documented outcome cannot be built without additional permanent design. An unresolved interface is being pushed into D&C.”
The key test is whether the required permanent outcome, constraints and acceptance criteria are adequately defined, or whether the builder is being asked to complete unresolved design under a methodology label.
24Quality, cost and programmeMake the trade-off explicit before each party defends only its own pressure›
25Information, decisions and changeConvert technical coordination into a controlled project outcome›
26RFIs, VE and substitutionsAsk for a decision with evidence, not a reaction to price pressure›
A strong RFI identifies the exact location, current references, conflict, actual condition, affected interfaces, decision required and genuine need date. A strong VE proposal compares the baseline and alternative across performance, approvals, interfaces, cost, programme, evidence, warranty, operation and work already released.
Before agreeing to “Can we reduce the number of lifts”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
Before agreeing to “Can we reduce lift speed”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
Before agreeing to “Can we reduce car size”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
For “Can we use standard finishes”, group requirements by traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, location and interface; retain exceptions where the design basis genuinely differs.
For “Can we simplify controls”, remove components, geometry or labour only where traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, access, testing, maintainability and adjacent packages remain protected.
Before agreeing to “Can we reduce destination control features”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
Before agreeing to “Can we use machine-room-less lifts”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
For “Can we rationalise shaft sizes”, group requirements by traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, location and interface; retain exceptions where the design basis genuinely differs.
For “Can we simplify lobby interfaces”, remove components, geometry or labour only where traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, access, testing, maintainability and adjacent packages remain protected.
Before agreeing to “Can we reduce special access-control integration”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
For “Can we use standard door sizes”, group requirements by traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, location and interface; retain exceptions where the design basis genuinely differs.
Before agreeing to “Can we reduce lift monitoring features”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
Before agreeing to “Can we eliminate a service lift”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
For “Can we use local finishes”, quantify what is being removed and what must replace its function elsewhere in the design or operating strategy.
For “Can we simplify pit waterproofing requirements”, remove components, geometry or labour only where traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, access, testing, maintainability and adjacent packages remain protected.
Before agreeing to “Can we reduce standby power requirements where permitted”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
For “Can we accept supplier-standard details”, group requirements by traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, location and interface; retain exceptions where the design basis genuinely differs.
Before agreeing to “Can we reduce lift-car customisation”, confirm the original demand and margin, then test effects on traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, architecture and lobbies, structure and shafts, electrical and communications, fire and security, future flexibility and acceptance evidence.
For “Can we defer non-essential features”, quantify what is being removed and what must replace its function elsewhere in the design or operating strategy.
For “What lift specification change saves the most without hurting capacity”, test the proposal against traffic handling and capacity, ride and speed performance, shaft, pit and headroom geometry, power and emergency operation, interfaces with architecture and lobbies, structure and shafts, electrical and communications, fire and security, evidence and work already procured.
27Chain of consequenceFollow a small decision through every downstream package›
Lift type changes
28Warning signsSignals an experienced project team notices early›
29Management playbookCreate the conditions for a coordinated team to perform›
Apply the judgement in realistic project situations.
30Interface assessmentVertical Transport Consultant Consultant Interface Assessment›
This tests whether you can work intelligently with the Vertical Transport Consultant and consulting team in live construction. It does not test whether you can perform the specialist professional role.
20 questions · 8 to 10 minutes