Unrest, an election week, a storm, an incident at one of your sites. GeoBit stands up a response desk for your sites, people and cities, and runs it for the week: a named incident lead, cascades and muster, situation reports every hour, a decision log, and the after-action report within five business days. One flat price per week, agreed before the desk stands up. The system carries the load, so your people stay on their own jobs.
Illustrative crisis desk · not a client · time sped up
Events set the order. What is included does not change. Here is how a week can run, day by day, and what lands with you after it.
The week starts the day you say yes. Your sites, people and cities go on the picture, a named incident lead takes the case and the decision log starts. If people are exposed, the first cascade goes out with check-in required within 15 minutes.
By the next business day the whole desk is running: cascades set for everyone in scope, the muster board live, and situation reports arriving every hour on your template.
Every acknowledgment is tracked. Anyone silent gets a push, then a text message, then a voice call, then a call to next of kin, until the muster board shows nobody unaccounted for.
The system re-reads the world every 20 minutes, each country in its own language. Two sources before anything is asserted. Rumors are watched, not broadcast, and nobody is woken for one.
Holding statements and stakeholder updates come from a fact base that keeps pace with events. Every decision is logged: who decided what, when, and on what evidence.
Evacuation and relocation planned on the live picture: corridors, assembly points, transport and safe locations, with the field app on every mover. The recommendation itself needs two named people.
If it has passed, the desk stands down through the same chain that stood it up and the decision log closes. If it has not, another week starts, agreed with you before this one ends.
What happened, what worked, what did not, and the changes it makes to your plans and playbooks. The plan gets better every time it is used.
You buy a finished week of crisis coverage, not hours and not seats. The price is agreed before the desk stands up, and it does not move with the hours we work or the number of people on the desk.
Not countedHours worked, seats, or how many people we put on the desk. None of them change the price.
Your footprint watched every day, with no event needed. If you want the watch to carry on after the week, this is it.
See The Watch → One deliverableA security, threat or risk assessment delivered on a date. A finished document, not live coverage.
See Assessments →Live coverage while it is happening, one week at a time, for the footprint you name.
Four ways to buy the work, each priced per unit: see them side by side →
The system does the reading, the drafting and the record-keeping. People make the calls, and the record shows who made each one.
One named person owns the case from the day it opens to stand-down. The incident lead decides; the system keeps the record. Anyone still unaccounted for after the cascade goes to a named person, not a queue.
Public statements, evacuation recommendations and mass notification above 50 people never fire on their own, at any autonomy tier. They wait for two named people, with the evidence attached. Every outbound action is also checked by a second AI model for accuracy and proportionality first.
Who decided what, when, and on what evidence, written as it happens rather than remembered afterwards. It closes at stand-down, and it is yours.
Every action and decision lands in an append-only log. Each record carries the hash of the one before it, so any edit or deletion breaks the chain at the exact line. Every decision can be rebuilt afterwards, including the system's own reasoning.
What the system may do on its own is written down and enforced. It starts at the most conservative tier, and the heaviest actions always need two named people, whatever the tier.
Without a desk, a bad week pulls your people off their jobs and into a room, and outside help arrives when it can.
Your people stop doing their own jobs for as long as it lasts. Who is in charge gets decided in the first hour, who has been told lives in an email chain, and who is accounted for ends up in a spreadsheet, eventually.
They start at their next available slot and own a slice of the work, usually the report, after the fact. The alerts, the muster and the record still land on your team.
Crisis Week puts that load on the system and a named desk. Your people stay on their jobs and get the decisions that are theirs to make, with the evidence attached.
| The job | Your own war room | Consultants, ad hoc | Crisis Week |
|---|---|---|---|
| Starting | When people can be pulled off their jobs | Their next available slot | The day you say yes |
| In charge | Decided in the first hour | Still your team | A named incident lead from day one |
| Telling people | An email chain | Left to your team | Cascades, every acknowledgment tracked |
| Accounting for people | A spreadsheet, eventually | Left to your team | A muster board worked until nobody is unaccounted for |
| Reporting | When someone has time | A report, after the fact | Every hour, on your template |
| The record | Memory | Not kept for you | A decision log and a hash-chained audit log |
| Afterwards | A meeting | Part of it, if it was in the brief | The after-action report within five business days |
| Your people | Off their jobs until it ends | Briefing the outside team | On their own jobs. The system carries the load |
Five steps, written down at every one. The incident lead decides; the system keeps the record.
Tell us what is happening, where, and who is in scope. Use the form below or call the number under it.
todayWe agree the footprint and one flat weekly price before anything starts.
agreed up frontA named incident lead, the case opened, the decision log started, cascades armed. The full desk by the next business day.
same dayThe watch around the clock, cascades and muster, situation reports every hour, decisions keyed by named people.
seven daysStand-down through the same chain, then the after-action report and the changes it makes to your plans.
five business daysCrisis Week runs on the same system and the same floor as the rest of GeoBit. Here is where each part is explained in full.
Plans, playbooks and drills before the day, and the response desk on call for when it comes.
Read more → /intelligence-servicesOne product on a date, including a crisis week run as a monitoring sprint.
Read more → /gsocOne example of the round-the-clock watch floor the response desk runs on.
Read more → /the-systemEverything included: the platform, the watch, the desks and the people who run them.
Read more →Tell us what is happening, where, and who is in scope. We come back within one working day with the footprint and one flat weekly price, or faster if it is happening now.