Export Site Plan Outputs

Site plan exports turn a saved or published layout into files other people can use. The important decision is not just which button to press. It is who needs the file, whether the plan is current, and whether the output should come from the working draft or the official published snapshot.

Before exporting

• Use the workflow panel to confirm whether the plan is Draft, Approved, Published, or behind the current working revision.
• Check that all expected participants are placed or deliberately unplaced.
• Review pitch references, zones, infrastructure, access routes, and labels.
• Confirm late participant changes, cancellations, or payment/compliance decisions that affect placement.
• Check that the plan is readable at the intended output size.
• Review power, water, waste, generator, fire-lane, access, welfare, noise, or supplier warnings before handover.

Choose the right output

• Visual PDF: best for quick review, crew briefings, print packs, and teams who need to see the layout rather than analyse data.
• Completeness, rule, zone, utility, or issue reports: best for planners who need a focused checklist before sign-off.
• Operations packs: best for site crew, check-in, security, emergency services, stage crew, or suppliers who need a filtered handover.
• Supplier schedules: best for power, water, or waste contractors who need practical installation and service details in a sortable file.
• Object data exports: best for mapping, GIS, or technical handoff where CSV, GeoJSON, or KML is more useful than a PDF.
• Published snapshot bundle: best when a coordinator needs one package containing the official layout, data, and supplier schedules.
• Export and change history: best when the team needs to prove which revision was saved, published, exported, or superseded.

Generate the export

Draft versus published data

• Current-plan reports use the saved working plan and are useful before final approval.
• Operations packs, supplier schedules, object data, and published bundles usually use the official published snapshot.
• Document Centre status can show when an export is older than the latest published revision or when a newer draft exists.
• If a team is acting from the file, use a published snapshot unless you deliberately need a draft review output.

Privacy and handover checks

• Use the narrowest audience that still gives the recipient what they need.
• Avoid sharing draft layout data outside the planning group unless that is deliberate.
• Check whether the output includes participant names, pitch details, utility needs, or operational notes before forwarding it.
• Regenerate files after material changes rather than editing exported copies manually.