Judgment: sign or send back — Cours — Académie

Everything converges here. The signature is not a "broadly agree": it is a binary, binding act that carries commitment.

1The bar, and how a referral is written

You only sign if the 8 sections hold up. A single blocker → the file goes back. The signature is not negotiated at "7 out of 8."

Signed — sealed, immutable and binding; your name is attached to it.
Referred back in full — several foundations are missing.
Referred back partially — the essentials hold, but targeted blockers remain.

A referral must be written up. "File needs improvement" helps no one. A good referral is actionable and tied to the sections, without dictating the remediation (the expert points out the gap, they don't do the client's work).

2What the signature is — and is not

The signature is an attestation of compliance of the data with respect to article 10, for a given scope and at a given moment. It is not a guarantee of outcome ("the system will never cause harm").

Who signs: the qualified expert who judged the file and who answers for it — not software, not the salesperson, not the client.
What it carries (binding): the signatory's identity, the exact scope (sources, version), an integrity seal.

Immutable and traceable. A signed file is not edited: in case of an error or an evolution, a new, traceable version is issued. Traceability (who signed what, on which version, when) matters as much as the content — without it, there is no way to prove or defend what was attested.

3Sign, refer back, start over

The bar

You only sign if the 8 sections hold up. A single blocker (missing legal basis, bias neither justified nor mitigated, unvalidated mapping…) → referral. A bounded gap — identified, planned for, excluded from the scope of use — remains signable; a partial scope is too, as long as it is explicit (never implicit coverage of unexamined sources).

A referral that moves things forward

Precise, tied to the sections, actionable, and constructive: it charts a clear path toward compliance rather than humiliating. For a non-expert client, the blocker is translated into plain terms — without dictating the technical fix. A good referral lists only the blockers (not the sections that hold up) and distinguishes a real blocker from a mere remark.

After correction

The client corrects and resubmits: the expert judges the new version and, if it holds up, issues a new signature. And any later substantial change (data, purpose, regulation) triggers a re-certification.

4Independence and responsibility

There is no such thing as a "signature with a reservation": a reservation is a point that doesn't hold up — hence a referral. Under commercial pressure ("sign it, this client is strategic"), the expert refuses what doesn't hold up: their independence is what gives their "yes" its value. And they do not sign what they themselves designed (conflict of interest).

The bar protects everyone. "The 8 hold up" gives the client real compliance (not a rubber stamp), protects the end user from a system trained on non-compliant data, and protects the expert (liability, credibility) — a clear bar withstands pressure.