Skip to content

Corrections & reporting

Employees can request a correction to their own time record, giving a reason for the change. Administrators can also initiate a correction on an employee’s behalf; when they do, it’s recorded with a distinct audit entry showing it was administrator-initiated rather than employee-requested.

  • Corrections never carry attachments.
  • A correction can be requested late (after it would normally be expected), and is marked with a late flag alongside the stated reason.

An administrator approves or rejects a correction with a reason that’s visible to the employee. The original recorded evidence is always preserved — approving a correction appends the decision and the correction’s evidence rather than overwriting history.

If an administrator approves their own correction request, that self-approval is flagged in the audit trail and in reports, rather than being silently indistinguishable from any other approval.

An approved correction for a missing session is marked as manually reported — Vespi never invents device, location, or activity evidence to back-fill a gap.

If revoking a device strands an employee’s session open (neither the old nor a new phone can continue or close it), the employee proposes an end time for a correction:

  • The proposed time can’t be earlier than the session’s start or its latest recorded event.
  • The proposed time can’t be in the future.

Approving that correction closes the session atomically, appending exactly one correction-sourced clock-out event. Rejecting it leaves the session unresolved rather than forcing a close.

The in-app status of a correction is always authoritative. A decision also queues an email notification intent in a small retry-backed outbox; one worker delivers it and exposes delivery status. A failed or delayed email never reverses, blocks, or hides the underlying decision — email is a convenience notice, not the system of record. Only minimal, transactional email is sent.

Employees can export their own data; administrators can export their whole organization’s data. The portal also shows sessions, breaks, daily and weekly totals, and approved corrections directly.

CSV exports contain working-time data only — no location, no monitoring data, and no unresolved or pending time. Only closed, confirmed time and explicitly approved corrections appear.