The pre-deployment checklist before AI touches a client

# The pre-deployment checklist before AI touches a client

Three weeks before launch, the room goes quiet. A creative director at a European maison asks the AI product lead one question: "If this styling assistant recommends a look that insults a client, who catches it before she sees it?" Nobody has a clean answer yet. The launch gets paused.

This scene repeats across the luxury sector more than brands admit. A go/no-go review, the formal gate where stakeholders decide whether a system is ready for real clients, is where good intentions meet operational reality. This lesson walks through what that review should actually check.

Why luxury needs its own checklist

Luxury AI carries risks that generic retail AI does not. A client-facing chatbot mispricing a sweater is embarrassing. A styling assistant making assumptions about a client's body, race, or budget based on their name or address is a brand crisis and, in Europe, a potential violation of the EU AI Act (the European Union's risk-tiered AI regulation, in force since 2024 with phased obligations through 2027).

The EU AI Act classifies systems by risk. Most client-facing luxury AI (styling advice, personal shopping, sizing recommendations) sits in the "limited risk" or "minimal risk" tier, but anything touching biometric categorization or emotion inference (think: a smart mirror inferring mood or ethnicity to tailor a pitch) can trigger "high-risk" obligations: documented risk management, human oversight, and technical documentation available to regulators. Full text: EU AI Act overview, European Commission.

In the US, there is no single federal AI law yet as of early 2026. Instead, luxury brands face a patchwork: the FTC (Federal Trade Commission) enforcing against "unfair or deceptive" AI practices, state laws like Colorado's AI Act (effective 2026, targeting "high-risk" consequential decisions), and California's various AI transparency and automated decision-making rules. A maison operating in both markets needs one governance framework that satisfies the stricter regime, usually the EU's.

The five checks that matter most

1. Bias testing

Bias testing means systematically checking whether a model's outputs differ unfairly across protected or sensitive groups (gender, ethnicity inferred from name, body size, geography).

For a styling assistant, this means running the same client profile through the model with only one variable changed, say, a name typically associated with a different ethnicity, and comparing recommendations. Do luxury tiers of product get suggested less often? Does language shift in tone or formality?

A simple test harness:

test_profiles = [
    {"name": "Amara Okafor", "budget": 5000, "occasion": "gala"},
    {"name": "Charlotte Dubois", "budget": 5000, "occasion": "gala"},
]

for profile in test_profiles:
    response = styling_model.recommend(profile)
    log_response(profile["name"], response.tier, response.tone_score)

Run this across hundreds of profile pairs before launch, not after a client complaint. Document the results. This documentation is exactly what the EU AI Act expects for high-risk systems, and it is good practice even when the system is not formally high-risk.

2. Escalation paths

An escalation path is the predefined route a flagged case takes to a human. Before launch, the review must answer: what triggers escalation, and who receives it?

Concrete example: if a client asks the styling assistant about a bereavement outfit, or mentions a medical condition affecting fit, the system should stop generating autonomous advice and route to a human client advisor within a defined time window (many maisons target under 15 minutes for VIP tiers). Test this path with simulated edge cases before go-live, not during it.

3. Human override points

A human override point is a place in the workflow where a person can stop, correct, or veto the AI's output before the client sees it. For client-facing luxury AI, the industry norm converging in 2026 is "human-in-the-loop" for anything involving final purchase recommendations above a price threshold, and "human-on-the-loop" (monitoring, not gating) for lower-stakes suggestions like accessory pairing.

The go/no-go review should force a walkthrough: show me, live, where a stylist can intercept a bad recommendation before it reaches the client app. If nobody can demonstrate this in the room, that is a no-go.

4. Brand-voice audit

A brand-voice audit checks whether AI-generated language matches the maison's tone, register, and values, not just factual accuracy. This is distinct from bias testing: a technically unbiased response can still sound wrong for a house known for restraint, or too casual for a house built on formality.

Practically, this means a panel (often merchandising plus brand plus a language model evaluator) scores a sample of 100 to 200 generated responses against a rubric: formality, cultural sensitivity, house-specific vocabulary, absence of competitor mentions. Anything below threshold gets retrained or hard-coded with guardrail prompts.

5. Data lineageData lineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète →

Data lineageData lineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète → is the documented trail of where training and input data came from, how it was processed, and who has rights to it. For luxury, this matters twice over: client purchase history is highly sensitive personal data under GDPR (General Data Protection Regulation, the EU's data protection law), and any imagery or style data scraped from runway shows or editorial content may carry copyright exposure.

The review must confirm: is client data used to train this model, and did clients consent to that specific use under GDPR Article 6 (lawful basis for processing)? If the answer is unclear, that alone is grounds for delay. See the ICO's guidance on AI and data protection for a practical framework, applicable in spirit even outside the UK.

What a go/no-go review actually looks like

In practice, this is a one-hour meeting with a written scorecard, not a vibe check. A realistic structure:

| Check | Owner | Status 3 weeks out | Blocking? |

|---|---|---|---|

| Bias testing across 5 sensitive attributes | Data science | Amber, 2 attributes untested | Yes |

| Escalation path tested end-to-end | Client experience | Green | No |

| Human override demoed live | Product | Red, no demo available | Yes |

| Brand-voice audit, 150 samples scored | Brand/marketing | Green | No |

| Data lineageData lineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.Voir la définition complète → documented, consent confirmed | Legal/privacy | Amber, awaiting DPO sign-off | Yes |

Three "blocking" reds or ambers means no-go, full stop, regardless of marketing timelines. The scorecard forces the room to separate "we're excited to launch" from "we're ready to launch."

🎬 [VIDEO: "AI Governance Explained: How Companies Manage AI Risk" - youtube.com - a clear walkthrough of enterprise AI risk frameworks applicable to client-facing deployments]

Model risk beyond the five checks