Skip to content
Docs

BCP Core

BCP Core puts business continuity on every employee’s phone. It watches hazards, lets the BCP team declare an incident and set the level, tells every phone at once, collects each person’s status and escalates anyone who has not reported.

BCP Core is the business continuity module of Risk Core, sharing its core with ERM Core. It is a web app that staff add to their home screen, with nothing to install from a store.

BCP Core from hazard to escalationHazard feeds raise status cards at criteria; the BCP head declares an incident and sets the level; every staff phone is notified; staff check in; the team view rolls up; people not reported are escalated and followed up in the incident room.PUSHCHECK INHazard feedsrain · PM2.5 · heat · watersatelliteBCP status cardsshown at criteriaBCP headdeclares · sets the levelEvery staff phonepush notificationStaff check insafe · affected · need helpTeam viewteam · line · whole companyEscalationnot reported → head → next levelIncident roomcall · report for · chatLEGENDExternal feedCommandStepAutomatic
One incident from first signal to follow-up. The system notifies and escalates; the BCP team decides.

Two ways in

Section titled “Two ways in”
StaffGeneral public
WhoEmployees on the staff register, signed in with their company e-mailAnyone with the link, when the company opens the public service
What they getSituation, company announcements, check-in, team view, incident rooms, flood-avoiding route to the officeForecast, map, route and cameras
Personal dataCompany e-mail and check-in answersNone collected

What it covers

Section titled “What it covers”
  • Situation: BCP status cards, a 3-day forecast, rain, PM2.5 and heat index, flood points, canal and river levels, and satellite flood extent. Details are on Situation and early warning.
  • Command: declaring an incident, the BCP level, roll-call rounds and announcements. See Incidents and command.
  • Check-in: one tap to report safe, affected or need help. See Check-in.
  • Call tree: team rooms, calls, reporting for someone and automatic escalation. See Call tree.

Scenarios

Section titled “Scenarios”

Each incident is declared under a scenario that carries its own official links and guides: flood, PM2.5 and heat, earthquake and toxic smoke, violent incident, protest, emergency decree or curfew, and epidemic.

Access and security

Section titled “Access and security”
  • Staff sign in with their company e-mail and password. An e-mail that is not on the staff register is refused.
  • Command roles must also enter a 6-digit code from an authenticator app. One-use backup codes cover a lost phone, and more than five wrong tries locks sign-in for an hour.
  • Every table has row-level security, and each company sees only its own data. Sign-ins are logged.
  • Check-in collects no location. Answers are kept for a period the company sets, then deleted.