When the situation in a city changes from hour to hour, the problem is often not a lack of information. The problem is that everyone is working with a different version of it.
Emergency services may be using a map prepared in the morning. The crisis management team has a newer file. A contractor received a screenshot showing where sandbags should be delivered. Meanwhile, one street has already been closed, the assembly point needs to be moved, and a field crew is reporting another location that requires attention.
During a flood, severe storm, major infrastructure failure or evacuation preparations, the physical situation changes faster than documents do. Every new PDF or spreadsheet therefore starts to describe only part of what is actually happening.
In this situation, PlanPlace can serve as a shared operational plan. It does not replace emergency systems or public warning channels. Its role is to organise where things are happening, what work needs to be done, who is responsible for it and how the current situation can be shared with people working in the field.
In a crisis, a list of addresses quickly stops being enough
A crisis always unfolds in specific places. It is not enough to know that the problem concerns Riverside Street. The team also needs to know which section is flooded, where the road becomes impassable, which direction crews can approach from and exactly where materials should be delivered.
The same applies to evacuation. “Assembly point by the school” is too vague if the site has three entrances, a car park and a separate yard. On the map, the assembly area, bus waiting zone and vehicle route can all be shown separately.
In PlanPlace, an affected area can be marked as a zone, a closed road as a specific section, and a medical point, sandbag storage area or crew work location as an object on the map.
This means the team does not have to explain every location in words. Everyone refers to the same place.
One plan brings together information that would usually end up in several files
During a larger operation, information separates very quickly. There may be one list of road closures, another plan for field crews, a separate equipment register, while the latest decisions are buried in emails and messenger threads.
The problem appears when someone needs to see the whole situation at once.
One PlanPlace plan can bring together hazard zones, diversions, assembly points, crew locations, barriers, equipment and temporary facilities. The goal is not to display everything at once, but to make sure all of that information refers to the same map.
This becomes especially important when something changes. If closing one road affects a contractor’s route or access to a support point, that relationship is visible in the context of the whole plan. There is no need to compare several documents and wonder which one was updated last.
Objects added to the map also create a list, so there is no need to re-enter them into a separate spreadsheet just to have an overview of what is already on the plan.
The map shows where, while tasks explain what needs to happen there
Marking a problem on the map does not yet organise the work.
If sandbags need to be placed along a particular section of an embankment, someone has to be assigned that task. If a road is closed, barriers and signs need to be set up. If an assembly point is created, someone has to prepare it before a specific time.
In PlanPlace, tasks can be linked to specific places on the map and included in the schedule. The coordinator can therefore see not only where the problem is, but also what needs to be done and who is responsible for that location.
This matters when several crews are working at the same time. Instead of having one map and a separate task table, the spatial plan and the work itself stay connected.
Contractors need the current plan, not another PDF
In a fast-changing situation, a file becomes outdated very quickly. A PDF sent in the morning may still be on a contractor’s phone several hours later, even though the access route or scope of work has already changed.
Instead of sending successive versions of documents, PlanPlace allows the plan to be shared through a link. The contractor opens the current view without having to create an account. The link can be password-protected and disabled when access is no longer needed.
The difference is simple: the contractor does not receive a copy of the plan from a specific moment in time. They receive access to a plan that the team can continue to update.
That means a change made by the coordinator does not have to trigger another email with a new attachment.
Information from the field can return directly to the map
Even a well-prepared plan cannot predict everything. The people on site are often the first to notice that a road is no longer passable, a new flooded area has appeared or a previously chosen location can no longer be used.
If that information comes back by phone, the same problem starts again. A photo goes into a messenger thread, the location is described as “past the bridge by the second entrance”, and the coordinator has to find the place on the map later.
In PlanPlace, a contractor who has been given permission can add an object found in the field directly to the plan. The situation can be described and photos can be attached, while the report location comes from the place where the person is standing.
The coordinator sees the new object on the plan immediately and decides what to do next. It can remain a piece of information about the situation or become the basis for another task.
This means the plan no longer works in only one direction. The coordinator shares the current situation with field crews, while knowledge from the field can return to the same map.
Residents can also see the changes that actually affect them
In a crisis, some information should reach not only crews and contractors, but residents as well. A closed street, changed diversion, new assembly point or relocated support point is often much easier to understand on a map than in a long text notice.
PlanPlace also allows a plan to be shared publicly. Residents can therefore see the current arrangement of points, zones and routes without access to the team’s internal working information. Internal comments, notes and tasks do not have to be part of that view.
This matters because a resident-facing plan serves a different purpose from the operational plan. It does not need to show the entire internal workflow of the city or services. It should answer practical questions: where traffic is still possible, where the assembly point is, which area is closed and what has changed since the previous announcement.
Such a view does not replace official alerts or municipal announcements. It can, however, complement them well, especially when a list of street names alone does not give residents a clear picture of the situation.
What matters most is one place that changes with the situation
In a crisis, it is impossible to prepare a plan that will remain correct throughout the whole day. The hazard zone may move, a diversion may stop working, and new tasks may appear after reports from the field.
The problem is not the changes themselves. The problem is when every change creates another document.
After a few hours, files start to appear with names such as “current”, “current 2”, “revised” and “version after 4 pm”. At that point, part of the coordinator’s work becomes figuring out who has the right material.
With one plan, only what actually needs to change is updated. A road is closed — the plan is updated. The assembly point moves — its position changes. A crew reports a new problem — it appears on the same map.
This is where PlanPlace provides the most value. It brings together space, tasks, scheduling, contractors and information sharing in one place. Instead of rebuilding the current picture from phone calls, spreadsheets, PDFs and messages, the team can work on one shared plan that changes along with the situation in the field.
