Loading
Core HR, attendance, timesheet and performance management delivered in a single phase — with the contingency spent on adoption rather than on sequencing, and modules introduced by how often people would use them.
Client
Dlite
Location
Published
October 2026
Reading Time
8 min read
Implement Zoho People across core HR, attendance, timesheet and performance management in a single phase — directing the implementation's risk budget at adoption rather than at phase sequencing.
Dlite engaged Interloop to move from manual HR administration to a configured platform covering core HR, attendance, timesheet and performance management, delivered in one phase with a staggered introduction inside it. The engagement covered onboarding, employee database, leave, attendance with shift configuration, project and job-level timesheet, performance management on a KRA framework, exit and organisation setup — closing with hypercare, admin enablement and documentation.
Delivering four functional areas in one phase concentrates the change into a single period. The technical side of that is manageable. The adoption side needs designing. When an organisation has run manually, people build their own supporting systems — a personal spreadsheet, a messaging thread, the habit of asking one particular colleague. These work, which is why they exist, and they do not appear in any requirements document. They are nonetheless what a new platform is compared against on the first day it is used. The alternative shape — staging attendance, then timesheet, then performance across three phases — appears lower risk and carries a cost of its own at this scale. Each boundary asks the organisation to re-engage with a project it had set down, and attention is harder to recover each time. The judgement was that one well-supported phase would land better than three lightly supported ones, provided the introduction inside it was sequenced thoughtfully.
Informal systems as the real comparison: Personal spreadsheets, message threads and go-to colleagues do not appear in requirements and are what the platform is measured against in use.
Phase boundaries carrying their own cost: Staging across three phases asks the organisation to re-engage repeatedly, and attention is harder to recover at each boundary.
Four habit frequencies at once: Daily check-in, weekly timesheet and annual appraisal are different behaviours. Introduced together, they ask people to form three habits in one week.
Customisation as ongoing cost: Every customisation is something to explain at training and maintain afterwards, which carries weight at this scale.
Regularisation handled informally: Attendance exceptions were approved conversationally, which worked but left no basis for looking at patterns.
Performance management at risk of deferral: A module deferred to a later engagement at this scale is often one that does not get built.
Interloop followed a structured, eight-step implementation in a single phase — discovery including a catalogue of the informal systems in use, policy blueprint, configuration, data migration, and a staggered introduction inside the phase followed by hypercare. The judgement that shaped delivery was where to direct the risk budget: not into additional phases, but into adoption — holding configuration close to default, introducing modules by habit frequency, and addressing the existing workarounds explicitly rather than assuming they would fall away.
Implementation Approach
This engagement refined Interloop's approach to mid-sized manual-to-digital transitions, where one well-supported phase can outperform a staged rollout. The technique that makes it work is staggering by habit frequency inside the phase, so people still learn one rhythm at a time.
The platform is compared against the spreadsheet, not the old process.
| Aspect | Before | After (Interloop) |
|---|---|---|
| Delivery shape | Four areas staged across three phases | One phase, with introduction staggered inside it |
| Module introduction | All at once, or separated by project boundaries | Daily behaviours first, then weekly, then annual |
| Informal workarounds | Left to fall away on their own | Catalogued and addressed directly |
| Regularisation | Approved conversationally | Recorded in the platform, available for pattern review |
| Performance management | At risk of deferral to a later engagement | Delivered in this one, live in its first cycle |
| Configuration | — | Held close to default where standard behaviour was adequate |
Four areas staged across three phases
One phase, with introduction staggered inside it
All at once, or separated by project boundaries
Daily behaviours first, then weekly, then annual
Left to fall away on their own
Catalogued and addressed directly
Approved conversationally
Recorded in the platform, available for pattern review
At risk of deferral to a later engagement
Delivered in this one, live in its first cycle
—
Held close to default where standard behaviour was adequate
Before vs. After
Dlite moved from manual administration to four configured functional areas in a single phase, with regularisation on record, appraisal running on a defined framework in its first cycle, and the informal workarounds addressed rather than left to persist alongside the system. For Interloop, the engagement demonstrated that phasing decisions are adoption decisions — and that the effort saved by not staging is well spent finding the systems nobody mentions in a requirements workshop.
Continue Reading
A wealth-management firm replaced fragmented spreadsheets with a secure, compliance-ready Zoho CRM — centralizing client data and eliminating manual follow-up risk.
DKC Exports replaced fragmented, manual HR processes with a centralized, automated Zoho People platform — streamlining onboarding, offboarding, and internal communication.
Streamline HR processes with a secure, scalable system that centralizes data, automates tasks, ensures compliance, boosts efficiency, and enhances employee engagement.