Deel

Deel exposes a wide range of objects: contracts, timesheets, people, payments, ATS job postings, departments, and organizations. This integration focuses on two object types that carry the clearest attribution signal: contracts, which govern the entire lifecycle from offer to termination, and timesheets, which capture the approval relationship between a worker and the manager accountable for validating their work. ATS job postings were evaluated but excluded because the confirmed API schema does not expose a recruiter attribution field, making per-person KPI calculation unreliable. Five KPIs were retained, selected against three criteria: ability to attribute to an owner, resistance to gaming, and balance between leading and lagging indicators.

HR operational speed and pipeline health

Time to Contract Activation measures the average number of days from contract creation to a worker reaching active status. It captures the end-to-end operational speed of an HR manager's onboarding process: drafting, compliance checks, signature collection, and system activation. An increase in this indicator precedes a downstream problem — a worker who has not been activated cannot begin work, cannot be paid, and cannot be counted in headcount OKRs. For this reason, it functions as a leading indicator of onboarding friction before that friction becomes visible in workforce output.

Pending Signature Backlog counts the contracts currently sitting in pending signature status. It is a point-in-time snapshot of the pipeline blockage managed by a given HR owner. Where Time to Contract Activation is a historical average, Pending Signature Backlog is the live queue. The two indicators interact directly: a growing backlog that is not resolved within the expected cycle predicts a deteriorating Time to Contract Activation in the subsequent period. Reading them together enables an HR manager to distinguish between a structural slowdown and a temporary accumulation.

Both indicators carry the same attribution mechanism: the client field on the contract record maps to the HR manager responsible for the hiring on the company side. This is direct attribution — the API surfaces the email address without requiring a secondary lookup. One implementation caveat applies: in organizations where a single generic account is used for all contract management, this field resolves to an org-level email rather than an individual, and per-person attribution falls back to partial coverage.

Workforce dynamics: entries and exits

New Hires counts the contracts that reached active status within the measurement period. It is the clearest lagging confirmation of actual workforce growth: unlike headcount targets or offer counts, this indicator reflects signed and activated contracts — workers who have crossed the threshold from pipeline to productive. It grounds headcount OKRs in observable API data rather than in declarative targets.

Offboardings counts contracts terminated in the same period. Taken alone, neither indicator is sufficient: a high New Hires figure in a period of equivalent or higher Offboardings produces no net workforce growth. Reading the two together reveals the actual workforce dynamic — growth, stability, or contraction — and connects that dynamic to the HR manager responsible for the contracts involved. A period where Offboardings systematically outpaces New Hires is a signal that retention or strategic staffing decisions require examination, independent of what headcount plans show on paper.

Manager responsiveness: Timesheet Approval Delay

Timesheet Approval Delay measures the average number of days between a contractor's timesheet submission and the manager's approval. This indicator is attributed to the approving manager, not to the worker. Its operational significance extends beyond administrative tidiness: for contractors paid on approved timesheets, a delayed approval is a delayed payment. Payment latency is one of the most direct levers on contractor satisfaction and retention, particularly in an international workforce where alternative platforms are accessible.

Timesheet Approval Delay is also resistant to gaming: there is no obvious incentive for a manager to delay approvals artificially, and faster approval is unambiguously better for all parties. It stands as the only KPI in this integration attributable to managers rather than to HR owners, which makes it the single instrument for measuring the responsiveness of the operational layer above the workforce, not just the HR administrative layer.

Scope and limits of the integration

Deel records contract status transitions and timesheet lifecycle events, but does not measure the quality of the hiring decisions behind those transitions. A contract activated quickly may represent an excellent onboarding or a rushed one; a low Offboardings count in a period may reflect healthy retention or a reluctance to formalize departures. The API data tracks what happened in the system, not why it happened or whether it was the right decision.

Several metrics that would be analytically useful were excluded because they cannot be attributed to individuals. Turnover rate requires averaging across headcount, diluting individual contribution. Worker type mix — the distribution between EOR, contractor, and direct employee contracts — is a strategic health indicator but has no individual owner. ATS pipeline KPIs remain out of scope because the confirmed job postings API schema does not expose a recruiter field. The reliability of the five retained KPIs depends directly on the consistency with which contracts are managed in Deel: organizations that use a shared administrative account rather than individual HR owner accounts will find per-person attribution unavailable for the contract-based indicators.