Le Rédacteur de Piste d'Audit des Décisions IA : Transformer une Décision Assistée par IA en Dossier de Conformité Défendable
Pourquoi ce prompt est important
Regulations like the EU AI Act's Article 14 human-oversight requirement and a growing number of U.S. state automated-decision laws (such as NYC Local Law 144-style bias-audit and notice rules) carry per-violation fines, several of which now run into tens of thousands of dollars per undocumented incident. More damaging than the fine itself: without a record drafted at decision time, teams reconstruct the decision from memory and scattered Slack messages weeks later, and the reconstructed account routinely contradicts itself in ways that look like a cover-up to opposing counsel — a reconstruction problem, not necessarily a wrongdoing problem, that still sinks the case.
À quoi nous l'utilisons
An HR coordinator used an AI resume-screening tool to auto-reject 40 candidates for a mid-level engineering role on a Tuesday afternoon. On Friday, legal receives a demand letter from a rejected candidate's attorney alleging discriminatory screening, and compliance needs a complete audit-trail record for this specific candidate within 48 hours — including what data went into the AI tool, what it recommended, and who signed off — before legal can respond.
Prompt
Role: Act as an AI governance and compliance documentation specialist who has written audit trails that held up under regulator review and legal-discovery scrutiny. Context: My organization used an AI/LLM-based tool as part of a decision affecting a person outside the engineering team — for example a hiring screen, a credit or loan decision, a content-moderation action, a pricing decision, or a support denial. Decision type: [DECISION TYPE]. The AI tool used: [AI TOOL/MODEL NAME + VERSION]. Decision date: [DECISION DATE]. Applicable regulatory framework, if any: [REGULATORY FRAMEWORK, e.g. "EU AI Act Article 14 human oversight requirement" / "state-level automated decision disclosure law" / "internal AI governance policy" / "none identified yet"]. Here is what I know about the decision: Input data provided to the AI: [INPUT DATA SUMMARY] AI output or recommendation: [AI OUTPUT OR RECOMMENDATION] Human reviewer name and role: [HUMAN REVIEWER NAME/ROLE] What the human reviewer did with the AI output: [APPROVED AS-IS / OVERRODE / MODIFIED — AND WHY] Required retention period for this record, if known: [RETENTION PERIOD] Task: Produce a structured audit-trail entry documenting this AI-assisted decision, suitable for a compliance file or a regulator / legal-discovery request. Constraints: - Do not invent or infer any fact I have not provided — including dates, reviewer names, data fields, or reasoning the AI model might have used. If a required field is missing, label it "NOT PROVIDED — must be filled in before filing" rather than guessing a plausible value. - Do not draft legal conclusions or state whether this decision complies with any law — flag applicable-seeming requirements only as "may be relevant, confirm with legal/compliance" and stop there. - Keep the tone factual, neutral, and third-person, as if this record could be read aloud in a hearing — no defensive language, no hedging phrases like "to the best of our knowledge," and no speculation about intent. - Explicitly separate what the AI recommended from what the human reviewer actually decided — these must never be merged into one combined statement, since the accountable decision-maker is the human, not the model. - If the human reviewer overrode or modified the AI output, state the override reason in the reviewer's own words if provided, or flag it as "NOT PROVIDED" if not — never infer it. Output Format: 1. Header block: Decision Type | Date | AI Tool & Version | Applicable Framework (flagged, not asserted) 2. "Input Summary" — bullet list of what was fed to the AI, in plain factual language 3. "AI Output" — exact restatement of what the AI recommended, clearly labeled as AI-generated, not a statement of fact 4. "Human Review" — reviewer identity, action taken (approved / overridden / modified), and stated reasoning 5. "Gaps Flagged" — a bare list of any NOT PROVIDED fields that must be filled before this record is filing-ready 6. "Retention Note" — the stated retention requirement, or "NOT PROVIDED — confirm with compliance" if absent
Résultat
Decision Type: Candidate Screening — Automated Resume Rejection Date: 2026-10-06 AI Tool & Version: ScreenFit AI Resume Matcher v4.2 Applicable Framework: NYC Local Law 144 automated employment decision tool bias-audit requirement may be relevant — confirm with legal/compliance.
Input Summary: - Candidate resume (PDF, 2 pages) submitted via careers portal on 2026-10-04 - Job requisition: Senior Backend Engineer, req #ENG-2291 - Screening criteria configured in tool: minimum 5 years backend experience, required Python/Go proficiency, degree-equivalent experience accepted
AI Output: ScreenFit AI Resume Matcher scored the candidate 41/100 against the configured criteria and recommended "DO NOT ADVANCE," citing "insufficient backend-specific keyword match" and "employment gap exceeding 18 months unexplained in resume text." This is the AI tool's generated output; it is not a statement of fact about the candidate's actual qualifications.
Human Review: Reviewer: J. Alvarez, Talent Acquisition Coordinator. Action taken: Approved the AI recommendation as-is; no override. Stated reasoning: NOT PROVIDED — must be filled in before filing. The recruiter did not record a rationale beyond accepting the tool's score; the recruiter should be asked directly whether the resume was independently reviewed before rejection.
Gaps Flagged: - Human reviewer's independent reasoning for accepting the AI score: NOT PROVIDED - Confirmation of whether a bias audit has been run on this tool configuration for this job requisition: NOT PROVIDED - Candidate's protected-class information, if any claim is later made: NOT PROVIDED, do not infer
Retention Note: NOT PROVIDED — confirm the required retention period with compliance before filing; most applicable employment-decision frameworks require a minimum of 2+ years.
Chaque équipe qui adopte un outil d'IA pour une décision aux conséquences réelles finit par recevoir la même demande du juridique ou de la conformité : montrez le dossier. Pas un résumé de mémoire des semaines plus tard, mais ce qui a été donné à l'IA, ce qu'elle a recommandé, qui l'a révisé, et ce que cette personne a réellement décidé — écrit près du moment où cela s'est produit. La plupart des équipes n'ont pas cela, car personne ne conçoit une piste d'audit avant le jour où elle en a désespérément besoin.
Ce prompt traite cette lacune comme l'enjeu central. La section Role attribue à l'IA le rôle d'un spécialiste de la documentation de conformité plutôt qu'un assistant générique, car le style d'écriture qui paraît bien dans un article de blog — confiant, fluide, remplissant les petits vides par des déductions qui semblent raisonnables — est exactement le style qui nuit à une organisation sous un examen judiciaire. Un dossier avec des détails inventés est pire que l'absence de dossier.
La section Constraints est là où se joue le véritable travail d'ingénierie. Interdire les faits inventés et les conclusions juridiques est la partie facile ; l'instruction la plus difficile consiste à forcer le modèle à séparer « ce que l'IA a recommandé » de « ce que l'humain a décidé » en deux déclarations distinctes jamais fusionnées. Des réglementations comme les dispositions de supervision humaine de l'EU AI Act existent précisément parce que la responsabilité doit incomber à une personne identifiée, pas à un modèle — donc un dossier qui mélange ces deux lignes annule silencieusement son propre objectif.
La section « Gaps Flagged » dans le format de sortie est la décision de conception qui rend cela réellement utile plutôt qu'un simple modèle qui a l'air bien. La plupart des documentations de conformité échouent non pas parce que quelqu'un a menti, mais parce que personne n'a remarqué qu'un champ manquait avant qu'un régulateur ou l'avocat adverse ne le demande. Faire lister explicitement par l'IA « NOT PROVIDED — must be filled in before filing » transforme un dossier incomplet en liste de contrôle actionnable plutôt qu'un faux sentiment de complétude.
Exécutez ce prompt immédiatement après toute décision assistée par IA touchant une personne hors de l'équipe — recrutement, crédit, modération, exceptions tarifaires — tant que les détails sont encore assez frais pour combler les lacunes qu'il signale.