Agreement outlineDefine scope, evidence, acceptance, and support before HRM goes live.
This is a buyer-facing agreement outline, not legal advice. It gives the implementation team and buyer a concrete checklist for sign-off.
Acceptance terms
Every rollout should explicitly cover these points.
ScopeIncluded workflowsHiring, employee records, departments, shifts, attendance, leave, payroll readiness, payslips, documents, support, reports, audit.
DataBuyer-provided recordsBuyer confirms accuracy of imports, salary data, statutory inputs, documents, approvers, and employee communication.
PayrollStatutory boundaryPF, ESI, PT, TDS, LOP, overtime, night allowance, leave encashment, and filing exports require accountant/payroll-owner review.
UATRequired workflow proofDepartment, import, roster, attendance, leave, payroll, payslip, documents, audit export, backup, and restore drill.
SecurityControls before go-liveMFA, RBAC, tenant isolation, invite/reset flow, document rules, backup schedule, support owner, and incident contact.
SupportLaunch handoffSeverity levels, response windows, escalation contacts, maintenance cadence, change requests, and first adoption review.
Sign-offGo-live requires buyer owner and EyeLogs owner approval.
Anything not accepted in UAT becomes a tracked remediation item, not a hidden promise.
Request implementation agreement