> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/products/ai-review/sign-off-levels.md).

# Sign-off levels

## The short version

Filed uses one sign-off model everywhere in the Binder, including on AI Review's leadsheets: four levels, L0 through L3, where each higher level implies the ones below it are done.

| Level | Who              | How it's applied                                                                         |
| ----- | ---------------- | ---------------------------------------------------------------------------------------- |
| L0    | AI (implicit)    | Applied automatically when there are no open AI issues on the item - not a human action. |
| L1    | Preparer         | First human sign-off.                                                                    |
| L2    | Reviewer         | Implies L1 is complete.                                                                  |
| L3    | Partner or admin | Implies L1 and L2 are complete.                                                          |

This is the same model documented in full in [Activity and sign-off](/reference/products/binder/activity-and-sign-off.md#sign-off-levels) - read that page for how sign-offs are placed, undone, and what makes a sign-off go stale.

## Sign-off on leadsheets specifically

Leadsheets support sign-off at two granularities: an individual row, or the entire leadsheet. Both use the same L1-L3 human levels (L0 remains implicit - it reflects the AI having no open issue on that item, not a person signing off). Signing off a whole leadsheet at, say, L2 asserts that both the L1 preparer pass and the L2 reviewer pass are complete for every row on it. See [Signing off on leadsheets](/reference/products/binder/leadsheets.md#signing-off-on-leadsheets).

## Who can sign at which level

A preparer's available sign-off level is determined by their workspace role - a preparer-level user can place an L1 sign-off but not an L2 or L3. This applies uniformly across documents and leadsheets.

## A stale sign-off counts as unsigned

If a signed row or leadsheet is modified afterward, the sign-off goes stale and the UI prompts for a fresh sign-off at the same level. A stale sign-off is treated as unsigned for review-tracking purposes until it's redone. See [What invalidates a sign-off](/reference/products/binder/activity-and-sign-off.md#what-invalidates-a-sign-off).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.filed.com/reference/products/ai-review/sign-off-levels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.