Build the dates backward from the site.
Elevator cab lead time tracking means working backward from the required site date through installation, freight, crating, fabrication, material receipt, vendor commitments, engineering release, approval, and submittal. Each milestone needs an owner, a current forecast, and a latest acceptable date so the team can see when delay has consumed the remaining float.
Published
It controls the dependencies that make delivery possible. A single “lead time” field hides drawing review, release, vendor availability, receiving, shop capacity, outside processing, crating, freight, and site access. Those activities have different owners, so the tracker must show their links.
For every milestone, retain the baseline, current forecast, latest acceptable date, actual completion, owner, status, and source. Sources include contracts, accepted schedules, vendor acknowledgements, shop commitments, freight bookings, and written site confirmations. Add the governing revision where it can change the date.
This date chain sits across the broader elevator cab project stages. It should not replace the stage record; it should explain what must happen next, by when, and what downstream date is exposed if it does not.
Start with the date the cab must be available at the site, then confirm whether it is a contractual requirement, requested target, or date inferred from another trade's schedule. Record the installation window separately. Delivery is not useful if unloading, storage, elevator access, or the installer is unavailable.
Work backward through site readiness, transit, pickup, inspection, and crating. Name the party confirming access, receiving hours, staging space, hoisting limits, and delivery sequence. Freight assumptions should include service and handoff points, not just transit.
Reserve a realistic fabrication window based on released scope, routing, labor and equipment constraints, outside processes, and inspection. Each material need date is the date the shop requires usable material, not the date a buyer hopes it ships. Allow for receiving, verification, damage resolution, and any conditioning or preprocessing.
A vendor promise date belongs to a defined item, quantity, finish, revision, ship-to point, and order status. Track the quote-valid-through date independently because price, availability, and promised shipment can change before release. Reconfirm both whenever specification, quantity, approval timing, or requested delivery changes.
The approved drawing basis must arrive early enough for engineering to resolve comments and release the purchasing and fabrication information. Work backward again to the submittal-issued date using the actual review path and named approvers. Pending approval is not float; it is unresolved schedule exposure.
Treating every date as equally firm creates false confidence. Classify the basis, preserve who supplied it, and change the class only when new evidence arrives. A confident verbal prediction is still an estimate if nobody responsible for performance has accepted it.
| Date type | Required evidence | How to use it | Common mistake |
|---|---|---|---|
| Required date | Contract, accepted schedule, or written request with a named source. | Use as the backward-planning constraint and clarify any delivery or access conditions. | Assuming the latest schedule email changed the contractual requirement. |
| Committed date | Acceptance by the party responsible, tied to defined scope and revision. | Plan dependent work against it while monitoring stated qualifications. | Calling a requested date a promise before the vendor or shop acknowledges it. |
| Forecast date | Current assessment based on known progress, constraints, and remaining work. | Update when facts change and compare it with the latest acceptable date. | Overwriting the baseline, which removes evidence of drift. |
| Planning assumption | Named rationale, owner, validation action, and deadline for confirmation. | Expose unresolved inputs and drive follow-up before they become critical. | Allowing an assumption to age into an apparent commitment. |
| Actual date | Receipt, release, approval, pickup, delivery, or completion record. | Recalculate every dependent forecast and retain it for future planning. | Recording completion without checking what it changes downstream. |
Forward scheduling answers when the job might finish if each activity starts after the previous one. Backward scheduling answers when each activity must finish to protect the required site date. Only the second question exposes infeasibility before the team spends money or promises a slot.
Begin with the usable-on-site requirement, not a vague ship date. Subtract installation access, receiving constraints, transit, crating, inspection, fabrication, material availability, vendor fulfillment, release, approval resolution, and review. The results are the latest acceptable milestones. Compare the forward forecast with each one.
Do not hide uncertainty in one pad. Put allowance beside the risk and state who controls it. That makes vendor, approval, shop, and site exposures visible rather than one unexplained buffer.
Float sits between a forecast completion and the latest acceptable completion of a linked activity. There may be float after approval, before a quote expires, between promised receipt and material need, after fabrication, or before installation access closes. Each interval protects a particular downstream event; it is not a shared bucket that every department can spend independently.
Show float by milestone and recalculate it whenever either side moves. Also distinguish project float from an activity allowance for expected variation. If approval consumes the gap before engineering release, that loss must flow through vendor commitments and the shop plan. It cannot remain displayed elsewhere as though still available.
Recalculate from the unchanged site date immediately. Mark the missed approval need date, reduce the affected float to its real value, and identify the first downstream milestone that is now impossible or exposed. Do not simply move approval while leaving every later bar untouched.
Separate facts from recovery options. Confirm the open review issues and decision owner. Ask engineering what can be safely released without creating revision risk. Revalidate quotes, availability, vendor promises, outside processing, shop capacity, crating, and freight. Partial release works only when interfaces are stable and later approval cannot invalidate released work.
Present options with consequences: changed scope, commercial exposure, resequenced work, different freight, or a revised site commitment. Give each a decision deadline. Expediting is not a schedule until responsible parties acknowledge what they can do and under which conditions.
Supplier coordination depends on current, qualified acknowledgements; see the present and planned boundaries on elevator supply chain software. Build It Track It holds job files, contacts, timelines, estimates with vendors and person-entered BOM lines, drawing revisions, change orders, and the Final for Record lock today. Purchasing, purchase orders, inventory, capacity, scheduling and delivery dates, production scheduling, installation, inspection and final payment, invoicing and accounting are planned for the Q3 2026 launch.
Look for stale relationships, not only overdue final dates. Approval may show “pending” with no engineering need date. A vendor line may carry an old assumption but no acknowledged promise. Material may appear on schedule because shipment was mistaken for usable receipt. A shop slot may remain reserved against unreleased drawings.
Run an exception review that asks: Which current forecast is later than its latest acceptable date? Which commitment lacks a defined scope or revision? Which quote expires before release? Which vendor promise has not been reconfirmed after a change? Which material arrives too late for receiving and inspection? Which site-readiness statement is older than the current construction plan?
The useful status is not red, amber, or green by itself. It is the breached milestone, remaining float, downstream commitment at risk, evidence date, owner, next action, and decision deadline. An elevator manufacturing ERP system can organize transactions, but the team still has to define these relationships and challenge unsupported dates.
Track the required site date, installation window, site-readiness confirmation, freight and crating window, fabrication start and finish, material receipt, every vendor promise date, quote-valid-through dates, engineering release, approval received, and submittal issued. Keep baseline, current forecast, and committed dates separate so a changed forecast does not erase the original plan.
The site date is the constraint the upstream work must serve. Working backward exposes the latest acceptable finish for installation, freight, crating, fabrication, material receipt, release, and approval. A forward schedule can look orderly while arriving after the required date; backward planning shows that conflict before commitments are made.
A commitment has an identified owner, accepted scope, stated date, and recorded basis. A customer-required site date, acknowledged vendor promise, or reserved freight pickup can qualify. Internal target dates, unconfirmed supplier lead times, likely approval dates, and provisional shop slots are estimates until the responsible party accepts them.
Float sits between linked events, not in one general project allowance. It may exist between approval and engineering release, release and ordering, promised receipt and fabrication need, fabrication finish and crating, or delivery and installation. Label each interval so the team can see who is consuming it and which downstream commitment it protects.
Recalculate the entire backward schedule immediately. Identify the first milestone that no longer has enough float, confirm whether partial release is technically safe, revalidate vendor quotes and promises, and ask the shop and freight providers for real options. Record each option's scope, decision owner, deadline, and consequence rather than replacing the old dates with optimistic ones.
Compare current forecasts with each milestone's latest acceptable date, not only with the final site date. Warning signs include approval still shown as pending after its need date, expired quotes, vendor dates without acknowledgements, material promised after its fabrication need date, a shop slot held without released drawings, and site readiness that has not been reconfirmed.
Review them whenever a governing input changes and at a regular cadence suited to the job's current risk. Approval, engineering release, vendor acknowledgement, material receipt, fabrication status, freight booking, or site-readiness changes should trigger an immediate recalculation. The useful review asks what changed, which float interval moved, and who must act next.
Request a walkthrough of Build It Track It's current job controls and the scheduling and delivery-date workflow planned for the Q3 2026 launch.
Request a demo