Review a filing

Request, correct, and review changes

Run an attributable correction cycle without losing the earlier review history.

Version 2026.8.18 minReviewer · Administrator · PreparerReviewed 2026-07-25

Who can perform the task

The assigned reviewer or administrator requests changes. Administrators and preparers with edit access make corrections and resubmit.

Before you begin

The reviewer should identify the affected table or evidence, expected correction, and reason. Do not use a vague request for a material issue.

Quick path

  1. Identify the exact value, finding, or evidence item that needs correction.
  2. Request changes with a specific, actionable comment.
  3. As preparer, correct the source or filing value and rerun validation.
  4. Resubmit the filing and preserve the response and evidence trail.
  5. As reviewer, verify the correction before approving or requesting another change.

Detailed guidance

  1. In Review and audit, add explanatory comments where useful.
  2. Enter the reason and select Request changes.
  3. The preparer confirms the status is Changes requested.
  4. Correct values by entry or by previewing and applying an import.
  5. Re-run validation and update supporting evidence.
  6. Reply through an attributable comment and submit to the assigned reviewer again.
  7. The reviewer compares the corrected state with the request and earlier audit events.
Reviewer workflow showing a synthetic correction comment, request reason, Request changes action, and audit history with timestamps masked.

The reviewer records both the correction context and the workflow decision.

Audit history showing the synthetic correction import, validation, and resubmission as attributable events with timestamps masked.

The corrected handoff remains distinguishable from the original submission.

Expected result

The status moves from ready for review to changes requested and back to ready for review. The reason, corrections, and resubmission remain visible.

How to verify

The reviewer checks the changed cells, related calculations, validation impact, evidence, comments, and audit sequence - not only the originally reported value.

Common problems

If values remain locked, confirm that Request changes completed and refresh. If a correction import proposes unrelated changes, stop, fix the source or mapping, and preview again.

Audit and data consequences

Correction cycles preserve earlier attribution. They can affect calculated fields, other validation findings, and any earlier working artifact. Reconcile the complete filing again where dependencies are material.

Product limitations

The product records the process but cannot decide whether the reviewer’s evidence threshold is sufficient.

Related tasks

Your privacy choices

We use essential storage for security and preferences. With your permission, PostHog EU measures filing steps and records a privacy-masked session replay so we can find and fix usability bottlenecks. Replays hide all text, form contents, media, console logs and network contents. This helps us improve SolvencyBridge.

Privacy details