About

ConflictRegistry helps organisers avoid avoidable clashes.

The registry is built for scientific, academic, technical, and research-adjacent events that need visibility before calendars are final. It is not a full calendar platform. It is an early-warning system for timing, audience, and thematic conflicts.

How it works

  • Organisers submit a public event record with dates, mode, location, and tags.
  • The event remains pending until the organiser verifies it by email link.
  • Once active, the registry compares it with nearby or related events and stores conflict signals.
  • The discovery timeline makes those overlaps easier to inspect before plans are locked in.

What it is not

  • No user-account system.
  • No social feed, comments, or engagement features.
  • No private-event workflow in the current version.
  • No external calendar sync yet, though the API is designed to support integration later.

Why this matters

Events do not only conflict when they happen at the same hour. They can also compete for the same audience, region, or thematic attention. ConflictRegistry gives organisers a shared planning surface so those issues show up early enough to act on.