> ## Documentation Index
> Fetch the complete documentation index at: https://braintrust.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Why mark complete is missing on log span reviews

export const plans_0 = "Any"

export const deployments_0 = "Any"

export const data_plane_version_0 = undefined

export const use_case_0 = "Use case - Mark log spans as reviewed (no scoring) when the UI hides the Mark complete button; provide reasons and workarounds so review counts are accurate."

<Note>
  **Applies to:**

  * Plan - {plans_0}
  * Deployment - {deployments_0}
  * {data_plane_version_0}
  * {use_case_0}
</Note>

## Summary

Review items show only a Continue button until a scorer or rubric field is answered. The UI requires at least one scorer interaction before offering Mark complete. Enter a minimal answer or add a simple "Reviewed" scorer so reviewers can mark items complete without full scoring.

## What is happening

In certain review configurations the completion action (Mark complete or Mark complete and continue) is gated on an answer to a scorer or rubric field. If no scorer/rubric field has been touched the UI shows only Continue. This is by-design for those configurations, so reviewers who only need to confirm they read a trace cannot mark it complete until one scorer/rubric value exists.

## Fix or suggestion

### Option 1: Enter a minimal answer (quickest)

Actionable steps:

* Open the review sidebar for the log span.
* Fill one scorer or rubric field with a minimal value (for example, type "Reviewed" in a free-text rubric or choose one option in a categorical scorer).
* Click Mark complete or Mark complete and continue.

Workaround to toggle without leaving an answer:

* Select a scorer option once, then clear or delete that answer. The Mark complete action will be enabled after this interaction.

### Option 2: Add a simple "Reviewed" scorer (project owner)

Actionable steps for project owners:

* Edit the project's rubric/scorers.
* Add a categorical scorer with one quick option (for example, "Reviewed" or "No issues").
* Save the rubric. Reviewers can now select that option to mark items complete without substantive scoring.

## How to confirm it worked

* After adding a scorer/rubric value, the button reads Mark complete or Mark complete and continue.
* The item moves from your queue into Completed and the project's completion counts update.

## Notes

* If auto-advance is enabled, the button label becomes "Mark complete and continue."
* Consider adding a short free-form rubric or a single-option categorical scorer for workflows where reviewers only need to confirm review.