Check a dated wedding schedule revision for exact activity durations, gaps, overlaps, concurrency and source ownership without invented standard timings.
Specialist tool for Wedding Events1 documented formula3 recommended next stepsPrivate in your browser
Use this result well
A quick decision brief for this specific tool
Inputs that matter
One named, dated, revisioned and de-identified wedding schedule; the exact event date, location-based IANA time-zone identifier and source-owned UTC offset for that date; current schedule, venue/vendor confirmation, accessibility/communication review, emergency/crowd/transport plan, responsible reviewer, review timestamp and retention/distribution sources; 2–8 source-owned activities with stable internal identifiers, de-identified labels, canonical local start/end date-times, location labels, accountable owner roles and exact source-line references; optional independent same-scope occupied-minute summary with its exact source and separate owner tolerance; plus explicit owner-entered-schedule, de-identified-data, source-owned-time and interval-arithmetic-only boundaries
Output to expect
Chronologically sorted source intervals with source-owned RFC3339-style timestamps; exact per-activity duration, total schedule span, summed activity minutes, occupied interval union, unoccupied gap minutes, concurrent-overlap minutes, maximum concurrency, pairwise conflict intervals and gap intervals; optional independently reported occupied minutes, signed reported-minus-reproduced residual and inside/outside owner-tolerance state; retained schedule/venue/vendor/accessibility/emergency/reviewer/time-zone/offset/retention evidence; deliberate page-session snapshots, copy/Markdown/print/share actions; and stable Project outputs that keep standard-duration/sequence generation, DST/offset/travel/vendor-call inference, accessibility/communication determination, emergency/crowd/transport/security/safety approval and vendor/contract/legal/compliance approval false
How it works
Validate one coherent schedule revision and strict local YYYY-MM-DDTHH:mm values without parsing them in the host time zone; require every end after its start and the next calendar date explicitly for cross-midnight activity; sort intervals by source start, merge touching/overlapping intervals to reproduce occupied union, subtract occupied union from the outer span for gap minutes, subtract occupied union from summed activity durations for overlap minutes, enumerate every positive pairwise intersection, sweep starts/ends for maximum concurrency, and optionally subtract reproduced occupied minutes from one independent same-scope report inside an owner-owned tolerance
The exact revision, event date, IANA identifier, UTC offset, schedule, venue/vendor confirmations, accessibility/communication review, emergency/crowd/transport plan, reviewer, review time and retention/distribution record must travel together. Short time-zone abbreviations, an offset change during the scope, impossible local time, missing source, mixed revision or more than fourteen days requires an authoritative calendar or separately reviewed record.
Every activity needs a de-identified label, explicit local start and end, location label, accountable owner role and source reference. Equal start/end is not assumed to mean 24 hours; an earlier end is refused instead of silently wrapping; touching endpoints are adjacent; pairwise conflicts and merged-union overlap are reported separately without choosing what should move.
Arithmetic agreement does not establish sequence, duration, travel feasibility, vendor readiness, accessible route, accommodation, effective communication, emergency coverage, crowd flow, transport, security, fire/medical readiness, contract, legal, safety or compliance status. Keep those decisions and any personal details with the current accountable sources, people and authorities.
Choose your path
Built around the job you need to finish
Check one dated, revisioned and de-identified wedding schedule from exact owner-entered local activity intervals, roles, locations and sources; reproduce duration, occupied-union, gap, overlap, concurrency and optional comparison arithmetic while refusing invented standard timings and every consequential vendor, accessibility, emergency, legal and safety decision.
Wedding coordinator reconciling the issued schedule
Expose exact time conflicts and gaps without replacing vendor and venue confirmations with generic wedding-day durations.
Name the revision, verify the event date/IANA zone/offset and source set, enter 2–8 de-identified activity intervals with owner/location/source evidence, affirm all four boundaries, then check the schedule.
Receives sorted source intervals, exact union/gap/overlap/concurrency arithmetic and pairwise conflicts without a recommendation to move, shorten or lengthen an activity.
Venue operations reviewer checking a cross-midnight revision
Confirm that explicit next-day timestamps, load-in/load-out windows and touching endpoints are interpreted consistently before an accountable coordination meeting.
Enter the next calendar date for cross-midnight work, add venue and vendor source lines, optionally compare occupied minutes with an independent summary and inspect the signed tolerance residual.
Can distinguish adjacency, gaps and concurrent overlap while DST, access, travel, staffing, emergency and safety decisions remain visibly outside the Tool.
Accessibility and records reviewer protecting participant data
Keep a reproducible operational schedule without copying names, contacts, health or accommodation details into a transient browser page.
Use role/location/source labels only, retain the accountable accessibility/communication and emergency plan references, inspect the decision boundary, then use deliberate snapshot, copy, Markdown, print, share or Project actions and clear snapshots when finished.
Exports only de-identified interval arithmetic and named provenance; personal needs and every accessibility, communication, emergency, security, legal and safety decision remain with accountable reviewers.
Authoritative checks for this tool
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
Each activity keeps an exact local YYYY-MM-DDTHH:mm start and end, a location-based IANA time-zone identifier and a source-owned numeric UTC offset. Enter the next calendar date explicitly for cross-midnight work. Verify offset changes and ambiguous civil times in an authoritative zoned calendar; this Tool does not infer them.
Activity duration = entered end minute index − entered start minute index
Union, gap and overlap arithmetic
The Tool sorts entered intervals and merges every touching or overlapping interval. The merged union is occupied time. Unoccupied minutes inside the outer span are gaps; summed activity durations above the union are concurrent overlap. Pairwise intersections are listed separately so no conflict is hidden.
Gap = outer span − occupied union; overlap = summed durations − occupied union
Accountable sources and nondecisions
Every row needs a de-identified activity label, location, owner role and source reference. Schedule, venue/vendor, accessibility/communication, emergency/transport, reviewer and retention records travel with the result. Arithmetic never chooses what moves or approves readiness.
A coordinator enters the current venue, portrait, ceremony, reception and load-out intervals. The Tool reproduces 485 occupied minutes, 55 gap minutes and 45 overlap minutes in the static training record, then lists the two exact intersections without proposing a revised schedule.
A venue reviewer enters a late activity ending on the following calendar date. The Tool uses the explicit date change and source-owned offset, rejects an earlier same-date end, and distinguishes a touching next activity from an overlap.
A records reviewer compares the reproduced occupied union with one independent same-scope schedule summary and an owner-defined tolerance. The signed residual remains arithmetic evidence only and cannot validate vendor, accessibility, emergency, legal or safety readiness.
Common Mistakes to Avoid
✕
Treating a short time-zone abbreviation or browser clock as the schedule authority
✓
Retain a location-based IANA identifier and the source-owned numeric offset for the exact event date. Use an authoritative zoned calendar when rules change or a local time is ambiguous.
✕
Treating zero gaps or conflicts as venue, accessibility, emergency or safety approval
✓
Interval agreement cannot validate travel, access, accommodations, communication, crowd flow, transport, security, fire/medical readiness, contracts or law. Keep those decisions with the current accountable sources and reviewers.
FAQ
No. It accepts only times and source references that the responsible schedule owners entered. Duration, sequence, staffing, travel and vendor-call decisions remain with the current venue, vendors, coordinator and other accountable reviewers.
A location identifier provides the civil-time rule set, while the numeric offset records the exact source basis for this revision. Rules can change and local times can be ambiguous around daylight-saving transitions, so verify the exact date and offset in an authoritative calendar.
Enter the following calendar date in the end field. The Tool rejects equal start/end and an end earlier than the start instead of silently treating either case as a 24-hour or next-day activity.
Not necessarily. Concurrent activities may be intentional and may have different owners or locations. The Tool reports the exact intersection; accountable people decide whether it is acceptable, feasible or needs revision.
Do not enter names, contacts, health information or accommodation details. Use de-identified operational labels and retain only the accountable accessibility or communication review reference. Page-session snapshots are transient and should be cleared on a shared device.
About Wedding Schedule Interval & Conflict Checker
Review one de-identified wedding schedule revision from the local start and end date-times that its owners actually supplied. The Tool sorts 2–8 activities, merges their occupied intervals, exposes gaps and concurrent overlap, and preserves the IANA time-zone identifier, UTC offset, owner role, location label and source line. It never invents a standard wedding sequence, default duration or vendor call time.
