What should a reviewer split memo explain?
Imagine this review situation: two analysts read the same public account of a rolling art cart and disagree about whether it describes a blocked task. A split memo preserves their reasons rather than averaging labels into certainty. It makes the missing context and the decision consequence explicit for an editor joining the review later.
Worksheet columns: passage; classification_question; reviewer_a_reason; reviewer_b_reason; missing_context; provisional_state; wording_effect.
Decision check: Seek clarification within the available public exchange without inventing an ending. If the outcome remains unknown, retain unresolved or split status.Define the decision unit
Identify the exact disputed passage and classification. Separate disagreement about the words from disagreement about the consequences of wobble. Keep a copy of the original context so a later reviewer can assess the issue without relying on either analyst's paraphrase.
Choose admissible evidence
Record both analysts' initial reasoning before discussion. Exclude later rationalizations presented as original judgments. Montage original references can support reinspection; if relevant context is unavailable, label the gap rather than assuming the cart either completed or prevented the task.
Build the working record
Ask each analyst what additional passage would change the classification. Make the needed context concrete, such as whether materials actually fell or the writer merely disliked movement. A more emphatic analyst does not supply stronger evidence simply by arguing with confidence.
Test the claim boundary
Seek clarification within the available public exchange without inventing an ending. If the outcome remains unknown, retain unresolved or split status. Automated classification can suggest another reading, but it is not an independent report of what happened to the writer.
Deliver the review artifact
Deliver shared observations, incompatible interpretations and their effect on the proposed sentence. State whether the uncertainty requires narrowing or holding the claim. Do not convert a local coding disagreement into a judgment about either analyst's competence or the author's private motives.
Keep the boundaries clear.
- Do not convert a local coding disagreement into a judgment about either analyst's competence or the author's private motives.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.