Reading a Table Into a Report Draft: Keep Row, Column and Footnote Together

When turning a table entry into report text, carry its row identity, column heading and applicable footnote with the value. A cell that says “2” does not explain what was counted, when the record applies or whether the number describes received documents rather than a finding. Write only what the complete table context supports, and leave unresolved context visible for review.

This guide provides an original manual reading record for report writers. It supports the documentation workflow described on the StateClaimAI field-adjuster page. It is not an automated table-extraction feature or a method for deciding coverage, liability, valuation or payment. A qualified professional remains responsible for reviewing the draft and its sources.

Identify the table before extracting a cell

Record the exact source copy, its version and the table's title or other visible identifier. Include the relevant page location and note whether the table continues across pages. Two files can contain tables with the same title but different entries; a title alone does not identify which copy the draft used.

Use the source-page map when printed labels and viewer positions differ. That map helps a reviewer find the page. The cell-context record starts after the page is located: it preserves the labels and qualifications needed to read an entry on that page.

Check that the supplied view includes the headings and notes. A cropped image containing only the middle rows may omit the information needed to interpret them. Keep the cropped copy identified, request the relevant context through the authorized workflow and avoid filling the gap from a similar-looking table elsewhere.

Follow the heading structure all the way to the value

Read the row label, any row group, the column label and any heading that spans several columns. A column marked “Date” beneath “Documents received” has different context from one beneath “Reported event.” Do not shorten both to an unqualified date in narrative text.

Look for units, time windows and status labels in the heading area as well as beside the value. A note at the top of a table can apply to every row even when it is not repeated in each cell. If a repeated header on the next page differs, record the difference and ask the designated reviewer which context applies; do not silently combine the pages.

For each entry intended for the draft, create a working record with:

• Source identity: the exact copy, version, page location and table identifier.
• Row context: the visible row label and any group heading above it.
• Column context: the column label and any spanning heading that qualifies it.
• Literal entry: the visible value or wording, including a blank or unclear entry.
• Qualifications: applicable units, date labels, symbols and footnote text or location.
• Proposed sentence: the wording the writer intends to carry into the draft.
• Review question: missing context, ambiguous scope or a conflict that needs a named reviewer.

This is a manual working record, not a required StateClaimAI upload format. Retain only information appropriate to your authorized drafting workflow, and keep source records in their approved locations.

A fictional received-photo register

Consider an original fictional exercise, unrelated to any real claim or customer. A table titled “Photo intake register — copy A” has columns labeled “Area,” “Photos received” and “Received date.” One row reads “Room A,” “2” and “12 October.” Another reads “Room B,” a blank cell and “13 October.” A footnote states that counts cover the current packet only.

For the first row, a supported draft statement is: “Copy A of the photo intake register lists two photos received for Room A on 12 October, within the current packet.” The wording keeps the table identity, counted object, receipt date and packet limitation together. It does not say that two items were damaged or that an event happened on that date.

For Room B, the blank count remains a question. The date entry does not make the blank count zero, and the blank does not establish that no photos exist elsewhere. A working note can say that the received-photo count is blank in copy A and requires clarification. Whether that note belongs in the final report is a separate review decision.

If the footnote had been cropped away, the writer would lack the basis for stating the packet limitation from that copy alone. The appropriate task would be to retrieve the relevant source context, not to add a limitation remembered from another example. This exercise demonstrates transcription boundaries; it does not validate the completeness or accuracy of the underlying register.

Keep blanks, symbols and summaries distinct

A blank, a dash, “not applicable” and a numeric zero are different visible entries. Preserve what the source shows. Only use a meaning supplied by the source or confirmed through the review process; a writer's preferred spreadsheet convention does not resolve an unexplained mark in someone else's table.

Check where footnote markers attach. A marker beside one entry might qualify that entry, while a note under a table might have broader stated scope. If the scope is unclear, record the question. Do not expand a narrow note to every row or omit it because it makes the sentence less tidy.

Identify totals and subtotals before describing a list. A summary row may summarize rows already present; treating it as one more item can misrepresent the source. This guide does not propose recalculating claim values. It asks the writer to preserve the source's row roles and leave arithmetic or interpretation questions to the appropriate reviewer.

Check the sentence back against its complete context

Read each proposed sentence beside the original row, its full heading structure and its applicable notes. Ask whether the sentence has changed the counted object, date type, scope or status. Then check whether it has added certainty that the table does not provide, such as turning a recorded receipt into a confirmed observation.

The source-labeling worksheet helps keep the resulting proposition attributed. The cell record supplies the context supporting that proposition. Both records should refer to the same source copy so the reviewer can retrace the wording without guessing which version was used.

When a replacement table arrives, compare the affected entries and their headings or notes, not just changed numbers. An unchanged value under a revised heading can support a different statement. Record the replacement's identity and route affected draft passages for review rather than describing the update as cosmetic.

Hand over the context and the open questions

Before drafting, separate entries whose context is clear from those still awaiting clarification. Include the relevant source references and a concise question for each unresolved entry. Do not fill uncertain cells merely to make every draft section appear complete. The broader field-notes-to-report guide can help organize these inputs with the rest of the authorized packet.

Once the inputs are ready, continue in the StateClaimAI drafting workspace and keep the manual reading record available for review. Follow the site's drafting standards and have a qualified professional check the resulting text against the sources. For an interface question, use official support with the minimum necessary details; a support request need not include passwords or unrelated source records.