Roadmap

CrowdCAD's roadmap reflects practical operational needs from collegiate EMS, volunteer first-aid teams, and related event medical organizations. Priorities evolve as feedback and contributor capacity change.

How this roadmap is used

This roadmap is a planning and communication tool. It highlights current priorities and likely next areas of work without promising fixed delivery timelines.

Suggestions from organizations around the world are welcome, especially where they reflect real volunteer operational needs in event medicine settings.

Current focus

Near-term work centers on usability, documentation quality, onboarding clarity, and making CrowdCAD easier for new organizations to evaluate responsibly.

Usability and interface clarity

Improve interaction clarity across dispatch, setup, and navigation to reduce friction under event conditions.

Documentation and onboarding quality

Strengthen docs so organizations can compare Lite Mode and self-hosting paths with clearer operational and privacy context.

Evaluation readiness

Make it easier for new teams to run practical evaluations and provide actionable feedback from real event workflows.

Planned improvements

These are active areas of planned improvement shaped by real organizational feedback and contributor availability.

Support for larger and more complex events

Expand workflow support for higher call volume, broader staffing structures, and multi-zone event operations.

Better multi-dispatch interfaces

Improve UI and role clarity for multiple simultaneous dispatchers coordinating from a shared operational board.

Stronger field workflows and communication

Explore improved supervisor and roaming-lead workflows, including correspondence and messaging models for field-team logins.

Mobile notifications where appropriate

Evaluate practical mobile notification patterns that support teams in the field without overloading users.

Organization-requested workflow refinements

Prioritize improvements requested by organizations based on real operational constraints and event-day use.

Broader support across regions and operating models

Improve fit for volunteer medical organizations operating in different regions, event structures, and staffing models.

Longer-term ideas

These are directional ideas rather than delivery promises. Scope and timing may evolve as project feedback and contributor capacity change.

Advanced operational coordination tools

Investigate additional coordination capabilities for complex event staffing, escalation, and distributed supervisory coverage.

Broader configuration flexibility

Support more organizational operating models while keeping defaults practical for smaller volunteer teams.

Deeper workflow customization

Enable configurable workflow adaptations that remain understandable and maintainable across deployments.

Internationalization and localization support

Improve language and regional adaptability for volunteer medical organizations in different countries and operating contexts.

Adoption and extension architecture

Continue architecture improvements that make CrowdCAD easier to adopt, self-host, and extend upstream.

Community input and upstream collaboration

CrowdCAD welcomes suggestions from organizations, feature requests tied to real workflows, and upstream contributions from teams that adapt the project for local use.

  • • Suggest improvements based on practical event operations.
  • • Share workflow constraints from your organization and region.
  • • Contribute implementation improvements that can help more than one team.
  • • Align new work with roadmap priorities where possible.

Roadmap scope note

Roadmap items are goals and areas of planned improvement. Scope and ordering may change based on operational feedback, design maturity, and contributor availability.

Release history and selected project documentation are sourced from the public CrowdCAD repository submodule when available.