One wedding is roughly twenty vendors, one venue, one couple, and several hundred emails: quotes, contracts, delivery windows, final counts, and the florist's van's arrival time, which matters more than it has any right to. A planner in season runs eight or ten of these coordination projects at once, each with a date that cannot move. There is no profession where a silently unconfirmed email costs more per incident.
Group by wedding, always
The unit of work is the event, so the inbox gets read through that lens: every arriving message attributes to its wedding on first read, and each wedding carries its own task list and its own confirmations ledger. A pile of mixed vendor mail is chaos; the same mail grouped by event is eight small, checkable projects.
Confirmations are the tracked object
The dangerous vendor isn't the rude one; it's the friendly one who never actually confirmed the delivery time, and nobody noticed until the morning of. Every booking, every delivery window, every final headcount is a dated waiting-for entry the moment it's requested, chased on a countdown schedule that tightens toward the date: monthly at six months out, weekly inside the final month, daily in the last week. The waiting-for method was built for exactly this shape of risk.
How do planners stop the midnight emails?
Scheduled updates that pre-empt them. Couples email at midnight because uncertainty compounds after dark; a stated update rhythm (biweekly, then weekly near the date) that answers the standard anxieties before they're asked converts most midnight threads into "see Friday's update." Reactive-only communication trains couples to chase; rhythm trains them to trust the rhythm. Batching the processing itself (method here) keeps venue visits and tastings interruption-free.
The coordination layer Pidgy carries
Sorting mail by wedding, extracting dates and deliverables from vendor threads, keeping the confirmations ledger, flagging what's unconfirmed as the countdown tightens, drafting the update emails and vendor chasers in your voice: that's the layer Pidgy runs on Gmail and Outlook, every send queued for the planner's approval. The planner keeps the taste and the calm; the machine keeps the ledger. The full picture: the wedding planners use case.
