Skip to content

Approving work

Approving a work activity is what turns a request into a commitment. It is also what makes the exclusion-zone clash rules bite, so it is worth understanding what your approval does.

The approvals queue in ToolboxFM, showing a Working at heights request with Dropped objects contained: No, a comment and a clash with an approved lockoutThe approvals queue in ToolboxFM, showing a Working at heights request with Dropped objects contained: No, a comment and a clash with an approved lockout
An approval card in full: the high-risk work, the dropped-objects answer, and the clash that stops a plain approval.

Approval needs the approve work activities permission. Head Office and Project Supervisor both have it; Subcontractor Supervisor and User do not. The full list is in Roles and permissions.

High-risk work travels with the request into the queue. The card lists every type the crew selected, and for Working at heights, Scaffolding and Precast concrete it also shows whether the exclusion zone is large enough to contain dropped objects.

Dropped objects contained: No is not a rejection and not an error. It means the crew has told you the drop zone is not fully contained, and the comment says what to consider. Read both before you decide, then approve with a note or reject with a reason.

An approved activity becomes blocking for its exclusion zone, if it has one. That means no other activity can be approved over the same zone and window.

Before that point, an activity is only a request, and requests do not block each other. Several crews may ask for the same crane slot. Nothing is wrong until somebody approves one of them.

If the window overlaps a booking that already holds the zone, the approval cannot go through. The card says Clashes with an approved lockout and names the blocking booking, and Approve Activity becomes Reschedule & approve.

Because requests do not block, a zone can have more pending requests than it can satisfy. Approving one of them may leave others stranded — those activities become bumped, and their crews need telling before they travel to the project.

When an activity does become bumped, the person who created it and the supervisors of the subcontractor it belongs to are notified automatically.

Cancel or change the winning booking and the other activity stops being bumped — again, because bumped is computed from the bookings that exist rather than recorded once.