Spreadsheets, whiteboards and email
The handoffs are where they break.
Excel and Google Sheets are good calculation tools. Whiteboards make today’s pressure visible. Email moves a file quickly. None of them owns the elevator cab job from lead intake through final signoff. The gap appears when one department hands the work to the next.
One job, twelve stages
01 / 12
Every stage is a controlled stop, not a file passed to the next person.
12 connected stages
Lead intake through final signoff, carried by one job record.
6 handoffs a workbook cannot police
Every row in the table below is a point where the work changes hands.
1 declared source per decision
One BOM, one released drawing, one capacity plan, one closeout.
The real incumbent
A careful estimator can build a strong BOM in a workbook. A production manager can make a useful whiteboard schedule. A project manager can keep a disciplined submittal log. The trouble is not the individual tool. It is the unprotected space between them. Each copy, attachment and status update asks a person to carry the latest decision forward without a hard gate.
| Elevator work item | Spreadsheets, boards and email | Build It Track It |
|---|---|---|
| Field survey | Measurements and photos are copied or attached after the visit. | Survey captures belong to the job and feed the next stage. |
| BOM control | Formula logic and version naming depend on workbook discipline. | BOM work stays tied to the job and its revision path. |
| Shop drawings | Teams identify the current PDF from folders, filenames or threads. | Revision history ends at a defined Final for Record lock. |
| Change order | Scope, price delta and approval are reconciled manually. | Scope change routes through change order and final estimate before purchasing. |
| Production capacity | Dates and station hours are maintained on a separate schedule. | Committed work is planned against station-level capacity. |
| Installation and closeout | Photos, punch items and acceptance may sit across phones and inboxes. | Field evidence and final signoff close the same job record. |
The surveyor records dimensions, access constraints and photos. The estimator is already working from the original request. Unless somebody merges those facts into the estimate, the BOM reflects the bid assumption instead of the field condition. A job record makes survey completion a structured stage, not an attachment someone must remember to open.
Rev C is approved, but Rev B is still attached to an old email and saved on a shared drive. A filename convention helps; it does not create a release gate. Build It Track It records revisions and locks the accepted drawing Final for Record so fabrication has a declared source.
Engineering changes the panel construction. The workbook changes, but a purchasing copy was exported yesterday. Material is committed against old scope. Connecting drawing revision, change order, final estimate and purchasing puts the commercial decision ahead of the PO instead of after the invoice.
A whiteboard shows jobs by week, while labour assumptions live in estimating sheets and vendor dates live in email. Two projects can look compatible until both need the same station hours. Capacity must be checked by station against committed work, not read from open space on a calendar.
Installers capture site conditions, completed work and punch-list evidence. If those files arrive through texts and personal camera rolls, the office has to reconstruct the record before acceptance. Structured installation evidence should flow into walkthrough, signoff and final closeout without another file chase.
The person who knows which tab matters, which formula must not be touched and which color means released is carrying undocumented operating logic. When that person is absent or leaves, the process drifts. Purpose-built stages make the expected sequence visible to the whole team.
Not another dashboard laid over the same manual process. Build It Track It is organized around the complete twelve-stage elevator cab workflow: lead, estimating and BOM, survey, contract, engineering, final estimate, deposit, purchasing, receipt, production, installation and closeout.
The value is the sequence. Survey facts reach estimating. Scope-changing revisions reach the change order. Final for Record releases purchasing. Material status and station hours shape production commitments. Installation evidence reaches acceptance. Review the elevator project software features to see how those controls fit together.
Drawing revisions
Which one is current?
Rev A, Rev B and Rev C stop competing the moment one of them is locked. Three drawing revisions scattered across an email thread and a shared drive collapse into a single stack. The approved revision is locked as Final for Record and released to fabrication; the earlier ones are marked superseded.
Keep the workbook when one person can genuinely control every handoff, job volume is low, scope is simple and version discipline is working. Keep it for ad hoc calculations and one-time analysis. Familiarity has real value.
Change when the team spends more time reconciling records than acting on them, or when controls depend on knowing which file to trust. If you need flexible grids rather than a raw workbook, compare the Smartsheet alternative for elevator teams. If you are considering building your own application, read the Quickbase comparison for manufacturers.
A replacement project starts by naming the authoritative workbook, decoding statuses and finding every side process around it. Then define owners and exit conditions for each stage. Historical sheets can remain source records. Active work needs one controlled transition plan. Build It Track It is in pre-sales now, with launch planned for Q3 2026.
A spreadsheet can list jobs, dates, costs and owners. It cannot reliably enforce the handoff between survey, estimating, approved drawings, purchasing, production and closeout. Those controls usually live in separate tabs, inboxes and people’s memory. As revisions accumulate, the team must manually prove that every downstream decision uses the current information.
Yes. Both can calculate quantities, material costs and labour hours when the workbook is designed and maintained carefully. The problem is connection, not arithmetic. A standalone BOM does not inherently know which drawing revision approved it, whether a scope change needs a change order, or whether a purchase order was raised against a superseded version.
Existing sheets remain valuable source records. Before migration, identify the owner of each workbook, remove duplicates, define status meanings and decide which version is authoritative. Build It Track It is designed to hold the continuing job record across twelve stages; the exact migration plan should be agreed during pre-sales based on the structure and condition of your current data.
Yes. A small team with low job volume, simple scope and one person controlling every handoff may be well served by a disciplined workbook. Spreadsheets are also useful for one-off analysis and calculations. They become risky as departments, revisions, vendors, station commitments and field evidence multiply across several active cab jobs.
Build It Track It keeps drawing revisions in the engineering stage and records their status with the job. A scope-changing revision routes into change-order and final-estimate work. Engineering can lock the approved drawing as Final for Record, giving purchasing and fabrication a defined release point instead of asking staff to infer the right attachment from an email thread.
Bring the workbook, the whiteboard and the real exceptions. We will walk through how the twelve-stage model handles them.
Request a demo