After a shift swap, who needs to see what?

Preserve the original assignment as the baseline

Keep employee, shift type, date/range and status on the original Shift Assignment. A swap request should reference the original assignments rather than editing the roster first and trying to reconstruct history later.

Frappe HR separates Shift Request from Shift Assignment and creates the assignment after an approved/submitted request, illustrating why proposal and effective schedule should be distinct records or states.

References: [1][2]

Identify both sides of the proposed schedule change

For a swap, retain requester, original assignment A, proposed assignment B, target employee, date/time, reason and request expiry. For a one-way release or transfer, model that explicitly rather than pretending another reciprocal assignment always exists.

Until the receiving employee accepts, the proposal should not silently become the active roster. States can distinguish Offered, Accepted, Pending Approval, Approved, Rejected and Expired according to organisational need.

Check eligibility before asking an approver to decide

Validate basic conflicts such as overlapping assignments, required role/unit and organisation-specific rules before approval. These checks apply schedule policy and data constraints; they are not independent clinical or fatigue-safety determinations.

Frappe HR allows organisations to enable or disable multiple Shift Assignments for the same day, illustrating that overlap policy must be explicit rather than assumed universally valid or invalid.

References: [2]

Separate employee acceptance from organisational approval

The receiving employee’s acceptance means agreement to the proposal. Where policy requires manager or HR approval, the effective roster should change only after that authority approves, followed by notification to both employees and relevant roster owners.

Frappe HR Shift Request supports approvers at Employee or Department level and creates Shift Assignment after approved submission, a useful example of separating intent from organisational authority.

References: [1]

Attendance and payroll should reference the final assignment revision

After approval, create a superseding assignment or revision with effective date and reference back to the request. Attendance exceptions and downstream reports should be able to identify which assignment version was active for that date.

Linda lists VertexHR for attendance, leave and payroll workflows while requiring module, permission and handoff confirmation before onboarding. UAT should include accepted-but-not-approved, rejected swap, overlap, cancellation after approval and attendance after roster change.

References: [3]

Apply it to your business

A traceable shift swap is a schedule transaction with proposal, consent, policy checks, approval and downstream lineage—not merely a changed name on a calendar.