Residents confirm their own hours. You only look at the ones who haven’t.
Attest™ asks each resident to confirm a recorded shift in the app, then locks it. Coordinators get one page showing who has confirmed, who has not, and who is disputing a shift — instead of a spreadsheet and a reminder email.
Premium feature · per program · off until it is turned on for your program
What a resident sees: hours already recorded, waiting on a word from them.
A recorded hour nobody has confirmed is still an open question.
Hours record themselves in ResQ — that is the point. But a passively recorded shift carries no statement from the person who worked it. Programs fill that gap with paper, email threads, or a coordinator reading times back to a resident in the hallway. Attest closes it inside the app the resident already has.
What a coordinator does today
- Exports hours to a spreadsheet
- Emails residents asking them to check it
- Re-sends to the ones who did not reply
- Keeps the replies somewhere, in case anyone asks
What Attest does instead
- The resident sees the shift in the app and confirms it
- The confirmed shift locks, with the date it was confirmed
- One page shows confirmed, outstanding and disputed
- The record is kept with the shift, not in an inbox
One shift, one screen, one decision.
A shift becomes confirmable once it has closed and settled. The app shows exactly what is being confirmed — date, start, end, total, and the location — and says so in plain language when the engine merged periods together, so nobody is asked to confirm a number they cannot see the basis for.
See the shift
Date, start, end, total and location. Where periods were merged, the app says how many and how much time was counted.
Confirm, in two steps
Confirming is deliberate and cannot be undone. The app says so before the resident commits.
Or say something is wrong
If the resident can fix it, they go straight to the existing edit screen and the corrected shift comes back ready to confirm. If they cannot — wrong WorkZone™, hours missing entirely — they leave a note and it is raised to the program.
It locks
A confirmed shift shows as locked, with the date, and no edit affordance.
Confirming is deliberate. The app says so before anything locks.
The residents who need chasing are at the top.
One row per resident: how many shifts are outstanding, how many are confirmed, the oldest one still waiting, and whether anything is disputed. Sorted so the people who need a nudge come first — because that is the only reason anyone opens this page. A program-level completion figure sits above the roster.
Internal Medicine · last 30 days · residents needing attention first
| Resident | Confirmed | Outstanding | Disputed | Oldest outstanding |
|---|---|---|---|---|
| Singh, Elena | 4 | 13 | 0 | Oct 13 |
| Muller, Ibrahim | 10 | 11 | 0 | Oct 14 |
| Lopez, Simone | 10 | 11 | 0 | Oct 19 |
| Martinez, Sean | 12 | 5 | 1 | Oct 27 |
| Wong, Farah | 14 | 4 | 0 | Oct 27 |
One row per resident, sorted so the people who need a nudge come first.
Last 30 days
| Shift | WorkZoneâ„¢ | State | Detail |
|---|---|---|---|
| Nov 2, 7:32 PM – 7:38 AM | Riverbend UMC | Confirmed | Confirmed Nov 3, 9:14 AM |
| Nov 3, 7:00 AM – 7:12 PM | Riverbend Ambulatory | Outstanding | — |
| Nov 3, 6:00 PM – 11:10 PM | Riverbend UMC | Disputed | Hours look short — I left at 11:40. Raised Nov 4 |
| Nov 4, 7:00 AM – open | Riverbend UMC | In progress | — |
| Nov 4, 1:00 PM – 5:12 PM | Riverbend Children’s Hospital | Not yet eligible | Still inside the WorkZone™ merge window |
Open a resident and every shift says where it stands, and why.
DashboardUsersProgramsReportsAttestationShift Attestation
Attestation is configured per program: enable, start date and weekly reminder.
A resident who disagrees is not a resident who forgot.
A disputed shift is a resident telling the program the record is wrong. It appears on the coordinator’s page as needing attention and comes out of the outstanding count while it is open — so the reminders stop while the question is open.
A confirmed shift stops moving.
Nothing quietly rewrites it
Resident edits, portal edits and administrator edits are all refused on a confirmed shift. Automated processes skip it rather than failing on it.
Unlocking leaves a mark
A confirmed shift can be unlocked, but only by ResQ, only with a written reason, and the unlock is recorded. The original confirmation is never deleted.
Every confirmation is stored with a timestamp against the shift it belongs to.
Part of the ResQ family.
See Attestâ„¢ on your own program.
We will walk through what your residents would see, what your coordinators would chase, and what the record looks like afterwards.