Coalition FAQ

Miami-Dade and South Florida healthcare providers and partner organizations may participate when they support coordinated emergency prevention, mitigation, preparedness, response, and recovery activities.

Use the membership contact path so coalition staff can learn about your organization, confirm the right points of contact, and explain current meeting and onboarding options.

Participation can vary by role, sector, and preparedness priorities. The coalition encourages steady engagement through meetings, training, exercises, planning work, and response coordination when needed.

Partners can request planning support, readiness consultation, training and exercise design, meeting support, resource coordination questions, and after-action improvement planning.

Use the Training & Exercises page or the booking form to share the audience, topic, desired dates, support needed, and any facility or sector context.

Yes. The coalition can support after-action discussion, improvement planning, corrective action tracking, and partner follow-up based on the scope of the activity.

The Calendar & Bookings area shows upcoming coalition activities and supports requests for planning, onboarding, or support meetings.

The symposium has its own public section for registration, agenda, speakers, sponsors, hotel and travel information, materials, and attendee portal support.

Sponsors and vendors should use the symposium sponsor pages for event-specific opportunities or contact the coalition for broader preparedness partnership questions.

No. Public pages provide general preparedness information and contact paths. Staff-only materials, sensitive files, operational details, and private downloads use authenticated workflows.

Use the Donate page to start a donation inquiry. Coalition staff can confirm the approved finance workflow, documentation needs, and any restrictions before a contribution is accepted.

Use the general contact path so the request can be routed to the appropriate coalition representative before information is shared externally.

Microsoft Entra ID / SSO is the target for staff access, with Supabase Auth metadata supporting platform roles and authorization.