Loading
A build tracking both attendance and project time — which raises a question most implementations leave open. Interloop settled the precedence rule at design time, before either system went live.
Client
Aspire
Location
Published
October 2026
Reading Time
7 min read
Implement Zoho People covering core HR, attendance, timesheet and performance management for an organisation moving from manual administration — with an explicit precedence rule governing the two overlapping time measures.
Aspire engaged Interloop to move from manual HR administration to a configured platform covering core HR, attendance, timesheet and performance management, delivered in a single phase. 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 covering the precedence rule and its owners.
Moving from manual administration to a configured platform is usually described as an efficiency project. It is more accurately a definitions project. Manual processes work because a person resolves each ambiguity as it arises — what counts as a half day, when regularisation is appropriate, which roles are treated differently. Those judgements are consistent and sensible, and they are rarely written down because nothing has required it. A configured system does require it, which means much of the implementation's real work is converting established judgement into stated rules. Including both attendance and timesheet added a second definitional question. The two measure different things and will sometimes disagree about the same week. Settling in advance what each is authoritative for — rather than discovering the question at month end — is what keeps both systems in use afterwards.
Established judgement without stated rules: Half-day thresholds, regularisation windows and role-specific shift treatment were applied consistently but had never needed writing down.
Two measures that will sometimes disagree: Attendance and timesheet answer different questions, and without an agreed precedence the disagreement surfaces at month end without a basis for resolution.
Rules needing an owner: A rule agreed in a workshop but owned by nobody tends not to hold the first time someone raises an objection to it.
Manual administrative load: Onboarding, leave, attendance and exit were each handled manually, absorbing HR capacity across the month.
Appraisal without a structure: Performance management ran without a KRA framework, with goals held informally.
Project cost timing: Cost data assembled periodically arrives after the decisions it would inform.
Interloop followed a structured, eight-step implementation in a single phase — discovery, precedence rule definition, an unusually substantial policy blueprint, configuration, data migration and go-live with hypercare. The blueprint was the project. A significant part of the engagement went to settling rules that had previously lived in judgement, run as decisions with named owners rather than as requirements gathering — because a rule agreed collectively and owned by nobody does not survive its first challenge.
Implementation Approach
This engagement clarified something Interloop now says at scoping to manual-to-digital clients: this is a definitions exercise carrying an efficiency label. Where two measures overlap, precedence is worth stating at design time and giving an owner.
A rule without an owner does not survive its first objection.
| Aspect | Before | After (Interloop) |
|---|---|---|
| Operating rules | Applied consistently by judgement, not written down | Stated, documented and assigned to named owners |
| Two time measures | No agreed relationship between them | Attendance authoritative for pay, timesheet for cost |
| Project cost | Assembled periodically | Captured as work happens, available in period |
| Appraisal | Run without a shared structure | Executed against a KRA framework with goals tagged |
| HR administration | Onboarding, leave, attendance and exit handled manually | Running in the platform |
| Handover | — | Documentation covering governance and rule ownership |
Applied consistently by judgement, not written down
Stated, documented and assigned to named owners
No agreed relationship between them
Attendance authoritative for pay, timesheet for cost
Assembled periodically
Captured as work happens, available in period
Run without a shared structure
Executed against a KRA framework with goals tagged
Onboarding, leave, attendance and exit handled manually
Running in the platform
—
Documentation covering governance and rule ownership
Before vs. After
Aspire runs attendance and timesheet together under a stated precedence rule, with project cost visible in period, appraisal executing against a defined framework, and the rules that previously lived in judgement now written down and owned. For Interloop, the engagement reinforced that moving an organisation off manual process is a governance exercise before it is a technology one — and that the blueprint, rather than the configuration, is where the value is created.
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.