Trips

Proposals and drafts

Sometimes Constellations asks before it acts. When new information would change something already on a trip, or when a confirmation was mostly but not fully read, a proposal or a draft appears instead of a silent change. This page explains each kind and what accepting or dismissing does.

Change proposals

A forwarded change email updates a booking directly, unless you've changed that booking yourself (see Changes and cancellations). When the airline changes a flight's schedule, a flight that came from an email updates by itself and everyone on it hears what changed. Its owner sees the change on the flight, with Undo to put the old times back until it leaves. After an Undo the times count as yours, so the airline's next change is proposed rather than applied. When a forwarded email or the airline's schedule disagrees with a flight you typed in or edited yourself (the airline moved the departure time, say), nothing is overwritten. The flight gets a proposed change: a field-by-field comparison of what's stored against what just came in, including a new flight number or day. It appears as a banner on the item itself and as a signal in the inbox.

  • Accept applies every proposed value to the item.
  • Dismiss keeps the item exactly as it was.

Only the item's owner can accept or dismiss; everyone else on the trip sees the pending change as read-only.

Places get proposed changes too. When a transfer on your trip goes to a hotel you're staying at, Constellations finds that hotel so the drive time is right. If the stay doesn't have an address yet and the hotel was found by its name, the stay gets a proposed change: Address found, with the address it found. Accept it to save the address on the stay. This one appears on the stay itself, not in the inbox, and it's only offered once. Dismiss it and it won't come back.

Requests to combine trips

Someone on a trip with you who wants to combine their trip with yours can ask. The request arrives in the notifications inbox:

  • Accept brings their items into the trip. They keep ownership of their own items and become an editor on the combined trip.
  • Decline leaves both trips as they were.

Changed your mind after asking? Withdraw it from the confirmation, or from your trip's Activity, where it waits until it's answered. It also leaves their inbox.

Combining two of one's own trips doesn't need a proposal. See Combining and splitting.

Expense proposals

A "your card was charged" email, or a forwarded receipt that looks like it belongs to an existing booking, shows up as an expense proposal in your signals. The card says which trip, and which booking if there's a likely one. From the card:

  • Add expense adds it to that trip, on the booking it names.
  • Change… puts it on a different booking, or on the trip with no booking (No booking, just the trip), for a taxi or a meal.
  • Not an expense adds nothing and closes the suggestion.
  • When no trip matched, Pick trip lets you choose one.

Clear-cut receipts skip this step and become expenses directly (see Email forwarding). Only ambiguous ones ask.

Draft items

When a forwarded confirmation is recognised but a required detail couldn't be read (a flight missing its flight number, for instance), a draft is created: a faded item plus a banner on the trip, "We pulled this from your inbox. Looks right?"

  • Edit opens the form with everything that was read pre-filled; add the missing pieces and save.
  • Confirm (on travel drafts that read complete) saves the item. Later bookings from that sender aren't asked about again.
  • Dismiss discards the draft.

Drafts are visible only to their owner. Nobody on the trip, and nobody in any constellation, sees an item until it's confirmed.

Proposals never expire on their own, but they're moments in time. Dismissing a schedule change the airline insists on means the next update raises a fresh proposal.