iRank for Boots

Rank the high street on work you already measure.

Three workplace seasons — pharmacy care, clinical training, beauty craft — on data Boots already files. No extra app. No world board for a Health MOT. Store versus store, inside one unlisted company group.

These pages are the programme. Parent-org admin, domain join, and warehouse import are not live yet. See what colleagues would open.

Health Cup · Destination class

Flu season store board

Health MOTs / hr
  • Manchester Piccadilly

    North West · destination

    2.41

  • Glasgow Fort

    Scotland · destination

    2.28

  • Bristol Cribbs

    South West · destination

    2.19

  • 4

    Birmingham Bullring

    Midlands · destination

    2.05

  • 5

    Cardiff St David’s

    Wales · destination

    1.94

Stores in one size class. Completed Health MOTs per pharmacist hour — not named clinicians.

Three programmes

Pharmacy, learning, beauty — each on its own board

  • Pharmacy teams

    High Street Health Cup

    September–January · flu season

    Rank stores and regions on Health MOTs, flu jabs, and Pharmacy First — the numbers already in NHS claims and the pharmacy stack. No new app on the shop floor. No named-pharmacist league.

    Company page
  • Pharmacy, healthcare, optometry, delivery

    Inspire League

    Each training wave

    Rank teams on the share of eligible colleagues who are current on the live module — Inspire, optometry higher quals, pharmacy-advisor pathways, delivery NVQs. Coverage, never speed.

    Company page
  • Beauty advisors and No7 consultants

    Beauty Hall Open

    Four-week sprints · launches and Christmas

    Skin analyses, makeovers, and Cosmetics Mastery already live on the beauty tablet and the till. Four-week sprints around a launch or Christmas. Flagship, destination, and high-street counters in separate classes.

    Company page

Why Boots

The warehouse is already there. The season is not.

iRank ranks anything you can measure. Gyms post a deadlift onto a world board. Boots does not. Workplace marks stay inside the company, on fields you already trust.

  • No extra capture.

    Pharmacy claims, L&D completions, and beauty-tablet consults already exist. Colleagues do not type a score. iRank is the board, not a new system of record.

  • A season, not a dashboard.

    Ops already has the warehouse. What it does not have is a consumer-grade board with a start, a finish, a class, and a shield — something a store can actually care about.

  • Built around the shop floor you have.

    Pharmacy, learning, and beauty are three workforces. Three programmes. One Boots company group. Store managers are not asked to become iRank admins of a global org.

  • Workplace scores stay at work.

    Unlike a gym, a Health MOT count is not a world board. Boots ranks stay inside the company. A colleague’s personal 5K can still live on iRank; it is a different membership.

Auth, admin, data — not built yet

How access would work

Today iRank company groups are a flat membership with an optional work-email domain. Boots needs a parent org, store fields, and a pipe — not 1,800 people creating their own company. This is the model we would ship; it is not in the product yet.

  1. 01

    Boots is a verified company, not a self-serve gym.

    iRank stands up one unlisted parent group for Boots UK. It does not appear in the public gyms directory. Org admins come from People, Pharmacy ops, Beauty, and L&D — not from whoever clicked “create company” first.

  2. 02

    Colleagues sign in with a Boots email.

    Clerk remains the account today. A matching work domain (boots.co.uk and agreed sister domains) joins the parent group. Later, Boots Entra ID can sit in front so nobody keeps a second password. The iRank profile is still theirs; Boots is a membership on it.

  3. 03

    A store is a child field, not a second company.

    After join, the colleague picks a store from a Boots-provided roster, or enters the store code on the staff-room noticeboard. Store managers are location admins: roster and local rewards copy. They do not see named people in another store, and they do not connect data pipes.

  4. 04

    Org admin owns seasons and the pipe.

    Org admins switch programmes on, set wave dates, size bands, and the reward lines Boots wants on the board. A nightly import from the warehouses you already run (claims, LMS, beauty tablet) writes store-level rows. Nobody submits a workplace score by hand.

  • Org admin

    People, Pharmacy, Beauty, L&D. Domains, SSO later, which programmes are live, season calendar, size bands, data connection, reward copy. Not every store manager.

  • Store / depot admin

    Confirm the rota belongs here. Cannot open another store’s named list. Cannot change how Pharmacy First is counted.

  • Colleague

    Follow the store board. Opt in to a named beauty row if they want. Never required to post a workplace score. Can still keep a personal iRank athlete profile for lifts and runs.

Before a contract

Questions we would answer first

Is this live for 1,800 stores today?
These pages are the programme and the access model. The parent-org tree, domain join, and warehouse import are not built yet. A region-sized Health Cup pilot is the first thing we would stand up.
Who is the data controller?
Boots remains controller of workforce and pharmacy-service data. iRank would process store-level aggregates under a DPA. Prefer counts and rates, not named clinical activity.
Can a pharmacist refuse to be on a board?
On the Health Cup they are not on a board. The store is. Inspire shows a percentage, not a named outstanding list. Beauty names are opt-in.

Start with one region, one flu season.

The Health Cup is the cleanest pilot: the claims already exist, the calendar is real, and nobody has to be named. Inspire and Beauty Hall can follow on the same parent group.

Questions? hello@irank.at · How access would work