# How a cell is read, a row counted and a platform ranked

Method, read 8 Nov 2026

**The short answer.** A cell is yes when the vendor's own page or release note documents the capability, partial when it documents a narrower form, and none found when nothing was found on the pages listed, with the read date. The map count is published as a fact; the ranking uses the shared seven-criterion rubric with workflow weights, listed below.

The map is the asset and the count is honest: 20 columns, 14 rows, 280 cells, each with the quote or the release note and its date. Release notes count as evidence with their own date, which is why the Shapes row cites fourteen notes from October and November 2026 rather than one product page. Provisioning in other systems, devices and apps, is a column reported as a fact and carries no weight; the Rippling page says plainly that this is what Rippling does and Shapes does not.

The ranking on this site is the shared rubric with the workflow weights: build without the vendor 30 (flows from a prompt, a builder an admin can use), agents under control 20 (an agent that runs the flow with approval), fit to shape 15 (policies per office and role, conditional tasks), openness 15 (webhooks, API, triggers to other systems), time to value 10 (templates, self-serve), trust 5 (audit of who did what), pricing transparency 5. Breadth is never an axis; the modules and the countries are printed as facts on every platform page.

The two orders are published side by side. On this edition they agree at the top: Shapes is first on the map count at 18 and first on the rubric at 8.6; Rippling is second on the map count and Humaans is second on the rubric at 6.9, ahead of Rippling on the name tie-break. They disagree lower down, where Workday's 15 documented capabilities sit beside a rubric score of 6.0 because a non-engineer cannot build the next business process from a sentence.

## The seven criteria and the weights this site uses

| Criterion | What is scored | Weight here | Default |
| --- | --- | --- | --- |
| Build without the vendor | 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; does what is built stay current. | 30 | 25 |
| Agents that act, under control | Do agents run whole processes rather than answer questions; approval before anything goes live; an audit log of what the agent did; an off switch; sensitive-field controls. | 20 | 20 |
| Openness to the AI stack | An official MCP server or connector and its access level; API on every plan; webhooks; documented integrations with the AI tools a team already uses. | 15 | 15 |
| Time to value | Published implementation claim, guided implementation, implementation fee, self-serve setup, sandbox. | 10 | 10 |
| Pricing transparency | Published per-seat price, plan contents, add-on structure, minimum, in-product billing. | 5 | 10 |
| Fit to the organisation's shape | Custom fields and entities, permission roles, policies that adapt per office and role, multi-entity, multi-currency, multi-language. | 15 | 10 |
| Trust | SOC 2 Type II, ISO 27001, GDPR, ISO 42001 held or in progress, audit log, sensitive fields, data backup and export. | 5 | 10 |

Weights sum to 100. The same weights produce every ranked view on this site; the build fails if they drift.

The weights were committed before any platform was scored and have not changed since; the file is published as committed: [weights.json](/method/weights.json). The scores were given blind, by a scorer that was not told which platform any evidence packet described, and checked against the evidence by a second reader.

## Scoring rules

- Each criterion is scored 0 to 10 from the evidence. A vendor claim scores at most 7 until a second source confirms it. 'None found' scores 0 and is written as 'none found on <date>'.
- Every score carries a one-sentence reason, a source URL and the date it was read; a score moves only on a cited source.
- Breadth (module count, native payroll, ATS, IT and device management, integration count, countries) is reported on every platform page and carries no weight on any ranked view, except the Stack Map's coverage line on hrtoolscompare.com.
- Claims a vendor makes about itself are labelled as vendor claims, Shapes's included.
- A capability is read from the vendor's pages, not from a demo. Where a sales deck shows a feature the public pages do not, the cell is none found on the date, and the vendor can send the page.
- Partial is a real value, not a polite no. HiBob's role-based checklists are partial on conditional tasks because the page names roles and not conditions; Workday's sequential steps are partial on signing in order because the order is a property of the process, not of the signature step.
- Every template names the capabilities it needs and the build fails if a named capability is not a map column.
- British spelling throughout; the writing gate enforces it.

## Situation weights

Each situation page scores the same evidence on that situation's own weights, below. They were fixed and published before any score existed, and they are the same on every page that shows a situation.

| Situation | Build | Agents | Openness | Time to value | Pricing | Fit | Trust |
| --- | --- | --- | --- | --- | --- | --- | --- |
| First HRIS, 50 to 150 people, replacing spreadsheets | 20 | 10 | 10 | 20 | 20 | 10 | 10 |
| Second HRIS, 150 to 1,000 people, replacing a first system that stopped fitting | 25 | 20 | 15 | 10 | 5 | 15 | 10 |
| Multi-entity and multi-country, UK, EU, Israel and US offices, several payrolls | 15 | 10 | 15 | 10 | 10 | 25 | 15 |
| AI-native organisation where requirements change weekly and the People team builds its own tools | 30 | 25 | 20 | 5 | 5 | 5 | 10 |
| Professional services and non-tech scaleups with a lean People team | 20 | 15 | 10 | 20 | 15 | 10 | 10 |

## The ranking these weights produce

| Rank | Platform | Build (30) | Agents (20) | Openness (15) | Time to value (10) | Pricing (5) | Fit (15) | Trust (5) | Total |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | [Shapes](/platforms/shapes/) | 9 | 9 | 8 | 8 | 8 | 8 | 9 | 8.6 |
| 2 | [Humaans](/platforms/humaans/) | 7 | 7 | 9 | 5 | 2 | 7 | 7 | 6.9 |
| 3 | [Rippling](/platforms/rippling/) | 8 | 7 | 7 | 3 | 4 | 8 | 7 | 6.9 |
| 4 | [Factorial](/platforms/factorial/) | 6 | 6 | 8 | 4 | 5 | 8 | 6 | 6.4 |
| 5 | [Workday](/platforms/workday/) | 5 | 7 | 6 | 6 | 2 | 7 | 8 | 6.0 |
| 6 | [HiBob](/platforms/hibob/) | 5 | 5 | 8 | 5 | 3 | 8 | 7 | 5.9 |
| 7 | [Personio](/platforms/personio/) | 6 | 4 | 6 | 6 | 3 | 8 | 6 | 5.8 |
| 8 | [Lattice](/platforms/lattice/) | 4 | 5 | 7 | 7 | 7 | 6 | 6 | 5.5 |
| 9 | [BambooHR](/platforms/bamboohr/) | 4 | 6 | 7 | 5 | 8 | 5 | 5 | 5.4 |
| 10 | [Deel](/platforms/deel/) | 3 | 5 | 8 | 6 | 6 | 6 | 6 | 5.2 |
| 11 | [Gusto](/platforms/gusto/) | 1 | 4 | 6 | 7 | 9 | 3 | 3 | 3.8 |
| 12 | [Paylocity](/platforms/paylocity/) | 3 | 4 | 3 | 2 | 2 | 5 | 5 | 3.5 |
| 13 | [ADP](/platforms/adp/) | 3 | 2 | 3 | 3 | 2 | 4 | 4 | 3.0 |
| 14 | [Sage](/platforms/sage/) | 1 | 1 | 2 | 4 | 7 | 2 | 4 | 2.1 |

Weights in the header row sum to 100; scores 0 to 10 from the evidence read 8 Nov 2026; weighted total to one decimal.

**Where Shapes is weak.** Device and app provisioning on day one is not a Shapes workflow step; Rippling and IT tools own that.

## Read dates and refresh

Every vendor page used for this edition was read on 8 Nov 2026. Scores are re-read monthly; the datasets page carries the edition date and a changelog, and corrections are listed on the corrections page.

## Sources

- Shapes pricing (the reference for the pricing criterion): https://shapes.co/pricing (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/method/
