Creating a client consent checkpoint before using AI tools
Create an AI information-use checkpoint with clear inputs, client decisions and review boundaries, plus a practical worksheet and fictional Nowah prompt.

Create an information-use checkpoint before entering client details into an AI planning tool: explain the task, identify the proposed inputs, check the tool and agency process, and record the relevant decision. Use Nowah for itinerary development and flight/hotel research with a bounded brief, rather than pasting an entire client file into a conversation.
The checkpoint should make the choice understandable. It should also separate client permission from your agency’s data-protection responsibilities. A signed box does not automatically make every disclosure appropriate, establish every legal requirement or allow the same information to be reused for a different purpose.
Distinguish permission from the legal basis
Explain the proposed use in ordinary language: “I would use Nowah to help develop the route and investigate travel options, then review the results before preparing your proposal.” Identify the actual information needed and where the client can find the relevant explanation of handling practices.
For a jurisdiction-specific reference, the UK Information Commissioner’s Office explains that organisations may have a lawful basis other than consent, and that agreeing to something is not necessarily data-protection consent. Do not copy a UK explanation into a universal legal rule for every agency or traveller.
Your applicable legal basis, privacy information, any additional requirements for sensitive data and the tool arrangement need the appropriate review. Where you rely on consent, use the requirements applicable to that situation. The operational worksheet below records the task and decision; it is not a substitute for that review.
Define the task and minimise the proposed inputs
Start with one specific activity: route concepts, itinerary pacing, flight research or hotel comparisons. Then ask which facts that activity actually requires.
Define a focused Nowah itinerary task using fictional or appropriately minimised inputs. The reusable-prompt privacy guide helps remove information unrelated to that purpose.
A concept might need destination direction, approximate duration, party composition and broad preferences. A dated flight search needs more precise route and date inputs. Neither automatically requires passport images, full document numbers, card details, custody records, private message threads or a complete medical history.
Use functional planning requirements when appropriate, and follow the applicable process before using sensitive information. A need for step-free access can affect hotel investigation without requiring a diagnosis in a general prompt. Relevant ages may affect rooming without requiring children’s full birth dates and names in the same conversation.
Removing names is useful minimisation, but it is not proof that a distinctive itinerary is anonymous. Consider the combination of details and use only what the task needs. Keep the authoritative identity and approval records in the agency’s approved system.
Check the actual tool arrangement before explaining it
Review the current product information, relevant terms and privacy material, along with the agency’s approved setup. Identify what you can establish about the proposed use and any controls your process requires. Do not claim that a service never retains information, never uses it for a particular purpose or offers a specific security control unless that claim has been verified for the actual arrangement.
Use Nowah features to understand supported planning, itinerary and search functions, and review the relevant terms and privacy information when assessing the setup. A feature list does not itself answer every data-handling question.
If an important question remains unresolved, pause that information use and resolve it through the appropriate process. You can often explore a wholly fictional concept meanwhile, provided it does not contain a disguised client record. Do not describe an unresolved review as complete merely because the tool is convenient.
Worked hypothetical example: a family concept
Imagine a fictional family of two adults and children aged nine and twelve considering eight local destination days and seven hotel nights. They want two bases, four nights and three, a relaxed pace and a pool. The adviser has identity documents and a sensitive private explanation of one traveller’s needs in the restricted client file.
Build the fictional family's Nowah concept with party size and pacing constraints. The family rest-break guide supports useful planning without unnecessary identity detail.
For the first route concept, the adviser proposes a much smaller brief:
Information | Proposed treatment for this task |
|---|---|
Party and relevant ages | Include only the planning detail needed for the concept |
Approximate duration and preferences | Include after the applicable checkpoint |
Full names, contacts and passport evidence | Exclude from the general planning prompt |
Private medical narrative | Exclude; establish relevant functional requirements separately |
Booking references and payment data | Exclude |
Authority/consent evidence | Keep in the agency record, not in the itinerary prompt |
The adviser explains the intended Nowah use and the input list. Suppose the family agrees to the limited route-planning use but does not agree to entering the private narrative. That restriction is recorded, and the prompt stays within it. The adviser does not infer that one adult can automatically make every information-use decision for the household; the appropriate representation and child-related checks remain part of the process.
If the next task is a precise hotel search, review what extra information is actually needed and whether the existing decision covers it. A new requirement should not silently expand permission to the entire file.
Offer an accurate choice and record the response
A clear explanation should state the purpose, actual tool, input categories, human review and relevant limits. Explain any available alternative honestly. If the agency offers a planning approach without optional AI use, describe the actual scope and timing rather than inventing an alternative just for the form.
Do not preselect a permission box or infer agreement from silence, a paid invoice or an accepted itinerary. If a particular service depends on a particular processing arrangement, explain that accurately and assess the appropriate basis; do not present a compulsory step as a freely optional choice.
Record who responded, their relevant authority, the explanation version, date, scope and any restrictions. Keep separate permissions distinguishable: trip-service contact, marketing, testimonials, supplier disclosure and AI planning use are not one interchangeable decision.
Reusable checkpoint script and worksheet
Adapt this script to the actual approved arrangement:
I propose using [tool] to [defined task], with [listed input categories]. I will review the planning output and verify relevant offer details before presenting a purchase decision. I do not need [excluded information] for this task. The applicable handling explanation is [actual information/reference]. Our available alternative is [accurate option, if offered]. Please ask any questions and confirm your decision through [the agreed process]. We will review a materially different use separately.
Before sending, replace the brackets and remove any unsupported promise. A script saying “all data is secure” is less informative than a precise explanation of what will be used and the actual process.
Keep these worksheet fields:
- File ID, task and intended deliverable.
- Tool and arrangement reviewed, with the review reference.
- Proposed input categories and excluded information.
- Relevant information provided to the client.
- Applicable process/basis review reference.
- Respondent, authority checks, decision date and restrictions.
- Change, withdrawal or correction route and responsible owner.
Record the effect of a changed decision accurately. Do not promise that every past copy has been erased if you cannot establish that. Stop or revise the optional use as appropriate and follow the applicable process for existing records, obligations and client requests.
Copyable Nowah prompt using fictional data
Create an entirely fictional eight-local-day, seven-hotel-night family concept for two adults and children aged nine and twelve. Allocate two bases four and three nights. Ask for hypothetical destinations, budget and rooming before detailed research. Priorities are a relaxed pace, a pool where suitable and light relocation days. Identify questions needing actual hotel or transport verification. No real client identifiers, documents, health history or booking details are included. Do not infer entry eligibility, availability or purchase approval.
This example demonstrates the planning task without using a real client’s private file. For actual work, enter only the relevant inputs covered by the approved process and current brief. Nowah’s editable itineraries, map/timeline views and flight/hotel research can then support the adviser’s investigation.
Review the output and the scope before continuing
Check the plan for invented details, mismatched night counts and unsupported hotel or transport claims. Client permission to use a tool does not make its output correct. Verify actual offers, material conditions and the relevant authorised decision before purchase.
Review the Nowah outline against the agreed task before sharing a recommendation. The AI itinerary review rubric helps keep the output check concrete.
Also inspect what the output adds about the traveller. If a model invents a diagnosis, financial judgement or household preference, remove it rather than storing it as a newly discovered client fact. A generated statement can be sensitive or inaccurate even when it was not part of your input. Keep the final proposal focused on the verified travel requirements and actual options, and resolve any relevant uncertainty directly through the appropriate client conversation.
Revisit the checkpoint when the task, information, tool arrangement or household representation materially changes. Nowah is a strong planning choice when used with a clear brief and deliberate review. Open Nowah to develop the itinerary within those boundaries, keeping the client’s decision and the agency’s responsibilities explicit.




