← All articles

Who Signs Off on a Change? Approvals That Keep Member Records Trustworthy

November 9, 2026 · 5 min read · By DockOps

A member record is never finished. People move. Certifications expire and get renewed. Status changes from casual to registered, or from active to inactive and back. Names change. Phone numbers change three times in a year. Every one of those edits is small on its own, and every one of them feeds something bigger — who gets dispatched, who sits where on the list, whose dues are current, and what the local can prove if a question comes up later.

The question that decides whether a record stays trustworthy isn't can someone make the change. It's who reviewed it, and can you tell six months from now.

Why Approvals Matter More Than They Look

Most record changes are routine and correct. The problem is that the routine ones look exactly like the ones that aren't — until a member disputes a rotation position or a seniority date, and the hall has to explain where the current number came from.

Without a review step, a few predictable things happen. A certification gets marked current based on a member's word, and nobody has the card on file. A seniority date gets corrected by one person and corrected back by another. A status change gets entered during a busy shape-up and nobody remembers the reason. None of that is bad faith. It's just what happens when edits go straight into the record with no second set of eyes and no note explaining why.

An approval step doesn't slow the hall down if it's built right. It just makes sure that the record reflects a decision somebody actually made, rather than a keystroke nobody remembers.

Not Every Field Needs the Same Treatment

The mistake locals make when they tighten this up is treating all changes alike. If a dispatcher has to route a phone number update through an officer, the process gets ignored within a week.

It's more useful to sort fields by what they affect:

  • Contact information — address, phone, emergency contact. Low risk. Update it and move on, with the edit logged.
  • Certifications and endorsements — these determine eligibility for specific work. They need documentation attached and a reviewer confirming it.
  • Status and classification — registered, casual, active, inactive, retired. These change how a member is treated on the list. Officer-level review.
  • Seniority dates and standing — the highest-stakes fields in the system. These should require a reason, supporting documentation, and sign-off by whoever the local's rules say owns that decision.

Where each field lands is the local's call. A small hall may want one officer approving everything above contact info. A larger one may split it between the dispatcher, the business agent and the secretary-treasurer. DockOps is configured around the local's own structure — who approves what is set up to match how the hall already assigns responsibility, not swapped for someone else's org chart.

What a Good Approval Record Contains

When a change is reviewed, the useful thing to capture isn't just approved. It's enough context that someone reading it cold can reconstruct the decision.

That generally means the field that changed, the old value and the new one, who requested it, who approved it, the date and time, the reason given, and any document attached — a certification card, a signed form, a referral slip. The old value matters more than people expect. If you only store the current state, you can't answer "what did it say before?" and that's the question that usually gets asked.

Handling Requests From Members

A lot of changes start with a member walking up to the window. Giving them a way to submit the request — in person, on paper, or through the system — and then routing it to the right reviewer accomplishes two things. The member gets a clear answer about where the request stands, and the hall gets a record that the member asked, rather than a mystery edit.

It also cuts down on the repeat visits. If a member can see that their certification update is pending review, they stop asking every shape-up.

A Short Checklist for Tightening This Up

  • List every field in the member record and mark which ones affect dispatch, dues or standing.
  • Decide who approves each tier, and name a backup so nothing stalls when someone's out.
  • Require a reason on any change to status, seniority or certification.
  • Attach documentation where documentation exists, rather than keeping it in a separate folder.
  • Review pending changes on a fixed schedule so requests don't sit.
  • Check the change log periodically — not to catch anyone, but to see where the process is being worked around.

The Payoff Shows Up Later

Nobody feels the benefit of an approval workflow on the day they set it up. It shows up the day a member questions their position on the list, or a reconciliation turns up a discrepancy that traces back to a status change, or an officer needs to explain a decision made under a previous administration. At that point, the record either answers the question or it doesn't.

Building the approval structure around how the local already divides responsibility is what keeps it in use. A process that matches the hall gets followed. One that fights it gets bypassed.

— The DockOps Team

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