How CheckSteady works

Supervisors and administrators may be asked for a six-digit code from their email after the password, if the site requires it or the login looks unusual. Type the code; tick Trust this device only on your own phone, never on a shared terminal.

You can switch screens at any time with the pill at the top. The colour follows you onto the buttons and the swipe strips, so you always know which record you are writing. Opening the app with ?view=inout or ?view=register on the address fixes a device's job the same way as the tick.

The first time you open each screen on a device, a short card at the top says the three things that matter; tap Got it and it never returns.

A platform administrator is an admin of their own site who can also add and close centres, and sees no other centre's residents.

Every row is enforced in the database, not the screen: a button a role should not press is refused even if someone finds the request behind it.

The three tiles. On site, Off site and Moved today count the list below them. Tap a tile to see only those residents; tap again for everyone.

Since when. Every card says on site since 14:20 or off site since Thu 4 Sep 09:10, the time of the last movement, with the day once it is not today. No movement on record means never signed in.

Nothing is edited afterwards. A wrong movement is corrected by recording the opposite one, and both stay on the log with the times.

Several at once. A box sits at the left of every card. Tick two or more, or tap Select all shown above the list (type a room or pick a tile first to narrow it), and a bar appears at the bottom with Sign IN and Sign OUT for everyone ticked. Each person still gets their own movement with the time and your name. Ticking one member of a family ticks the whole family on screen. ✕ in the bar clears the ticks; a single ticked box does nothing on its own, since Sign in or Sign out on the card is the one-person act.

The sheet. Tap a name and a sheet slides up. Close it with the ✕ at the top of the sheet (it stays in view while you scroll), a tap on the dimmed page behind it, Escape on a keyboard, or Close at the bottom. Tapping another name swaps straight to that person.

Spelling. Accents and name order are forgiven; a near miss still finds the person.

Supervisors and admins have three reports under Admin → Reports. Absent now is everyone off site this moment, with when they left, who signed them out, and whether the absence is authorised. Absent overnight is who was off site at midnight on each night in a range: the app takes that snapshot itself just after midnight and keeps it as long as the register, so a night months ago is still there after the movement log has been cleared. Out and back is the check-out and check-in list: one row per absence with room, date and time out, date and time back, hours away, and who signed each. All three mark under-18s, so a child's overnight absence stands out. The Weekly register update is the report behind the Sunday email: each absence as one line, "was absent from Monday to Wednesday, back on Thursday. Approved by management", the weekend's on their own, the week's departures, and rooms under maintenance or with free beds.

On one person's History, Both / In & out / Check-ins narrows it to one register, and supervisors and admins also see Export CSV: give a reason and the rows shown download as a spreadsheet, on the record like any other export.

The tiles. Not seen is today's work. Seen today is who has already checked in, and each card says the time. Runs of missed nights and days absent in the rolling window are not on this screen; supervisors and admins read them under Admin → Absences.

The detail sheet. Tap a name: the ID document type and number, today's check-ins with who recorded each, consecutive missed nights and days absent in the window each shown beside the figure in Settings ("2 of 3", "9 of 10"), the last 30 days as a strip (green seen, red missed, grey not required; tap a cell for the date and time), and a note when a count has reached a figure. The note states the count; it never gives a verdict. Supervisors and admins can add or change the ID number here.

Away with the centre's agreement. A resident on an authorised absence shows Away until a date on their card and is not counted as not seen; those days never count as missed.

The door switch. Where the site has turned on "An In & out sign-in counts as check-in" under Settings, a sign IN (never a sign OUT) is also recorded as the day's check-in. Leave it off where the policy makes residents responsible for their own check-in.

The ID number is on the sheet only, never in a list, and every opening of the sheet is logged with your name. An inspector can ask who looked at a record.

A person is counted once however many wardens tick them; a swipe never un-marks anyone. The drill is kept as a record with who was accounted for, by whom, when, and the note. The report Roll call: who was marked safe lists it person by person.

With no connection each phone keeps its own ticks and they merge when the network returns. Two phones cannot see each other's ticks while both are offline.

They appear under On site with the time and your name, then under Left today. During a roll call everyone still signed in is listed under Staff, visitors and contractors and marked safe like a resident. Only a kind, a name, an optional company and the times are held, kept as long as the movement log. Signing visitors in and out needs a connection; the roll call keeps the last on-site list on the phone so a drill can still count them.

Import. Every line gets a verdict: ready, already on the register, or the problem to fix. Only the ready lines are added; import again after fixing the sheet and nobody is duplicated. Dates can be day first (14/03/1988) or year first (1988-03-14). The evacuation column can be words, such as "needs help to move" or "wheelchair".

The edit sheet. Details, room, evacuation need, family, authorised absences, breach reports, the rooms they have had, and their history. A departed resident's record stays for the retention period and can be reactivated. Admins can export or erase the whole record from here.

Families. Select several, tick, Family. If one of them is already in a family the others join it. A family stays together on the roll call, children marked, and a room reads as a family.

Absences tab. Every active resident with a run of missed nights or a missed day in the rolling window, worst first, each count beside the figure in Settings, with whether they are checked in today or away, and the last breach report. Type a name or room to filter. Nothing is decided here; the letter is the manager's.

Breach reports. When a figure is reached, or a resident misuses the verification tablet by signing in for others, staff issue a breach report to IPAS. Record on the person's sheet that it was issued, which kind, the day and its reference, so nobody issues one twice.

The nightly reminder. With the switch on under Settings, supervisors and admins are emailed the residents at or over a figure after close-out, on the nights there is anyone to list.

Assign residents to rooms on their edit sheet. The tab then shows occupancy per room: each person is a chip with a filled dot for on site, a hollow dot for off site, child where under the adult age, and their evacuation need where that feature is on. Tap a chip to open their record. A room never lived in is simply removed; one that was is archived, keeps its history, and takes nobody new.

Daily register: one row per resident per day, required, presented, first seen. Attendance: one row per resident with days required, presented and missed. Movement log: every sign in and out. Out and back: one row per absence, out and back on one line, hours away. Absent now, Absent overnight: see off site. Weekly register update: the Sunday report, see Send the Sunday report. Drills and Who was marked safe: the roll-call record. Occupancy and Vacancies: per room, the latter against contracted beds. Evacuation list: everyone with room, presence and need. Administrators also have Who viewed which record.

Features are off until turned on here; turning one off hides its screens and deletes nothing. The IPAS policy says six months for the register; the audit trail and access log follow it. Movements default to 90 days; raise it if you need the log itself for longer, though the overnight snapshot keeps the answer regardless.

In & out and the register keep working when the connection drops; the list you last saw stays on screen. When the connection returns the queue is sent with the time you actually recorded it, and the cards update. A queued event survives a logout and is sent the next time anyone logs in on that device. Events older than the site's sync window are refused and listed so you can re-record them. The copy of the register held on the device is encrypted.