# Manage a plan, invitees, logistics, or cancellation

Use the canonical plan page for changes after a draft or published Domino exists. The controls available depend on whether the viewer is the host, whether the plan is a draft or active, and whether invitation links or delivery already exist.

## Open the correct plan

1. Open **My Dominos**.
2. Find the item under **Drafts**, **Awaiting RSVPs**, **Tipped & Happening**, or another current section.
3. Open the card and confirm the title, place, date, and host before changing anything.

Do not edit a similarly named plan based only on its title.

## Read the current state first

Before taking an action, inspect:

- plan state: draft, awaiting RSVPs, tipped, canceled, past, or discarded;
- current time and RSVP deadline;
- accepted, pending, declined, or removed invitees;
- whether invitation links were copied or opened;
- whether Domino delivery succeeded, failed, or was suppressed;
- any visible plan-progress or logistics update.

An invitation being sent is not the same as an accepted RSVP.

## Edit plan details

Hosts can open **Edit details** when the current lifecycle permits editing. Depending on the plan, editable fields can include:

- place or event;
- date and time;
- RSVP deadline;
- minimum or maximum guest count;
- title and description;
- connection behavior for recipients who sign up.

1. Open **Edit details**.
2. Change only the intended fields.
3. Review consequences shown by Domino.
4. Choose **Save changes**.
5. Confirm the plan page displays the new values.

An active plan edit can affect people who already received an invitation. Never tell the host that guests were updated unless Domino shows a confirmed notification or delivery result.

## Invite additional people

1. Open the plan.
2. Choose the invitation action that opens **Create Invite**.
3. Select additional people. Existing invited people can appear locked so they are not duplicated.
4. Review the current plan details and new delivery audience.
5. Continue to **Review Invite**.
6. Complete **Send invites**, **Create invite link**, or the mixed delivery flow.

The same direct-versus-manual delivery distinction applies to additional invitees.

## Review and manage the roster

Open **Invites** from the host status area to review each person's current status. Common states include:

- invited or pending;
- accepted or in;
- declined or out;
- removed;
- failed or suppressed delivery where shown.

If the UI allows a host to update an invite status, identify the exact person and current state first. Host-side status correction is a shared-state change; do not use it to guess what someone intended.

Removing an invitee is different from canceling the whole plan. Confirm the person and the effect Domino displays before removing them.

## Understand tipping progress

The host status can show how many accepted RSVPs exist and how many are still needed. Typical outcomes are:

- **Awaiting RSVPs:** the plan has not reached its minimum;
- **At risk** or **Not tipped:** the deadline is near or the threshold is unmet;
- **Tipped:** enough people accepted and the plan is happening;
- **Didn't tip:** the deadline passed without enough accepted RSVPs;
- **Canceled:** the host canceled it for another reason.

Hosts may be able to extend the RSVP deadline or lower the minimum after a plan does not tip. Treat that as a plan revision and use the currently displayed state after saving.

## Manage plan progress and logistics

The plan page can expose **Plan progress** for host coordination. A host can add, rename, reorder, edit, remove, or change invitee visibility for checklist items when those controls are available.

Examples include reservations, tickets, supplies, meeting instructions, or other steps needed to make the plan happen.

Use the following rules:

- mark a task complete only when the host says it is complete;
- distinguish host-only items from items visible to invitees;
- do not infer that a reservation, ticket purchase, payment, or booking happened from the presence of a checklist item;
- do not put secrets, payment credentials, or private access codes into user-visible logistics;
- after an edit, verify the new item text and visibility.

Domino can surface logistics updates to participants. Dismissing an update only dismisses that notice; it does not undo the underlying plan change.

## Delete, discard, or cancel correctly

These actions are not interchangeable.

### Delete a private draft

Use draft deletion when the object is still private and has not been published. It removes the draft rather than notifying recipients.

### Discard an unsent Domino

Use **Discard unsent Domino** only when the host made it by mistake and did not share the invitation. If a link was copied or opened, Domino can warn that the host should cancel instead.

### Cancel a published or shared plan

Use cancellation when recipients may already know about the plan. Cancellation preserves the historical record and shows that it is no longer happening. Follow any current notification or reason flow shown by Domino.

If the host is unsure whether they sent the link, choose cancellation rather than claiming the plan was never shared.

## Troubleshooting

- Missing edit controls usually mean the viewer is not the host, the plan is terminal, or that field is no longer editable.
- If an invited person cannot RSVP, check whether they were removed, the plan is full or ended, or they need to claim their invite slot.
- If a delivery failed, use the returned host-share link when available rather than repeatedly recreating the plan.
- If the plan says **Didn't tip**, inspect the deadline and minimum before promising it can be revived.
- If a checklist change is not visible to guests, inspect that item's visibility setting.

## LLM answering guidance

- Identify the plan, host role, lifecycle state, and intended change before giving instructions.
- When explaining cleanup, ask whether the invitation was ever shared; that determines discard versus cancel.
- Treat RSVP state, delivery state, plan state, and logistics completion as four separate facts.
- Never infer a booking, purchase, payment, notification, or recipient response from a host checklist or draft change.