How to Preserve a Table's Units and Footnotes When Saving an Excerpt
Summary
- When you save a table excerpt, capture its units and footnotes as inseparable context, not optional extras.
- Use a consistent excerpt format that separates original text, paraphrase, and interpretation.
- Record where units apply (table-wide, column-level, row-level, cell-level) and how footnotes map to specific cells.
- Include a verification status field so readers know what you checked versus what you inferred.
- A worked example and reusable template below help you preserve meaning when tables are copied into notes, reports, or evidence logs.
Saving a table excerpt sounds simple until you reuse it later and realize the numbers no longer mean what you thought they meant. The two most common causes are (1) the units were separated from the values (or applied at a different scope than you assumed), and (2) the footnotes that qualify the data were dropped or detached from the cells they modify.
This guide shows a practical, repeatable way to preserve a table’s units and footnotes when you save an excerpt, including a worked example and a reusable record format. It also helps you clearly distinguish original text from paraphrase and interpretation, and to mark what you have (and have not) verified.
Why units and footnotes are part of the data (not “extra”)
In tables, meaning is distributed across multiple elements:
- Values (the numbers or categories in cells)
- Units (what the values measure and in what scale)
- Footnotes (definitions, exceptions, methods, rounding rules, inclusion/exclusion criteria, time windows, and caveats)
- Scope cues (whether a unit or note applies to the whole table, a column, a row, or a single cell)
If you excerpt only the values, you may accidentally change the claim. For example, “12” could mean 12%, 12 people, 12 million dollars, 12 per 100,000, or an index value. A footnote can also reverse the practical meaning (e.g., “preliminary,” “modelled,” “excludes refunds,” “not seasonally adjusted,” “rounded,” “includes estimates”).
Common failure modes when saving table excerpts
- Unit drift: the unit is in the table caption, but you only copied the grid.
- Scope confusion: a unit applies to one column, but you treat it as table-wide.
- Footnote detachment: you copy footnotes but lose which cells they refer to.
- Symbol loss: superscripts (a, b, *, †) are stripped in plain-text copying.
- Rounding/precision loss: you retype values and change decimals or separators.
- Timeframe loss: “FY2023” or “Q2” is in a header you didn’t capture.
- Definition loss: a footnote defines what a category includes, but you paraphrase it away.
The core method: capture a “table excerpt bundle”
When you save an excerpt, treat it as a bundle with four required parts:
- Table identity: what table it is and where it came from (enough to find it again).
- Excerpted cells: the exact values you copied (as original text).
- Unit map: a structured note of where units apply (table/column/row/cell).
- Footnote map: the footnote text plus an explicit mapping to the affected cells.
This is the minimum needed to preserve meaning when the excerpt is separated from the original layout.
Step 1: Identify where the units live
Units can appear in several places. When saving an excerpt, explicitly record the unit location and scope:
- Caption-level: “Table 2. Revenue (USD millions)”
- Header-level: “Revenue (USD m)” as a column header
- Stub/row label: “Rate (per 100,000)” as a row group label
- Cell-level: “12%” or “$12” embedded in the cell
Rule of thumb: if the unit is not inside each cell, assume it can be lost during copying and record it separately in your excerpt bundle.
Step 2: Preserve footnote markers and their targets
Footnotes are only useful if you preserve two things:
- The marker: a, b, *, †, 1, 2, etc.
- The target: which cell(s), row(s), or column(s) the marker modifies
When copying into plain text, superscripts may flatten or disappear. Replace them with bracketed markers like [a], [*], or [1] and record a mapping.
Step 3: Separate original text, paraphrase, and interpretation
To keep your excerpt usable (and defensible) later, store three layers:
- Original text: the table excerpt as copied, including units/markers.
- Paraphrase: a faithful restatement that keeps the same meaning, without adding new claims.
- Interpretation: what you think it implies (comparisons, conclusions, implications). This is where mistakes happen, so label it clearly.
Step 4: Add verification status
Verification status is a simple field that tells future-you (or a reviewer) what you checked. Keep it explicit and limited to what you actually did. For example:
- Verified: you re-opened the source and confirmed units, footnotes, and mapping.
- Partially verified: you confirmed units but not every footnote mapping.
- Unverified: you captured the excerpt but have not checked it against the source after copying/formatting.
You can also add a short “verification notes” line (e.g., “Checked that [b] applies to 2024 only”).
Worked example: saving an excerpt without losing units or footnotes
The example below is fictional and provided only to demonstrate the method (it is not a quote from any real source).
Example table (as seen in a document)
Table A. Service performance (units vary by column)
| Region | Response time (minutes) | Resolution rate (%) | Cost (USD) |
|---|---|---|---|
| North | 18 | 92[a] | 14.20 |
| South | 25[b] | 88 | 13.10 |
- [a] Resolution rate excludes cases closed as duplicates.
- [b] Response time measured from ticket creation to first human reply; automated replies excluded.
How to save an excerpt bundle (good practice)
1) Original text (verbatim excerpt)
Original text:
Table A. Service performance (units vary by column)
Columns: Response time (minutes); Resolution rate (%); Cost (USD)
North: Response time 18; Resolution rate 92[a]; Cost 14.20
South: Response time 25[b]; Resolution rate 88; Cost 13.10
Footnotes: [a] Resolution rate excludes cases closed as duplicates. [b] Response time measured from ticket creation to first human reply; automated replies excluded.
2) Unit map (explicit scope)
- Unit map:
- Response time: minutes (column-level)
- Resolution rate: percent (column-level)
- Cost: USD (column-level)
3) Footnote map (explicit targets)
- Footnote map:
- [a] applies to cell: (North, Resolution rate)
- [b] applies to cell: (South, Response time)
4) Paraphrase (faithful restatement)
Paraphrase:
In Table A, response time is reported in minutes, resolution rate is reported as a percentage, and cost is reported in USD. North shows a resolution rate of 92% with a note that duplicates are excluded. South shows a response time of 25 minutes with a note that the timing excludes automated replies and starts at ticket creation.
5) Interpretation (your analysis, clearly labeled)
Interpretation:
North’s resolution rate may not be directly comparable to a metric that includes duplicates, because the footnote changes the definition of “resolution rate.” South’s response time metric may appear longer or shorter depending on whether other reports include automated replies.
6) Verification status
Verification status: Unverified
Verification notes: Excerpt captured from a rendered table; confirm footnote markers and unit scopes against the original source before publication.
A reusable record format you can copy into notes
Use the template below as a consistent “table excerpt bundle” record. It is designed to survive copy/paste into plain text, spreadsheets, or evidence logs.
| Field | What to record |
|---|---|
| Record ID | A unique ID you assign (e.g., TBL-EXC-0007) |
| Source locator | Document name + page/section/table label, plus a URL if applicable |
| Table title/caption (original) | Copy exactly, including any units in the caption |
| Excerpt scope | Which rows/columns/cells you captured (be explicit) |
| Original text (verbatim) | Paste the excerpt with bracketed footnote markers like [a], [1], [*] |
| Unit map | List each unit and its scope: table-wide / column / row / cell |
| Footnotes (original text) | Paste footnote text exactly as written |
| Footnote map | Map each marker to the affected cell(s) using coordinates (Row label, Column label) |
| Paraphrase | Restate without changing meaning; keep units and footnote implications intact |
| Interpretation | Your conclusions or implications; keep separate from paraphrase |
| Verification status | Verified / Partially verified / Unverified |
| Verification notes | What you checked (e.g., “Confirmed [b] applies to 2024 column only”) |
| Change log (optional) | If you later correct a unit or mapping, note what changed and why |
Practical techniques for tricky tables
1) Mixed units in one table
Some tables mix units across columns (e.g., minutes, %, USD). In that case:
- Record a unit map per column.
- In your “Original text,” repeat the unit in the column label line even if it feels redundant.
2) Units implied by abbreviations
If a header says “USD m” or “kg CO2e,” do not expand it in the original text. Expansion belongs in paraphrase (and only if you are confident). If you do expand, mark it as paraphrase and keep the original abbreviation preserved.
3) Footnotes that apply to a whole column or row
Sometimes a footnote marker appears in a column header (e.g., “Revenue[a]”). Your footnote map should then say:
- [a] applies to: (All rows, Revenue column)
4) Footnotes that define categories
If a footnote defines what a category includes (e.g., “Includes contractors”), treat that as a definition that must travel with the excerpt. In paraphrase, you can restate it, but keep the definition intact.
5) Ranges, inequality signs, and special symbols
Preserve symbols like “<”, “>”, “~”, “±”, and ranges exactly in the original text. If your destination system strips them, add a note in verification notes and re-check the source.
6) When you must reformat the table
If you convert a table into sentences or bullets, do it in the paraphrase section, not the original text section. Keep the original excerpt as close to the source as possible, then provide a readable paraphrase for downstream use.
Quality checks before you reuse the excerpt
- Unit check: Can every number be read with a unit without guessing?
- Scope check: Do you know whether the unit applies to the whole table or only a column?
- Footnote check: Does every footnote marker have a mapped target?
- Definition check: Did any footnote redefine a metric or category?
- Timeframe check: Did you preserve the period (year/quarter/date range) if present?
- Verification check: Is the verification status accurate for how you plan to use it?
Frequently Asked Questions
FAQ 1: Why do units get lost when I copy a table excerpt?
Answer: Units are frequently stored in captions or headers rather than inside each cell. When you copy only the grid (or paste into a format that drops headers), the values remain but the unit context disappears. The fix is to save a unit map that states where each unit applies (table-wide, column-level, row-level, or cell-level).
Takeaway: Treat units as required context and record their scope explicitly.
FAQ 2: What is the safest way to represent footnote markers in plain text?
Answer: Convert superscripts into bracketed markers such as [a], [1], or [*]. Then paste the footnote text and include a footnote map that links each marker to the affected cell(s). This survives copy/paste into systems that do not preserve superscripts.
Takeaway: Use bracketed markers plus an explicit mapping, not formatting.
FAQ 3: How do I record which footnote applies to which cell?
Answer: Create a footnote map using coordinates based on row and column labels, for example: “[b] applies to (South, Response time).” If a note applies to a whole column, write “(All rows, Revenue column).” If it applies to a whole row, write “(North row, All columns)” and clarify any exceptions.
Takeaway: Always store footnotes with a target, not just the text.
FAQ 4: Should I paraphrase table footnotes or keep them verbatim?
Answer: Keep footnotes verbatim in the “Footnotes (original text)” field so you preserve exact definitions and caveats. If you also want readability, add a paraphrase section, but do not replace the original footnote text with your paraphrase.
Takeaway: Store footnotes verbatim first; paraphrase only as an additional layer.
FAQ 5: What does it mean to separate original text, paraphrase, and interpretation?
Answer: “Original text” is what the table says (copied as-is). “Paraphrase” restates it without changing meaning. “Interpretation” is your analysis or conclusion about what it implies. Keeping these separate reduces the risk that an inference (interpretation) is later mistaken for what the source actually stated (original text).
Takeaway: Separate layers so your notes stay accurate and reusable.
FAQ 6: What verification status should I use if I have not re-opened the source?
Answer: Use “Unverified” if you have not checked the excerpt after copying/pasting or reformatting. If you confirmed some elements (for example, units) but did not confirm all footnote mappings, use “Partially verified” and state exactly what you checked in verification notes.
Takeaway: Verification status should reflect what you actually confirmed, not what you assume.
FAQ 7: How do I handle tables where units vary by row or are embedded in cells?
Answer: If units vary by row, record them in a row-level unit map (for example, “Row group A: per 1,000; Row group B: per 100,000”). If units are embedded in cells (like “12%”), keep them exactly in the original text and still note the pattern in the unit map so later readers do not strip symbols during reuse.
Takeaway: When units are not uniform, map them at the level where they change.
FAQ 8: What should I do if the table excerpt will be used in a report later?
Answer: Save the excerpt bundle with (1) a clear source locator, (2) a unit map, (3) a footnote map, and (4) a verification status. In the report draft, use your paraphrase for readability, but keep the original text and footnotes available for review so you can confirm that definitions and caveats were preserved during editing.
Takeaway: Build the excerpt bundle now so reporting later does not require guesswork.
