Skip to main content
Chora has two sides: a hiring team on one side, and the scouts they invite on the other. Everything below exists to connect those two sides around a hire.

The two sides

Hiring team

The company doing the hiring. Posts roles, invites scouts, confirms hires, pays the scout fee. Works out of /hiring.

Scout

An individual with a network, referring candidates. Shares role links, tracks their pipeline, gets paid when a hire lands. Works out of /scouts.

Core objects

Programme. A hiring team’s setup on Chora: the company name, logo, scouts, roles, and payout config, all bundled. One company = one programme. Scouts join programmes; they don’t join Chora at large. Role. An open job the hiring team wants to fill. Scouts can only refer candidates to roles with status Active. Closed roles still appear in referral history but can’t accept new ones. Share link. A personal, trackable URL the scout copies from the Roles tab and sends to someone. Looks like app.trychora.com/go/<role-slug>?ref=<scout-token>. Every click, application, interview, and hire that comes through this link is attributed back to the scout who shared it. Referral. A candidate who’s touched a scout’s share link. Starts life as “Shared” and progresses through pipeline stages until it either lands as a Hire or ends as Rejected/Withdrawn. Invite link. Separate thing. This is what a hiring team sends to a scout so they can join the programme. Not to be confused with a share link.

Scout classes

When a scout signs up, Chora classifies them automatically: Classification happens once at sign-up but can be changed by the hiring admin.

Pipeline stages

A referral moves through these states, in order, as the hiring team progresses or rejects the candidate:
1

Shared

Scout has shared the link. No one’s clicked yet.
2

Clicked

A candidate has opened the link. No application yet.
3

Applied

The candidate submitted the role’s application form.
4

Interviewing

The hiring team is actively progressing them.
5

Offer out

The team has made an offer. Awaiting candidate’s decision.
6

Hired

Candidate accepted. Scout fee is quoted but not yet paid.
7

Confirmed

The hiring team has confirmed the hire. Chora charges the hirer’s card and queues the scout payout.
Two terminal states exist off the happy path:
  • Rejected. The hiring team isn’t moving forward with the candidate.
  • Withdrawn. The candidate pulled out themselves.
Neither triggers a payout.

Money terms

Scout fee. The flat GBP amount the scout receives when their referral is confirmed as a hire. Set programme-wide as a default, or overridden per role. Quoted upfront to the scout. Once a scout sees the fee on a role, that’s the number they get. Chora fee. Platform fee the hiring team pays on top of the scout fee. 20% on the Free plan, 15% on Pro. Charged alongside the scout fee the moment the hire is confirmed. Hirer total. Scout fee + Chora fee. The amount actually charged to the hiring team’s card. A £500 scout fee on Free plan = £600 total charge. Payout holding period. Optional buffer the hiring team can set between confirming a hire and releasing the scout fee. Useful as a safety net against cancelled offers or candidate no-shows. Defaults to 0 days (instant release). Payout states, as seen on /scouts/payouts:

Plans and capacity

Free

£0/month
Up to 10 active scouts
20% Chora fee on each payout

Pro

£99/month
Unlimited scouts
15% Chora fee on each payout
Upgrade or downgrade from /hiring/billing. Downgrade is blocked if you have more than 10 active scouts. Deactivate some first.

What’s next