Going Back Years: Getting a Local's Records Ready for a Historical Reconciliation

Most reconciliation work looks at the current period: what was dispatched this week against what was reported on the next payroll run. But a lot of what a local wants to know sits further back — seasons and contract years where nobody had time to compare line by line, where the dispatcher who remembers the details has retired, and where the only account of what happened is whatever paper and files the hall kept. Reaching back is possible. It just depends almost entirely on how the records come together before anyone starts comparing numbers.
This is a practical look at that preparation stage: what a local needs on hand, how to get it into comparable shape, and what kinds of gaps show up along the way.
Start With What the Local Actually Has
A historical reconciliation can only go back as far as the local can supply data. That sounds obvious, but it changes how officers should think about the project. The question isn't "how many years do we want to review" — it's "how many years can we document on both sides."
Both sides matter. A reconciliation compares the hall's record of work dispatched against the employer-reported record of work paid and reported to the local. If the local has dispatch sheets for a given year but nothing from the reporting side, that year can be organized and preserved, but it can't be matched. The reverse is also true. The usable window is wherever the two overlap.
Before committing to a scope, it helps to inventory:
- Dispatch records: shape-up sheets, gang assignments, call-back logs, replacement and skip notes
- Reported work: the remittance and reporting detail the local received, by period and by employer
- Dues records: what was assessed, what came in, and how it was credited to each member
- Member records: seniority order, status changes, certifications and effective dates for the years in question
- Format notes: what changed, and when — a new form, a new reporting layout, a switch from paper to spreadsheets
That last item gets skipped and shouldn't be. Knowing that the hall changed its dispatch sheet format in a particular year explains a lot of apparent anomalies later.
Make the Years Comparable
Records from different eras rarely line up on their own. Names appear in different forms. Member numbers get reissued or reformatted. One year's sheets record a gang as a unit; another year records each member separately. Job categories get renamed. Periods don't always start and end on the same day across sources.
The prep work is mostly normalization: settling on one way to identify a member across every year, one way to express a work period, and one set of job and category labels with notes on what the older terms mapped to. None of that changes the underlying record — it just makes two sources describable in the same language so a difference is a real difference and not a formatting artifact.
This is where locals should expect the most time to go. It is also where the work pays off, because once the records speak the same language, the comparison itself is fast and repeatable.
What a Back-Year Pass Tends to Surface
When historical records are matched, the differences fall into familiar categories. Shifts that appear in dispatch but not in what was reported. Members reported under the wrong classification or at the wrong rate category for the work performed. Gangs reported short — fewer members than the hall dispatched to the job. Periods where reporting simply stopped and resumed. Dues that were assessed but never credited, or credited to the wrong member record.
Some of these turn out to be record-keeping differences on the hall's side, and finding those is useful too. Others point to work the local was never paid on, or to money an employer owes the local. The purpose of the pass isn't to assume any particular outcome — it's to produce a documented, period-by-period account of where the two records disagree, with the supporting pages attached to each item so the local can take it forward.
Sequence It So the Hall Keeps Running
A back-year review shouldn't compete with this week's dispatch. The practical approach is to get current-period reconciliation running cleanly first, then work backward one period at a time, finishing and documenting each before starting the next. That way the project produces usable findings early instead of one large result at the end, and the hall staff carrying it can set it down and pick it up without losing the thread.
It also helps to decide up front who reviews and signs off on each completed period, and where the findings live. A discrepancy nobody has reviewed is just a note in a file.
Built Around Your Records
No two locals kept records the same way, and no two will reconcile the same way either. DockOps is set up around the records a local actually has — its formats, its periods, its job categories, its sign-off process — rather than requiring the hall to reshape its history to fit a template. The goal is that the local's own record, going back as far as it reaches, becomes something it can query and stand behind.
— The DockOps Team
See how DockOps would fit your local — book a demo at dockops.app/book.