BloodBridge: connecting urgent blood requests with nearby, eligible donors in minutes
A blood donation charity coordinated donors through WhatsApp groups and phone trees. Urgent requests went to hundreds of people, many ineligible or too far away, while the right donor never saw the message. We built BloodBridge: a donor registry with eligibility tracking, targeted matching by blood group and distance, verified hospital requests, camp management and donor recognition.

Four hundred messages for one donor
BloodBridge's volunteer coordinator showed us a WhatsApp group where an urgent request for a rare blood group had been forwarded dozens of times. Hundreds of people saw it; many had the wrong blood group, lived across the city or had donated recently. The request was eventually met — hours later — by a donor who had nearly missed the message among the noise.
“We don't lack donors. We lack a way to reach the right one quickly.”
Understanding donors and hospitals
We spoke to regular donors, hospital blood bank staff and volunteers. Donors were willing but annoyed by irrelevant messages. Hospitals worried about fake or duplicate requests. Volunteers spent hours making calls. Everyone wanted fewer, better-targeted requests and a clear confirmation when a need was met.
- Notify only compatible, eligible, nearby donors
- Only verified hospitals can raise urgent requests
- Close requests the moment they are met
- Respect donor rest periods automatically

Targeted, verified, closed
Verified hospitals raise requests through a portal. BloodBridge finds compatible donors who are eligible — based on their last donation date — and nearby, and notifies them in widening circles until enough have responded. Once the hospital confirms donations, the request closes and everyone else is told it has been met.
Donors see their donation history, next eligible date and the difference their donations made, which keeps them coming back.
The team
A small team working with volunteer coordinators every week.
Coordinator and hospital workshops.
Donor app and hospital portal.
Donor app and notifications.
Matching, hospital portal and coordinator console.
5 people in total, working as one team.
Decisions we made
Agreed with the charity's trustees and coordinators.
Broadcast or targeted requests?
- Broadcast to all donors
- Target compatible, eligible, nearby donors
Our call: Target compatible, eligible, nearby donors. Targeting reached the right donors faster and reduced fatigue.
Who can raise requests?
- Anyone
- Verified hospitals and coordinators
Our call: Verified hospitals and coordinators. Verification stopped fake and duplicate requests.
How to expand search?
- Fixed radius
- Widening circles until enough donors respond
Our call: Widening circles until enough donors respond. Nearby donors were asked first; the search widened only if needed.
Every feature, module by module
Everything that shipped for donors, hospitals and coordinators.
- 01Donor registration
Blood group, location and consent.
- 02Eligibility tracking
Next eligible date from last donation.
- 03Targeted requests
Only compatible, nearby, eligible donors.
- 04One-tap response
Respond and get hospital directions.
- 05Donation history
Past donations and impact.
- 06Camp registration
Sign up for donation camps.
- 07Hospital verification
Hospitals verified before access.
- 08Request portal
Blood group, units and urgency.
- 09Donor arrival tracking
Responding donors and ETAs.
- 10Fulfilment confirmation
Close requests when met.
- 11Request dashboard
All active requests and responses.
- 12Widening search
Automatic expansion of search radius.
- 13Camp management
Plan camps and track donors.
- 14Donor communications
Thank-you and reminder messages.
- 15Multi-channel notifications
App, SMS and WhatsApp.
- 16Donor privacy
Contact details shared only on response.
- 17Impact reports
Requests met and response times.
- 18Role-based access
Donors, hospitals and coordinators.
- 19Audit trail
Requests and responses recorded.

Launch
We imported the charity's existing donor lists with consent, invited donors to the app and onboarded hospitals one by one after verification. WhatsApp groups were gradually retired as requests moved to BloodBridge.
- Weeks 1–2Discovery
Donor, hospital and volunteer interviews.
- Weeks 3–4Design
Targeted request flow prototyped.
- Weeks 5–11Build
Apps, matching, portal and console.
- Weeks 12–13Donor migration
Existing donors invited with consent.
- Week 14Launch
Hospitals onboarded and live.
What we learned
Relevance is respect. Donors stayed engaged because they were only asked when they could help.
Close the loop. Telling donors a need was met reduced repeated calls and built trust.
- React Native
- Next.js
- NestJS
- PostgreSQL with PostGIS
- Push, SMS and WhatsApp notifications
- AWS Mumbai

