View Categories

Collie Attendance – IN/OUT & On-Site Behaviour

Collie Attendance – IN/OUT & On-Site Behaviour #

Understanding attendance status, IN/OUT sequences, and On-Site behaviour in Collie.

Overview #

Collie uses an IN/OUT attendance sequence to determine whether a personnel is currently
On Site or Off Site.

A personnel who has checked IN but has not completed a proper OUT
will remain On Site in Collie.

Attendance Sequence #

The expected attendance sequence is:

IN → OUT → IN → OUT

Each IN should be followed by a corresponding OUT
before the next IN.

On-Site Status #

When a personnel checks IN, the personnel becomes On Site:

IN

On Site

The personnel remains On Site until a proper OUT is recorded.

Consequence of an Incomplete Sequence #

If a personnel forgets to check OUT, the personnel will remain
On Site.

Day 1
08:30 → IN

On Site
No OUT recorded
Still On Site
Day 2
08:30 → IN

Personnel is already considered
“On Site” in Collie
The new IN is not recorded/displayed
as a new transaction

Therefore, a user may report that their morning IN is missing,
while the underlying cause is an incomplete previous IN/OUT sequence.

How to Check On-Site Personnel #

To identify personnel who are currently considered On Site:

Collie → On-Site → Export Report

The exported report can be used to review personnel who may have an incomplete
IN/OUT sequence.

Breakdown Report Behaviour #

The Breakdown Report includes IN records and looks for the
first OUT with the same personnel/PIN on the same day to calculate
the attendance duration.

Note: An OUT without a corresponding IN is not included in the
Breakdown Report.

Troubleshooting Guideline #

  1. Check whether the personnel is currently On Site.
  2. Review the personnel’s previous IN/OUT sequence.
  3. Check whether the previous OUT was properly recorded.
  4. If there is an incomplete sequence, explain the On-Site behaviour to the user.
  5. Do not immediately treat the case as a system issue before checking the attendance sequence.

Quick Reference #

IN → OUT → IN → OUT

Always complete the OUT transaction before the next IN.

Powered by BetterDocs