Labour tracking for demolition contractors

WBSync tracks demolition labour per building, per floor and per operation — soft strip, structural demolition, salvage, crushing — against the hours the job was priced on. Discoveries that change the scope are logged as variations with their own hours from the moment they're found, and the audit-logged record of who worked where, when, is built into every entry.

Demolition is priced fast and won tight, and the labour is the price: soft-strip crews by the floor, burners and machine drivers by the structure, attendance on the crusher. Whether the job makes money is decided in days, not months — which makes a month-end labour report a post-mortem.

WBSync structures the site as buildings and floors on a 4-level WBS. Crews are logged from a phone per floor and per operation, and earned-versus-spent hours are live daily — fast enough to matter on a six-week job.

Where the hours go on demolition contractors packages

Soft-strip productivity is a rumour

Strip crews move floor to floor and the hours arrive as one weekly figure. Logging per floor turns 'we're behind' into 'level 3 took 210 hours against 160' — while the crew is still in the building, not after the scaffold is down.

Discoveries rewrite the job daily

Hidden tanks, unexpected structure, materials that need licensed removal. Raising each discovery as a variation with its own activities means the extra hours accrue against the variation from day one — not blended into contract hours you can't recharge.

Sequence gates hide the real slippage

Structural demolition can't start until the strip is done; the crusher stands idle until material comes down. Planning crew-days on the WBS with a rolling look-ahead shows which operation is holding the gate — with at-risk flags before the date, not after.

Who-was-where matters more than most trades

Short jobs, transient labour, high-consequence work: the record of who worked which floor on which day has to survive scrutiny. Every entry is time-stamped, approved and audit-logged — the attendance record builds itself.

Example — how a package maps to the 4-level WBS
L1 Location Mill Street site
L2 Sub-location Building 2, Level 3
L3 Discipline Demolition
L4 Activity Soft strip & salvage, Level 3DM-B2-007

How WBSync fits

Per-floor, per-operation tracking

Every floor is a WBS branch and every operation an activity with budgeted hours. S/E (Spent vs Earned) is live per floor, per building and per site — daily resolution on jobs measured in weeks.

Variations from the day of discovery

The variations register holds each discovery as its own scoped item with its own activities; hours logged against it stay separate from contract works, so the recharge case is built contemporaneously.

Crews logged in seconds, offline

The phone PWA logs a whole crew against a floor without signal — it syncs when coverage returns. Operatives don't need logins, and clock-in systems can feed the same activities through an open ingest API.

An approval gate and a full audit trail

Hours reach the live figures only after approval; duplicates and over-16-hour days are blocked until resolved, and every state change writes an audit log entry.

Frequently asked questions

Jobs only run six to twelve weeks — is setup worth it?

Setup is an afternoon: import the priced schedule as XLSX and the WBS and cost codes are built. On a short job the payoff is bigger, not smaller — a week of unnoticed overrun on a six-week job is the margin.

What happens when we find something unexpected?

Raise it as a variation. It gets its own activities and budgeted hours, crews log against it like any other work, and the extra cost accrues against the variation from the day it was found — with the audit trail to back the claim.

Do operatives need to install anything?

No. Operatives are tracked without logins — the foreman logs the crew from one phone, or your clock-in system feeds hours automatically. Only supervisors and office staff need accounts, and those seats are unlimited.

Can the machines be tracked too?

WBSync tracks labour. Machine drivers and banksmen are logged like any operative against the operation they're on, so machine-crew hours per structure are visible — plant itself is costed in your plant system.

See your own package's S/E live within an afternoon — import the BOQ, add the crew, log a day. Start free with WBSync — 30-day trial, up to 30 active operatives, no card required.

Related

Comparing WBSync to other tools?

Every comparison below is built from the vendor's own public pages, with sources linked and a "last verified" date on the page.

WBSync vs Assignar WBSync vs Procore WBSync vs Raken WBSync vs Rhumbix Alternatives to Excel