Flagged attendance

Firecrest flags attendance records it suspects were not recorded during the session itself — typically members scanning the QR much later, from home or the following day. Officers review the flagged records and decide whether each one stands or gets rejected.

The Flagged link at the top of the navbar shows the current queue.

What triggers a flag

A scan is flagged when it happens more than 1.5× the session duration past the session end time.

Two worked examples:

• A 2-hour drill ending at 9 pm. Any scan after midnight (9 pm + 3 h) is flagged.
• A 30-minute briefing ending at 7:30 pm. Any scan after 8:15 pm (7:30 pm + 45 min) is flagged.

Only member self-scans can land in the flagged queue. Officer-entered attendance is never flagged.

The record still gets created — flagging just tags it for review. The attendance counts toward the member's SMP hours unless and until an officer rejects it.

Where flagged records show up

Two places:

• Flagged in the top navbar. Single-page queue, one row per flagged record. This is the primary review surface.
• The session detail page shows a small ⚑ marker next to any flagged attendee in the Attendance table. Use this if you want context — e.g. to see whether the rest of the attendees were on time.

The decision: Approve or Reject

Each row in the Flagged queue has two buttons.

Approve

Clears the flag. The attendance stays on the member's record and continues to count toward their SMP hours.

Use Approve when the late scan has a legitimate explanation, for example:

• The member arrived on time but had a phone/signal issue and couldn't scan until later.
• The member asked you to record them manually, but you forgot in the moment and they scanned later in the day.
• The QR code itself had a problem on the night and the member only got through once you reset something.

Reject

Opens a confirmation modal that names both the member and the session, then permanently deletes the attendance record on confirmation.

Use Reject when the scan clearly should not stand, for example:

• The member wasn't actually at the session.
• A member is trying to log attendance after the fact for sessions they missed.
• The scan happened so far outside the session window that it's not plausibly tied to the session.

Reject is final

Once rejected, the attendance record is gone — there is no undo. If you reject in error, the only recovery path is to manually add the attendance back from the session detail page.

What the member sees when you reject

If the member has the "Email me if my attendance is rejected by an officer" preference enabled on their My Profile (it's the default for verified email addresses), they receive an email with the subject "Attendance rejected" that says their record has been reviewed, could not be verified, and will not count toward their SMP hours. The email lists the session name, date, and location, and tells them to contact you if they think it's a mistake.

If they don't have the preference enabled or don't have a verified email, no email goes out — the record just disappears from their profile.

Practical implication: if you're about to reject something that the member might reasonably have thought was fine, send them a quick message yourself first. The auto-generated email is brief and gives no explanation beyond "could not be verified".

How often to review

Weekly at minimum. Monthly is too long because by then nobody remembers whether John was actually at the drill three Tuesdays ago. The Flagged queue is small in most brigades — usually 0–2 entries a week — and a five-minute habit on a regular day clears it.

The queue is empty when everything is in order; the page just shows "No flagged records."