Skip to main content

Attendance Operational Checklist

Summary​

Use these evidence-based checks in approved environments; adapt ownership and thresholds through operational governance.

Audience​

  • DevOps/SRE, release engineers, support, QA, migration owners, and reviewers

Reference Content​

Pre-deployment​

  • Approve artifact, configuration categories, migration plan, dependency readiness, rollback owner and evidence plan.
  • Confirm no development seed behavior in the target environment.

Post-deployment​

  • Check process health, migration/startup logs, tenant-scoped safe read, intended gateway route, Payroll dependency signal and outbox state.
  • Run approved representative smoke checks.

Regular and incident checks​

  • Review error/latency trends, restarts, migration failures, Payroll-call failures, outbox backlog and consumer lag evidence.
  • Classify incidents by identity/tenant, UI/API, database, messaging, Payroll or gateway boundary.

Payroll-period checks​

  • Confirm lock/freeze availability, reopen behavior, snapshot evidence and downstream consistency.

Backfill/cutover/rollback readiness​

  • Approve isolated source/target scope, dry run, idempotency, parity, smoke, reconciliation, cutover gate and rollback criteria.
  • Ensure writes during any routing window can be reconciled.

Documentation review​

  • Revalidate source paths, implementation status, known limitations, safe configuration categories and ownership quarterly.

Source References​

  • microservices/src/attendance-service/Program.cs
  • microservices/scripts/smoke-attendance.ps1
  • microservices/scripts/attendance-shift-cutover-go-no-go.ps1
  • microservices/src/attendance-service/Backfill/ShiftPolicyBackfillCli.cs

See Also​

Keywords​

  • Attendance operations
  • Support
  • Reliability

Revision Information​

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