From site plan to event operations

1. Start the event

Create a project, select its venue and set build-to-strike dates. A general warehouse project can work without a map. To reuse a previous event, choose Copy for a new event: an independent copy is the default. You can instead copy permanent venue features or deliberately share a map. Copies reset task completion, assignments and allocations. New project dates shift the task schedule; blank dates leave copied work unscheduled.

2. Plan the map

Open the mapper from the project's Map screen. Layout records the general arrangement; Logistics adds facilities, routes and equipment detail; Player presents selected public features. Existing drafts, commits, history and browser recovery remain available.

Commit a feature, select it and open Project actions to link a Place, add equipment requirements or create work. A Place is a useful operational destination; trees and decorative geometry do not need one. The Map screen shows readiness markers and links back to the selected feature.

3. Specify and allocate equipment

In Equipment, add catalogue specifications and requirements. Catalogue items can describe individually tracked assets, quantity stock, consumables or hire. Requirements show required, allocated, short, delivered and returned quantities. Reserve owned stock for explicit dates or record the hire supplier. Overlapping reservations are checked before saving.

Record deliveries and returns on an allocation, or complete linked delivery/return work. Individual assets move to the destination and retain movement history. Consumables reduce available stock when delivered; record only unused quantities as returns. Their work package ends with a usage reconciliation, rather than assuming all stock returns.

4. Plan utilities

Draw and connect electrical or water components in Logistics. In Project actions, expand Materials & capacity inputs for loads, phase, pressure, pipe data, cable coefficients and route allowance. Commit the map, then open Equipment → Utility planning. Review unmatched materials and connection warnings before importing requirements or exporting a CSV.

Stock-length specifications round cable and pipe quantities up to whole lengths. Joining fittings and adaptors still need review. Electrical phase/load and water pressure estimates use the values entered and support radial networks with a single source. Missing inputs, loops and multiple-source networks are flagged. Calculations are planning estimates: they do not automatically choose safe cable sizes or replace an installation design review. Parking and camping illustrations also remain planning estimates.

5. Schedule, build and operate

A requirement can generate linked delivery, installation, inspection, removal and return tasks. Use Work as a list, board, schedule or map; filter by team, person or unassigned work. Dates and dependencies are edited on the task. Cycles and cross-project dependencies are rejected. Completion checks prerequisites and checklist items; a deliberate override needs a reason.

On a phone, open My team, choose a team and open the next task. Follow its map link, complete the checklist, add notes/photos or report an issue. General work completes without moving equipment. Delivery and return completion explains its stock movement. Completed movements are repeat-safe and their equipment/destination cannot be rewritten afterwards; create follow-up work for a correction.

The team display is read-only, identifies its project and reports refresh failures. Photos and field updates need a network connection; map browser recovery is not full offline field synchronisation.

6. Review and issue the plan

A map Commit saves a version; it does not approve or publish it. In Outputs, request review to capture the committed map and an operations snapshot. Record the reviewer, approve and issue that snapshot. Layout, Logistics, full-site Player, IC Player and the operations pack then remain stable while the working plan changes. Print/save PDF or download map SVGs.

Moving or deleting a linked feature, including by restoring an older map, asks you to keep the operational records and review the effect. The Overview/Outputs change queue lets you acknowledge the change, reassign open work or cancel work that has not been deployed. Completed history is retained.