Handling complexity with grace.
Enterprise contingent workforce programs don’t fit a 2008 template. Multi-tier rate structures, jurisdictional labor law, multi-dimensional cost allocation, parent-and-child org rules, project and SOW economics, industrial environments, global localization — WorkPerfect was built for programs that live where complexity is the norm.
Where complexity actually lives.
These are the seven areas that derail VMS programs at scale. Not because the rules are exotic, but because most platforms weren’t designed with them as first-class concerns.
Complex rate structures
Multi-tier bill and pay rates, shift differentials, overtime bands by jurisdiction, geographic premiums, statutory holiday math, blended rates across multi-assignment workers, and rate cards that change mid-engagement. Cost-plus, markup, fixed-fee, and milestone billing in the same program. WorkPerfect models all of this in a single rate engine so program operators can configure scenarios without writing scripts, and finance can audit how every dollar was calculated.
Labor-law compliance
Co-employment exposure, jurisdictional tenure caps, statutory rest periods, regulated industries (financial services, healthcare, defense), and the documentation that comes with each. Programs operating across US states, Canadian provinces, and EU member states need rules-as-data, not hard-coded policies. WorkPerfect lets you define a policy once, attach it to the populations it governs, and trust the platform to enforce it consistently across every requisition, assignment, and timecard.
Cost allocation
Multi-dimensional chart of accounts, split allocation across cost centers, intercompany flows for shared services, project-coded spend, and rollups that match the way your finance team reports. WorkPerfect treats the COA as a first-class object — not as flat strings glued to invoices — so allocations are validated upstream and extracts to your ERP arrive without manual cleanup.
Parent ↔ child org rules
Enterprise programs run divisional autonomy under corporate visibility. Business units inherit policies but override the ones that don’t fit. Reference data — vendors, rate cards, distribution rules, approval chains — is scoped to the right level of the hierarchy. WorkPerfect models the org tree explicitly, with per-business-unit roles, scoped reference data, and clean rollups to the corporate parent. No more bolted-on per-division workarounds.
Project & SOW economics
Milestone billing, burn-rate tracking, accruals, deliverable acceptance, mid-flight scope changes, and the financial visibility that lets project owners and finance see the same numbers. WorkPerfect models project and SOW engagements with their own lifecycle — distinct from hourly contingent — so milestones, deliverables, retainers, and not-to-exceed amounts are handled natively, not as exception flows on a timecard-shaped object.
Industrial environments
Kiosk timecards on the plant floor. Badge-in feeds from access-control systems. Supervisor batch approval for shift-based crews. Per-line rosters, day-of-week schedules, and reconciliation against the operational system of record. WorkPerfect is built to live in industrial and manufacturing environments — not just office-worker programs — and to take feeds from the systems that already track who’s on site.
Global programs
Multi-currency, multi-language (US English, UK English, and French Canadian today, with more on the roadmap), regional payroll calendars, country-specific holiday math, and reporting that slices spend by region without re-keying anything. The platform handles localization as a product property rather than a configurable add-on, so global programs ship with the same speed as a single-country one.
Three foundations. Every program built on them.
Configurable rule engine
A single engine drives approvals, distributions, validations, eligibility, and notifications. Rules are data, not code — editable by program operators, audit-logged, and version-controlled.
Semantic data model
Reports, dashboards, and APIs all read from the same defined metrics, dimensions, and joins. The numbers match because the source of truth is shared, not because someone reconciled three reports.
Composable workflow primitives
Workflows assemble from the same primitives — forms, conditions, approvals, integrations, notifications. New workflows ship in days, not the typical six-month services engagement.