The Conflict Center
One screen for problems found across everything you have booked — grouped by the event they affect, re-checked every hour, and cleared automatically once you fix them.
Conflict Center collects the problems found across everything you have booked and groups them by the event they affect. It exists so a clash found by one part of CeremonySync does not stay buried there — a maintenance ticket raised on Tuesday that threatens Saturday's wedding sits on the same card as the kitchen cooking for the wrong number of guests.
What is on the screen
Filter chips across the top — All, Critical, Warning, Info — each with a count. A Show handled chip on the right brings back anything you have acknowledged or snoozed.
Below that, one card per event, soonest first. Each card is headed by the event, its date, how far away it is, and how many issues it has. Inside, the worst thing is listed first. Every line says what is wrong, which part of CeremonySync noticed, and — where there is something to open — links straight to the screen where you fix it.
Down the side, Venue Health summarizes the worst thing open, and By Module counts what each part of the product has raised.
The three levels, and why they change
- Critical — act now.
- Warning — review it.
- Info — a note.
The level is not fixed. It is worked out from two things: how bad the problem is, and how close the event is. The same short turnaround is a note eight months out and an emergency on Thursday, so a conflict can climb on its own as the date approaches, with nothing about it changing except the calendar.
How fast it climbs depends on what kind of problem it is:
- Blocking — the event cannot happen as booked. A double-booked space, nobody rostered, a room out of service.
- Degrading — it happens, but worse. A tight turnaround, an unapproved menu, an unconfirmed shift.
- Admin — paperwork and records. A missing client link, a booking with no ceremony time.
Anything dated in the past closes automatically. A conflict about an event that already happened is history, not a task.
Where conflicts come from
Every part of CeremonySync feeds this screen. There are fifty-eight checks in all, and the eighteen in the first two rows need no paid module at all.
| Source | Checks | What it flags |
|---|---|---|
| Coverage | 2 | Bookings that cannot be fully checked — no ceremony time set, or no spaces assigned |
| Core | 16 | Double-booked dates and spaces, bookings on blocked dates, weddings with no client linked, unsigned contracts, overdue deposits and balances, guest counts still unconfirmed, RSVP deadlines gone by, capacity exceeded, timelines never approved, and vendors whose insurance or license lapses before the event — or who are booked for two of your events on one day |
| EventSync | 6 | A booked event clashing with a wedding or with another event, a recurring series colliding with itself, timeline items double-booking a space, ticket sales past capacity, and event vendors who have not confirmed |
| FacilitySync | 9 | A space out of service across a booking, an open critical ticket in a room the booking uses, reported faults past their deadline, the recurring-maintenance backlog as one line, compliance expiring or already expired before a booking you hold, inspections still pending, contractors who never answered, and back-to-back bookings with no turnover scheduled |
| AssetSync | 7 | More of an item needed than you own, items not returned, rentals past their return deadline, the same set reserved for two events at once, maintenance falling inside a reservation, tight turnarounds on shared kit, and pull lists still unfinished |
| KitchenSync | 11 | A kitchen cooking for a different number than the booking says, no catering order at all, unapproved menus, selection deadlines passed, dietary requests unresolved, overdue prep, tastings never scheduled, HACCP reviews overdue, stock below par, kitchen spaces double-booked, and anyone excluded on health grounds who is still rostered |
| StaffSync | 7 | Roles short of their target, one person rostered twice, someone rostered on a day they marked off, shifts nobody has accepted, shifts declined and never refilled, missing breaks, and shifts never clocked out of |
Maintenance shows up twice, on purpose
A reported fault past its deadline gets a line of its own, and where the room it is in has a booking coming up, that line sits on the booking's card with the date — so it climbs in urgency as the day approaches rather than sitting in a pile.
Recurring maintenance is different. Those jobs are created on a schedule, not reported by a person, and a venue with an active schedule will always have some running late. They arrive as a single line — "28 scheduled maintenance jobs are past the time they were due" — because that is one fact about your schedule, not twenty-eight problems with your bookings.
Five checks ship switched off
Most of the fifty-seven run from the day you sign up. Five do not, because they are records you review on your own schedule rather than risks to Saturday, and each already has a screen of its own: the two Coverage checks, missing breaks and missing clock-outs in StaffSync, and stock below par in KitchenSync.
Open What we check at the foot of the screen to switch any of them on — or to switch off anything you would rather not be told about. The switches are per venue, and an owner or manager can change them.
Coverage conflicts are the ones worth clearing first
These say a check could not run, rather than that something is wrong. A booking with no ceremony time cannot be tested for turnaround or overlap; a booking with no spaces cannot be tested against maintenance or double-booking.
They are switched off by default, because on a venue that has just signed up they would be most of the list and none of them is a problem with a booking. Turn them on in What we check when you want to see how much of your calendar is being checked properly — every one you clear makes the rest of this screen sharper for that booking.
Where a check cannot be certain, it says nothing
A critical maintenance ticket is only raised against a booking that records the same space. It is never raised on a guess. Where spaces are missing, the coverage conflict above is the honest answer, and it is said once per booking rather than once per ticket.
Acknowledge, snooze, resolve
Three different things.
Acknowledge means you have seen it. The problem is still there — the line dims and stops counting toward venue health, but nothing about the booking has changed.
Snooze 7d hides it for a week. Same idea, with a timer. It comes back on its own.
Resolve is not yours to press on most lines, and that is deliberate. Nearly everything here clears itself the moment the problem is actually fixed: link the client, set the ceremony time, roster the fourth server, and the line goes within the hour. Marking such a line resolved by hand would only bring it back on the next check, because the problem had not gone anywhere.
Reopen undoes an acknowledge or a snooze.
Whether fixing the problem clears the row
Yes, on its own.
Every hour — and immediately whenever you change a booking — the checks are re-run from scratch. Anything still true is kept and re-scored; anything that has stopped being true is closed automatically. Cancel one of two clashing weddings, set a missing ceremony time, or fill the last bartender shift, and the row disappears without anyone pressing anything.
Being told without looking
You do not have to visit this screen to hear about a problem.
When something becomes Critical, the people who can act on it are notified in the app — a staffing gap reaches your staff coordinator, a kitchen problem your kitchen manager. You are told once. It will not repeat every hour, and only speaks up again if the problem gets worse.
There is a daily limit per venue so that a bad morning cannot bury you, and the nearest events are told about first. Anything above the limit is still here on the screen.
Readiness on the booking itself
A booking with open problems carries a badge in its header: At risk when something could stop the event happening as booked, or Needs attention for anything else outstanding. A booking with nothing open carries no badge at all.
Acknowledged and snoozed items do not count toward it — you have already decided about those.
If the screen is empty
"No active conflicts — all clear!" means the checks ran and found nothing, and the screen lists what was checked so you can see the scope of that reassurance.
If the checks could not be read at all, the screen says so plainly instead of showing an all-clear. An empty list and a failed lookup are not the same thing, and this screen will never show you one dressed as the other.
Most of these checks run for every venue whatever you subscribe to — a date with two weddings on it is the single most expensive mistake this product can catch.
Not the same as the other two conflict screens
- The warning you get the moment you book two things into one space is conflict detection
- The checks across a single wedding's day are in the Event Flow timeline
This screen collects what is found after the fact, across everything already booked.
Practical use
- Work down the cards from the top. They are ordered by how soon the event is, so the top card is the one closest to happening.
- Clear coverage conflicts on quiet weeks. They are the cheapest thing here and they make everything else work better.
- If By Module is always the same module, the problem is that module's configuration rather than your week.
Frequently Asked Questions
Why did something become critical overnight? Because the event got closer. Severity is re-worked every hour from how near the date is.
Why can I not resolve this row? Because it clears itself. Fix the underlying problem and it will go. Acknowledge it if you just want it quiet.
Something is wrong and it is not on this screen. Why? Check the booking for a coverage conflict. If it has no spaces or no ceremony time, several checks cannot run for it.
Who can act on conflicts? Owners, managers and coordinators can acknowledge, snooze and reopen. Facility managers, kitchen managers and staff coordinators can see the screen. Other roles cannot.
Does acknowledging tell anyone? No. It records who acknowledged it and when.
Keep reading
Still stuck? A person reads every email.
If a guide and the app disagree, the app is right. Tell us and the guide gets fixed.