- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Scoring
- Question Types
- Question Authoring
- Browsing Questions
- Content Blocks
- Media Library
- Metadata Rules & Schema
- Roles & Access
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
Submission Statuses & Message History
A submission's status controls whether it's locked or editable and who can act on it next, and every status change is recorded permanently in a message log both the contributor and reviewer can see.
Every submission is in exactly one status at a time. The status decides two things: whether the record is locked (only a reviewer can act on it) or unlocked (the contributor can edit it), and whether it's a dead end or can move again.
The Five Statuses
- Draft — unlocked. The contributor is still writing; it can be edited or deleted freely and was never seen by a reviewer.
- Submitted — locked. Sent for review; the contributor can no longer touch it until a reviewer acts.
- Revise — unlocked. A reviewer sent it back with feedback; the contributor edits and resubmits, which returns it to Submitted.
- Approved — locked, terminal. The question has been published into the live Question Bank and the submission record is permanently linked to it.
- Rejected — locked, terminal. Permanently declined; there is no path back to editing from here.
How States Connect
Draft → Submitted is the only way in. From Submitted, a reviewer's decision (see Reviewing & Approving Submissions) sends it to exactly one of three places: Approved or Rejected (both dead ends), or Revise — which is the only status that loops: Revise → (contributor edits) → Submitted → (reviewer decides again). A submission can cycle through Revise as many times as it takes.
The Message History
Every Submit, Revise, and Reject appends an entry to the submission's message log — who acted, what status it moved to, and the message that came with it. The log is the shared record between contributor and reviewer: a contributor returning to a Revised submission sees exactly what was asked of them, and a reviewer picking up a submission that's already looped through Revise once can see the full history of what changed and why, not just the current draft.