Media

The noticeboard surfaces site activity — alerts, deliveries and clashes ranked by severity — beside the live map as it glides across the plan. Recorded against the live demo site, not a mock.

Every worker, vehicle and exclusion zone lives in time as well as space. Winding the timeline scrubber moves the whole site to any moment — the plan comes alive. Recorded against the live demo site.

A worker is a person on site — a hard-hat token with a footprint that lives in time. Placing one drops a person onto the live map at a moment. Recorded against the live demo site.

Plant is the heavy equipment — a crane brings its red drop zone with it, the ground a load could fall onto. Recorded against the live demo site.

An area is a time-bounded polygon — a work area, exclusion zone or laydown — traced onto the ground. Recorded against the live demo site.

A road is a routed corridor for site traffic, drawn as a centreline SimOops widens into trafficked ground. Recorded against the live demo site.

The Noticeboard rolls up every live clash and delivery on site, ranked by severity — who is involved, which safety rule was breached, how serious it is. Recorded against the live demo site.

Every permit to work is a first-class object in SimOops — issued, tracked, and tied to the people and ground it covers, so the paperwork and the map never drift apart. Recorded against the live demo site.

A permit starts as an application, and the application belongs to the firm doing the work. The workbench arms the place-tools against this permit, holds the crew and plant it will authorise, and carries the window, the company, the pre-work checks and the method statement the work stands on — a draft that stays on the board until it is sent for review. Recorded against the live demo site.

Requested, endorsed, approved, issued — a permit is a state, and someone put it there. The board wears one band per stage, and the two review stages belong to two different desks: the coordinator endorses, health and safety approves. Approving is not a button but a sheet — the application, the conflicts its window was checked against, and how much of that window the check reached. Recorded against the live demo site.

A live permit already says who, where and when, so the map does not ask again. Placing under a permit arms the tools against it: the creation form arrives with the permit on it, the firm locked to the permit’s firm and the time fixed by the permit — its whole window already expanded into a schedule. The map matches the paper by construction. Recorded against the live demo site.

Approved is not live. A permit is issued at the workface: its conditions of issue become a walk-down the appointed person completes item by item on a phone, with anything imposed on the day recorded on the permit itself. Then the crew taking the work countersign the same conditions back. Two signatures, then the work is permitted. Recorded against the live demo site.

The wallet is a holder’s own permits rather than the site’s board — banded into what is live now and what is still in flight, filtered to just yours or your whole firm’s. A live card’s countdown is also the door to ask for more time, and when the paperwork is what is holding the crew up, the card opens the blocker capture with that permit already named as the cause. Recorded against the live demo site.

Most sites already run their permits off a spreadsheet, and that spreadsheet is the intake: one file, parsed by the layout the customer’s own export already uses, matched to this site’s buildings and zones, and added to the board as permits. Every batch stays named with what it brought, so the board is the record that schedule became. Recorded against the live demo site.

The Health & Safety panel is the home for incidents and observations — reported, driven through review, and tied to the ground and people they concern. Recorded against the live demo site.

A hazard reported from the workface on a phone: what kind of thing it is, how serious it could be, a sentence, a photo and where exactly it was. Filed, it sits in the site’s triage queue rather than in somebody’s head. Recorded against the live demo site.

Raised observations wait in one queue — however they arrived, from the app, a QR poster, a geofence or anonymously. The health and safety lead opens one, and the five-by-five grid derives its risk band from how likely against how bad, before it is accepted into the register or declined with a reason. Recorded against the live demo site.

The Browser lists everything on site — every worker, machine, area and point of interest, grouped by kind and counted, over the buildings and zones they sit on. Filter it to narrow the list, click a row to select it, double-click to fly the map to it. Recorded against the live demo site.

A delivery is booked onto the plan rather than into a diary: dropped where the truck will stand, against a firm, a day and a shift window, and the permit it arrives under. It is on the map and on the day before the truck sets off. Recorded against the live demo site.

Everything on the plan is drawn in layers — the live crews, plant and work areas over the static reference ground of buildings and zones. Click a row to take that layer off the map and click it again to bring it back, so the plan can be cleared down to the one thing being looked at. Recorded against the live demo site.

The Site maps panel picks the calibrated background the site is drawn over and flips between building floors. Recorded against the live demo site.

The Planner is a read-only view of reality — what each contractor is doing, in which place, on which day — to cross-reference against the master programme. Recorded against the live demo site.

The Report panel assembles a safety report from the live scene — clashes ranked by severity, accepted or rejected by a coordinator, rendered to a branded document. Recorded against the live demo site.

Signing off IS the receive. A booked delivery carries a manifest, and the count taken at the gate — line by line, what actually came off the truck — is what becomes the site’s ledger entry. A line received short stays visibly short against what was expected, and anything damaged or wrong gets its own flagged row with a reason and a photograph. The discrepancy becomes a dated record rather than a number quietly corrected. Recorded against the live demo site.

A coordination session is not the document — it is what the document is rendered from. Once the day’s scenes have been accepted or rejected, the finished session renders on demand to the branded PDF or Word file a human signs, with the week ahead riding out beside it as plates of the ground as it is scheduled to change. The app hands you the file rather than keeping a copy of it, so the signed paper is the record. Recorded against the live demo site.

The seeded clash rules are a floor, not a ceiling. A site holds its own copy of the standard profile — same rules, its own to change — so tightening a distance, raising a severity or switching a rule off for this site never edits the template every other site inherits. Inside a rule, the permit matrix refines when it fires: a cell overrides one permit combination, a cell switched off means it does not fire there at all, an absent cell inherits, and where two answers disagree the more severe one wins. Recorded against the live demo site.

A method statement is not a file on somebody’s laptop — it is a document in a register, revision by revision. Each revision is reviewed one discipline at a time, every lane naming its reviewer and its verdict, and a revision that is rejected is superseded by the next rather than overwritten. The briefing roster records who has been briefed on it, and a permit standing on this method stands on one named revision of it. Recorded against the live demo site.

Point at any ground on the plan and ask what is scheduled to change there. The region evolution stepper cuts the days ahead into changepoints — the moments the population of that ground actually changes — and walks them one at a time, naming who arrives, who leaves and how much is in scope, moving the whole site’s clock with each step. It reads the plan rather than editing it. Recorded against the live demo site.

The drawing office works in CAD and the site works on the plan; a DXF is the joint between them. A drawing lands as vector floor plans placed per storey, so stepping into a building lays the real drawing for that level underneath the work. It arrives as geometry rather than a picture — the drawing’s own CAD layers stay listed and counted, and can be switched on and off one at a time. Recorded against the live demo site.

Two different things share this ground. Contractors are the firms doing the work — each one drawn as itself on the map, carrying its trades, its people and everything it currently has placed. People are separate: they join by invitation, hold one role per site from viewer up to admin, and sit in a pending list until somebody approves them. An invite link is the same door held open for a whole crew at once. Recorded against the live demo site.

Capture does not wait for bars. Filled in with no signal, a report is written straight into the phone’s own outbox — words, photographs and all — and the phone says plainly that it is saved on the device and not yet sent. When the signal comes back it walks itself in, retrying on its own schedule until the site has it, so nothing is lost because somebody was standing in the wrong part of the building. Recorded against the live demo site.

A clash is an unsafe overlap SimOops detects automatically across space and time — a worker in a live crane drop zone, two trades in one place at once. Recorded against the live demo site.

Floor focus narrows the whole site to one level of a building, dimming the floors above and below so a single storey reads cleanly. Recorded against the live demo site.

A stoppage raised from the field lands as a suggestion; a coordinator opens the Completions Blockers tab and confirms it into a live, counted blocker. Recorded against the live demo site, not a mock.

The lost-time ledger rolls confirmed blockers up as crew-hours — the stoppage window times the stood-down headcount — split by who lost the time and who is responsible. Recorded against the live demo site.

Recording work complete on the demo site, flagging an own-work snag on the same gesture (the "wee box"), and closing it against a close-out photo. Recorded against the live demo site.

A firm that lost no time still answers: a nil return is authored against the week's own cell, so an empty figure reads as a stated answer rather than paperwork nobody got round to. Recorded against the live demo site.

The work plan grows an accounting cell per line when the variance lens is on: hours expected against hours lost, with the stoppages behind the figure one click away — and a line with nothing to declare renders an empty set rather than a silence. Recorded against the live demo site.

Two marks the lost-time ledger puts on a record: the window absorbed into a longer stoppage so the same hours are never counted twice, and the accounting flag that never renders blank — so a reader can see how the week's figure was arrived at. Recorded against the live demo site.

A stoppage is declared at the desk from the Add menu on the demo site — A, then B, then the click that says where work stopped. One select names whose crew lost the time, another names the firm responsible, with "nobody at fault" an answer that has to be given rather than a blank left behind; there is no title, and the description that stands in for one is owed on every raise. Recorded against the live demo site.

Stoppages raised from the field wait in the Blockers inbox, each ageing in whole days until somebody decides it, and Review opens the record on the very window that age is counted from. The same table, read in meeting mode, is the coordination meeting — every open raise, grouped by firm, worked in place. Recorded against the live demo site.

The lost-time ledger keeps two totals apart — the crew-hours already confirmed, and the ones still awaiting triage — and states the same three lines on the noticeboard for whoever never opens the panel. Clearing the backlog moves hours between them, never blends them. Recorded against the live demo site.

A firm's own panel shows the stoppages that cost it time, the records still waiting on its own count, and — as a separate band over the same population — the ones it is named responsible for. Recorded against the live demo site.

Every lost-time record points at the work it stopped — the permits, tasks and crew behind the figure — and says plainly when it points at nothing at all. Recorded against the live demo site.

A safety adviser reaching another firm's stoppage can attach the work it affected as a proposal for that firm to endorse — but is offered no headcount anywhere, because how many of a firm's people stopped is that firm's own answer to give. Recorded against the live demo site.

A stoppage raised in error is removed with its reason, and the removal is stated on the row rather than quietly erasing it — the form says plainly that sending a crew elsewhere is not what removal is for. Recorded against the live demo site.

A stoppage that has not been closed off stays on the ledger as an open window — stated as what it still is, with the state of the nudges asking the firm to say when work resumed. Nothing about it is guessed while it is still running. Recorded against the live demo site.

Idle time has a price: the crew-hours at the rate agreed for that firm, and where a firm has no rate of its own, the site default — said openly rather than hidden in the figure. Each record's cost opens onto the rates that produced it. Recorded against the live demo site.

A stoppage waiting to be decided opens as one sheet: the work it rests on, and a plain sentence saying where its headcount came from — with no money anywhere on the page, because deciding what happened is not the same act as pricing it. Recorded against the live demo site.

An injury the law requires to be written down gets a register row that names which duty has been reached, and keeps two counts side by side — how long the statutory clock has run, and how many days that person has actually been off. They are labelled apart and never added together. Recorded against the live demo site.

When a crew goes home overnight and comes back, the lost time is recorded as the stretches they were actually on site — still one claim, split into parts. It reaches the decider as a single item, and each stretch can be answered on its own. Recorded against the live demo site.

Accident rates are ratios — cases against hours worked — so SimOops will not publish one until the hours have been declared, month by month, and signed off by someone other than the person who submitted them. The band states the window, what each figure counts, and where the hours behind it came from. Recorded against the live demo site.

The weekly lost-time sheet is struck at a moment and frozen there: it names the week it covers, the instant it was taken, and its own issue number, so nobody can re-read it later as if it had said something else. Recorded against the live demo site.

One event can stop several firms at once, and each loses a different amount — so the sheet carries a row per firm with its own count rather than averaging the difference away, and names the causes beneath with the day they fell on. Recorded against the live demo site.

A firm can be named responsible for time another firm lost — and the firm named gets to say so on the record itself. The ledger then keeps the disputed hours legible instead of blending them into the total, so a reader can see what is settled and what is not. Recorded against the live demo site.

Correcting a rate never edits a sheet that has already been issued. Re-open it and its printed figures stand exactly as struck — with a mark across the top saying the live figures have moved since, and which issue has replaced it. Recorded against the live demo site.

Four cases a register has to be honest about: days off that stopped and started again, so the break is disclosed and the shorter official reading is stated beside the longer one; a death recorded long after the accident, which raises a fresh duty without quietly erasing the one already missed; a serious failure that hurt nobody, which still gets its own row with every personal detail left blank rather than invented; and a reminder that has been set but not yet sent, shown only to the person who owes it. Recorded against the live demo site.

Work finishes at the workface, not at the desk. The crew hand the permit back from their own phone — the scaffold struck, the area left safe — and that handback is a declaration, not a closure: the permit stays live until somebody has walked it down. At the desk it arrives as a task with the permit’s own close-out one step away, so the paper is only closed when a person closes it. Recorded against the live demo site.

Three taps and a sentence, standing in front of it: what happened, how bad it was, and where. It lands as a real submitted incident rather than a phone call somebody has to remember to make. At the desk health and safety opens that same record — the reporter’s own words, the place, the time it happened — and decides whether it goes into review. Recorded against the live demo site.

A corrective action is closed from where the work was done — the fix photographed, what was actually done written down — and sent for review rather than marked done by the person who owed it. At the desk health and safety holds the verify queue, and the answer is accept, or send it back for rework with the reason kept on the record. Recorded against the live demo site.

A walk-round on a phone: the template and the firm being audited are chosen first, then it is item by item — pass, pass, fail — with a failed item able to raise a corrective action there and then. At the desk the register holds the completed run and its score, and the actions that failure raised sit in the actions register, each still naming the question it came from. Recorded against the live demo site.

Two phones and a desk, and no clipboard between them. The briefer’s phone holds the QR and a code that changes every few seconds, so signing on means being in the room; the operative’s phone names the document and the exact revision they are signing on to; and the register at the desk fills name by name as they do. Nobody transcribes a sheet afterwards. Recorded against the live demo site.

A notification says something happened; a task says something is owed, by you. My Tasks is that queue and nothing else — the application waiting on your endorsement, the handed-back permit still to close out, the clash to acknowledge, the load to book in — each carrying the day it is due and a way straight into the exact sheet where the decision is made, rather than a notice you have to decode. Recorded against the live demo site.

The day’s record is filled in on a round rather than typed up afterwards: it opens where the gaps are and asks one question at a time, so each answer is written by the person who has it. Nothing to report is an answer of its own — one tap, attributed like any other — while a question left alone stays a gap and publishes as one. Entries are never edited afterwards: each stands with the name and the time it was written. Recorded against the live demo site.

The Document is the assembled day in the order the page prints it — the answers as they were written and attributed, the questions nobody answered showing as the gaps they will publish as, and the figures SimOps is itself the record of filled in by SimOps and frozen at the moment the day closed. It publishes itself at the end of the working period; there is no publish button, and this is the copy the morning email carries. A correction afterwards is an erratum on the back of the record, timed and attributed — the day itself is never edited. Who it reaches is worked out from the site, plus any address added by name. Recorded against the live demo site.

Defects are contractual: work notified as not meeting the specification, and owed back put right. The register is imported — each firm’s own export, uploaded against that firm — and it is read per firm, so a contractor sees their own rows and nobody else’s while a surveyor sees the whole site. Open means one thing only here: not yet closed out. A photograph taken when the work was signed off can be cited against the entry it answers. A defect is not a snag: one is notified under the contract, the other raised here on site. Recorded against the live demo site.

The master programme lives in P6, and reaches the site as revisions: each one uploaded against the series, parsed into its work breakdown, and badged with what it was staged from — because a P6 export and a PDF print do not carry the same fidelity. What lands is the programme itself, browsable band by band, with the activities already promoted carrying the work line they became. A newer revision is read against the standing basis before anything moves: date changes, logic deltas and new codes grouped into facets that are accepted one at a time. And the variance lens reads that plan back against the site — expected against planned, and what has slipped. Recorded against the live demo site.

The homepage hero loop: a slow camera glide across the demo site with every crew, machine, work area and exclusion zone placed in space and time, and the clash pulses live on the plan. One continuous take, no narration — recorded against the live demo site, not a mock.

The camera never moves; only the moment does. Winding the clock across the working day shows the same ground carrying different work — the day shift’s crews and plant clearing at the turnover, the back shift’s taking their place. One continuous take, no narration. Recorded against the live demo site, not a mock.

A clash is not an event that happened — it is two work windows overlapping in space and time, so it exists days before anyone is on the ground and clears the moment one window moves. Winding the clock across the working day shows the noticeboard’s ranked list being born and clearing with the work. Recorded against the live demo site.

Selecting a live permit on the board casts a lens over the map: the crew and plant that permit authorises stay lit while the rest of the site steps back, and the same set is named beside it. Closing the permit brings the site back. Recorded against the live demo site, not a mock.

An issued permit carries the exact RAMS revision it was approved against, frozen at submit. When a newer revision is accepted the permit says so — it warns rather than silently re-papering approved work — and the register keeps both revisions on the record. Recorded against the live demo site.

The noticeboard ranks the site’s day without anyone going looking, and the report wizard turns it into the paper somebody signs: a finalized session with its clash scenes ranked critical, notable and minor, and a human’s decision on record for each. Recorded against the live demo site.

An open incident under investigation: a five-by-five likelihood-against-consequence rating with the band derived from it rather than asserted, the cause pinned to the Swiss-Cheese barrier layer that should have caught it instead of filed as “human error”, and the corrective action still outstanding — which is why the case is still open. Recorded against the live demo site.

A corrective action’s own timeline: closed out with photo evidence, sent back by HSE with a reason on the record, resubmitted with better evidence, accepted. Nothing is overwritten — the whole argument is still there a week later. Recorded against the live demo site.

A templated, versioned inspection that failed one item — the isolation that could not be proven on the walk-round — and the corrective Actions that item raised, sitting in the register against the company that has to fix them, each naming the question it came from. Recorded against the live demo site.

Materials are located, not listed: a lot knows the laydown it stands in, and the laydown answers for its balance. Behind it an append-only ledger — the delivery in, the move, and the short load found at the goods-in count, kept as its own dated and attributed entry rather than a number quietly corrected. Recorded against the live demo site.

An evidence pack is a declared window — a span of time, an area, a firm — frozen with the contents that existed when it was drawn and fingerprinted with a content hash. Re-verifying the attestation re-reads and re-hashes the pack and answers that nothing has moved underneath it. Filmed from the QS seat, which sees everything and touches nothing. Recorded against the live demo site.

Two crews stopped in the same week for two entirely different reasons — one of them a clash between trades booked into the same riser — and both were declared while they were happening, each with its own dated window and its own stood-down headcount. The overlap is a matter of record rather than of reconstruction, and the ledger prices each one’s hours separately. Recorded against the live demo site.

A coordinator opens the site before anybody has called them: the day’s clashes ranked worst first, the work that has already stopped and who declared it, what is permitted today and who is under it, and the corrective action somebody still owes from yesterday. None of it was assembled by hand. Recorded against the live demo site.

A printed QR beside the work opens one page on any phone — no app, no account — and that page names the document and the exact revision being signed on to. Back at the desk the register shows who signed it and that each of them signed themselves, rather than a supervisor transcribing a sheet afterwards. Recorded against the live demo site.

Every site plan draws a building as one outline. A real building is not one outline: the podium takes the full plan and the tower above it steps in, so the same coordinates sit inside a different boundary on every floor. Walking up the storeys shows each plate against the whole envelope it sits within. Recorded against the live demo site.

A site plan that is only right on one screen is not right. Everyone on the site is on the same plan at the same moment: who else is here shows in the presence roster, and when somebody moves a crew the token moves on every screen at once — no refresh, no saving down and sending round. Recorded against the live demo site, not a mock.

A printed QR by the gate opens one page on any phone — no app, no account, no invitation. What kind of thing it is, how likely against how bad on a five-by-five grid, a sentence and a photograph — and it lands in the site’s triage queue beside everything reported from inside the app. Recorded against the live demo site.

One address for every site, and standing somewhere is the credential. The page asks for a location once; what it is physically inside decides which site is being reported on, and opens that site’s own hazard report with that site’s own categories on it. Nothing to install, no link to be sent, nothing to type. Recorded against the live demo site.

A slow glide across the live demo site — crews in contractor colours, plant with drop zones, work areas in time — passing a red clash pulsing where two work windows overlap.

Two work windows dragged into overlap on the demo site: a red clash is born on the plan, days ahead — and clears the moment the window moves back.

One seat drives a demo-site permit from requested to issued: reviewed and approved at the desk, walked down at the point of work, countersigned to start work.

The Work home’s Reality view on the demo site: the contractor × place × day matrix swept through a week while the map choropleth shows the work moving.

The demo site’s noticeboard, ranked by severity, feeding the report wizard: the day’s scenes accepted into the briefing and the session finalised.

A phone reports a hazard on the demo site — photo, a tap on the 5×5 grid, submit — and the report lands in the HSE triage queue with its evidence attached.

An inspection run on the demo site ends on a failed item — and mints corrective actions on the spot: one owner, one due date, evidence required.

A demo-site incident investigation read end to end: the 5×5 rating deriving the band, the chain of events, causes pinned to barrier layers.

The demo site’s diary: My Round answers the one question the system can’t know, the Document view assembles the day, and yesterday stands published as Revision A.

A stoppage declared from a live clash on the demo site, two windows overlapping on one timeline — concurrent delay as a picture — ending on the crew-hours ledger.

An evidence pack generated for a declared window on the demo site — narrative PDF, raw annexes — frozen under its content-hash attestation.

A coordinator’s day on the demo site in four beats: the noticeboard triaged, the permit board worked, Thursday’s clash moved before it happens, the briefing rendered.

Selecting permits on the demo site’s board lights each one’s work on the map — the board carries the state so the map can show it.

Another seat moves a plant item on the demo site — and it glides live across this screen, presence avatars showing who’s on.

A phone scans a RAMS QR on the demo site, reads the briefing and signs on — the signature landing at the top of the revision’s chain.

The demo site’s geofenced URL opens straight in a phone browser: photo, severity tap, submit — a hazard report before the moment passes.

The demo site scrubbed through a day: crews and work areas appear, shift and clear as their windows pass — the record, replayed.

“What was in that laydown three weeks ago?” — every movement on the demo site’s materials ledger is a dated, append-only entry, so the record already holds the answer.

Two close-outs on the demo site’s actions board: the thin one rejected and returned with its rework count, the evidenced one accepted and closed.

A demo-site permit rests on the exact RAMS revision it was approved against, hash-frozen — the board warns the moment a newer upload supersedes it.

The demo site’s contractual defects register — imported, tracked per contractor, each defect carrying its reference and status.

The demo site’s lost-time ledger: crew-hours derived as window × headcount over the countersigned stoppage record — a firm’s position, and the site’s.

A day photo taken at the demo site’s workface lands in the day’s record — timed, placed, attributed — no evening upload session.

The demo site’s morning diary email, opened into the published daily PDF — the record in the inbox before anyone asks for it.