People
Every app on Zubl already shares one people list and one organisation tree. This family adds the employment relationship: engagements with their terms and dates, positions and job architecture, right-to-work and classification evidence, jurisdiction-aware self-identification — and the compliance clocks that run on top of them.
Written for the people who carry this
The Chief People Officer
Employees are in the HRIS, contractors in procurement, agency staff in a spreadsheet from the agency. Nobody can list who is working for the organisation this week, or prove a contractor was classified correctly.
The General Counsel
Right-to-work checks and classification assessments are filed somewhere. When a regulator asks, retrieving them is a project.
The line manager
A position outlives the person in it, but the systems only know people. Handover, vacancies and acting arrangements are tracked by email.
One app, built to be extended
Workforce◦ early access
The workforce register: who works for you, on what terms, doing which job. It covers employees, contractors, agency and supplied workers, secondees and affiliates in one place, and holds the evidence — classification assessments, right-to-work checks, pay history — that employment law expects you to be able to produce.
Job families · job profiles · grades · engagements · work assignments; extends positions and people
◦ Early access: in the catalogue now and installed for design partners first; general availability follows as partners put it to work.
How it connects. Payroll stays where it is: this family records the inputs, not the pay run. Self-service — a person seeing their own engagement — is a platform access rule, not a separate portal.
One person. One engagement at a time. The evidence attached.
An engagement on Zubl is a person × an engaging entity, with a type — employee, contractor, agency worker, secondee — that determines which evidence the record must carry. Positions are first-class, so an obligation can be assigned to a role when it outlives the incumbent. Remuneration is effective-dated and Confidential by construction; diversity self-identification is governed by jurisdiction, so a scheme a country forbids simply does not exist there. Compliance clocks — probation ends, visa expiries, review cycles — are obligations that raise tasks.
Extend these apps, or build the one you need.
Every app here is open to extension on the same licence: a field, a lifecycle state, a link to a record in another family, a rule. Additions sit beside our definition and survive every upgrade.
And if the register your organisation needs is not here, describe it to the AI builder. It arrives governed — same access engine, same audit trail, same reports — because those belong to the platform, not to the app.
Every family is included on every plan
Governance, risk and compliance
Entities, delegations, risk, obligations, incidents, sensitive registers, insurance, audit and policy — on one model of the organisation.
Legal and contracts
The agreements in force and the obligations inside them — after signature, where the commitments have to be met.
Strategy and delivery
From a strategic plan to the objectives, projects, products, releases and sprints that deliver it — with measures, not slideware.
Operations
Assets, items, customers and suppliers, expenses and travel — the operational registers that feed finance and usually live in five systems.
Finance
The chart of accounts, dimensions, periods and journal that operational apps post into — foundations, stated honestly as foundations.
Community services
Volunteers and supporters, for not-for-profits: the people who give time and the people who give money, as relationships on the same people list — not two more lists.
We're working with design partners now.
A small number of organisations shaping the first release, in exchange for early access, direct influence over what ships next, and pricing that reflects the risk of going first.