Skip to content
Handbook

Edit an approved submission safely

Understand why a change sends the submission back to review.

Owner · Recruiter2 min readGuided walkthrough
Before you begin

Editing access and the current staffing submission revision.

On this page
Why an edit needs another reviewSynthetic example

A guided view of the actual product controls. Move step by step or play the walkthrough.

Step 1 of 3

Begin with an approved revision

Approval applies to one saved presentation. A downloaded copy reflects that revision.

Fictional data · Local example only · No account changes, messages, payments or device recordings
  1. Begin with an approved revision

    Approval applies to one saved presentation. A downloaded copy reflects that revision.

  2. Make an edit

    An unsaved change makes the presentation dirty. Exports and attestation wait until it is saved.

  3. Return to review

    Saving creates a new revision with Review required. Review and attest again before sharing.

Read the complete walkthrough
  1. Begin with an approved revisionApproval applies to one saved presentation. A downloaded copy reflects that revision.
  2. Make an editAn unsaved change makes the presentation dirty. Exports and attestation wait until it is saved.
  3. Return to reviewSaving creates a new revision with Review required. Review and attest again before sharing.

Step by step#

  1. Open the current revision

    Check the status and revision number. If someone else changed it, load the current version before applying your edit.

  2. Make the correction

    Change the information state, selected excerpt, contradiction or recruiter assessment. Original candidate answers remain separate from your edited presentation.

  3. Save edits — review required

    The new revision returns to review. Even an edit to the recruiter assessment needs review; the old approval does not silently transfer.

  4. Review and approve again

    Inspect the changed presentation and its evidence, attest again and approve the new revision before exporting it.

Keep the sequence understandable#

Revision history distinguishes original, edited and approved snapshots. Use it to understand what changed. A previously downloaded export remains an older copy; replace it with the newly approved document when appropriate.

Your save conflicts with another edit#

Reload and compare the current revision with the change you intended. Do not repeatedly submit a stale revision or overwrite someone else’s review without checking it.

Explore the handbook

Find an answer, a button or your next step.

Search the complete handbook. Your query stays in this browser.

Something not working? Start here →
Local handbook search↑ ↓ to move · Esc to close