Troubleshoot the floorplan builder

The failure modes of upload, trace, cleanup, zoning and saving — what causes each and what actually fixes it.

Applies toMain platformWeb
Needssites.manage

A reference list rather than a procedure. Find the symptom, read the cause, apply the fix.

Before you start

Have these ready.

  • Access to the floorplan builder for the floor in question.
  1. 01

    Upload problems

    The file picker accepts images, PDF, TIF and TIFF. Anything else is silently ignored rather than rejected with a message, so a file that appears to do nothing is usually the wrong type.

    • Nothing happens on selecting a file — check the extension is one of the accepted types.
    • The plan appears but is blurry — it exceeded 2048 pixels on its longest edge and was downscaled. Crop rather than shrink.
    • A PDF appears blank — it rasterised to an empty page; export it as an image from the source instead.
  2. 02

    Trace problems

    Most trace failures are source-quality failures. Before re-running, ask whether the drawing would be readable to you at 2048 pixels wide.

    • No rooms detected — faint, dashed or hatched walls, or a photographed source.
    • Too many rooms — legends, title blocks and furniture were traced. Crop the source.
    • Rooms with no names — labels were unreadable after downscaling. Use Name unnamed rooms.
    • Some tiles missing — transient failures; re-run the auto-trace.
    • AI Mode buttons disabled — no image uploaded, an analysis is already running, or the organisation is in demo mode.
  3. 03

    Geometry problems

    Overlaps and gaps have specific tools; anything else is usually a case for drawing by hand.

    • Overlapping rooms along a line — a tile seam. Run Fix overlaps.
    • Rooms that should connect but do not — run Fill gaps, then check Adjacent rooms.
    • A room boundary that ignores a wall — delete it and use Draw room.
    • Routes crossing open ground — the boundary is too generous. Use Edit boundary.
  4. 04

    Door and route problems

    Doors come only from the full analysis or from being placed by hand.

    • No doors after tracing — The room trace does not detect doors. Run Full AI Analysis, or use Add doors.
    • Route ends mid-floor — a missing door breaks the chain to any exit.
    • Route goes to a locked door — an exit was marked that should not have been.
    • Upper-floor route does not descend — the room's Evacuate via is set to Direct to assembly point rather than Via staircase.
    • Staircase route restarts on the floor below — the two staircase entrances were never linked as the same staircase.
  5. 05

    Zone and assembly problems

    Both of these fail silently, which is why they are worth checking explicitly rather than waiting to notice.

    • Rooms showing Not in a zone — assign them; they are excluded from zone-scoped incidents.
    • Zone has no assembly point set — attach one, or people in that zone get no muster destination.
    • Select a zone first — you tried to assign rooms with no zone selected.
    • Suggested zones overwrote your structure — they were applied without review. Reassign the affected rooms.
  6. 06

    Saving and history problems

    Save is the checkpoint. Undo is convenience.

    • Undo runs out — history keeps the last 50 actions and does not survive a reload.
    • Work lost on navigating away — it was never saved. Save floor plan before leaving.
    • Editing the wrong floor — the builder is scoped to one floor; check the header before uploading.
    • Rebuilding a floor you traced before — use Import JSON rather than re-tracing.

Good to know

Small details that prevent big confusion.

  • If you cannot tell which parts of a trace are wrong, discard it. An unauditable trace is worse than none.
  • Almost every trace complaint is a source-image complaint in disguise.
  • Save before experimenting, not after.

Was this guide clear?

Help us make the next version better.