Product

One workflow from need to coverage

A clinic posts a gap. LocuPedia matches clinicians, verifies credentials against source, routes both human approvals, and locks the schedule — every handoff, decision and approver on one record. Follow a real coverage request below.

The coverage journey

From posted need to closed post — five stages, no black box

The journey plays through the five stages once when it appears — pause it, or move through the stages yourself with the controls below. Names and dates are illustrative — the stages and records are the product. Notice what isn’t here: LocuPedia introduces the two sides, then steps out. Terms and payment are settled directly between the clinic and the clinician.

Stage 1 of 5 — Request: the clinic publishes exactly what it needs covered.

Plays once when it appears · use Back / Next stage, the stage tabs, or arrow keys to explore at your own pace

System action: request validated against clinic profile and published to clinicians who fit the specialty, registration and travel area.

ResponsibleDana Whitfield · Clinic Operations Manager
DecisionNeed written up and published — rate included
TimeThu 8 Jan, 09:12 EST
Next actionMatching engine ranks qualified clinicians

System action: 14 eligible clinicians compared against schedule, registration status, facility history and travel area · ranked Thu 8 Jan, 09:14 EST.

ResponsibleMatching system · reviewed by D. Whitfield
Decision3 matched clinicians notified, with the reasons
TimeThu 8 Jan, 09:14 EST
Next actionClinicians apply — applications land in Candidates

System action: applications delivered to the clinic’s Candidates view with verified passports attached. No booking is created — nothing is confirmed by LocuPedia.

ResponsibleDr. Maya Chen (applicant) · Dana Whitfield (reviewing)
DecisionTwo applications received — clinic reviewing
TimeThu 8 Jan, 11:02 & 14:51 EST
Next actionThe clinic replies directly — terms stay between them

Verification is our job; hiring is not. We check the licence, the identity and the references so the clinic doesn’t have to. Whether to hire — and on what terms — is the clinic’s decision, made directly with the clinician.

ResponsibleLocuPedia verification team
DecisionPassport verified — travels with every application
TimeChecked at onboarding · kept current
Next actionClinic and clinician agree terms directly

Where the metrics come from: fill rate, time to first application and repeat-posting are built from close-out reports like this one — always labelled self-reported, never presented as verified outcomes. Individual applications are purged after 12 months; the aggregates remain.

ResponsibleDana Whitfield (self-report)
DecisionOutcome: filled through LocuPedia
TimeSat 17 Jan, 14:20 EST
Next actionNothing — the engagement belongs to the clinic and Dr. Chen

Built to scale

Same workflow, any size of organization

A single clinic and a multi-department hospital run the identical five stages — what changes is who sits in each seat. Choose an organization size to see how the roles adapt.

Single clinic

One or two people run staffing alongside everything else — the workflow keeps it lightweight.

  1. Create the needPublished by the owner or office manager in minutes.
  2. MatchThe owner reviews matched clinicians and fit reasons directly.
  3. VerifyThe lead clinician checks credentials against the request’s requirements.
  4. Coordinate & confirmThe owner approves; the clinician accepts; the schedule locks.
  5. TrackCompletion and agreement status on record; trusted clinicians become the clinic’s preferred network.

Multi-location group

Several sites share one organization — local coordination, central oversight.

  1. Create the needA site coordinator publishes for their location, under group-wide templates.
  2. MatchThe site coordinator works matches; the group administrator sees every site’s pipeline.
  3. VerifyA shared credentialing reviewer verifies once — valid across every site in the group.
  4. Coordinate & confirmSite lead approval chains per location, with group-level visibility.
  5. TrackCoverage analytics across sites; one preferred network shared by the whole group.

Hospital / health system

Facilities, departments and teams of approvers — structure the platform carries, not works around.

  1. Create the needA department manager publishes against their unit, facility and specialty.
  2. MatchStaffing coordinators work matches across departments from a shared queue.
  3. VerifyCentral credentialing owns review responsibilities, with decisions recorded per placement.
  4. Coordinate & confirmStandardized approval chains per department — manager, credentialing, administration.
  5. TrackDepartment-level reporting, full audit history and exportable records for HR, operations and finance.

Get started

Run your next coverage request through it.

Publish a need, watch it move through the five stages, and keep the whole journey on record.

Organization posting free during launch, then CAD 300 per 7-day period — see pricing · Core clinician workflow free