Attendance Parity and Cutover Validation

Summary

Parity and go/no-go tooling validates supported Time Office data and routing before ownership changes.

Audience

• Migration owners, QA, Gateway/Attendance owners, architects, and release approvers

Validation model

Compare legacy and Attendance-owned Shift, weekly-off and assignment representations using source-supported normalization. Validate compatibility responses, direct/shadow responses, intended gateway source, smoke coverage, backfill evidence, health and rollback readiness.

Go/no-go requires sanitized evidence for row/content parity, no unexplained discrepancies, healthy target behavior, stable dependent flows, approved routing plan, reconciliation ownership and rollback criteria. Existing scripts are strongest for Time Office extraction; complete daily Attendance parity coverage remains Requires confirmation.

Exact routing toggles are intentionally omitted. A route returning success is insufficient—confirm route ownership and representative response semantics.

Source References

• microservices/scripts/compare-attendance-shift-parity.ps1
• microservices/scripts/attendance-shift-cutover-go-no-go.ps1
• microservices/scripts/smoke-attendance.ps1
• microservices/docs/attendance-shift-cutover-runbook.md

Related Articles

• Attendance operations
• Attendance troubleshooting
• Attendance technical documentation

See Also

• Attendance database documentation
• Attendance events documentation

Keywords

• Attendance operations
• Support
• Reliability

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly