💡 A rejected item is terminal: it moves to Discarded Items → Rejected, stays visible for audit, and stops counting toward its topic's target. Rejection doesn't shrink your exam — it reopens a gap that a new item must fill.
❓ Who rejected my item?
Check the item's Summary and History tabs: reviews are attributed to the reviewer, and AI-performed reviews are attributed to Certiverse AI. If AI Item Review is enabled on the blueprint, the AI may have rejected the item during its automatic pass, before any human saw it. The rationale for the decision lives in the item's review feedback either way.
8.3.1 Open Item Management and click Rejected under Discarded Items in the status sidebar to see every rejected item.
8.3.2 Open the rejected item and read the review feedback in its Summary and History tabs. Understand why it was rejected before writing anything new: if the testing point itself was the problem (off-topic, factually wrong premise), don't recreate it; if the execution was the problem, the testing point may still be worth a fresh attempt.
❓ Can I just fix and resubmit a rejected item?
No. Rejection is the terminal outcome: unlike For Revision or For Rewrite, a rejected item doesn't return to the author's queue for editing. If the reviewer believed the item was fixable, they would have returned it instead. The rejected item remains in the audit trail, and the gap it leaves is filled by writing a new item.
8.3.3 Check the impact: return to Item Writing in Authoring and find the affected topic. Its Items Needed count will have increased by the rejection, and if the topic previously showed DONE, it reopens with a Write button available again.
8.3.4 Write the replacement item for that topic, using either path:
- Write on the topic row: the standard AI-assisted or manual flow (see Steps 7.1 and 7.2). Best when you're replacing one or two items.
- AI Bulk Generation: the panel recalculates against your current gaps, so a fresh run generates only the missing items. Best when many rejections have accumulated.
💡 If the rejected item covered a specific, necessary testing point, put that point directly into your Question Description when generating, or write it manually — don't leave it to chance that the AI's replacement lands on the same content.
8.3.5 The replacement enters the standard workflow: submitted → reviewed (by AI, a human reviewer, or both, per your blueprint's settings) → Accepted. Once accepted, the topic's Items Needed drops back and the pool moves toward form-ready.
⚠️ Do this accounting before form building, not during. The Blueprint-Driven Fixed Form's pool health check will block form generation if any topic's accepted count falls short — a rejection discovered at that gate sends you back through this entire loop under deadline pressure.
Next step → Step 9: Reviewing Items (The Reviewer's Workflow)
Updated
Comments
0 comments
Please sign in to leave a comment.