Details
The Details tab holds the information that describes one event and supports its agreement with the client. This is where you manage the event date, people, locations, notes, flower palette, timeline, files, contract, payments, and event-specific settings.
For example, a wedding event can identify the couple, planner, venue schedule, contract signer, deposit due date, and final payment in one place. Those records serve different purposes, even when they refer to the same event.
The top of Details keeps the event name, event number, people, and locations together. The numbered badge beside the tab points to an item that needs attention elsewhere on the page.
Event data and planning details
Key Event Data identifies the event and the team working on it. Learn how to manage event data and team assignments when the name, date, tags, assignees, or Event Roles need attention. Contacts & Locations separates clients from professional contacts, such as a planner or venue contact. Use clients, signers, and professional contacts to choose the right record and understand what is shared across events. Notes can hold internal context that your team needs while planning.
The Locations list within Contacts & Locations associates reusable places with the event, independently of the schedule. Manage event locations to add places, record event-specific notes, and select a primary location for the Events report. Build recipe location choices include these places and places used by the timeline.
The Timeline describes scheduled activities such as delivery, setup, ceremony, and collection. A timeline item can have a time, location, notes, and a choice about whether it appears in the proposal. See Plan the event timeline for the difference between a saved location and an activity at that location.
Event Flowers is the flower palette you plan to use across the event. It is a starting selection for the designs, not a list of the quantities already assigned to each recipe. Build the Event Flowers palette explains manual selection, AI drafting, and what saving a replacement palette changes.
Contracts, payments, and amendments
The Contract section contains the terms you prepare for the event. One client is designated as the signer. Prepare the contract terms and signer requirements before sharing the Client Portal. Previewing the terms does not create a signable document. A generated document appears in Files after the signer begins the contract process, where its status shows whether signing is complete.
After a contract is signed, pricing-related changes can become amendments. Manage contract amendments explains how client approval differs from irreversible manual confirmation.
The Payments section separates what is expected from what has been received:
A payment schedule states amounts and due dates.
An invoice explains an amount owed.
A payment records money received.
A receipt acknowledges a payment.
Keeping those records distinct helps the schedule show what is still outstanding. Start with Set up the payment schedule for expected amounts and due dates, then use Manage invoices, payments, and receipts when money is billed, received, acknowledged, or refunded.
Event-specific settings
Markups contains the pricing, labor, overhead, and suggested-price assumptions copied into this event. Settings contains its automatic payment-notification choices, profit display, price-warning tolerance, and date format. Configure event pricing and settings explains which values affect calculations and which affect only display or future notifications. Changing these sections affects this event rather than changing the defaults used to create future events.
QuickBooks Sync can connect this event's invoice with a connected QuickBooks company.
Event Actions contains Apply event template. Apply an event template explains the Add, Replace, and Keep existing choices before you make this one-time update. Applying a template does not create a continuing connection to that template.
In this section
Last updated
Was this helpful?