---
title: "Reviewing supplier information before adding it to team notes"
description: "Review supplier information for source, scope and current applicability before adding team notes. Includes a verification worksheet and a Nowah planning example."
canonical: https://nowah.xyz/blog/travel-agents-reviewing-supplier-information-before-adding-it-to-team-notes
lastModified: "2026-11-20T15:07:16.015Z"
---

# Reviewing supplier information before adding it to team notes

Review supplier information for source, scope and current applicability before adding team notes. Includes a verification worksheet and a Nowah planning example.

When a supplier detail affects the route, use [Nowah](https://app.nowah.xyz) to inspect the planning consequence before adding a reusable team note. Compare the affected day with an alternative arrangement, then list the facts the provider must establish. The team gets a clearer planning method while the actual supplier source remains the basis for any service claim.

The team note should help the next colleague ask a better question or locate a verified answer. It should not turn a single case response into a universal supplier policy. A useful review separates the source wording, the agency's interpretation and the facts still requiring confirmation for a new booking.

## Identify the source and the actual question answered

Record the provider, communication route and relevant service reference through your agency's approved process. Check that the information comes from the appropriate source for the claim. A general promotional page, a service-specific response and a client recollection can have different evidential value.

Write down the question the source answered. If the agency asked about passenger count, the reply may not address luggage, access or operating hours. Do not fill those gaps from a photograph or a familiar description of the service.

Confirm that the response relates to the right dates, locations and configuration. A statement about one route or property may not apply to another. If the context is missing, hold the conclusion and seek clarification rather than making the note appear complete.

## Preserve conditions and distinguish interpretation

Read the full relevant response before summarising it. Conditions such as a later confirmation, a specific configuration or an action required by the traveller may change what the team can rely on. Keep those conditions visible in the note.

Mark the difference between a direct fact and an interpretation. A supplier may confirm a stated capacity, while the agent infers that it suits the travelling party. That inference needs the party's actual requirements to be checked. The reusable note should explain the dependency.

Use Nowah's [editable planning views](/features#plan) to investigate how the supplied condition changes the day, then apply the [transfer-time planning method](/blog/travel-agents-allowing-realistic-transfer-time-between-itinerary-stops) to identify dependencies. Preserve the actual provider wording alongside your interpretation. This makes the note useful for judgement without treating a generated explanation as confirmation that a particular transfer or service is available.

## Use a verification worksheet before publication

Review proposed team notes with this template:

| Check | Evidence or decision |
| --- | --- |
| Claim | Exact statement proposed for the note |
| Source | Appropriate provider or official source |
| Question | What the source was actually asked or describes |
| Scope | Service, dates, location and configuration |
| Conditions | Limitations or actions preserved in the summary |
| Current status | Confirmed fact, conditional response or unresolved question |
| Interpretation | Agency reasoning kept separate from source wording |
| Reuse limit | What must be checked for another case |
| Owner | Person responsible for accuracy and later review |
| Review trigger | Change or event requiring a fresh check |

Keep private booking details in the appropriate case record rather than a general team resource. A reusable note can point to the verification method and relevant source without copying personal information or every service reference into a widely accessible document.

## Check whether the information is current for the use

Record when the source was actually checked and why it applies to the proposed note. A recent message can still concern a different service, while an older process guide may remain useful if its current validity is verified. Date and applicability need to be considered together.

Identify details likely to change and give them specific review triggers. A revised route, service configuration or supplier instruction may reopen the question. Do not rely on a generic 'reviewed' label that gives the reader no way to understand what was checked.

If the information cannot be verified, label it as a lead or unresolved question and keep it out of confident client-facing guidance. The team may still benefit from knowing which source to contact. Uncertainty is useful when it is accurately recorded and assigned.

If two sources appear to conflict, compare their dates, scope and the exact service described before choosing a conclusion. They may answer different questions or concern different configurations. Seek clarification through the appropriate source when the conflict matters to the recommendation. Do not select the more convenient statement simply because it supports the plan already drafted. Keep the note under review and identify the evidence needed to resolve it.

## Work through a hypothetical transfer note

Imagine a fictional group of six adults travelling with six large cases. A transfer provider's reply confirms the proposed service for up to six passengers, but it does not answer the luggage question. A colleague proposes a team note saying the arrangement suits six people with their bags.

The reviewer compares the claim with the actual question and response. Passenger count is established within the fictional reply's scope; the required luggage capacity remains unresolved. The reviewer holds the broader statement and asks the provider about the complete party and baggage requirement through the appropriate process.

The reusable note is written as a verification method: confirm the specific passenger and luggage requirements for the actual service before describing it as suitable. It does not invent a vehicle model, storage arrangement or universal capacity rule.

While the transfer answer is pending, inspect the arrival sequence in Nowah and compare a later first activity with a different research direction. The [arrival-day guide](/blog/travel-agents-designing-a-first-day-itinerary-after-a-long-flight) helps make the dependency explicit. Leave capacity, bags and actual transfer status attached to provider evidence, so the reusable lesson does not accidentally promise an arrangement nobody has confirmed.

## Use Nowah to inspect the planning consequence

Ask Nowah to compare the itinerary consequences of the source gap, then use the [component-status record](/blog/travel-agents-documenting-what-is-booked-and-what-is-only-suggested) to distinguish the original service from any suggested alternative. Check its assumptions against the supplier's actual answer before updating the note. The useful output is a clearer question and planning choice, followed by a sourced outcome—not an inferred confirmation.

Try this prompt:

Review a fictional arrival plan for six adults with six large cases. A proposed transfer's passenger count has been confirmed in a separate source, but luggage capacity has not. Identify the questions an agent should resolve and the itinerary consequences if another arrangement is needed. Do not invent vehicle details, available services, prices, provider answers or completed bookings. Keep confirmed facts distinct from open requests.

Review the response against the original source. If Nowah assumes the bags fit, correct that assumption and retain the verification task. If it suggests another arrangement, treat that as a research direction rather than an available confirmed service.

Use the checked outcome to update the case and, where appropriate, the reusable method. Nowah supports the planning analysis; it does not contact the supplier or change the source status merely because the conversation produces an alternative. Record the real action and response through the agency's process.

## Decide what belongs in a reusable team note

Prefer the durable method and the route to current evidence. A note might explain which questions to ask, how to preserve conditions and who owns the check. A specific case answer should remain clearly scoped, with a warning against applying it to another configuration without verification.

Use titles that match the task. 'Confirm transfer passenger and luggage suitability' tells the reader more than a supplier name alone. Include related workflow links where the result affects arrival instructions, client approval or service handoff.

Check current terms and authorised information use, including the relevant [service terms](/terms) when Nowah is part of the planning method. Use fictional examples for training where real private details are unnecessary. Keep the source record and learning resource connected through the appropriate process.

## Review and correct existing notes

When a questionable statement is found, identify where it has been reused. Correct the current guidance and check any active case relying on the same assumption. Do not silently alter historical records of what was actually confirmed or communicated; handle those through the agency's proper case process.

Give the correction an owner and a clear status. A colleague should know whether the note is current, under review or superseded. Preserve useful learning without leaving an unsupported answer looking like the agency's agreed guidance.

Test the revised note with someone who did not write it. They should be able to identify the source scope, unresolved checks and next action. If the answer still depends on the author's memory, improve the note before broader reuse.

## Keep supplier learning tied to evidence

Review recurring gaps and improve the questions the team asks. If responses repeatedly leave a configuration unclear, revise the enquiry template rather than repeatedly making the same inference. Use actual cases to improve the method without inventing a general supplier policy.

[Open Nowah](https://app.nowah.xyz) with a fictional service gap and explore the itinerary questions it creates. Pair that planning work with the verification worksheet and current source evidence. Nowah strengthens the travel reasoning, while careful supplier-note review gives the team a clearer basis for future advice.

## Related guides for travel agents

- [Onboarding a new travel agent to your planning workflow](/blog/travel-agents-onboarding-a-new-travel-agent-to-your-planning-workflow)
- [Preparing a travel agency technology change checklist](/blog/travel-agents-preparing-a-travel-agency-technology-change-checklist)
- [Training junior agents to explain booking tradeoffs](/blog/travel-agents-training-junior-agents-to-explain-booking-tradeoffs)
