For coordinators

Reviewing clashes, building safety reports, importing permits and DXF floor plans, and managing contractors.

Coordinators run the day-to-day safety picture for a site. This page walks the four jobs that make up most of that day; each links on to the page that goes deeper.

Review the day's clashes

The platform detects where overlapping work areas, plant and people are about to collide and ranks them by severity. Your job is to walk that list and decide what to do about each one.

Press N to open the Noticeboard. Clash items are grouped by severity, red first, with the delivery items beside them.
Open a row to see the two entities in conflict, the rule that fired and the window over which they overlap. A pair can produce more than one row — every distinct hazard surfaces on its own, so a proximity clash and a permit conflict between the same two people are two rows, not one.
Fix it in the plan, or record a decision on it. Detection is server-side and continuous, so a moved window or a moved position clears the row on the next evaluation without anyone marking it resolved.
Where a clash has actually stopped work, use the row's ⛔ mark as blocker action — it writes the stance and the loss record in one atomic transaction. See Raising a blocker.

What counts as a clash, at what severity, and who gets told is site policy rather than code: Configuring clash rules is the authoring surface, and nothing there needs a deploy.

Build a safety report

The report wizard ranks the day's clash scenes and lets you accept the ones worth surfacing, then renders a branded PDF or DOCX for the coordination meeting.

Press R to open the Report panel.
Set the window the report covers, then walk the ranked scenes. Ranking is multi-factor — severity, cross-contractor exposure, diversity, proximity and temporal density — and the scenes are tiered critical / notable / minor.
Accept or reject each scene. Your decisions are what the document contains, and they are also recorded against the session, so the ranking can be trained on what coordinators actually chose.
Render. The output carries the site's own branding, and the weather ribbon for the window is rasterised into it.

Import permits and floor plans

Both live behind the Imports panel (Z), whose accordion holds Work Permits, Reference Layers, Site Data and DXF Floor Plans.

Open Imports (Z) and pick Work Permits. Permit spreadsheets drive entity creation: selecting a permit later pre-fills the work areas, schedules and contractors so the plan matches what was actually approved. Any customer layout is readable — the parser is config-driven, not hard-coded to one spreadsheet shape.
For floor plans, pick DXF Floor Plans and upload one georeferenced CAD drawing. It becomes a floor plan per selected building and level.
Set the drawing coordinate system — an EPSG code, defaulting to 27700 (OSGB36 / British National Grid). Where the DXF carries embedded geodata the field pre-fills itself. Drawings in local, unreferenced coordinates cannot be imported here; export an image and place it with the floor-plan image upload instead.
Choose initial visibility and window padding. On the default vector path everything is extracted and the profile (everything visible, walls, no annotations) only decides which drawing layers start visible; on the raster fallback the same control is the classic layer preset and does gate what is baked into the image. Padding (default 10 m) is how far past each building's outline the import reaches, so protruding grid lines and reference annotations survive.
Watch progress per building. Re-running with Replace existing floor plans ticked overwrites plans that already exist at the selected level.

By default each building's linework is extracted as a native vector plan — crisp at every zoom and restyleable without re-import. The raster fallback toggle bakes a fixed-resolution image instead; reach for it only when a drawing extracts badly.

Manage contractors and oversight

Contractors are colour-coded teams, and oversight relationships decide which teams a supervising contractor can see and act on across the site.

Press C to open the Contractors panel.
Set each team's colour — it is the identity every surface reads, from map fill to noticeboard swatch, so keep it stable once work has started.
Where one firm supervises another, record the oversight relationship rather than widening the supervisor's role. Oversight is one seam: it decides which contractors' work a supervisor can reach, and it is enforced server-side.