Requested, pending, confirmed, waitlisted, cancelled, rescheduled and no-show do not mean the same thing. Requested means a customer has asked for a place or time. Pending means a decision or processing step remains unresolved. Confirmed generally means the supplier has accepted an actual reservation under its rules. Waitlisted means an interested person is waiting for availability, not that a seat is guaranteed. Cancelled means the identified reservation has ended. No-show reports nonattendance under a provider’s policy, not an advance cancellation.
The fastest way to translate a booking message accurately is to separate what was requested, what the provider actually accepted, whether payment has succeeded, and what happened on the appointment date. An alternative time suggested by a guest is not a completed reschedule. A cancellation request is not automatically a cancellation. A cancelled booking does not itself prove a refund was paid. These are distinct states, and confusing them can make somebody turn up at the wrong time or believe they have a reservation that does not exist.
- Requested or pending: acceptance not yet established
- Waitlisted: waiting for a place or offer
- Confirmed: active reservation in the source system
- Reschedule requested: a change was sought, not necessarily granted
- Cancelled: identified reservation withdrawn; refund separate
- No-show: nonattendance under provider criteria
- Checked in: arrival or check-in recorded, not service completed
Find your booking or appointment status
- Booking status quick reference and the question to ask
- A reservation needs more than one status
- Requested does not mean booked
- Pending can apply to a booking or a change request
- Waitlisted is an interest record, not a secured place
- Temporary hold is not necessarily final confirmation
- Confirmed means a particular item is booked
- Booking confirmed is different from attendance confirmed
- A proposed new time has not yet been accepted
- Reschedule requested versus rescheduled
- Cancellation requested versus cancelled
- Who cancelled: guest, provider or automated system?
- No-show is not the same as cancellation
- Late arrival may still count as attended
- Check-in, attended and completed describe different events
- Payment processing is separate from reservation confirmation
- Deposit, card authorization and final payment
- Refund requested, approved, initiated and received
- Cancellation fee and no-show fee may have different triggers
- A waitlist offer can expire before a booking is made
- Hotel example: quote, booking, stay and no-show
Booking status quick reference and the question to ask
Requested — a customer asked; has the provider accepted? Pending — a step is unresolved; which step? On hold — a temporary reservation or transaction hold may exist; what are its expiration terms? Waitlisted — interest is recorded; has an offer actually been made? Confirmed — a booking is reported active; what date, time and service are confirmed?
Reschedule requested — a different time was asked for; is the old reservation still valid? Rescheduled — an accepted change is reflected in the booking; what is the newly confirmed time? Cancelled — a specified reservation is withdrawn; who cancelled and what happens to payment? No-show — nonattendance was recorded; under whose policy and for which appointment? Checked in — arrival was recorded; was the service actually delivered?
Refund pending — financial processing remains unresolved; has money arrived? Completed — a service or stay is marked finished under the system’s definition; is completion being confused with customer satisfaction? No response — a reply has not been recorded; do not translate it as decline. These questions are the beginning of accurate translation rather than a universal set of legal or operational definitions.
The source system controls its own status codes. Read its help text, terms, email, confirmation number and time zone. Translate the source meaning, not the most reassuring outcome a reader might hope occurred.
| Status | Meaning | Do not claim |
|---|---|---|
| Requested | Customer asked for booking | Confirmed appointment |
| Pending | Unresolved processing stage | Accepted or rejected |
| Waitlisted | Waiting for an offer or place | Guaranteed seat |
| Confirmed | Active booking under provider rules | Attended or completed |
| Reschedule requested | Alternative time sought | New time accepted |
| Cancelled | Identified booking ended | Refund received |
| No-show | Nonattendance under policy | Intentional refusal |
| Checked in | Arrival recorded | Service completed |
A reservation needs more than one status
A booking can be confirmed even if its payment is still pending under a particular provider’s rules. A customer can submit a cancellation request while the original booking remains active. A guest can have a confirmed reservation but later fail to attend. These situations are not contradictions: booking, payment, change request and attendance are separate records.
This is why copying one word from an email into a translated status table can be misleading. The phrase “pending” might describe a refund rather than the table reservation. “Confirmed” might describe receipt of a request rather than confirmation of the time. A translator should identify the noun each label modifies, even if that noun is omitted in the short notification.
Create a four-column ledger: entity, actor, event and recorded status. For example, booking / supplier / accepted reservation / confirmed; cancellation request / customer / requested change / pending; payment / provider / refund initiated / processing; attendance / guest / did not arrive / no-show. This lets a reviewer reconstruct the message without inventing a global all-or-nothing status.
A natural target language may repeat the entity for clarity. This can be more faithful than retaining an ambiguous two-word label. The test is whether a reader would take the same next action as someone reading the complete source.
Requested does not mean booked
“Booking requested” commonly says that a customer submitted a preference for a slot, room, table or service. It does not prove the provider has approved it, has space available or has issued a reservation confirmation. Translating “Request received” as “Your appointment is booked” advances the process by a step that the source did not establish.
An invented school example makes the distinction clear. A parent enters a preferred consultation time in a form, and the email says “We received your request.” The parent should not assume a place has been allocated unless a later message or system state confirms it. The target must preserve the same uncertainty. This applies equally to an event registration, equipment rental or travel service.
The reverse error can also happen. If the source explicitly states “Your booking is confirmed for Monday,” translating it as “Your request is being reviewed” understates a valid reservation and might cause the customer to fail to attend. Accuracy means preserving the state actually recorded, not always choosing the most cautious or least committed wording.
Before publishing, ask what evidence would prove the stronger status: accepted supplier record, issued confirmation, specific reservation identifier or verified provider message. If the source supplies none, do not invent one. The translation can say the request is pending in natural, helpful language.
Pending can apply to a booking or a change request
“Pending” is particularly dangerous because its referent is often silent. It may describe original appointment confirmation, payment authorization, identity verification, rescheduling, cancellation, eligibility review or a refund. The correct target should specify the object when context provides it.
The NHS App guidance for hospital appointments gives a useful example. If a patient requests to reschedule or cancel, the request may remain pending while the provider reviews it. If the request is not accepted, the appointment can remain booked. If accepted, the app may show the changed time or cancellation. Therefore “change pending” does not itself cancel the original appointment.
Commercial systems also distinguish processing from confirmed status. The Booking.com Demand API documentation lists separate car rental statuses including processing, not_confirmed, confirmed and quote. The source system’s definitions matter more than a translator’s generic idea of what pending usually means.
When the meaning is consequential, translate “cancellation request pending” rather than simply “cancelled,” or “awaiting booking confirmation” rather than “fully booked.” If the source is ambiguous, request clarification. A more definite target is not better when it reports the wrong state.
Waitlisted is an interest record, not a secured place
A waitlist generally shows that a person wants a place but does not yet have a confirmed one. A supplier may notify the person if capacity opens, offer a place subject to a response deadline, or use eligibility and priority criteria. None of that is a guarantee unless the provider actually commits to it.
A workshop might say “Added to waiting list for Thursday.” That does not mean Thursday’s workshop has a seat reserved for the person. A restaurant walk-in queue might estimate a waiting time; the estimate is not necessarily a confirmed dining reservation. A clinic could place a patient on a list before a specific appointment is scheduled. Translate each according to its real service and policy.
The phrase “Waitlist confirmed” can mean merely that inclusion in the waiting list was acknowledged. Do not turn it into “booking confirmed.” Likewise, “number 3 on the waitlist” describes a queue position under a particular system, not a promise that exactly three seats will become available.
An accurate target says whether the person is waiting, has received an offer, accepted the offer or has a confirmed place. These are stages. If a message does not specify what action comes next, do not invent payment or acceptance instructions.
Temporary hold is not necessarily final confirmation
Some providers place a temporary hold on a room, seat, booking slot or payment card. A hold can expire, depend on checkout or require another approval. A message “Seats held for ten minutes” does not mean the tickets have been purchased. “Room temporarily held pending payment” is not necessarily a final booking.
The word hold also applies to funds on a card, which is a financial state rather than proof that inventory is secured forever. A payment authorization can exist without a completed service purchase, depending on the payment and booking platform. A translator should identify what is being held: money, a timeslot, stock or a request.
A system may show both a temporary inventory hold and a pending payment status. That is possible and should not be rewritten into one simple confirmed state. If the hold has a source-stated expiry, keep the exact date and timezone. Do not invent a grace period because one is common elsewhere.
A clear customer-facing target may say “Your selected slot is being held temporarily until the stated deadline,” when supported. It must not claim that the customer can arrive without completing the required booking steps. Source conditions and actual confirmation determine the next action.
Confirmed means a particular item is booked
“Confirmed” is meaningful only together with the service and scope it identifies. A room booking for two people, a restaurant table for four, a clinic visit at 10 a.m. and a class consultation have different details. A translator should preserve the service, date, time, party or participant count, and any stated conditions rather than presenting confirmation as a vague universal success.
The Booking.com Demand API Orders FAQ describes its booked accommodation order as an active confirmed reservation, distinguished from cancellation and completed stay outcomes. This is a provider-specific status model, not a universal definition imposed on every reservation business. It illustrates why exact labels matter.
A confirmation may include an outstanding action such as presenting identification, paying a balance or checking in at a location. Do not strip those conditions when simplifying the message. Conversely, do not invent new conditions beyond the provider’s source terms.
A target that says “Your room is confirmed” should not be taken to mean the customer has already arrived, the stay is complete, or a full refund is guaranteed. Those are separate propositions. The correct translation keeps the booking strong enough to be useful without overstating it.
Booking confirmed is different from attendance confirmed
A positive reservation exists before a person attends the event. Actual attendance occurs later and must be recorded separately. A person can accept a school briefing invitation but miss the briefing. A customer can book a consultation and fail to appear. A guest can check in and leave before the booked service is completed.
The NHS Digital appointment-status guide distinguishes Available, Booked, Cancelled, Attended/Seen and DNA, short for Did Not Attend. The system’s approach is a useful example of why a booked slot should not be treated as an attendance record.
A school report that converts all confirmed consultation bookings into “parents attended” would be inaccurate. It could also inflate participation statistics. Similarly, a transport booking does not establish that a passenger actually boarded, and a restaurant confirmation does not prove the table was used.
Translate the reported state at the relevant stage. Before the event, a positive RSVP or confirmed booking concerns expectation. After the event, use actual attendance or service outcomes when supported. Do not backfill the latter from the former.
A proposed new time has not yet been accepted
A customer may suggest changing an appointment from 9 a.m. to 3 p.m. That request does not in itself free the original slot or reserve the new one. An organizer or supplier may need to review the proposal and update the booking. Translation should distinguish who suggested the time and who accepted it.
“Can you move it to Friday?” is a request. “Friday is available” reports availability, which may still require selection and confirmation. “We have moved your appointment to Friday at 3 p.m.” reports an accepted change if issued by the authoritative provider. All three can appear in one conversation, and each has different practical consequences.
Do not insert a confirmation reference that the source did not give. If a platform says the original booking remains active while a change request is pending, preserve that fact. A target that announces the original booking cancelled and the new one confirmed could cause the customer to miss the actual scheduled service.
The companion Calendar RSVP Status guide handles invitations and proposed meeting times. Reservation systems may add payment and supplier-approval steps, so use the specific booking record as the source of truth.
Reschedule requested versus rescheduled
“Rescheduling requested” describes an action initiated by a customer or another party. “Rescheduled” describes a changed appointment record under the provider’s process. The first is not proof of the second. The difference is important when customers must still attend the original appointment unless the change is approved.
The official NHS App guidance states that a requested appointment change can remain pending during provider review and that an unsuccessful request can leave the original appointment booked. This supports a careful translation of “change pending” rather than a premature claim that the appointment was moved.
Even when the provider confirms a reschedule, the target should preserve the new date, clock time, timezone, service location and relevant booking reference. A sentence saying “moved to next Tuesday” can be ambiguous if the source and target readers use different dates or the message is encountered much later. Use verified absolute dates when an authorized format requires them.
For QA, record three states: old appointment, change request, and new appointment. A target should not simultaneously present two conflicting confirmed times unless the source actually indicates two separate bookings. Clarify source ambiguities before creating a definitive-looking instruction.
Cancellation requested versus cancelled
A user may request cancellation before the provider actually processes it. “Cancellation requested” is an outstanding request; “booking cancelled” is a completed change to the identified reservation’s state. These are different statuses even when the provider normally accepts cancellations quickly.
A short reply “Request received” does not prove cancellation occurred. A subsequent message may say “Cancellation confirmed” and identify the booking or service affected. Translate that second status distinctly. If the request remains pending and the original booking remains live, do not tell the customer to assume it has ended.
Cancellation may also be subject to deadlines, approval or charges. The translator must preserve stated conditions and the exact event affected. Do not invent a free-cancellation entitlement or promise that a fee will be waived merely because the cancellation was requested before the event.
A clear target can name the entity: “We have received your request to cancel the 10 a.m. appointment,” compared with “Your 10 a.m. appointment has been cancelled.” The two sentences differ by a single underlying workflow transition, and that difference determines what a reader should do next.
Who cancelled: guest, provider or automated system?
A reservation can be cancelled by the customer, by a supplier or automatically under stated system rules. Those actors matter. Translating “provider cancelled” as “customer cancelled” changes responsibility and may mislead readers about fees, remedies or available next steps.
The Booking.com cancellation API documentation distinguishes accommodation statuses such as cancelled_by_guest, cancelled_by_accommodation and automatically cancelled. These are concrete examples of status codes carrying different event causes. A translation should preserve the distinction in both user-visible messages and machine-readable records.
If the source says “Cancelled by accommodation due to operational constraints,” translate that reason accurately. If no reason is given, do not invent one such as guest misconduct, payment fraud or equipment failure. A policy might define financial consequences, but they require separate source evidence.
Scope matters too. Cancellation of one room in a multiroom booking does not automatically cancel all rooms. Cancellation of one occurrence of a recurring appointment does not necessarily end the entire series. Keep the exact booking item and actor in the target.
No-show is not the same as cancellation
A no-show is an attendance outcome under the provider’s policy: the customer did not arrive or attend as expected. It should not automatically be translated as an advance cancellation or a voluntary refusal to use the service. A person may have intended to attend and encountered an unexpected obstacle. The status records nonattendance, not motive.
In NHS appointment data, DNA stands for Did Not Attend and is distinct from Cancelled and Attended/Seen. The NHS England guide to missed appointments discusses reasons such as inaccessible reminders, transport difficulties and other access barriers. That context demonstrates why translators should avoid judgmental language that attributes negligence from a bare no-show label.
A hotel no-show might have provider-specific fee terms, while a clinic DNA might have a separate follow-up process. Do not assume a universal penalty, cancellation right or rebooking rule. Translate the source-defined outcome and only the conditions actually attached to it.
A neutral target often says “did not attend the scheduled appointment,” with the date and person where stated. It does not need to imply the guest ignored the organizer. In customer care, respectful accuracy matters as much as terminology.
Late arrival may still count as attended
A person can arrive late and still receive service, arrive too late to be seen, or fail to arrive at all. These are separate events. Some systems have specific codes for late arrival with service and late arrival without service. A translator should not collapse all of them into “no-show.”
The NHS data definitions distinguish late arrival where a patient was seen from late arrival where they could not be seen. That illustrates the broader principle: arrival time, service start, and attendance outcome may be independently recorded. The same concept applies to training sessions, classes, airport transfers and service appointments.
A target that reports “did not attend” when a participant actually arrived but was turned away might lose a consequential distinction. On the other hand, showing up at the wrong time does not always meet a provider’s criteria for attendance; the actual system rules control the formal label.
When translating, preserve the description used by the record: “arrived late, seen,” “arrived late, not served,” or “not present,” if supported. Avoid inferring the reason or blame. A precise factual description is more useful than an emotionally loaded label.
Check-in, attended and completed describe different events
“Checked in” may report that a guest arrived or completed a registration step. “Attended” reports participation under a particular service’s definition. “Completed” may describe finished service, a stay or another terminal workflow state. These often follow one another but are not synonymous.
A customer can check in at a clinic and leave before being seen. A student can attend a workshop but leave before completing its activities. A traveller can arrive at a property without the full stay having finished. A target that says “service completed” solely from “checked in” adds an outcome.
Some booking systems transition to a completed state automatically after a certain time or after staff close an appointment. This may not be independent proof of customer satisfaction. Translate the recorded status honestly, using the provider’s actual definition where the difference matters.
A simple audit uses four fields: arrived, started, served or attended, and completed or closed. Fill only the fields the source supplies. The final translation can remain concise while preventing a record of arrival from becoming an unsupported claim that the promised service was delivered successfully.
Payment processing is separate from reservation confirmation
A customer may receive “booking confirmed; payment pending.” Depending on the supplier’s terms, that combination can be valid. Another provider may require payment before confirmation. Translation should not impose one universal booking-to-payment sequence on all systems.
“Payment authorized” can denote a temporary card authorization rather than final capture. “Deposit received” is not necessarily “balance paid.” “Pay at venue” is not equivalent to “prepaid.” These are financial meanings distinct from whether a slot or seat is reserved.
A target that turns “payment required before booking” into “booking guaranteed” can cause an unconfirmed customer to stop checking. Conversely, replacing “confirmed, pay on arrival” with “payment failed, booking cancelled” creates a false problem. The source provider’s actual terms determine the relationship.
Keep booking and payment in separate columns. Record status, amount, currency, due time and evidence for each. For refunds or cancellation fees, use further separate fields. This simple structure helps customer-facing messages stay clear without inventing financial outcomes.
Deposit, card authorization and final payment
A deposit may be a partial payment, a security amount or a payment whose refundability depends on specified terms. A preauthorization may temporarily reserve funds on a card. A final charge records a different financial event. Translators should not use one word for all three just because the customer sees an amount.
If a message says “card verified,” that is not automatically “full payment collected.” If it says “deposit received,” it does not necessarily prove the remaining balance was paid or the reservation is fully confirmed unless the provider states those things. The same source could show a deposit and a still-pending request.
Refund rules depend on the product, contract and cancellation cutoff. Do not promise that every deposit will be returned or retained. A translation should preserve “refundable until” and “nonrefundable after,” including exact monetary amounts and time zones when provided.
For quality control, identify whether each monetary statement is a hold, authorization, charge, deposit, balance due, refund approval, or refund settlement. An accurate service booking text can give the customer confidence without claiming money moved when the source only reports a provisional financial state.
Refund requested, approved, initiated and received
A cancelled booking can have several refund stages: request submitted, refund eligibility checked, refund approved, refund initiated, and funds received. These stages may be combined or labeled differently by individual providers, but they should not be assumed interchangeable. “Refund processing” does not mean the customer’s account has been credited.
Imagine a message “Your refund is approved.” This reports a decision under the supplier’s policy. It does not necessarily say the payment processor has settled the transaction. Another message “Refund issued” might describe a payment action, while a customer statement “Funds arrived” describes actual receipt. Translate each with the source’s claimed actor and evidence level.
If a cancellation fee or nonrefundable deposit is involved, the refund may be partial. Do not change its amount or currency. If the source provides an estimated refund window, preserve the wording and its uncertainty. Do not add a fixed number of banking days from an unrelated provider’s policy.
A good target explains what has happened and what remains pending. Customer service language is most helpful when it avoids falsely reassuring a person that a transaction is complete before the source system reports completion.
Cancellation fee and no-show fee may have different triggers
A provider may charge a fee for cancelling after a specified cutoff. It may also have a separate no-show fee for not attending without suitable notice. The amounts can overlap, but the triggering events are not necessarily identical. A translator must retain which action or nonaction the provider’s rule covers.
“Cancellation fee may apply” is a possibility, not proof the amount was charged. “Fee charged” reports a financial event. “Free cancellation until 6 p.m.” has a cutoff that must be interpreted in the relevant local time, not guessed from the reader’s timezone. A target that changes until to after can reverse the policy.
The word refundable also has an object: a deposit, part of a room rate, a ticket cost or something else. Do not translate “deposit refundable” as “entire reservation fully refundable.” The source may treat different charges separately.
For a reliable check, build a row with event, source policy, cutoff, fee amount, actual fee status and refund status. Unknown details stay unknown. A faithful translation should not sound as if it authored the booking terms itself.
A waitlist offer can expire before a booking is made
A provider may notify a person when a place opens up: “A seat is available; respond within two hours.” This is an opportunity or offer, not necessarily a confirmed booking. The person may need to accept, pay, or complete another step before being enrolled. Translating “offer sent” as “seat secured” could lead them to miss the deadline or travel without a valid reservation.
A different message may say “Your booking has been confirmed from the waitlist.” That reports a later state. The exact moment of confirmation depends on the source system. Some providers accept a person automatically from the queue; others require a reply. The translator cannot infer which process applies from the word waitlist alone.
A rank such as “position 4” does not guarantee a particular date or waiting time. The queue may depend on capacity and eligibility. A target should not invent a forecast merely because the source includes an ordering number.
The next-action question is decisive: must the user respond, continue waiting, or attend a confirmed appointment? The translated notification should support the same decision as the source while retaining any stated expiration time or conditions.
Hotel example: quote, booking, stay and no-show
A hotel can provide a quote before accepting a reservation. “Rate available” is not identical to “room confirmed.” A confirmed booking can remain active before check-in. “Stay completed” refers to a later event. “No-show” may be recorded if the guest does not arrive under the property’s policy.
The Booking.com Demand API distinguishes accommodation statuses such as booked, cancelled, stayed and no_show, as well as different cancellation initiators. These illustrate how a service can represent the booking lifecycle explicitly. Do not assume those precise codes govern an unrelated platform, but they are useful examples of distinct state meanings.
An order containing several rooms may have mixed product statuses. One room may be cancelled while another was used. A target saying “the entire booking was cancelled” without reviewing the item-level records could be misleading. Preserve room count, occupancy, dates and service type as provided.
An accurate accommodation translation keeps the distinction between offer, active booking, arrival, completed stay, and absence. It also separates cancellation policy from refund processing. That preserves reader expectations better than a generic “reservation successful” for every positive-looking message.
Restaurant example: waitlist, table request and actual reservation
Restaurants may operate both waitlists and reservations. “Added to waitlist” does not promise a table at a specific clock time. “Requested table for four at 7 p.m.” records a preference; the restaurant may still need to accept it. “Reservation confirmed for four at 7 p.m.” is a stronger statement about an allocated booking under the restaurant’s system.
Availability can also change. A listing that showed a table at 7 p.m. before checkout is not necessarily a completed reservation. Translating “available” as “booked for you” would invent the customer’s transaction. A reliable confirmation should come from the restaurant or authoritative reservation platform.
No-show and late-arrival terms vary by restaurant. Do not invent a universal grace period or fee. A dietary request attached to a reservation is not automatic assurance that the restaurant can meet it; preserve request versus confirmed accommodation.
For a restaurant message, identify exact date, party size, time, seating or service restrictions if stated, and status. The final target should tell diners whether they need to book, wait, reply, or arrive for a confirmed table, without pretending to check live availability.
School consultation: a preferred slot is not a confirmed class
Parents often request a time for a consultation, workshop or trial lesson. An email saying “preferred slot received” acknowledges the selection, while “consultation confirmed for Saturday at 10 a.m.” reports an accepted appointment under the organizer’s process. The first should never be translated as the second without provider confirmation.
A trial lesson can have separate steps for inquiry, availability, booking, attendance and registration. A parent may have requested a trial but not enrolled their child; attendance at a trial is not automatically enrollment in a recurring class. A waiting list for a small group is not proof the child’s place has been allocated.
A source may offer an alternative time if the preferred one is unavailable. “Can offer Monday at 4 p.m.” is an offer, not a completed booking if the parent must still respond. Keep the child or parent reference and any source-stated conditions accurate.
The easiest way to help a parent is to translate the actual next step plainly: reply with a preferred time, await confirmation, or attend a confirmed consultation. Avoid inventing teacher availability, fees, course entitlement or academic outcomes.
Healthcare appointment: referral and booking are separate
Healthcare systems can distinguish a referral, triage, appointment booking, requested change, attendance and completed consultation. A referral accepted by a service does not automatically mean an appointment time has been allocated. A booked appointment does not prove a patient was seen.
The NHS App help on appointments notes that a pending rescheduling or cancellation request can leave a booking unchanged until provider review. It also explains that some providers do not share all appointment information with the app. A missing app entry therefore does not always prove that an appointment has been cancelled.
Translate the provider’s authoritative statement and avoid inferring clinical outcomes. “Patient checked in” is not necessarily “consultation completed.” “Did Not Attend” is an attendance status, not a diagnosis or a claim about why the person did not arrive. Where patient safety or rights are affected, qualified review is necessary.
This is an administrative translation guide, not medical advice. Its central purpose is to prevent language from moving an appointment, inventing a completed visit or changing a referral status without source evidence.
Workshop, course and training enrollment stages
Training programmes may use labels such as interest registered, application received, eligibility pending, offer made, place accepted, enrolled, attended and completed. They are related but not equivalent. A student whose application is under review is not necessarily enrolled. A place offered may still need acceptance; enrollment does not prove attendance at every session.
Not every organization uses this same sequence. A short workshop could confirm registration immediately, while a competitive course could have several reviews. The translator should follow the original system rather than apply a universal admissions model.
A source may say “You have been shortlisted.” That can mean selection for further review, not final admission. “Registration closes Friday” states a deadline, not an event date. “Training completed” may report course work, while certification could require another assessment. Do not invent qualifications or guaranteed outcomes.
Use a compact learner record: person, course, application status, seat status, response deadline and actual attendance. Translate each source field separately. Families and students benefit from clear messages that tell them whether they should wait, accept an offer, pay or attend.
Multi-item orders and partial confirmation
An order may contain several products with independent statuses: one room booked, another cancelled, a transfer pending and a class seat waitlisted. A provider may calculate an overall order status using internal priority rules. Translators must not assume the overall label describes every item in ordinary language.
The Booking.com Demand API documents that overall status can follow a priority order when products in one accommodation order have different states. For example, an order can present a high-priority stayed state while another product has been cancelled. That is a product-specific aggregation rule. Read item-level detail before saying every room was used.
A customer-facing itinerary should preserve each confirmed service and unresolved part. If the flight is ticketed but the hotel is only requested, translating the entire trip as “fully booked” is misleading. Conversely, one cancelled add-on does not prove a confirmed core service vanished.
Use one row per service, with its own date, party count, reference and status. This approach is especially valuable for travel agents, events and bundled bookings. It keeps the complete picture without reducing mixed outcomes to one false sentence.
Dates, timezones, cutoffs and local clocks
A correct booking status is not enough if the target shifts the appointment time. “By Friday” generally sets a latest time, while “on Friday” targets the day itself. “Before 18:00” can differ from “at or before 18:00.” Cancellation cutoffs may use venue local time rather than customer local time. The translator should not guess an offset from the target language.
A date such as 05/11/2026 can be ambiguous across locale conventions. An authorized localization may use an unambiguous month name or the product’s defined date format, but only after verifying the intended source date. Recurring appointments may span daylight-saving changes, which means a named regional timezone can matter.
Booking reference IDs may be case-sensitive or include significant leading zeros. Keep them exact where machine-readable. A translated confirmation should not alter a room number, service code or URL merely to look natural. If the original does not provide a reference, do not invent one.
A useful review compares source date, local clock time, timezone, cancellation cutoff and target display. All should point to the same intended action and instant. Otherwise the translation could make a valid reservation unusable despite correct vocabulary.
One appointment or the entire series?
A recurring consultation may consist of many separate appointments. Cancelling one occurrence does not necessarily cancel all future lessons. Changing a Tuesday slot this week does not automatically alter every Tuesday. The correct scope depends on the source message and the provider’s recurrence rules.
If the source says “All remaining appointments cancelled,” retain all remaining. If it says “Next Friday’s appointment cancelled,” name that one occurrence. If the message leaves scope unclear and readers need to know whether to attend future sessions, seek clarification rather than generalize.
A refund or credit associated with one missed appointment also does not automatically settle the financial status of a whole package. Different providers use different fee and make-up policies. Do not infer entitlement from one generic cancellation word.
The checking question is “Which dates and which service items are affected?” A source-to-target table with occurrence IDs and statuses can make the distinction visible. That is more reliable than a single summary saying the booking was changed when only one appointment moved.
No response, not confirmed and unavailable
“No response” describes an absent or unrecorded reply, not necessarily a decision. “Not confirmed” describes a reservation that has not reached the source’s confirmed state, or confirmation not yet provided. “Unavailable” states that the relevant resource or time is not available according to a particular check. These are different negatives.
A request left unanswered is not proof the supplier rejected it. A pending reservation is not necessarily sold out. A slot unavailable at one moment is not necessarily unavailable forever. A waitlist may still be operating when no immediate places can be booked.
A translation that says “declined” where the source says “no response” imputes a decision. A target that says “guaranteed available tomorrow” from a momentary search result invents future inventory. The right message describes exactly which information is missing or which state the provider recorded.
Ask who or what is absent: response, confirmation, slot or completed transaction? Translate that object, leaving the others unknown. This simple negative-scope check can prevent needless calls, failed visits and false assurances.
Confirmation subject to conditions
A source may say “booking confirmed subject to valid identification,” or “room held pending deposit.” These phrases combine a status with a condition. Dropping the condition can make the target appear unconditional; inventing an additional requirement can make a valid confirmation look uncertain.
The key question is whether the provider states that a reservation currently exists, whether a temporary hold exists, and what action is still required. “Identity must be shown at check-in” does not necessarily mean “identity already verified.” A verified payment method is not proof every condition was fulfilled.
A helpful target can state the confirmed object and the outstanding source-supported requirement in separate sentences. It should not add unverified penalty fees, documents or staff instructions simply to be more detailed.
When an authorized system uses controlled terms, keep them consistent across the email, booking page and reminder. A reader should not see “confirmed” in one language and “pending” in another for the same recorded state unless the original truly describes different entities.
AI translation risks false confirmations
Automated translation may expand “slot requested” into “appointment confirmed” because those phrases often appear in the same workflow. It may turn “waitlist invitation offered” into “seat allocated,” “refund processing” into “money returned,” or “reschedule pending” into “new booking active.” Such changes make prose fluent but factual status wrong.
A robust QA prompt first extracts the source entity, actor, state, time, condition and next action. The target draft must preserve that record. A second checker can read the target alone and extract the same fields. If a field changed without source evidence, reject the output.
Machine-readable status codes should remain unchanged unless the user explicitly authorizes a corresponding data transformation. If a database uses the code no_show, translating the visible label does not require mutating the stored code or falsely calling it cancelled. Interface terminology and underlying state must remain aligned.
A model may also invent cancellation fees or time limits based on common policies. Do not accept unverified additions. Translation communicates the provider’s actual statement, not a suggested future workflow.
Four-week learning plan for booking-status translation
Week 1: Learn the basic states. Practise with twenty invented messages using requested, pending, waitlisted, confirmed, cancelled and no-show. For each message, write the exact entity described, the source status, and one stronger false inference to avoid. Translate the correct reading naturally into the target language.
Week 2: Learn transitions. Pair cancellation requested with cancelled, reschedule suggested with rescheduled, waitlist offered with seat confirmed, and refund approved with refund received. Create an event timeline for each pair. Check that the target does not report the second stage when the first is all that happened.
Week 3: Add consequential details. Use cases for a hotel, school consultation, restaurant and clinic. Include dates, group size, time zone, deposits, cutoffs and recurring appointments. Preserve source terms and avoid inventing provider policies. Ask a domain reviewer which details actually matter to a reader’s next action.
Week 4: Audit translated messages. Create ten deliberately flawed examples involving false confirmation, changed party size, incorrect cancellation actor, premature refund, invented grace period or false no-show. Ask a bilingual reader to find and correct them. Finish with a verified glossary, not a universal one-word map.
This four-week practice method builds the habit of separating events, policies and evidence. The goal is not to memorize labels but to recognize exactly what a short service message does and does not say.
Ten-step source-to-target booking audit
1. Identify the provider and relevant service. 2. Read the complete booking notice, not only the status label. 3. Determine whether it concerns reservation, change request, payment, attendance or service completion. 4. Identify who initiated or approved the action. 5. Record the source status without upgrading it.
6. Preserve date, time, timezone, booking reference, service, guest count and scope when provided. 7. Check any conditions, cancellation policy, fee or response deadline against the source. 8. Translate into natural target grammar while preserving state and certainty. 9. Ask a target-language reader what they would do next. 10. Compare that action with what a careful source-language reader would do and fix any mismatch.
For high-stakes medical or financial notices, qualified review may be necessary. Translation cannot establish the provider’s live booking availability or certify a payment merely through fluent text. A source ambiguity should remain visible or be clarified by the responsible party.
The result should be auditable: someone can show which original phrase supports the translated booking status and which details are still unknown. The best message is not necessarily the shortest. It is the one that enables the right next step without inventing a reservation.
Twelve practice messages and the correct interpretation
1. “Booking requested.” A request exists; confirmation is unknown. 2. “Confirmation pending.” Some verification remains unresolved. 3. “Waitlisted for Monday.” A place is sought, not guaranteed. 4. “Seats temporarily held.” A hold exists under source terms, not necessarily a final purchase.
5. “Confirmed for two guests.” A reservation for the stated party is reported active. 6. “New time proposed.” An alternative is suggested, not yet accepted. 7. “Cancellation request under review.” A request is pending; original booking may remain valid. 8. “Appointment moved to Thursday.” The provider reports a changed appointment date.
9. “Cancelled by supplier.” The supplier initiated cancellation, not necessarily the customer. 10. “No-show recorded.” The provider recorded nonattendance under its rules; no motive is established. 11. “Checked in, waiting.” Arrival is recorded; service completion is not. 12. “Refund processing.” Financial settlement remains unresolved.
For each practice message, expand the status in plain language and translate it into the target language. Then write one overconfident version that would be wrong: confirmed instead of requested, attended instead of booked, refunded instead of processing, or negligent instead of absent. A short counterexample exposes the factual boundary quickly.
Frequently asked questions
Is a booking request a booking confirmation? No. The provider may need to approve it. Does pending mean rejected? No. It can mean many unfinished stages; check the object. Is a waitlist a guaranteed place? Not ordinarily. Does confirmed mean I attended? No, attendance happens later.
Does proposing a new time reschedule automatically? Not necessarily. Is cancellation requested the same as cancelled? No. Does cancelled mean refunded? No. Refund entitlement and money received are separate. Does a no-show imply deliberate refusal? No. It records nonattendance under provider criteria.
Can a late attendee still be served? Yes, depending on the provider. Can a booking be confirmed while payment is pending? Some systems allow this; follow the source rules. Does a temporary hold guarantee a seat? Not necessarily. Can one order contain mixed item statuses? Yes, depending on the booking platform.
What if an appointment is missing from an app? Follow the provider’s authoritative record and instructions; absence from one app does not always prove cancellation. What if the source status is ambiguous? Ask for clarification instead of guessing. How do I avoid AI mistranslation? Compare entity, status, actor, time and condition before publishing.
Verified sources and connected articles
For the editorial system, start with Master Art of Translation. Follow the Calendar RSVP Status guide for guest responses and new-time proposals, and the Short Email Replies guide for the difference between receipt, acknowledgment, promise and completed work.
Provider-specific references include NHS Digital Appointment Status, NHS App appointment help, Booking.com Demand API order states and Booking.com cancellation states. These documents demonstrate how actual systems define statuses; they do not make one provider’s rules universal.
The final rule is to translate the recorded stage, not the next stage you expect. Requested is not confirmed. Waitlisted is not enrolled. A proposed time is not a completed reschedule. Cancelled is not refunded. No-show is not a statement of motive. When these limits survive, booking communications become genuinely useful across languages.