Glossary, read 8 Nov 2026
42 terms a buyer meets, each with a sourced example
- Agents under controlThe Index's second criterion, weighted 20: do agents run whole processes such as onboarding, a compensation cycle and employee questions rather than answer questions; is there approval before anything goes live; an audit log of what the agent did; an off switch for AI features; and sensitive-field controls.
- AI off switchAn admin setting that turns AI features off, ideally in parts, so a company can run the HRIS without the chat, without AI-built views or without outside AI access while keeping the rest.
- API on every planWhether the product's programming interface is included on its lowest plan or reserved for a higher tier.
- Applicant tracking systemThe system that holds candidates and job openings before an offer is accepted, after which the person becomes a record in the HRIS.
- Approval before actionThe control under which an agent drafts a change and a named person applies it, so nothing reaches the record without a human decision.
- Audit logA record of who changed what and when, including what an agent changed, that an admin can filter and export.
- Breadth rowThe row of facts on every profile that reports module count, native payroll, ATS, IT and device management, integration count as the vendor states it, and country coverage.
- Build without the vendorThe Index's first criterion, weighted 25 of 100: can an HR admin create a report, dashboard, tool or workflow by describing it, on live data, with permissions respected, and share it; is there a library of built things; and does what is built stay current.
- Custom fieldA field the company adds to the person record beyond the vendor's defaults, such as a cost center, a visa expiry or a level.
- Data processing agreementThe contract under GDPR and the UK GDPR that sets how a vendor processes personal data on a customer's behalf, including sub-processors, security measures and what happens to the data when the contract ends.
- Data retention after terminationThe window after a contract ends during which a customer can export its records before the vendor deletes them, published in the DPA or the subscription terms.
- Employer of recordA service under which a provider employs a person in a country where the customer has no entity, runs the local payroll and compliance, and bills the customer per employee per month.
- Field-level permissionsFields such as salary, national ID or a custom field that are masked across the product and revealed only by a click from someone with the right permission, so a view, an export or an AI answer carries the mask rather than the value.
- Fit to the organization's shapeThe Index's sixth criterion, weighted 10: custom fields and entities, permission roles, policies that adapt per office and role, multi-entity, multi-currency and multi-language support.
- Guided implementationAn onboarding service the vendor runs with the customer, named on the pricing page as a plan feature or sold as a fee, as opposed to self-serve setup.
- HCMHuman capital management is the enterprise label for a suite that adds payroll, recruiting, talent, learning and planning to the person record, sold by quote with an implementation program.
- HRISA human resources information system is the system of record for people: each person's entity, manager, job, contract, location, policies, documents and the history of changes to them.
- HRMSHuman resource management system is the older name for the suite now sold as HCM, still searched 12,100 times a month in the US and still used in RFP templates whose questions are about payroll and compliance.
- Implementation feeA one-time charge for setting a company up on the system, published as an amount, described as dependent on company size, or left off the pricing page.
- ISO 27001The international standard for an information security management system, certified by an accredited auditor and renewed on a cycle.
- ISO 42001The international standard for an AI management system, covering how an organization governs the AI it builds and uses.
- Legal entityA company registration under which people are employed, such as a UK limited company and a US corporation inside the same group.
- MCP serverA server that exposes a product's data and actions to AI clients through the Model Context Protocol, so an assistant such as Claude or ChatGPT can read or change records with the asking user's permissions.
- Minimum subscriptionThe smallest contract a vendor will sign, expressed as a number of seats, an annual amount or a term, which sets the real floor of the price for a small company.
- Natural-language builderA feature that takes a description in plain words and produces a report, a dashboard, an automation or an app on the product's own data.
- Official connectorA connector the vendor itself publishes and supports for a named AI client, as opposed to a wrapper built by a third party or a community server.
- On requestThe pricing-page phrase, with its cousins 'talk to sales' and 'get pricing', that marks a number the vendor will give only in a sales conversation.
- Openness to the AI stackThe Index's third criterion, weighted 15: an official MCP server or connector and its access level, an API on every plan, webhooks, and documented connections to the AI tools a team already uses.
- Per-seat pricingA price charged for each person on the system each month, sometimes billed annually and sometimes with a monthly base fee on top.
- Permission roleA named set of rights that decides what a person can see and change, scoped by filters such as office, team or entity.
- Pricing transparencyThe Index's fifth criterion, weighted 10 here and up to 25 on a pricing-led view: whether the per-seat price, the plan contents, the add-on structure, the minimum and in-product billing are published.
- Read-only accessAn MCP or API access level under which an outside AI can read records but not change them, so every write still happens inside the product with its own approvals.
- Release ledgerA count of every dated entry on a vendor's public changelog or release-notes page for the trailing twelve months, per month, classified AI or not.
- Situation pageA page that re-scores the field for one buyer situation (a first HRIS, a second HRIS, a multi-entity company, an AI-native organization, a professional-services firm) on that situation's own weights, and names the top three under the result.
- SOC 2 Type IIAn audit report under the AICPA's trust services criteria that tests whether a vendor's security controls operated over a period, usually a year, rather than existed at a point in time.
- Time to valueThe Index's fourth criterion, weighted 10: the published implementation claim, guided implementation, the implementation fee, self-serve setup such as building the directory from a spreadsheet or with an agent, and a sandbox.
- TrustThe Index's seventh criterion, weighted 10: SOC 2 Type II, ISO 27001, GDPR, ISO 42001 held or in progress, an audit log, field-level controls, data backup and export.
- Vendor claimA statement a vendor makes about its own product on a marketing page, as distinct from a documentation page, a dated release note or a customer statement.
- Vibe ViewShapes's name for a dashboard, tool, report or workflow built from a plain-language description on live, permission-aware data.
- WebhookAn HTTP call the HRIS sends to another system when something changes, so a field update in the record can start work elsewhere without polling the API.
- Weighted totalThe Index score for a platform: each of the seven criterion scores multiplied by its weight, summed, divided by the sum of the weights and shown to one decimal.
- WorkflowA sequence of tasks, forms, signatures, emails, messages and webhooks that runs when a trigger fires: a new hire, a field change, a date, or a manual run.
Last reviewed 10 Nov 2026.