Showing the Order of Steps When the Appointment Time Is Not Yet Agreed

The situation

A customer has asked for an appointment, but nobody has agreed on a time. A common mistake is to show a timeline with placeholder times or a default time zone. Customers read those as promises, or they misread them because they are in a different place. This article proposes a time neutral sequence display for a customer facing web app. It is an example workflow, not an observed result, and the scenario below is hypothetical.

Inputs

Imagine a small tutoring service. Before a time exists, list:

The ordered steps the customer will go through, such as request received, availability proposed, customer chooses, confirmation sent, session held, follow up notes.
Who acts at each step: the customer or the business.
Which steps depend on a previous one.
Which step is the one that fixes a time.

Nothing in this list should contain a clock time or time zone.

The display

Show numbered or ordered steps with a clear state for each: Done, Waiting on you, Waiting on us, or Not started. Show a single line such as Time not yet agreed near the top. Do not display dates, clock times or time zone names until the step that fixes a time is complete. When it is complete, show the agreed time once, together with the zone it applies to, in a separate block clearly labelled as the confirmed appointment.

Decision branches

If the customer has not yet chosen from proposed options, show Waiting on you and describe the action in words, such as Choose one of the proposed options.
If the business has not proposed options, show Waiting on us, with a plain statement of what the customer can expect to happen next, without a promised response time.
If a time was agreed and later changes, mark the confirmation step as needing re-confirmation and hide the old time or label it Previous time, no longer valid.
If customer and business may be in different places, display the zone only alongside a confirmed time, never as a default.

Stop conditions

Do not release the display if:

Any text before confirmation contains a clock time, date or time zone.
Two steps can appear Waiting on you at once without explanation.
A changed time can still appear as confirmed.
A customer cannot tell whose turn it is.

Worked example

The tutoring request shows: 1 Request received, Done. 2 Availability proposed, Waiting on us. 3 You choose, Not started. 4 Confirmation sent, Not started. 5 Session, Not started. Top line: Time not yet agreed. Later the business proposes options and step 2 becomes Done while step 3 becomes Waiting on you. After the customer chooses, a separate block appears: Confirmed appointment, with the date, time and zone. Steps 1 to 4 show Done.

Acceptance test

Walk through four test records: new request, options proposed, time confirmed, time changed after confirmation. For each, ask a tester who has not seen the screen to answer:

Whose turn is it?
Has a time been agreed?
If so, which one, and in which zone?

The proposal passes when testers answer correctly for all four records and no pre confirmation screen contains any time or zone. Also confirm the changed time record never shows the old time as current. If a tester guesses a time that was not shown, treat that as a failure and revise the wording.

Conclusion

When a time is not agreed, show order and ownership, not clocks. A short sequence with clear states keeps customers oriented and avoids accidental promises. Introduce the time, with its zone, only at the moment it becomes real.