Put people records and floor work in context.

An employee record is more than a login

Keep the employment record, site assignment and system permissions distinct. A floor worker may need assigned tasks and their own attendance; a supervisor needs a team view and authorised review actions. When someone changes role, site or employment status, review access as part of that change rather than leave an old account active.

Review attendance in its working context

A missing clock-out, overnight shift or approved correction can change how a day's record should be interpreted. Check the shift and recorded events before approving an exception. Veristow includes employee profiles and attendance review; site QR and location-dependent flows need the relevant site configuration and device permissions.

Assign work the team can complete

A useful assignment identifies the workflow, warehouse and next action. Review availability and operational constraints before changing assignments. A worker's task count alone does not describe difficulty, travel distance or quality. Use productivity records to investigate workload with the supervisor, rather than treat a raw count as a universal performance score.

• Pilot an assigned pick, a reassignment and an exception requiring review.
• Check an employee's own record separately from the manager's view.
• Verify that a person assigned to one warehouse cannot access another site's private work.

Keep payment recording separate from payment execution

The initial operating model supports manually managed payment processes, including online or cash settlement records where configured. It does not imply automatic bank transfers, a connected payroll provider or installed biometric terminals. Bring employment categories, attendance rules, approvals and payment records to onboarding so the agreed setup reflects your actual operation.