Charts as Draft Sources: Keep Axes, Series and Value Evidence Together

Before using a chart in a report draft, record what its axes, series and labels actually identify. Keep an explicitly printed value separate from a value you merely estimate from the picture. If the scale, unit or series cannot be read, preserve the source reference and raise that specific question instead of turning an uncertain visual impression into a precise statement.

This is a document-preparation method for material you are authorized to use. It does not validate the underlying measurements, explain an event's cause or support a coverage, liability or payment decision. The aim is to give a human reviewer enough context to trace a proposed sentence back to the supplied chart.

Locate the chart as a complete source item

Start with the file identity, version, page and chart caption. Retain the surrounding heading, legend and notes when they affect what the chart represents. A screenshot containing only the coloured lines may omit the very information needed to identify them. Keep the original authorized file reference alongside any working extract.

Record the chart title as source text, not as your own conclusion. A title can describe a topic without proving every statement in it. Where the title and the nearby explanation appear to refer to different periods or categories, log the mismatch for review. Do not silently choose the wording that makes the draft easier to complete.

For tabular source material, the separate row-and-column context guide handles cell location. A chart needs additional care because position, scale and a visual series can carry meaning even when there is no printed value beside a mark.

Read the axes before reading a height

Write down the horizontal axis label, the categories or times shown, and any visible ordering. Then record each vertical axis, its unit and the displayed scale. If a chart has two vertical axes, associate each series with the correct one only where the source makes that relationship clear. Do not assume every line shares the left-hand scale.

Check whether the visible extract includes the beginning and end of the scale. A cropped axis or missing unit is a source-context gap. It is not an invitation to supply a familiar unit or a likely starting value. Preserve the relevant question, such as which scale belongs to the dotted line, rather than writing a broad claim that the chart is wrong.

The W3C complex-images tutorial illustrates how a chart's fuller description can convey scales, values and relationships that a short label alone does not provide. That guidance concerns accessible presentation. Here, it is a useful reminder to retain context; it does not independently verify the contents of a source chart.

Match each statement to a named series

Use the source legend and labels to identify the series you intend to mention. Keep the exact source term in the working record, with a plain-language explanation only when its meaning has been established. A blue line on one page need not represent the same item as a blue line on another page.

If two colours are difficult to distinguish, use any supported line style, marker or direct label as additional context. If that still leaves the identity unclear, describe the limitation. Do not improve the source by assigning new identities to its marks. A reviewer should be able to distinguish the source's labels from the preparer's own annotations.

The related sketch-label guide connects diagram labels with pictured objects. In a chart, also identify the category or time position and the value evidence for the particular statement. Correctly naming a series does not establish the number at every point along it.

Separate printed, tabulated and visually estimated values

A number printed beside a bar is a different kind of source evidence from a number read off its apparent height. A supporting table may provide another source location, but first confirm that it belongs to the same chart, version and series. Do not join a newer table to an older image without recording the difference.

Where a value is only visually estimated, do not type extra decimal places into the draft. For document preparation, a safer next step is to identify the point and ask for the corresponding readable value or authorized supporting table. If the drafting task needs only a bounded description, have the reviewer decide whether the available source supports that description.

An absent point also needs context. It may reflect missing information, a category not shown or a display convention explained elsewhere. Do not automatically transcribe it as zero. Keep the absence as an observation about the supplied view until its meaning is established.

Use a compact chart-reading card

• Source identity: file, version, page, chart caption and location of the original authorized item.
• Scope: the period, categories and exclusions stated by the source, with unresolved scope left open.
• Axes: labels, units, visible scale and any second axis or missing portion.
• Series: exact legend label, marker or line style, and how it maps to the statement being considered.
• Value evidence: printed label, identified table entry or visual estimate; preserve the actual source location.
• Proposed wording: a bounded draft sentence that does not add causation or unsupported precision.
• Review question: the missing or conflicting detail, who needs to check it and the response reference.

The card is a manual preparation aid, not a claim that StateClaimAI automatically reads charts or validates numerical data. It can stay with the authorized working materials so a reviewer sees why a sentence was proposed and which details remain uncertain.

Work through a fictional transcription problem

Consider a wholly fictional chart in document DEMO-CHART-01, page 3. Its title is “Packets received by review group.” The horizontal categories are Group A and Group B. The vertical axis is labelled “packets,” and the printed value above Group A is 12. Group B has a bar but no readable value label in the supplied extract.

A preparer writes, “Group A had 12 complete packets and Group B had 18.” Neither the word “complete” nor the exact second value is supported by the stated source description. The title says received, not complete, and Group B's apparent height should not be promoted to an exact transcription.

A bounded working note would say: “The chart labels Group A as 12 packets received. The supplied extract does not provide a readable printed value for Group B; request the associated value or a clearer authorized source.” This preserves what is available and makes the next question specific. The example contains no real claim information or product output.

If a corresponding table later arrives, record its identity and verify its relationship to the chart before using it. Add the new reading and its source to the working history. Do not rewrite the original note to imply that the missing value had always been legible, and do not treat receipt of the table as proof that its measurements are correct.

Hand over the source relationship with the draft

Before handoff, trace each chart-based sentence back to its named series, position and value evidence. Look for added words such as complete, verified or caused, and check whether the source actually supports them. Keep unresolved points in the review questions rather than hiding them inside confident prose.

When the relevant inputs are organized, use the StateClaimAI field-adjuster workflow and drafting workspace. Retain the source card for human review and follow the site's editorial policy. A generated draft still needs to be checked against the authorized originals.

For an interface question, contact official support with only the relevant steps and screen message. A fictional chart can illustrate a formatting problem without sending unrelated private records. This workflow organizes evidence for review; it does not turn a visual chart into a verified finding or a professional decision.