Tov+ Tov+ Planner sign up

Public launch surface

One Occasion. Multiple Events. One coordinated plan.

Tov+ helps planners run wedding weekends and other complex occasions from one operating system. Events stay connected, guests see a clear portal, vendors get scoped context, and every module works from the same source of truth.

Planner sign up Planner sign in Explore docs

1 occasion

One control surface for a full wedding weekend, not five disconnected tools.

Many events

Ceremony, reception, brunch, travel, and vendor moments stay coordinated.

Every actor

Planners, hosts, guests, vendors, households, and teams see their version of the plan.

Audience fit

Planner-first, but built for everyone involved.

The primary call to action is for planners because they need the control surface. The product model still accounts for hosts, guests, vendors, households, and teams from the beginning.

Planners

Run the whole occasion from one place: people, timelines, communications, seating, publishing, and vendor coordination.

Hosts

Stay aligned on every event without inheriting planner-only complexity or losing visibility across the weekend.

Guests

Get a clear, personalized portal with only the events, details, and actions that matter to your invitation.

Vendors

Receive scoped operational context, event-specific assignments, and the latest published materials without inbox chaos.

Occasion-first

A coordinated event operating system, not a pile of forms and links.

Tov+ starts from the Occasion. Every Event, Actor, Module, communication, and asset hangs from that shared context so planners can operate the full experience without rebuilding structure for each event.

Module-driven

Install only what the occasion needs.

RSVP, gallery, seating, timeline, publishing, reminders, and future workflows live as Modules. You turn them on per occasion and enable them where they matter per event.

Audience-aware

Everyone sees the right slice of the same truth.

Actors unify guests, vendors, groups, households, teams, and helpers. Permissions stay centralized so every route, message, and published artifact respects scope.

Modules in practice

Install the capabilities the occasion actually needs.

Tov+ stays modular on purpose. Modules can be added per Occasion and enabled per Event, so the product can support a single dinner, a full wedding weekend, or a future multi-day company offsite without warping the core model.

Timeline

Coordinate run-of-show, assignments, and operational visibility across the weekend.

RSVP + Forms

Collect event-specific responses, meal choices, travel details, and guest submissions without losing audience context.

Seating + Publishing

Generate charts, QR-linked materials, and guest-facing outputs from the same source of truth.

Gallery + Assets

Manage uploads, derivatives, visibility, and shared media workflows without re-implementing file handling per feature.

Documentation discovery

Read the model behind the product.

The public landing site should not over-explain implementation details, but it should make the shape of the platform legible. The docs route is the entry point for architecture, contracts, and planning-model context.

Architecture

See how Occasion, Event, Actor, Module, Permissions, Communications, and Assets fit together.

Backend contracts

Understand the API, webhook, server, and worker foundations that power future apps and integrations.

Planning model

Review the language and assumptions behind multi-event coordination, guest flows, and vendor operations.

Planner entry

Start with one occasion and grow the operating system around it.

Create planner access See the product model