Ale dirèk nan kontni prensipal la

Keep the door moving when the connection drops

The bus is here and the kiosk badge has just turned amber. You can keep scanning. This page tells you what the kiosk records while it is offline, what it cannot check, and how those records reach PTRS when the connection comes back.

Offline works for check-ins only. There is no offline check-out. If you check children out while offline, PTRS has no record of it.

Before you go offline​

Two things must happen while you still have a connection, because the offline kiosk depends on them.

  1. Open the kiosk while online. That opens today's session and the kiosk remembers it. If the kiosk is first opened with no connection, it makes up a provisional session on the device instead, and check-ins queued against a made-up session are at risk. See When the queue will not empty.
  2. Leave the kiosk on that device. The queue lives in that browser on that device. Closing the tab is fine. Clearing the browser's site data loses the queue.

Check the badge at the top of the kiosk. It reads Online in green with a signal icon.

While offline​

The badge turns amber and reads Offline. Scan badges exactly as you normally would.

Each scan is kept on the device and the message reads "Queued offline, will sync when connected". The badge shows a pending count that grows with each scan.

What you lose for those children, and cannot get back later:

  • No allergy alert. The allergy list comes from PTRS, and PTRS is not there. Keep the allergy list on paper.
  • No duplicate check. The "already checked in" rule cannot run.
  • No illness check. A child inside a 24-hour illness exclusion will be checked in by an offline scan, and PTRS will accept that record when it arrives. Keep the exclusion list on paper.
  • No missing-paperwork warning.
  • No room, so no ratio figure.

How the records get in​

You do not normally do anything. While the browser reports a connection, the kiosk tries to send its queue every 30 seconds, and it tries immediately when the connection comes back. Records go up in batches of 50. The pending count on the badge refreshes every 10 seconds.

Watch the count fall to zero. That is your confirmation.

The refresh button appears only when it cannot work

The refresh icon next to the pending count is shown only while the badge says Offline, and the kiosk refuses to send anything without a connection. Pressing it does nothing. Once you are back online the button is gone. There is no working manual trigger, and you do not need one.

What PTRS does with each queued check-in​

Each record is checked on its own. One rejected record does not stop the rest of the batch going in.

PTRS rejects a record whenWhy it happens
Session (id) not found.The session never existed in PTRS. Almost always a made-up provisional session.
Member (id) not found.The child's record was deleted, or belongs to another organisation.
Staff (id) not found.The staff member recorded on the device does not exist in PTRS.
Duplicate check-in for member (id).The child already had an open check-in within one minute of the queued time.
Invalid attendance method.The record's method was neither a badge scan nor manual. This does not happen from the kiosk.

Notice how narrow the duplicate rule is. It only catches a second check-in within one minute of the first. A child scanned offline at 3:02 pm and again by someone else online at 3:30 pm ends up with two open check-ins, and PTRS accepts both.

Accepted records keep the time they were scanned on the device, not the time they arrived. PTRS trusts the device's clock, with one minute of tolerance. If the device's clock is more than a minute fast, every record in the batch is refused.

When the queue will not empty​

A record that fails is retried on the next attempt, up to five times, and then abandoned. Records that were sent successfully are cleared from the device after 72 hours.

The failure worth understanding is the provisional session.

If the kiosk was first opened with no connection, it made up a session on the device with a placeholder where the staff member should be. When the connection returns, the kiosk opens a real session and points the queued records at it, but it does not replace the placeholder staff member. PTRS requires a real one, and it refuses the whole batch, not just one record.

So check-ins captured on a kiosk that never reached PTRS that day can fail to send, all of them, every time. The pending count stays where it is and the badge shows an error.

If that happens:

  1. Write down the pending count and the children involved before you do anything else.
  2. Confirm the kiosk can now reach PTRS. The badge reads Online.
  3. Record those check-ins again at the kiosk or from Quick Check-In. The times will be the times you re-enter them, so keep the real arrival times on paper.
  4. Report it. This is a defect in PTRS, not something you set up wrong.

Always open the kiosk while online at the start of the day. That one habit avoids all of this.

What offline does not cover​

  • Check-out. There is no offline check-out and no way to send one later.
  • The grid of child tiles. The kiosk's roster is empty online, so it is empty offline too. Badge scanning is the route.
  • These pages. This guide has no offline mode either. Print the pages you need to carry.

Checked against PTRS on 7 September 2026.