Skip to content

Hub

Demo data

Project Management · Tisch — Wing B

Stop-work orders

BID-1247 · FW #31247

The gravest register in the Hub — and the one we want empty. Every order that has ever halted work on the Wing B millwork scope lives here: who placed it, what it held, and the paper that released it.

Register status · FW #31247

No active stop-work orders.

Every crew on the Wing B millwork scope is cleared to proceed. The only order ever placed against this job — SWO-001, Level 2 West Wall — was released on approved treater certificates after a 2-day hold.

All clearWork proceeding
Last order
SWO-001
Hold released
Mar 14, 2026
Active now
0
89

Days since last stop-work

12 wks 5 days · measured Mar 14, 2026Jun 11, 2026 sync

Register · 1 order of record

The register

1 resolved0 active

Issued in red, released in green — each entry keeps its full arc, from the condition that stopped work to the document that cleared it.

Stop-work order · Tisch — Wing B

SWO-001Executed
ResolvedMar 14, 2026
Issued by
Hunter Roberts Construction Group — Site Safety
Issued
Mar 12, 2026
Hold stood
2 days
Area affected
Level 2 West Wall — blocking installation zone

Hold placed · Mar 12, 2026

Fire-treated blocking installed at Level 2 west wall without treater certificates on file. Installation halted pending certification per spec 06 10 53.

— held 2 days —

Hold released · Mar 14, 2026

Mill and treater certificates expedited and approved same week (SUB-006, approved 2026-03-14). Installed material verified against cert lot numbers; hold released.

SUB-006 · treater certificates

Logged by M. Delgado, PM · source: GC correspondence + FW #31247 task hold — wired in the integration phase

Protocol

How an order moves

Three steps, no improvisation — the same sequence whether the order comes from Hunter Roberts, the AHJ, or our own foreman.

  1. 01Issuance

    An order reaches Ellicorp from the GC's site-safety team or the authority having jurisdiction — or our own foreman places an internal hold when a safety or quality condition warrants it. The order names the area and the specific condition. Work elsewhere continues.

  2. 02Notification

    The Ellicorp PM acknowledges in writing, stands the affected crew down, and places a hold on the affected Fieldwire tasks. The order is entered in this register the same day with the originating document attached.

  3. 03Release

    Work resumes only on written release from the issuing party — certificates on file, inspection passed, condition corrected. The hold is lifted task by task and the release is logged against its reference.

Specimen · design verification

If an order were active

Stop-work is the one banner we hope never renders. The treatment below is the live design for an active order, kept here as a specimen so the bad day is already designed.

How this connects

Data flows from Fieldwire job #31247 (Safety tasks, Inspections, Photos) through the Fieldwire bridge into the Stop-Work Workflow skill, which produces SWO notices (.pdf) + register.

Demo data — the bridge automation that watches FW #31247 safety tasks, inspection results, and photo documentation for hold conditions ships in the integration phase. Until then, this register is kept by hand.

Project
Tisch School of the Arts — Wing B Renovation
Drawn by
MD
Scale
NTS
Date
Mar 14, 2026
Rev
Δ 1
Sheet no.
SWO-LOG