Guide
Hand-written orientation that links into and embeds the generated system reference. Authored prose, reviewed through the same integrity gate as the spines.
authored in docs-site/content 6f9bc1c2be7841 pages
Blockers & lost timeThe single record of stopped work — raised from the field as a suggestion, confirmed by the coordination team, and rolled up as lost time in crew-hours, with the slip it leaves on the work plan and the statutory record of injuries and days lost.Read →Mobile capture & the outboxCapture built for the person standing in the building: shell-free phone surfaces, three doors that need no account at all, and a durable outbox that holds a report on the device until the signal comes back.Read →Permits (Permit-to-Work)The Permit-to-Work subsystem — raise, review, issue and close out permits for hazardous work, tied to the live spatial picture.Read →Site diaryThe per-day site record: written across the day by several named people, part-answered by SimOps itself, and published untouched at the day's boundary as the PDF the client reads first thing every morning.Read →What this site isThe authored narrative layer, and how it relates to the generated system reference.Read →Completions, work plan & snagsRecording that work is done, day by day, and flagging own-work snags on the same gesture — self-certified, photo-gated, and honest about the last 2%.Read →ImportsThe one door for everything the site already has on paper or in another system — the master programme, the drawing office's floor plans, survey layers, a bulk restore, and the contractual defect register.Read →IncidentsThe something-happened record: raised where it happened, walked through a reviewed workflow to a formal H&S record, investigated with causes pinned to the defences they breached, and never quietly rewritten.Read →Planner & region evolutionThe read-only reality view — who is working where, on which day, read straight off the live site — plus the changepoint stepper that walks one piece of ground forward through time. SimOps holds no master programme of its own; it shows you the site so you can judge yours against it.Read →The spatial and temporal modelHow on-map entities, areas, and time fit together.Read →DefectsThe contractual quality register — NEC4 defects raised and accepted in the system the contract names, imported per contractor, and read in SimOps beside everything else the site knows.Read →ObservationsSafety Observation Reports: anyone on site can say what they saw — by app, QR poster, geofence or anonymously — and every one lands in a single H&S triage queue before it reaches the wider site.Read →How activity reaches peopleFrom a detected clash to a notification, a task, and a briefing.Read →Corrective actionsThe close-the-loop tracker every H&S finding converges on — one responsible company, an evidence-gated close-out, and an H&S sign-off that can send it back for rework with the reason kept.Read →Deliveries & inventoryWhat a load says it carries, what actually came off the truck, and where it went — the manifest, the receipt taken at the gate, and the append-only ledger that turns both into a stock balance nobody has to type.Read →InspectionsThe scheduled, checklist-driven safety walk: a versioned template, a named firm being audited, item-by-item answers with comments and photos, a score, and a corrective action offered on every failure.Read →RAMSThe register over the contractor's Risk Assessment & Method Statement paperwork — revision by revision, reviewed discipline by discipline, and briefed to named people whose sign-on is captured on a phone instead of a clipboard.Read →Getting startedSign in, find your site, and get your bearings on the map, timeline and dock panels.Read →For coordinatorsReviewing clashes, building safety reports, importing permits and DXF floor plans, and managing contractors.Read →For contractorsSeeing your zones and people, scheduling deliveries, and reading the alerts that affect you.Read →Permits (Permit-to-Work)What a permit is, who does what, the lifecycle states, and the permit-type catalogue.Read →Applying for a permitRaising a permit, linking its entities, submitting it for approval, and handling corrections, withdrawal, extension and reissue.Read →Reviewing & approving permitsThe two approval gates — coordinator endorsement and HSE approval — plus rejection, close-out, extensions and the permit board.Read →On-site: issuing & countersigningThe dual-signature walk-down: the authorised issuer signs, the named receiver countersigns to take a permit live, plus the on-site close-out.Read →Configuring permitsConfiguring the permit programme — permit types, authorised-issuer appointments, site policy (coverage and close-out gate), and the XLSX import.Read →Configuring clash rulesSetting up clash policy in the UI — the clash policy matrix, severities, per-pair overrides, suppression (Off), consequences, and how the engine picks one winner per pair.Read →Blockers & delaysWhat a blocker is (and what it isn't), the suggest→confirm triage model, who can do what, the intakes that raise one, how lost time is counted, and where blockers surface.Read →Reviewing & triaging blockersThe coordinator's triage job — confirm or reject a suggestion, record who's responsible, resolve and archive, acknowledge a disputed claim, and read the lost-time ledger. Plus the QS's commercial-author role.Read →Raising a blockerEvery intake — the phone-first 'Raise a blocker' two-tap suggest sheet, the delay (dependency-violation) handoff, the desktop declare and mark-clash-as-blocker, and the mobile permit-wait doorway — and why a raise is a suggestion, never an active blocker.Read →Snags & work close-outRecording that work is complete, flagging own-work snags on the completion record (the 'wee box'), the photo-gated self-certified snag close, and how the '98% → 100%' caveat clears as snags close.Read →How lost time is countedThe plain-language rules behind every lost-time figure: the stoppage record, the two questions it asks, the window, what a count rests on, multi-day chains, and the two piles that never mix.Read →Reading the lost-time ledgerThe coordinator's and QS's read surface: the two tiers, the three columns, the still-running chase list, the noticeboard lines, the breakdown views, and the marks a record carries.Read →Your firm's lost timeThe subcontractor's own surface: the view's header and sections, answering for a count, closing and splitting a stoppage, contesting blame, and re-raising after a rejection.Read →Slip, accounting cells and nil returnsHow the work plan reconciles late lines with declared lost time: the variance lens, the three accounting cells, the disclosure behind each, the nil return, and the absorbed marker.Read →Standing cost — money on lost timeHow £ figures ride the crew-hours: the rates table and its append-only history, labour and plant standing cost, the dashes and their reasons, the money line, who sees money, and how issued paper defends its ink.Read →The incapacitation register & injury ratesPerson-days, kept apart from crew-hours: the injury door that drafts a stoppage record, the register that stores facts and derives the statutory answers, the deadline chases, and the exposure entries behind AFR/LTIFR.Read →Lost time, scene by sceneEighteen everyday scenes — a stoppage declared and confirmed, a crane down, a storm, a week with nothing to declare, an injury at the hoist gate — each walked through step by step, with its screen recording.Read →The site diaryThe per-day site record: the working period, the main-contractor gate, append-only attributed entries, holes vs nil-reports vs computed cells, the boundary sweep that publishes without a button, and the errata that are the only thing a published day admits.Read →Filling in your roundThe phone-first My Round runner: answering one question at a time, 'Nothing to report' vs Skip, confirming the permit tick-list, photos, and recording an erratum once the day has published.Read →Defects — the contractual registerThe imported contractual quality register: what a defect is (and why it is not a snag), uploading a per-contractor export, the status × closed pair, who sees which rows, and what the diary counts.Read →Receiving a deliveryTaking the count at the gate: signing a load in line by line at what actually arrived, saying where it went, flagging damage and wrong items with a photograph, and closing the load when the last of it lands.Read →
Was this page useful? Report a problem
No cookies and no third-party analytics. A verdict records this page's path — and a search that finds nothing records the words you typed — in this site's own server log.