Skip to content
CHRONOMANCER
Use case

Run your casual pool without the group-chat chaos

A hundred names in one thread doesn't scale. Give every casual their own link, and let the roster tell you who's actually dependable.

Roster lifecycleCurrent · Allocating
  1. Draft
  2. Requesting
  3. Allocating
  4. Scheduled
  5. Revise
  6. Live
  7. Completed

Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.

Seven states · one verb at a timeRevise loops back from Scheduled and Live
Notch gauge11 of 18
Lit · allocatedHalf · reserveGhost · still open
ChronometerStanding by

No request window is open on this page; the chronometer is shown without a time.

Countdown and absolute time,in the tenant's own timezone

Instruments drawn on an example night. This site carries no customer data.

Every casual gets their own link, not a spot in a group thread

A shared group chat breaks down the moment your pool grows past a dozen people — messages get buried, opt-outs get missed, and nobody can tell who actually saw the call for a night. Chronomancer sends each contact a unique, signed link by SMS and email. They open it, bid, done — no app install, no password, no group thread to scroll through.

  • One signed link per contact per period
  • No app install, no login for casuals
  • Opt-outs are respected automatically, per channel

Response tracking shows who never replies

Every link click, every bid, every non-response is on the record. Instead of wondering who's still active in your pool, you can see exactly who opens the link and never bids, who bids and never shows, and who's quietly reliable every time. That's the difference between a casual pool you're guessing about and one you're managing.

  • Response-rate reporting, by roster and by contact
  • Reliability score separates the dependable core from the rest
  • Recency-weighted, so a bad run doesn't haunt someone forever

From a full pool to a filled roster

STEP 01

Load your pool

Every casual is a contact with their own phone number, email, and opt-out preferences.

STEP 02

Publish the period

One publish sends a personal signed link to every contact — SMS, email, or both.

STEP 03

Track responses as they land

Watch who's opened the link, who's bid, and who's gone quiet, in real time.

STEP 04

Nudge the non-responders

Reminders target only the people who haven't replied — nobody gets pestered twice.

STEP 05

Allocate by priority and reliability

The dependable core rises to the top of a contested night; reserve absorbs the rest.

STEP 06

Let the score do the sorting next time

Attendance from this period feeds straight into everyone's reliability score for the next.

Zero logins
FOR EVERY CASUAL, EVERY PERIOD
2-way SMS
REPLIES FLOW BACK INTO THE SAME THREAD
Per-contact link
NO SHARED THREAD, NO CROSSED WIRES
The plumbing that keeps a large casual pool legible instead of chaotic.

Common questions

Do casuals need to install an app to bid for work?

No. They receive a signed link by SMS or email, open it in their phone's browser, and bid — no app, no account, no password.

How do we know who's actually reliable in a pool this size?

Reliability is scored automatically from attendance rate and hours fulfilment each time a period completes, weighted so recent periods count more than old ones — shown as a simple green/amber/red band.

What happens if someone opts out of SMS?

Opt-out is enforced before every send, per channel. A contact who replies STOP stops receiving SMS immediately, and that's respected on every future roster.

Can we see who never responds to invites?

Yes — response-rate reporting shows the full funnel per roster (invited, opened, bid) and flags non-responders by name, so you can follow up or let the pool self-select.

Bring order to your casual pool

Tell us the size of your pool and how you're running it today — we'll show you what it looks like under Chronomancer.