Worksheet Notes and Comments: Keep Source Context Separate From Cell Entries

When a source worksheet contains notes or comment replies, record them separately from the cell entry. Keep the file, worksheet and cell locator with the original annotation, then identify whether it describes the entry, asks a question or records a response. A question attached to a cell is not a corrected value, and a completed discussion is not proof that the underlying information has been verified.

This is a manual preparation method for the StateClaimAI field-adjuster drafting workflow. It helps a writer preserve the context of supplied material before preparing a draft for human review. It does not audit a workbook, decide claim outcomes or describe automatic spreadsheet-comment import in StateClaimAI.

Identify the kind of material you actually received

A workbook, a screenshot and an exported document are different source forms. Record which one you were authorised to inspect. If you only received an image of several cells, do not say you reviewed the workbook's annotations or the rest of a discussion that the image does not show.

Microsoft's explanation of comments and notes distinguishes threaded comments, which support discussion and replies, from notes used for annotations or reminders. The explanation applies to the listed Excel for Microsoft 365 products. Use that distinction to ask what the supplied material contains; do not infer a feature or its behaviour in another application from the word “comment” alone.

For the drafting task, the important distinction is between an entry and statements attached to it. A cell may display a location label while an annotation asks whether that label is current. Copying only the cell omits the question. Replacing the cell with the proposed label treats an unresolved question as a completed change. Neither move preserves the source relationship.

Start with a stable locator

Record the received file reference and version or receipt identifier, worksheet name, cell address, and enough surrounding row and column labels to identify the entry. A cell address without its file and worksheet is incomplete: “D8” can refer to unrelated material in many files.

Keep the displayed entry as observed, including its relevant label or unit. Then record the annotation as a separate item with a pointer to the same cell. If the annotation concerns a wider range, record that stated scope rather than assuming it applies only to the selected cell or to the entire table.

The calculation-context guide addresses a different question: what connects a displayed result to its inputs and calculation context. Here, the task is to preserve who said what around an entry. An explanatory comment does not establish that a calculation was checked, just as an inspected formula does not resolve an unanswered discussion.

Make an annotation context record

One short record per relevant note or discussion is usually easier to review than a paragraph combining several cells. Use the team's existing authorised storage and references, with fields such as:

• Source identity: received file, version or receipt reference, worksheet, cell or range, and relevant labels.
• Displayed entry: the value or wording actually observed, kept separate from any suggested replacement.
• Annotation form: note, threaded discussion, supplied screenshot of an annotation, or form not established.
• Original wording and locator: the relevant text or a clearly labelled paraphrase, with a way to reopen the authorised source.
• Discussion context: relevant question and replies, the displayed participants and dates where available, and any part not accessible to the preparer.
• Intended use and open question: what the writer proposes to say, what needs clarification, and who should address it through the existing process.

The fields are editorial suggestions, not a required StateClaimAI input schema. Do not copy unrelated private discussions merely to make the record look complete. Preserve enough authorised context to understand the relevant statement and identify any limitation in the material available to the reviewer.

Follow the discussion without inventing its conclusion

Read the relevant question and responses together. A reply such as “I will check” describes a future action, not its result. “Updated” still needs a clear object: which cell, which version and what change? Record a response faithfully rather than expanding it into a broader confirmation.

Keep the difference between the displayed participant name and any independently established responsibility. A name shown beside text helps locate the statement, but it does not by itself establish the person's authority to confirm the underlying fact. Use the existing review process to determine what confirmation the drafting task needs.

A status label such as resolved can be recorded as an interface observation when actually seen. It should not silently become “the information was verified” in the draft. Ask what conclusion is supported by the text and any linked evidence, within the scope of the reviewer's task.

A fictional room-register example

This original exercise contains no real claim, customer or payment information. A supplied worksheet called “Room Register B” shows “Store room” in cell D8. A threaded comment attached to that cell asks, “Check whether the label on the sketch is Utility.” A later reply in the supplied discussion says, “I will compare the sketch tomorrow.”

The preparer should not replace “Store room” with “Utility” in the working narrative simply because the alternative appears in the annotation. Nor should the preparer omit the question and write that the room identification has been confirmed. The received material shows an entry and an unresolved comparison, not an agreed replacement.

A bounded preparation note could read: “The received register labels D8 as Store room. Its annotation requests comparison with a possible Utility label on the sketch; the supplied reply records an intention to check, with no result included in this material.” Keep the register and annotation locators with that note and route the naming question to the responsible reviewer.

Suppose a later identified response states that the intended label is “Store room” and points to an identified sketch version. Add that response and its scope to the record. Do not erase the earlier question: it explains why clarification was requested. The reviewer must still decide what wording is supported for the actual task; this example does not establish a rule for resolving conflicting evidence.

If the later message only says “done,” retain the uncertainty. A completion word without an identifiable action does not tell the writer which proposed label was accepted or whether the supplied workbook was changed.

Keep the source intact while preparing the handoff

Do not edit the received annotation to make the discussion look settled. Use the organisation's authorised method for inspecting source material and distinguish any permitted working copy from the received file. This workflow does not require enabling macros, refreshing connections, changing access permissions or contacting anyone outside the approved process.

When an export or screenshot does not show enough discussion context, request an appropriately identified view through the existing channel. Record the limitation until it is resolved. Do not recreate missing replies from memory or assume that a blank-looking margin means no annotation exists in the original file.

Comments on the report draft itself belong in a different workflow. The parallel-review disposition register coordinates reviewers' instructions about draft wording. A source-worksheet annotation describes or questions source material. Link the records when necessary, while keeping those roles distinct.

Carry the distinction into the draft

Before handing over prepared notes, check each proposed sentence against its source record. Has a question become a fact? Has a promised check become a completed check? Has a cell entry been replaced by an unconfirmed alternative? These are concrete editing questions that a second reader can repeat.

Use the source-labeling worksheet to keep received statements, observations and unresolved items distinguishable. Then continue in the report drafting workspace with only the authorised material needed for the task. Retain the external annotation record in its approved location; do not assume it was imported or preserved by the workspace.

Review generated wording against the actual sources and the site's editorial policy. For product-interface questions, use official support, providing only necessary information. This process organises documentation for human review; it makes no coverage, liability, payment, legal, medical or financial determination.