Xoxoday Loyalife formalises every engagement through a final Statement of Work (SOW) that explicitly confirms what Xoxoday will deliver, the acceptance criteria, and the boundaries of the implementation.
What the Statement of Work Covers
The SOW captures the full picture of the Xoxoday Loyalife deployment for your organisation. This includes the modules being activated (points engine, rewards catalogue, tiers, gamification, referral programs), the configuration depth for each module, and any bespoke workflows agreed upon during pre-sales discovery. Delivery timelines are broken into defined milestones. Each milestone carries a clear owner — either Xoxoday or the customer — so accountability is unambiguous from day one. If your organisation is integrating Loyalife with an HRMS such as Workday, SAP SuccessFactors, or Darwinbox, those integration touchpoints are explicitly listed in the SOW alongside the expected data flows and sync frequencies.Communication and Collaboration Channels
The SOW also specifies how the two teams will work together throughout the engagement. For organisations using Slack or Microsoft Teams, the preferred communication channels and escalation paths are documented so that blockers surface quickly and do not delay go-live. Training deliverables — admin walkthroughs, end-user enablement sessions, and recorded assets — are listed with their scheduled dates. Any third-party tools involved in the rollout are called out so there are no surprise dependencies mid-project.Security and Compliance Scope
For enterprise customers operating under regulatory frameworks, the SOW references Xoxoday Loyalife’s compliance posture, including ISO 27001 certification and SOC 2 Type II attestation. This gives procurement and InfoSec teams a clear view of the security obligations Xoxoday commits to honouring throughout the engagement — not just at launch.What Happens After the SOW is Signed
Once both parties sign the final SOW, Xoxoday Loyalife’s implementation team begins the onboarding sequence in the order defined in the document. Change requests that arise after signing go through a formal change-control process, ensuring scope creep does not affect timelines or budgets without explicit agreement on both sides. This structured approach means your HR operations, IT, and rewards-program teams always know what Xoxoday Loyalife has committed to — and what falls outside the current engagement. Learn more: Xoxoday Loyalife Help Centre — GeneralImplementation timeline and milestones
Understand the typical phases and milestone structure for a Loyalife deployment, from kickoff to go-live.
Integration capabilities
See which HRMS, communication, and SSO tools Xoxoday Loyalife connects with out of the box.