Why am I seeing Availability Conflict Detected?

What’s Changed

We’ve moved volunteer availability management from the program-level to the organisation-level. This means that instead of setting different availability for each volunteer across multiple programs, you’ll now manage all volunteer availability from one central source.

Migration Process

We’ve automatically migrated your existing volunteer availability data to the organisation-level. Here’s how the process worked:

Volunteers with consistent availability

For volunteers who had the same availability settings across all programs, we’ve automatically set their organisation-level availability to match their existing settings.

Volunteers with conflicting availability

For volunteers who had different availability across programs (e.g., unavailable Mondays in Program A but available Mondays in Program B), we’ve left their organisation-level availability unset to avoid making assumptions about their true availability.

To resolve these conflicts, you’ll see a notification prompting you to set the correct organisation-level availability for affected volunteers.

Important: Program schedules will continue displaying greyed-out dates based on their previous program-specific settings until the organisation-level availability is set which will then apply consistently across all programs.

Next Steps

Review any volunteers with conflicting availability and configure their correct availability settings to ensure consistent scheduling across all your programs.

This change reflects feedback from organisations looking for simpler, more consistent volunteer management tools while maintaining the scheduling flexibility you need.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.