Help
How to read this prototype
Plain language for a laptop or a shared screen. The welcome in the header is the short version. This page is the rest.
What this is
OpportunityIQ here is a prototype of a tool that could sit beside the real pilot. It is not the pilot, and it is not a place to put donor, Biomed, or staff data. Every name ends in @example.test. Every drive is generated.
The banner at the top of every page says the same thing: prototype, simulated data.
The question it answers
Is Humanitarian Services supporting blood drives during the appeal, and where should a leader push?
The Brief is built to answer that without a tour. The headline is the answer. “Where to push” names the regions and which side is missing. Six numbers sit under the headline, and no more.
The three-step loop
- An RDSE flags a drive in their ZIP footprint and says why, and what help is needed.
- The executive director of that chapter, or the regional executive, acknowledges the flag and logs what they did.
- The RDSE sees the acknowledgement and the action. Each step is on the audit trail with a time.
Alerts show up in the app within a few seconds. A 5:00 AM digest is previewed and is not sent.
Role switcher
Demo persona is in the header. Choose a person, then Switch. You become that person for this browser: what you see, and which buttons work, follow their role and assignment. It is not a login. Switching does not count as a sign-in, so the activity story on the Brief stays stable while you demo.
A private window can hold a second persona if you want to watch an alert arrive. Two tabs in the same window share the persona.
By role
RDSE
A recruitment district sales executive covers a set of ZIPs, or a whole region. They see drives in that footprint, flag one that needs chapter help, and later read what the chapter did. They cannot acknowledge their own flag. After the chapter acknowledges, they can add a comment. Priya Lantern is assigned a whole region. The others are assigned ZIP by ZIP.
Executive director
An ED is mapped to a region, and separately to a chapter. They see drives in their chapters, acknowledge flags, and log actions. They cannot flag a drive. Skye Harper has a Piedmont region and no chapter list, so drive alerts are not routed to her until Humanitarian Services supplies that list.
Regional executive
An RE covers a region. They see that region’s drives and can acknowledge or log an action for any chapter in it, including when the chapter ED has not. Sacramento’s seeded flag is acknowledged by the regional executive on purpose, so that path is visible.
District recruitment manager
A DRM belongs to one Biomed district and has an email on the person row. The pilot used to call this seat a collections manager. This prototype always says DRM.
DRM participation is a switch under the navigation, for an executive or the admin. Off is the MVP: the flag goes to the ED and the RE only, and a DRM cannot open drives. On, the DRM is notified and can see drives in the district. The switch does not change region activity. A DRM sign-in never counts as the Biomed side.
Districts are not the same as regions. District 1041, Prairie, includes Des Moines, Omaha, and Kansas City, so it crosses Heartland and Riverbend.
Executive
Morgan Hale sees the national brief, every drive, and the mock outbox. Executives do not flag, acknowledge, or log actions. They can star a drive and turn DRM participation on or off. They are not on the per-flag alert route. Their morning note is the roll-up, not a list of sponsors.
Admin
Sam Ledger can take any demo action, including flagging outside a footprint, and can erase demo actions from People. Reset clears the session log. The seeded appeal stays. The admin cookie is still only a demo switch.
Screens
Brief
National, division, or region. The headline changes with the scope. Decision metrics are the six tiles. Where to push lists partial and inactive regions, inactive first, and says which side is missing. The division chart and the region chart use the same numbers as the tables under them. Sort the region table by sessions. Flag counts are drives you are allowed to see. Activity status is for the whole region.
Drives
Grouped division, then region, then chapter. Search, division, region, chapter, status, fixed or mobile, flagged, sort, and favorites are one set of filters. Favorites is a checkbox with the others, not a separate control. A chapter with a flag still waiting opens on its own. Star saves the drive for the current persona.
A single drive
Date, site, ZIP, sponsor, fixed or mobile, goal, projected units, collected units, and fill. The fill uses collected units after the drive is over, and the projection before that. The page names the RDSE, the chapter ED, the regional executive, and the DRM, so a demo can switch to the right person. The red button is Flag this drive, and only when this persona is allowed to flag and the drive is not already flagged.
A flag
Reason, help needed, and the note. Acknowledge is the red button until someone has acknowledged. Log action becomes the red button after that. Another action, or an RDSE comment, stays a plain button. The audit trail is the history: flagged, routed, acknowledged, action, comment.
Alerts
Notices for the current persona. Unread rows have a red rail. Open flag marks that notice read. The header sound control starts off and is stored in this browser. New notices are polled every few seconds. Nothing is emailed from this screen.
Results
Read the sand box before the bars. Then supported versus unsupported fill, the tighter cut of flagged drives with and without an action, completed drives only, the time distributions, and the week-by-week table. Each chart is paired with the table of the same numbers.
Digest
The note a 5:00 AM CT job would build for the current persona, with links back to the flag or the brief. Executives and the admin can open anyone’s preview from the mock outbox. The outbox is a list, not a sent folder.
People
Your own assignment, in one paragraph. Executives and the admin also see the roster and the ZIP crosswalk, which is the shape a real list would use. The admin reset box is on this page.
Glossary
- RDSE
- Biomed account manager who flags drives that need chapter help. Covers ZIPs or a region.
- DRM
- District recruitment manager. One Biomed district and an email. Formerly called a collections manager in the pilot. Same seat.
- ED
- Executive director of a chapter. Mapped to a region, and to chapters when Humanitarian Services supplies that list.
- RE
- Regional executive. Covers a humanitarian region and can act for its chapters.
- Fill rate
- Units divided by the goal. Collected units once the drive is over. The projection until then.
- Appeal
- The simulated window, November 9 through December 6, 2026. The clock is frozen on the afternoon of December 3.
- Fixed
- A drive at a donor center.
- Mobile
- A drive at a sponsor’s site.
- Active
- Both an RDSE and an ED or RE signed in or acted in the last 7 days.
- Partial
- Only one of those sides did.
- Inactive
- Neither side did. A DRM session does not change this.
- Supported drive
- A drive whose flag has at least one logged action. A comment alone does not count.
How each metric is calculated
Cancelled drives are left out. Empty groups show a dash, not zero, so a quiet view is not reported as a failure.
| Metric | Formula |
|---|---|
| Flagged drives | Count of flags on appeal drives you can see. The hint is that count divided by appeal drives. |
| Acknowledged | Flags with an acknowledgement time, divided by flagged drives. |
| Median time to acknowledge | Median of (acknowledged time minus flagged time), in hours. Flags with no acknowledgement are left out of the median and counted on Results. |
| Logged an action | Flags with at least one response whose action is not “comment”, divided by flagged drives. |
| Appeal yield | Sum of units divided by sum of goals. Units are collected when the drive is over, otherwise projected. |
| Regions to push | Regions in the current view whose status is not active. |
On Results, average fill gives every drive the same weight. Unit yield weights by the goal. A 20-unit drive and an 80-unit drive are equal in the average and not in the yield.
Time bars use these buckets, lower bound included and upper bound excluded: under 4 hours, 4 to 12, 12 to 24, 1 to 2 days, 2 to 4 days, over 4 days. Time to action is from the flag to the first logged action, not from the acknowledgement.
Activity status rules
The window is 7 days, ending at the scenario clock, and the endpoints count.
- Biomed side: an RDSE who covers the region signed in, flagged a drive, or commented.
- Humanitarian side: an ED or RE who covers the region signed in, acknowledged, logged an action, or commented.
- Active means both sides. Partial means one. Inactive means neither.
- A DRM sign-in adds a session and does not satisfy the Biomed side.
- An action counts even without a separate sign-in. Sessions are sign-ins only.
- A sign-in counts once in every region that person covers.
- An ED with a region assignment and no chapter still counts for that region if they sign in.
The Brief does not list individual sign-ins. It says which side is missing.
Notifications and the daily digest
A new flag is routed from the drive’s ZIP. The chapter ED and the region’s RE are notified. The district’s DRM is notified only while DRM participation is on. The RDSE who flagged it is not notified of their own flag. An ED who is only on the region list, with no chapter row, is not notified.
Acknowledgement and a logged action notify the RDSE who created the flag. The page you have open polls for a new revision and refreshes. Sound plays only after you turn it on, and only when the unread count goes up.
The digest is the note for the next 5:00 AM Central Time. Chapter leaders see flags that still need them. An RDSE sees flags still waiting and updates since the previous morning. A DRM, when participation is on, sees open flags in the district. Executives get links to the Brief and Results, not every sponsor. Nothing is handed to a mail server.
Effectiveness caveats
The gap on Results is simulated. Read it as a discussion prop.
- Selection bias. In a real appeal, RDSEs flag drives that already look shaky. Help can be real and still lose to that starting point, or look stronger than it is.
- Sample size. Each row prints n. A handful of supported drives is not a finding.
- Fixed and mobile drives fill differently. The table splits them so a mix shift is visible.
- Projections are not collections. The “already held” cut uses collected units only.
- The median hides a long tail. The distribution is on the same page for that reason.
Data model and CSV import
Lists in data/lists/ are the stand-in for the pilot’s files: divisions, regions, chapters, districts, ZIPs, people, and the separate assignment files. Drives and history are generated from those lists with a fixed seed, so a restart looks the same until someone acts in the demo.
Column layouts, the email lock to @example.test, and what happens if a chapter sits outside an ED’s region are in the repository README. Executives can inspect the roster and the ZIP crosswalk on People. Replacing a CSV and restarting does not import real drives.
FAQ
Is any of this real Red Cross data?
No. Cities and ZIPs are plausible. People, sponsors, and results are fictional.
Why can a region look inactive when someone signed in?
If that someone is a DRM, the session counts and the status does not move. Status asks for an RDSE and an ED or RE.
Why is the date December 2026?
The scenario is near the end of a holiday appeal, so collected units and a trend both exist. The clock does not follow today’s wall date.
Can I load a real staff list to try the shape?
Not in this prototype. Any address outside @example.test is refused on purpose.
Who can change the DRM switch?
The executive and the admin. Everyone else can see whether it is on.
Does a star notify anyone?
No. Stars are a personal filter.
Before real data
This prototype is built as if the records were sensitive, and it is still not a place for them. The demo persona is a cookie, not single sign-on. Hosting here is not an approved Red Cross tenant. Mail is not sent.
Before any real list, drive, or comment: Red Cross sign-in through Entra ID, written approval from Biomed and Humanitarian Services, hosting in an approved tenant, mail only through the approved service, audit retention, a privacy review, and a penetration test. The checklist and the threat model are in SECURITY.md.