1
Catch the 80-hour week before you approve it.
Pagerflow flags an ACGME breach the moment a swap is approved, for the trainees those limits cover, straight from the workbook your chief keeps.
0
hours logged by hand
Duty hours are computed from the schedule itself, so nobody types in their week and nobody can forget.
80h
checked before you approve
Before a chief signs off on a trade, Pagerflow flags it if the trade would push a resident or fellow past an ACGME limit.
1
week from workbook to live
We read the workbook you keep, learn your shorthand, and go live for the whole program in a normal week.
Your whole program, on one live schedule.
Residents, fellows, and attendings read the same schedule, across every rotation and service, with ACGME duty-hour limits watched for the trainees they apply to. Pick a piece to see it.
The chief builds the month once. Residents, fellows, and attendings all read the same live schedule, and it updates the moment a swap is approved.
Worst-first. See who is over an ACGME limit and who is close, for the trainees those limits apply to, before the schedule is worked.
Settle the "you gave me more weekends" argument with the record. Filter by year or service and put two people side by side.
Approve a trade only after Pagerflow checks it against the 80-hour limit. The warning shows at the moment of approval, not three weeks later.
Every schedule syncs to the iPhone or Android calendar. Your next call shows up beside the rest of your week, with no app to open and no login.
Before you approve, not after
The hours come from the calendar, not from memory.
Every program has felt it: a swap gets approved on a Tuesday, and three weeks later the hours do not add up. If a trade would push a resident or fellow past an ACGME limit, the chief sees the warning at the moment of approval, while there is still time to decline. The picture is read from the schedule itself, not from what a tired trainee remembered to enter. It is an advisory estimate from scheduled time.
The doctor app
The one app your doctors actually open.
Sign in with a PIN, no account to create, and it opens instantly, works offline, and never shows an ad. It holds their own schedule, who is on call, and the backup roster.
Cross-schedule access
Everyone sees what they need, nothing they don't.
You decide who sees which schedule. Give attendings a window into the resident call schedule, let residents see who is supervising them, and keep everything else private.
Onboarding
You keep the workbook. We do the rest.
Pagerflow reads the Excel file your chief builds and knows that "JR" means Reyes. You keep working the way you do; the live schedule, the phone app, and the duty-hour math come for free.
Sized for a program, not a hospital.
Built for residency, fellowship, and department scheduling, without the enterprise weight you have to grow into. Everything below is live today, not coming soon.
Stop rebuilding the schedule every July.
Your rules, your shorthand for who's who, and the full history of changes carry across the chief handoff, so a new chief starts where the last one left off.
Know what changed without reading two spreadsheets side by side.
Every time you upload a new version, Pagerflow shows exactly what moved, who got added, and who came off.
End the "you gave me more weekends" argument.
Filter by training year and put two people next to each other on a fairness tally, so load questions get settled with the record, not a hallway debate.
Never end up with half a swap.
An approved swap moves both doctors' shifts together or neither, so you never end up with a trade where one name changed and the other didn't.
An answer for "who's covering if someone drops."
The backup and jeopardy roster is right there on the schedule, so you know who is covering the moment someone drops, not a phone tree taped to the workroom wall.
A clean paper trail when someone asks.
Download a Word record of every schedule change over any date range, so the coordinator hands it over in one click.
Multiple rotations and services, one program view.
Wards, clinic, ICU, night float, and every service each keep their own shift shorthand and their own people, under one program view.
Nobody works a shift they didn't know moved.
When a published schedule changes, the doctors it affects get an email, so an approved swap never turns into a no-show at 6am.
Made for the chief, the coordinator, and the PD.
The chief who inherits the schedule every July. The coordinator who fields every swap and every "am I really working that weekend." The program director who has to stand behind the hours. Pagerflow gives all three one honest source of truth, and gives residents, fellows, and attendings an app they will actually open.
We show our work
An estimate, and we say so.
Pagerflow's duty-hour view is an estimate built from scheduled time. It does not see clinic, holdover, at-home call, or moonlighting, so real hours usually run higher, and we say so on the screen. What we give you is a clear, checkable read of the schedule you set, early enough to act on it.
No ads, ever
Your program's data stays private
Physician-built
Live from the workbook you keep
Bring the workbook you already have.
Send us the Excel file your chief builds and we will show you your program live in Pagerflow, hours flagged and all. You send one file. We do the rest.