Attendance Box Setup Automation Wizard

A guided policy maker that explains payroll and attendance in normal language, then builds an automation plan.

Preview only v0.1-preview

Step 1

Company and Files

Start with what a support person asks on day one: company type, salary month, old salary sheet, attendance sheet, and employee master quality.

Used only in this plan preview.
This helps the wizard suggest shifts, weekly off, OT, and reports.

Step 2

Employee and Organisation Structure

The system needs clean groups before policies can run: payroll location, department, category, employment status, and shift assignment.

Maps to Payroll Location and Organisation Salary Configuration.

Step 3

Shift Designer

Shift is the heart of attendance. It decides which punch belongs to which day, when login/logout is valid, lunch behavior, half day, early logout, OT, and what Android terminal will accept.

Day Shift

Normal same-day duty. Employee logs in and logs out on the same calendar date.

Use when: office, shop, general staff, or simple factory shift like 09:00 to 18:00.

With Lunch

Same-day duty where lunch in/out punch is important and can affect work hours.

Use when: lunch break must be captured, extra lunch time should reduce payable hours, or canteen/lunch compliance matters.

Night / Midnight

Duty crosses date boundary. The system must decide whether a punch belongs to today or yesterday.

Use when: shift starts evening/night and ends next morning, for example 20:00 to 08:00.

Multi-day / Long Duty

Long-running duty where logout can happen much later and Android may continue an open shift.

Use when: drivers, security, medical duty, field duty, or any case where duty can continue beyond one normal shift.
Choose the closest real working pattern. This controls Android punch selection and later attendance policy.
Fixed is easiest. Roster is best when shift changes by date. Auto-nearest needs careful testing.
Each row becomes one Shift Master candidate. Shift type tells Android how to treat in/out, lunch, night, or long duty.
Example: if shift starts 09:00 and grace is 10, login up to 09:10 is not late.
Allows small early exit without early logout penalty.
If worked hours are below this, system can mark half day or deduction.
Used when full day is allowed but short working creates lost hours or short day.

Step 4

Attendance Rules

These rules turn raw punches into payable attendance values: present, absent, weekly off, holiday, OT, late mark, lost hours, and allowance days.

Step 5

Leave and Comp Off

Leave setup should answer what leave exists, how it is earned, what can be carried forward, and how comp off or encashment is handled.

Step 6

Salary Components and Pay Scale

Salary Config decides how attendance becomes money. The wizard will convert simple salary-sheet questions into component and payscale setup actions.

Step 7

Monthly Operations

Choose what the client will do every month. The wizard will prepare the operation checklist and remove unnecessary screens from the user journey.

Step 8

Reports and Final Audit

Select the outputs the client expects. These reports become the acceptance checklist after setup automation runs.

Step 9

Generated Setup Blueprint

This is the plan the automation engine would follow. In this prototype it is preview-only, but the mapping is prepared for real PHP save functions later.