← All articles

Closing the Week Clean: What Belongs in a Weekly Closing Report

October 26, 2026 · 5 min read · By DockOps

Friday afternoon at the hall has a particular feel. The last dispatches are out, the phones have slowed, and someone is standing at the counter with a question about a job from Tuesday. Whether that question takes two minutes or two hours depends almost entirely on how the week was closed.

A weekly closing report is the hall's own summary of what happened: who was dispatched, who checked in, what dues came through, what got corrected, and what is still open. Done well, it becomes the record everyone trusts when a question comes up six weeks later. Done poorly — or skipped — it leaves the local reconstructing the week from memory, loose notes, and whatever the employer reported.

What a Closing Report Actually Covers

Every local runs a little differently, and a closing report should reflect the local's own practice rather than some generic template. That said, most closing reports pull from the same handful of areas.

  • Dispatch activity: jobs called, gangs filled, which list each dispatch came off, and any job that went unfilled or was filled out of normal rotation with the reason noted.
  • Check-in records: who checked in each day, who was marked absent or excused, and any check-in entered late or corrected after the fact.
  • Dues status: payments posted during the week, check-off amounts received, short or missed payments flagged, and members approaching the end of a grace period.
  • Member record changes: address and contact updates, seniority or certification changes, status changes, and who approved each one.
  • Open items: anything carried into next week — a disputed dispatch, a reconciliation question, a record change waiting on documentation.

That list is a starting point. Some locals add departmental breakdowns, certification coverage, or a separate section for call-back list movement. The point is that the report covers the week's operational reality, not just the parts that went smoothly.

Why Closing Clean Matters More Than It Looks

The argument for closing the week cleanly isn't paperwork discipline for its own sake. It's that almost every hard conversation the hall has later depends on records made during an ordinary week.

When a member asks why they were passed over on a particular morning, the answer lives in that week's dispatch record. When payroll reconciliation compares what was worked against what was reported, the hall's own dispatch and check-in data is the baseline on the local's side of the comparison. When a dues question surfaces months out, the trail of payments and flags written at the time is far more reliable than anyone's recollection.

Closing also surfaces small problems while they're still small. A check-in that never got entered, a dispatch logged to the wrong list, a dues payment short by a few dollars — each is a five-minute fix on Friday and a much bigger one in March.

Who Closes, and Who Reviews

In most halls, the dispatcher or hall staff assembles the week and an officer or business agent reviews it. Separating those two roles matters. The person who entered the week's activity is the right person to compile it, and a second set of eyes is the right way to catch what the first set missed.

Review doesn't have to be exhaustive. It usually means scanning for exceptions: out-of-order dispatches, late or amended check-ins, record changes made without approval, and dues flags that have been sitting too long. Those are the entries that tend to generate questions later, so they're worth a look while the week is still fresh.

Write down who closed the week and who reviewed it. If a record is ever questioned, knowing who handled it is half the answer.

Making It a Routine, Not an Event

Closing is easiest when it's a short, predictable step rather than a Friday scramble. A few habits help:

Enter dispatches and check-ins as they happen, not in a batch at the end of the week. Post dues and check-off as they arrive. Handle member-record changes through the local's approval process when they come in, so nothing is sitting unapproved at close. By Friday, closing should mostly be reviewing and confirming rather than catching up.

It also helps to keep the closed week visible. Officers, dispatchers, and business agents should be able to pull up last week — and the week before that — without digging through a drawer. When past weeks are a click away, questions get answered at the counter instead of becoming follow-ups.

How DockOps Handles It

DockOps assembles the week from the activity already recorded in the system: dispatch, check-in, dues, member-change approvals, and reconciliation status. The closing report is built around how the local already closes — which sections it includes, which exceptions it flags, and who reviews and signs off. Past weeks stay available, so a question about a job in October can be answered with October's record rather than a reconstruction.

No two locals run the hall the same way, and the closing report shouldn't pretend otherwise. It should look like the local's week, in the local's order, with the local's approvals attached.

See how DockOps would fit your local — book a demo at dockops.app/book.

— The DockOps Team