Email Threads as Draft Sources: Separate New Replies from Quoted History

Before using an email thread as a report-drafting source, separate each message's new text from the earlier text it quotes. Give the individual messages stable references, link repeated passages to their apparent origins, and check which attachments are actually present. A sentence copied into three replies is not automatically three independent statements, and the date of the latest reply does not become the date of everything below it.

This is a manual preparation method for correspondence you are authorized to handle. It does not establish whether a statement is true or determine a claim outcome. The StateClaimAI field-adjuster page describes support for organizing material into drafts for human review; the worksheet here does not imply an email import, verification or automatic thread-cleaning feature.

Identify messages before extracting sentences

Retain the correspondence in your team's existing authorized location. Assign a working reference to each message you intend to use, along with a locator that lets the reviewer reopen it. Record the displayed sender, date wording and subject as received. Treat those as source details rather than independent proof of identity or timing.

A conversation displayed as one item can contain several messages. Gmail's conversation guidance explains that replies may be grouped and that a changed subject can start another conversation. An inbox grouping therefore should not be treated as the definitive boundary of a source packet. Record what you actually received and reviewed, including any apparent continuation whose original is missing.

Do not use a label such as “latest email” as the only reference. Another reply can arrive while the draft is under review. A stable reference such as MSG-02, paired with its original location, remains useful even when the displayed order changes. These identifiers are a proposed working convention, not a required product format.

Mark new text, quotations and unclear boundaries

Read the whole relevant message, including inline replies and any collapsed quoted material available in the authorized record. Google's reply guidance describes viewing trimmed content and distinguishing quoted text from a response. That is a reason to inspect the actual message structure; it is not a reason to trust indentation alone in a copied or exported version.

For each useful passage, record whether it appears to be new text from that message, a quotation of an earlier item, or a boundary that remains unclear. Preserve enough surrounding wording to understand the response. A short “yes” separated from the question it answers can be misleading, especially when several questions appear above it.

When an earlier original is available, compare the quoted passage with it. Note omissions or changes relevant to the intended draft sentence. Do not silently repair a quotation and then present the repaired text as what was received. If the original is absent, describe the passage as quoted within the message you do have, with the original unavailable for comparison.

The source-labeling worksheet helps trace individual propositions. This preliminary pass establishes which message and which part of that message the proposed attribution actually refers to.

Keep attachment mentions separate from received files

A line saying “see attached” does not establish that the referenced file is in your packet. List the files actually received, their existing identifiers or filenames, and the message with which each can be associated. Check their content and version through the normal authorized review process before using them as drafting sources.

If a forwarded message mentions a photograph but no matching file is available, record that specific gap. Do not substitute a similarly named image from another folder simply to complete the row. If several files share a name, keep their separate locators until their relationship has been checked.

This is a presence and reference check, not a forensic authentication procedure. The worksheet does not establish that an attachment is complete, unaltered or suitable for a professional conclusion. Those questions remain with the relevant review process.

Copy a message and quotation map

Use one row for each passage that matters to the draft, linking rows where the same text appears again. Useful fields are:

• Message reference and original locator: the specific received item, rather than only the conversation subject.
• Displayed sender and date: retained as shown, with any missing timezone or other uncertainty visible.
• Passage location: new opening text, an inline response, or a particular quoted block, with enough context to find it.
• Apparent origin: the earlier message reference, or “quoted original not available” when comparison cannot be made.
• Relationship: repeated wording, an explicit correction, added information, or an unresolved relationship, with the basis for that description.
• Attachment reference: the file actually present, the message that supplies it, or the precise missing item.
• Draft use and open question: the proposed attributed wording, remaining clarification and responsible review role.

Keep administrative fields in the working map unless the report format needs them. There is no benefit in copying every routing detail into the narrative. Provide only the source information needed for the task and follow the existing handling rules for private correspondence.

Follow a fictional three-message chain

The following messages and identifiers are invented for a documentation exercise. They are not a customer file or a generated StateClaimAI report. MSG-01 contains a person's statement, “The label beside the doorway reads Room A.” MSG-02 quotes that sentence and adds, “I have attached the wider view.” MSG-03 quotes the preceding history and adds, “Please use the wider view when checking the label.”

The map records the label statement once under MSG-01, with links showing where it is repeated in MSG-02 and MSG-03. It does not summarize the thread as “three people confirmed Room A.” The later messages may carry the earlier wording without making a separate observation about it.

Suppose the packet contains a file identified as IMG-07 with MSG-02. The reviewer checks that association and records what the file actually shows within the assigned scope. MSG-03's instruction does not itself establish the label's content, and mentioning a wider view does not make that view available if the file was omitted.

Now consider a different version of MSG-03 that explicitly says, “My earlier wording should read Room B.” That passage is an apparent correction to locate and review, not another copy of the original statement. Preserve the earlier wording, the new wording and the relationship the author expressly states. Do not expand the correction to other locations or statements that it does not address.

If only MSG-03's forwarded copy is available, the map should say so. It cannot claim that MSG-01 and MSG-02 were independently opened or compared. The preparer can flag the missing originals without inventing them or describing the packet as complete.

Carry only supported wording into the draft

For each proposed sentence, check its message reference, passage boundary and attribution. Keep the time described in a passage separate from the time the email arrived; the event chronology and intake-log guide handles those two views. Repeated quoted dates should not create extra events merely because the same history appears in several replies.

At handoff, identify which originals and attachments were available, what was compared, and what remains unresolved. Ask the next reviewer to check the resulting sentence against the identified source, not just approve a completed-looking register. A message map organizes the packet; it does not approve the report.

When the source set is ready, continue in the StateClaimAI drafting workspace using the workflow available to your account. Supply only the authorized material needed and review the output against the actual sources. Product questions can go through official support without including unnecessary private correspondence. Coverage, liability, payment and legal conclusions remain outside this documentation workflow.