Keep booking dates, appointments, and delivery deadlines distinct

Before you start

• Set your business timezone in Business profile & branding. It is the shared business/calendar reference, not a separate timezone for each project.
• Decide whether several times and places are stops within one event or genuinely separate sessions.

Step-by-step

1. 01

   Save the event and its stops

   Enter booking date/time/location when creating a project or edit them afterward. Group multiple timed locations for the same event, such as preparation, ceremony, and reception. Use a separate event for a separate engagement session. Only enter an event title when you need one.

2. 02

   Choose a calendar view

   Use Month for broader planning, Week for upcoming commitments, and Day for the day's detail. The current date is highlighted. Booking entries show time, contact, and project context rather than repeating an empty event title.

3. 03

   Filter the kinds of entries

   Use the labels above the calendar to toggle booked work, leads or pending requests, delivery deadlines, tasks, and unavailable dates. A delivery deadline is distinct from the shoot itself, so you can review future commitments without treating the shoot as a second delivery event.

4. 04

   Create directly from a date

   Click the date box to add a project, task, or unavailable range. Manual entries may overlap when you intentionally need them at the same time; the calendar is not a blanket ban on overlapping internal records.

5. 05

   Choose how Google connects

   In Settings → Google Calendar, connect the intended account, then choose Two-way: review booking changes (recommended). Project-event details go to the primary Google calendar. Google's busy events are imported privately and block offered booking times. Existing connections stay send-only until you enable two-way sync.

6. 06

   Review outside booking edits

   If a linked booking's time or location changes in Google, open Changes to review in Google Calendar settings. Compare both versions. Keep Flovuni updates Google; Use Google applies its time/location and can move relative delivery deadlines. A deleted Google event never deletes your project. Multi-location bookings must be edited in Flovuni.

Seeing an entry is not always reserving that time

Confirmed jobs and unavailable ranges block offered availability. Leads and pending requests are visible possibilities, not reservations. Delivery deadlines tell you when work is due, not that a client appointment occupies the day.

Use one clear timezone reference

Review times against your business timezone when scheduling and sharing. The public booking form allows a visitor's viewing timezone while your saved schedule remains the reference. For a destination event, agree clearly with the client which timezone a discussed time refers to before entering it.

• Do not change the business timezone casually just to make one event display differently.
• Google Calendar may display an event in the viewer's own timezone; compare the actual instant and timezone context.
• Google all-day busy events block the corresponding days in the business timezone. Free/transparent or declined events do not block availability.

What sync does—and does not—change

Sync uses the connected account's primary calendar. Imported details appear internally to owners/admins, not in portals or public booking forms. Only availability is used publicly. Google events do not create contacts, projects or workflow tasks.

Review is the recommended mode. Automatically applying Google date changes is optional; conflicting edits and multi-location bookings still require review. Google title edits do not rename your project. Workflow deadlines and task completion are managed in Flovuni, not imported as Google tasks.

• Sync now refreshes both sides; large calendars may need additional batches.
• Google change notifications trigger refreshes, with scheduled maintenance as a fallback. Sync is not an instant availability guarantee.
• An incomplete or failed Google availability refresh asks the visitor to retry rather than offering potentially stale slots.
• Deleting a Google event keeps the project and its date; Keep Flovuni can recreate the event.
• Disconnecting removes Flovuni's imported cache and stops using Google busy times. It leaves Google events untouched.
• Apple Calendar can display this Google account's calendar, but this is not direct iCloud synchronization.

See the pieces together

A wedding with three stops and one delivery promise

A fictional wedding is one event, even though the team moves locations.

1. 1
   Preparation

   13:00 at the first location.

2. 2
   Ceremony & reception

   Later stops remain grouped with the same wedding event.

3. 3
   Optional separate session

   An engagement shoot has its own event and workflow delivery action.

4. 4
   Delivery

   The wedding delivery deadline uses the wedding event as its anchor.

Times are illustrative. A multi-stop event is not a reason to multiply the client's bookings or use each stop as a separate delivery deadline.

How it connects to the rest of your workspace

The same booking context carries through these tools. Follow a guide to see the next part of the process.

Common questions