Sign Off Exact Outputs
One or two people you designate approve or reject each exact output with their own passkey. Your system acts on an output only when its signed approval verifies.
Use named sign-off when a named person must approve every output before it takes effect. A review panel, where invited reviewers answer without their names, remains the choice for feedback and quality checks. The public Alpha accepts only public, synthetic or safely redacted material, so use sign-off there to test the workflow, not for real decisions about people.
1. Designate signers
A new agent starts at Minor inconvenience, independent AI review only, where Setup hides Reviewers and Who decides. First choose Edit setup and move Impact of an AI mistake above Minor inconvenience.
Owners and admins open the agent's Setup and, under Reviewers, select Designate signer for an invited reviewer with current access. Enter the person's legal name, role, competence for these decisions, optional training records and a Valid until date: 12 months by default, at most 24.
You attest these details; RateLoop does not verify anyone's identity. Each change is versioned and audited, and you can renew or revoke a designation at any time. A reviewer who is removed and invited again needs a new designation. Sign-offs are personally attributable, so sign-off history must not be used to rank or assess employees.
2. Choose named sign-off
In Edit setup, set Who decides to Named sign-off. Choose One signer or Two signers (four-eyes), name each signer and up to four deputies in the order they step in, and turn on Require device-bound passkeys to accept only passkeys that report themselves as device-bound. RateLoop does not check the hardware.
- The question is fixed: approve or reject this exact output. You choose whether a rationale is optional or required, and the response window.
- Every eligible output goes to its signers. Rating AI cannot approve or replace a sign-off.
- The agent's permission must be Prepare for approval or Send automatically.
- Every signer and deputy needs a current designation for this agent before you can save.
- A sign-off uses one review case per output version, like a review.
3. Approve or reject with a passkey
Signers find the task in Humans → To review. It shows the exact source and output under the fixed question, without other answers or Rating AI results, and says before the first sign-off that the decision is personally attributable.
The signer chooses Approve or Reject, adds reasons and a rationale as the setup asks, and selects Sign with passkey. After the device checks the signer with a PIN or biometric, the passkey signs a statement that names this exact output, the decision, the review setup and the signer's designation. Email codes cannot sign: a signer without a passkey first adds one in Humans → Settings. Passkeys that report themselves as synced, such as iCloud Keychain or Google Password Manager, can sign unless you require device-bound passkeys.
- Every required signer must approve. One rejection is final.
- A changed output is a new version and needs a new sign-off.
- A deputy takes a seat, in your order, when a signer is no longer designated, steps aside or does not open the task in time.
- Signatures still missing at the response deadline leave the output not authorized. If too few designated people are available, the request is refused and nothing is charged or approved.
4. Read and verify the result
Owners and admins open the record in Agents → Results. It shows the outcome — Approved by every required signer, Rejected · not authorized, or Incomplete at the deadline · not authorized — and, for each signer, the attested name and role, the decision, the time, whether the passkey reported itself as synced or device-bound and whether the session used enterprise sign-in.
Download signed record saves the record. Check it offline with the published verifier and a key from the public verification-key endpoint:
curl --fail --show-error --output verify-rateloop-evidence.mjs \
https://www.rateloop.ai/docs/verify-rateloop-evidence.mjs
node verify-rateloop-evidence.mjs ./sign-off.json \
--public-key ./trusted-evidence-key.txt --key-id ed25519:…The verifier checks RateLoop's signature, each signer's passkey signature against the recorded credential key, that every statement names the same output, and the approval rule. The browser verifier checks evidence packets, not sign-off records.
Act only on a verified approval
The agent receives the same signed record as its sign-off receipt. Before your system uses the output, it must verify the receipt for the exact output bytes, its opportunity and its policy binding. A rejected or incomplete sign-off, changed bytes, an unknown key or a receipt from another review never authorizes.
Evidence and coverage exports
The oversight evidence bundle includes each sign-off as its signed record. These records name their signers; they are not pseudonymous like panel responses.
Owners and admins can export sign-off coverage for a window of up to 366 days, 30 by default. For each eligible output it lists the receipt status and the use your team reported, and it flags outputs used without an approved receipt, outputs revised and used, and approvals never reported as used. RateLoop cannot see your system: use comes from the outcomes you record.
POST /api/account/workspaces/{workspaceId}/assurance/coverage/sign-off/export?from=…&to=…What the signature shows
A passkey signature shows that the signer's authenticator, after checking the signer locally, signed this exact statement. Its link to a person rests on your designation and the passkey registered to their RateLoop account. RateLoop does not present it as an advanced or qualified electronic signature, and it does not replace a statutory written form. It does not show that the output is correct or that your process is compliant; whether a sign-off suffices for a decision is your legal assessment.
Personal data in a sign-off
A sign-off records the signer's legal name, role, competence and training as you attest them, every version of the designation, the passkey's credential ID, public key, authenticator model and backup flags at signing, the signed statements and passkey assertions, the signing time and whether the session used enterprise sign-in.
Deleting the signer's account or the workspace erases the name, role, competence and training text from every designation version and keeps its digest, unless a legal hold covers it. Signed records remain as workspace evidence after the signer deletes their account; they identify the signer by an opaque account ID, not by name or email, and are erased one year after the workspace is deleted, unless a legal hold applies. Where a name was erased, Results shows Signer’s details erased.
Privacy notice · Download this guide · Human oversight · Evidence