Docs
Browse Docs
Field guide · Structure and layout

One table split across sheets

Rows that belong in one table are spread over several sheets or files, one per month, region, or person.

What it looks like

Before
sheetmonthdonoramount
Jan·Ana Ruiz50
Feb·Ben Cho75
Feb·Ana Ruiz50
After
sheetmonthdonoramount
combinedJanAna Ruiz50
combinedFebBen Cho75
combinedFebAna Ruiz50
The month was recorded only in the name of each sheet. It becomes a column before the sheets are stacked, so no row loses it.

How it happens

  • A new sheet was started each period to keep things manageable.
  • Each team or site kept its own copy of the same template.
  • A system limited the size of each export, so the data arrived in pieces.

What it breaks

  • No question that spans sheets can be answered without combining them by hand each time.
  • The fact that distinguishes the sheets lives in a tab or file name, where formulas and imports do not see it.
  • The sheets drift apart: a column is added to one, renamed in another, and reordered in a third.

How to spot it

  • Look for tabs or files named after periods, places, or people, each with a similar layout.
  • Compare the headers of every sheet. Small differences show where the copies have drifted.
  • Check for rows that appear in more than one sheet, such as a record carried over from one month to the next.

How to fix it

  • Add a column to each sheet for whatever its name was recording, before combining.
  • Bring the column names and order into agreement. See inconsistent column names across files.
  • Stack the sheets into one table, and check that the combined row count equals the sum of the parts.
  • Check for overlap afterward. Whether a row repeated across sheets is a duplicate or a real repeat is a judgment about the data.

TermsSpreadsheet, Schema, Provenance, Tidy data

Karg checks for many of these when it profiles a file, applies the fixes it is confident about, and sets the rest aside for your review. See how it works, or have our team clean your data for you.