← Features

Reports & exports

The coordination report: a session built from a template for one report day, the day's clash scenes ranked for you to accept or reject, a Region-evolution rail per scene showing the ground ahead, and a branded PDF or Word file rendered from it on demand.

Every site ends its day with a coordination report: what clashed, where, whose work was involved and what is coming. On most sites that is a slide deck somebody assembles from screenshots. In SimOps it is a coordination session: a draft built from a report template for one report day, filled from the live site, curated by the coordinator, and rendered on demand to a branded PDF or Word file for the meeting.

What it does for you

  • The day's clashes arrive ranked. The session gathers the report day's clashes into ReportScenes — pieces of ground where the trouble is — and ranks them on severity, cross-contractor exposure, diversity, proximity and temporal density, tiered critical, notable and minor.
  • You decide what the document says. Every scene starts unaccepted. Accepting one puts it in the report with a headline map picture at the moment it clashes and room for your note; leaving it unaccepted keeps it out. Your decisions are recorded against the session.
  • The days ahead ride out beside each scene. An accepted scene can carry a Region evolution rail: the scheduled changes in that scene's ground over the coming days, pre-ticked at each day's busiest moment, so the report shows where the trouble is heading as well as where it was.
  • The paper is rendered, not typed. Export renders the session to a PDF or DOCX with the site's branding, on demand, as many times as you like. Finalize locks the session when the meeting is done; export stays open after that — and exporting a finalized session is the issuing act: each export mints a Report issue, a copy kept exactly as it went out, which every role on the site (the client included) can download from the Commercial surface's Reports tile. A draft's export is not paper, and a finished session nobody has exported has no issued copy yet.

Where it lives

The Report panel on the dock, or R. It opens on the picker — the report date, the delivery lookahead, the template to start from, and any drafts or completed reports to resume. A session's sections run down the panel's left edge; the one this page is mostly about is Clash Highlights, where the scenes are accepted and their Region-evolution rails curated. How many days a rail looks forward by default is a site setting, under Settings ▸ Site ▸ Reports. The issued copies of finished reports are read somewhere else: Commercial (I) ▸ Reports, open to every role, where the Report panel itself stays the coordinator's.

See it / try it

Where to go next

  • Reports — the concepts: the session, scenes and decisions, the Region-evolution rail, the day peak and when it ticks, and the site's forward-days setting.
  • Building and exporting a report — the how-to: start a session, accept scenes, curate the rails, export.
  • Planner & region evolution — the same Region-evolution engine live on the map, outside a report.
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.

Generated from source · SimOops living system reference