Hospitals, EMS, public health, emergency management, and long-term care, working from one roster, one library, one calendar, one work plan, and one record of decisions. coalition1 replaces the email blasts, shared drives, and spreadsheets a coalition runs on today.
Pricing is scoped per coalition. Email and you get a quote and a walkthrough, not a sales sequence.
Five sectors, dozens of organizations, one small staff holding it together. That is the job coalition1 is built for.
A regional healthcare coalition is a partnership of independent organizations with a grant-funded staff of one or two. Ask how the work actually gets done and the answer is a stack of consumer tools held together by the coordinator's inbox.
Meeting notices, documents, surveys, and deadlines all go out as email blasts. Members scroll past, staff resend, and nobody can tell who saw what. The record of what was communicated lives in one person's sent folder.
Base plans, annexes, hazard vulnerability analyses, bylaws, and meeting minutes sit across shared drives, inbox attachments, and personal folders. Finding out which version is current is a phone call.
Who belongs, which organization they represent, who holds a committee seat, and who is still active are maintained by hand. The list is wrong the week after it is cleaned up, and new member organizations wait for someone to find time.
Preparedness program deliverables and state reporting live in a staff spreadsheet. Members cannot see progress or where funding went, and the coordinator carries every deadline alone.
Steering committee approvals happen in email replies. When a funder, an auditor, or a new chair asks who approved what and when, someone rebuilds the answer from an inbox.
A website here, a drive there, a mailing list, a survey tool, a calendar. Staff turnover resets all of it. Across a state, no two coalitions work the same way, and no member who sits on two of them sees the same thing twice.
These are not people problems. They are the predictable result of running a regional partnership on tools built for individuals. The fix is unification: one platform that holds the members, the record, and the work together, so the coalition can act as one healthcare system instead of a mailing list.
coalition1 is built around the three things a coalition has to hold together. Each one is a first-class part of the portal, not a bolt-on.
One roster that is the truth, maintained by the people in it.
Everything the coalition produces, findable, versioned, and in one place.
The grant deliverables, the money, the decisions, and the follow-through.
Each coalition runs its own coalition1 instance with its own isolated database, its own domain, and its own branding. A state or region that standardizes on coalition1 gets coalitions that look and work the same, members who move between them without relearning anything, and staff turnover that no longer takes the system with it.
Every screen below is the portal as it ships today, shown on a demonstration coalition. Every organization, person, and document in the screens is fictional.
Categories for general discussion, planning, training and exercises, resource sharing, and opportunities. Members follow the threads they care about and get notified on replies. Staff can pin, close, and archive. The archive is searchable, so last year's answer is still findable.
Plans and procedures, governance, training and exercises, situational awareness, and templates, each with a version history. Meeting records keep the recording, notes, and materials for every meeting in one place. Every file can be previewed before it is downloaded.
Meetings, trainings, exercises, and conferences on one calendar the whole region can see, so a full-scale exercise does not land on the same day as a partner's academy class. Members register in the portal, get reminders, and can subscribe from their own calendar app.
Preparedness program deliverables tracked by capability, with status from not started through accepted, progress by capability, and deadline alerts. Steering committee members see the plan. Staff stop carrying it alone.
Post funding opportunities, take applications from member organizations, route them through steering committee review, and allocate against the opportunity. Members can see what was awarded and what remains.
Committee approval requests go to the people who hold the positions. Each signer signs with a signature on file and a PIN. The portal records who signed, who is still waiting, and when it closed, and generates the approval document. A decline pauses the request instead of losing it.
Upload an after-action report or start a review in the portal, track every corrective action by priority and owner, and watch the improvement items go from open to complete instead of into a binder.
Staff build forms in the portal: capability surveys, resource requests, exercise participation. Name, email, and organization fill themselves in from the member's account. Responses stay with the coalition, with analytics by question, and a funding request can start from a form.
Access requests, members, organizations, committee seats, and role permissions on one admin screen. Approve a new organization once and its people are auto-approved by email domain. Export the roster when the state asks for it.
Four roles, each seeing exactly what it should. An administrator can view the portal as any role to check what a member sees.
Anyone from a member organization
Position holders and advisory board
Coalition coordinator and program staff
Whoever owns the portal
Notifications reach members in the portal and by email, with each member choosing what they subscribe to. Every page works on a phone, because staff review from the field and members read on the move.
Member count, migration from what you have today, onboarding, and the support level you want all shape the number. Email with your coalition's name and a rough member count and you will get a quote and a walkthrough of a live demonstration instance.
or write to rory@dbcp.dev