Product structure

The public explanation of the Tov+ model.

Tov+ is not a single checklist app. It is an occasion-first coordination layer for multi-event experiences where the guest view, vendor view, and planner control surfaces all need to stay connected without sharing the same complexity.

Occasion

The root workspace. Branding, defaults, actors, installed modules, communications, assets, and permissions all start here.

Event

A scoped sub-part of the Occasion. Ceremony, reception, brunch, travel, and private operational moments each keep their own audience, timing, and module enablement.

Actor

The shared participant model for people, vendors, households, teams, and groups. This is how Tov+ keeps visibility and coordination coherent.

Modules

RSVP, seating, gallery, timeline, and future features remain installable layers so the occasion can stay adaptable instead of rigid.

Why this matters publicly

The landing site needs to explain enough for planners to understand why Tov+ exists: it replaces disconnected forms, guest spreadsheets, vendor threads, published PDFs, and one-off portals with one coordinated model.