Turnaround Between Back-to-Back Events

AssetSync → Turnaround looks at events booked close together and asks a single question: do they need the same things at the same time?

What it shows

Each row is a pair of consecutive events — the one finishing and the one starting — with the gap between them in the middle, and a verdict:

• NO CONFLICTS — they share nothing, and the changeover is not tight.
• TIGHT WINDOW — the changeover is under six hours, but nothing is contested.
• Amber or red — they share assets. The pill counts them — "3 shared assets", or "2 shortfalls" in red when the combined demand exceeds what you own.

A pair that shares assets always shows the count rather than a verdict word, so TIGHT WINDOW and NO CONFLICTS are what you see on pairs with nothing in common.

Only pairs of consecutive weddings within two days of each other are considered, and only weddings with a status of Confirmed or Pending. EventSync events are not paired here, despite the page talking about events.

Expanding a pair shows the Shared Assets table: which items both events need, how many each needs, and what you own — so you can see whether the total demand actually exceeds your stock, or whether it merely looks tight. Below it sit each event's full asset list side by side, and an Action Needed block spelling out the fix in units ("Rent 40 additional Chiavari Chairs to cover both events, or adjust timing…").

Where the demand comes from — read this first

An event contributes to this page only through checkouts that are currently out and active reservations. Nothing else counts.

A pull list does not. Until a list goes through Confirm & Check Out, or you reserve the assets, the event looks like it needs nothing — so two events genuinely fighting over the same 150 chairs will both read NO CONFLICTS while their lists sit in draft.

That is the single most important thing to know about this page. It reports contention between commitments already made, not between plans.

How the gap is worked out

The gap comes from each wedding's day-of timeline: from the latest end time on the first event's timeline to the earliest start time on the next. A wedding that wraps at 11:00 PM followed by one whose first item is 10:00 AM the next morning shows an 11-hour gap.

It reads the latest end across every timeline row, not the last row in the list — so if your closing item has no end time filled in, the measured end quietly comes from whichever earlier item finishes latest, and the gap looks longer than it is.

What happens with the shared assets depends on that gap:

• If the events overlap (the second starts before the first ends) — both need the stock at the same time, so their requirements are added together. The badge reads Overlap.
• If there is time in between, the first event's items come back before the second needs them, so you only need the larger of the two amounts. A gap under six hours is still marked TIGHT WINDOW, because that is not much time to strike, clean and reset.

When a timeline has no times

If either event has no times on its day-of timeline, there is nothing to measure, and the badge says so — Same day, Next day or 2 days, captioned no times — rather than showing an hour count it has made up.

• Same day, no times — assumed to overlap, and requirements are added together. That is the cautious reading.
• Different days, no times — treated as one after the other, so only the larger requirement counts.

Add times to both day-of timelines to get a measured gap. It takes a few minutes and turns a guess into a number.

Using it

The value is in the shared-asset table rather than the verdict. Reading which specific items are contested tells you what to do — hire in an extra fifty chairs, move the second event's linens to a different color you have more of, or schedule the turnaround crew for the overnight rather than the morning.

Every pair that is not green is also written to the Conflict Center as an asset turnaround conflict, and removed again once it stops conflicting — so these surface outside AssetSync too, and a job that runs twice a day keeps them current whether or not anyone opens this page.