LocumTenens.com: From Booked to Day One, and Paid

01 · The Map

A Booking Is Only the Start

Before a clinician works a shift, LocumTenens.com has to verify their credentials, license them in the right state, get them privileged at the facility, and insure them. Booking takes about 72 hours. Credentials can take three months. A different team owns each step, and each one contacts the clinician.

I shadowed more than 30 people across 10+ specialties, researched the workflows and the platforms behind them, then talked to clinicians. The blueprint above is what came out of it: read across for time, down for who's involved.

02 · Where It Slows Down

01Clinicians hear from too many people.
02Everyone does data entry, in several tools.
03Verifying credentials takes days at some sources and weeks at others.

03 · What to Do About It

What the Blueprint Pointed To

Eight patterns stood out once every step was on one board, and most came back to the same thing: many hands, many tools, and nobody seeing the whole file. These are the opportunities that followed, grouped four ways.

Automation

AI for clinician support, self-service, and routine messages.Template emails from Salesforce in place of personal Outlook messages.Tell every new booking what’s required, and follow up automatically.

Clinician Workflow

One place for every document and conversation, so nobody asks twice.Pre-filled records that arrive complete and in one format.One real-time checklist every role sees from its own view.

Clinician Experience

One point of contact for the clinician.Show clinicians where they are in the process, from the same checklist.A digital welcome packet and a better Day 1.

Document Management

One document library in place of several SharePoint instances.Upload each document once.Create folders automatically for every new booking.

04 · Map to App

Each Pain Point Became a Screen

An assignment: schedule, rate, timesheets, expenses, travel, documents, contacts — Too many people → AssignmentOne place for the assignment: schedule, rate, timesheets, expenses, travel, documents, and the contacts.

Too many people → AssignmentOne place for the assignment: schedule, rate, timesheets, expenses, travel, documents, and the contacts.

Add Expense, filled in from a receipt — Data entry → Expense from a receiptA photo fills in the merchant, amount, and date. Every field the app filled is marked, so clinicians know what to check.

Data entry → Expense from a receiptA photo fills in the merchant, amount, and date. Every field the app filled is marked, so clinicians know what to check.

Home: today's assignments, each with its hours this week and one Add button — Falling behind → HomeToday's assignments come first, each with its hours this week and one Add button for time or an expense, filed to that hospital.

Falling behind → HomeToday's assignments come first, each with its hours this week and one Add button for time or an expense, filed to that hospital.

05 · The Design System

One System, Then Every Screen Onto It

There was no design system when I arrived — their first mobile app was being drawn a screen at a time. I built one in Figma for that app, then went back through the whole thing and moved the one-off styles onto it.

Artifact · the design system

One card, one row, one chip doing three jobs, one tile in four tints, one tab bar. Drawn from the shipped app, at its own values.

Job Details: the same card carrying a job — specialty, title, location, dates, attribute chips and the rate — The card, againCarrying a job instead of an assignment.

The card, againCarrying a job instead of an assignment.

New expense: a sheet offering four ways to capture a receipt, each as the same row — The row, againFour ways to start an expense, and the selected one.

The row, againFour ways to start an expense, and the selected one.

06 · The App

The Expense Tab, Working

Clinicians pay for flights, hotels, rides, and meals on assignment. Create an Expense starts from a receipt: scan it, pick a photo, or choose a file, and the app fills in the amount, date, and merchant. A returned expense says why it came back.

This is the React prototype engineering builds from. Tap Create an Expense, open an expense, or go to Home.

Open it full screen

Open jobs — Jobs lead with rate and dates

A flight and its confirmation — The flight and its confirmation

07 · How I Built It

Created the Figma design system for their first mobile app, then moved one-off styles onto it across the whole app.
Moved the team from Figma to Claude Design, then to Claude Code, as the organization's Claude Enterprise superuser. Output doubled.
Wrote the specs and rules, and directed the agents that built the React prototype from the real data model.
Ran usability testing with physicians.

08 · What Happened

Engineering builds the production app from my prototype. It's the reference for every screen and flow.