Skip to content

Check-in

Check-in is how you tell your company, in one tap, whether you are safe. It opens when an incident is open. Your latest check-in is your current status, and you can change it at any time.

Who may do it: every employee, for themselves. A team head can record a check-in for a member after reaching them — see Team room and call tree.

One check-inStaff open BCP Core from the push, choose Safe, Affected or Need help, optionally add location (opt-in), a note and a photo, and send. The system stamps the time and the latest check-in is the current status. Team and line see the status only; the team head, HR and the BCP head see the detail. Every check-in is kept in the incident timeline. Sending again changes it at any time.SENDCHANGE ANY TIME: SEND AGAINStaff memberopens from the pushChoose statusSafe · Affected · Need helpOptionallocation (opt-in)note · photoCurrent statustime-stampedlatest one countsIncident timelineevery check-in, timedexported at closeTeam · line executivestatus onlyTeam head · HR · BCP headstatus with detailLEGENDUserStepOptionalSystem recordRecord
Choose a status, add location, a note or a photo if you want, and send. The latest check-in is your current status; every one is kept in the incident timeline.
  1. Open BCP Core — from the notification, or from the home-screen icon.
  2. Tap Check-in.
  3. Choose one status:
    • Safe — you are safe;
    • Affected — you are safe but affected, for example water near your home or no way to travel;
    • Need help — you need help now.
  4. If you want, add:
    • Location — share where you are for this check-in. It is off unless you turn it on, and it is asked for each check-in;
    • Note — a short message, for example a phone number you can be reached on now;
    • Photo — for example the water level at your door.
  5. Tap Send. The time is recorded and your status is updated at once.

Send a new check-in whenever your situation changes — for example from Affected to Need help, or back to Safe. The newest one becomes your current status. Earlier check-ins are kept in the incident’s timeline; they are not overwritten.

The BCP head or operator may start a new round when everyone should report again, for example each morning of a long incident. A new round asks you to check in again; your earlier answers stay in the timeline.

ViewerSees
Your teamYour status — Safe, Affected, Need help or not reported — without the note, photo or location
Your line executiveEvery status in their line, without the note, photo or location
Your team headYour status with the note, photo and location
HR, the BCP head and the operatorEvery status in the company, with the detail

BCP Core shows you this before you send, together with how long your check-ins are kept. See Team and unit status for the views themselves.

  • Only when an incident is open. Check-in opens at Standby or Activated and stops when the incident is Closed.
  • Your own account only. Check-in is tied to your signed-in account; nobody can check in under your e-mail.
  • Location is opt-in. No location is recorded unless you turn it on for that check-in.
  • Kept, then deleted. Check-ins are kept for the period your company sets, then deleted. Deleting a check-in before then is an act of HR, or of an activated operator, and needs an authenticator code — see Roles and permissions.