Skip to main content

Manager Review of Verifications

The manager review is the first approval step in the dual-approval workflow. Project managers look at worker self-verification submissions to confirm that the workers were actually there.

What the Manager Sees​

For each pending verification submission, the manager gets to see:

  • The worker's name and identifier (NIC or Employee ID)
  • The project name
  • The date of attendance
  • Whether it is an arrival or departure submission
  • The time the worker submitted
  • Photo evidence (if the worker uploaded one)
  • When the submission was made (the server timestamp)

Actions Available​

Approve​

  • Confirms the worker was present at the time they claimed
  • The system checks that there are no cross-project attendance conflicts (making sure the worker is not already marked on another project that day)
  • The submission moves to the admin's review queue
  • The system records which manager approved and when
  • A notification goes out to the admin
  • No attendance record is created at this point -- that only happens after the admin gives the final approval

Reject​

  • Denies the verification claim
  • A rejection reason is required (the manager has to explain why)
  • The manager's rejection is not the final word -- the submission moves to the admin's queue with the rejection reason attached
  • The admin then reviews the manager's rejection and makes the ultimate decision:
    • The admin can back the rejection and deny the submission for good
    • The admin can override the rejection and approve the submission anyway
  • The system records which manager rejected and when

Scope​

Managers can only review verifications for projects they are assigned to. They have no visibility into submissions for other projects.

Review Queue​

The manager's verification review page shows:

  • All submissions waiting for manager review across their assigned projects
  • Submissions are typically sorted by date and time
  • Managers can filter by project if they are handling more than one

Business Rules​

  1. Only project managers can perform first-level review
  2. The manager has to be assigned to the project in question
  3. Approval gets blocked if the worker already has attendance on a different project for the same date (cross-project check)
  4. The worker must be properly identified before approval can go through
  5. Rejection requires a reason -- no exceptions -- to maintain accountability
  6. Once the manager approves, they cannot take it back -- it moves on to the admin
  7. A manager rejection is not the end of the story -- the admin always has the final say