← All articles

Nothing Changes Until the Local Says So

June 1, 2026 · 5 min read · By DockOps

Who changed that member's phone number? Their documents? Their status?

And who approved it?

At too many locals, the honest answer is "we're not sure." A record got updated somewhere along the way. Maybe at the window, maybe in a spreadsheet, maybe by someone who's since moved on. The change might have been right. It might not have been. Either way, there's no trail.

That's a quiet problem until it isn't. A wrong address means a missed notice. A wrong status can affect standing. A document that was never really verified can create headaches at the worst possible time.

DockOps is built on a simple principle: the member record belongs to the local, and nothing changes until the local says so.

Why member records drift

Member records drift for ordinary reasons. People move. Phone numbers change. Certifications expire and get renewed. Names change. Documents get updated.

Each of those is a legitimate change. The trouble is how they get made. When changes come in through hallway conversations, phone calls, paper forms and spreadsheet edits, the record slowly becomes a patchwork. Nobody can say with confidence which version is current, or why it changed.

The traditional fix is to lock everything down so only the office can make changes. That creates a different problem: members wait, the office gets buried, and updates fall behind.

The better answer is to let members request changes easily, and keep the local firmly in control of approving them.

How the approval queue works

In DockOps, members can submit an information change request directly from their profile. They don't edit the record themselves.

The request goes to your administration's approval queue with three things side by side: the current information, the proposed change and any supporting documents. An authorized administrator reviews it and decides.

Nothing replaces the live member record until your local approves it. And DockOps keeps who submitted the request, who reviewed it, the decision and the before-and-after values.

That's a safeguard against errors in both directions. Members can't accidentally (or deliberately) put wrong information on their own record. And legitimate updates don't get lost in a stack of paper, because they're sitting in a queue waiting for a decision.

Documents get the same treatment

The same principle applies to documents. When members upload documents, they go into an approval queue for administrator review rather than straight onto the record.

A member's profile shows approved documents only. Pending and rejected submissions stay out of the profile view, while the underlying records are kept for history. So there's always a trail of what was submitted and what happened to it.

One living record per member

The approval queue matters because of what it protects. In DockOps, each member has one record that holds seniority, member type and status, hours worked, certifications with their expiry dates, approved documents, assignment and work history, and the contact and emergency information the local maintains.

That one record is used across dispatch, payroll and administration rather than duplicated per department. When it's right, everything downstream is right: check-in eligibility, gang assignments, dues standing, notices. When it's wrong, the errors spread.

Protecting that record isn't bureaucracy. It's how a local makes sure every member is treated correctly everywhere the record is used.

Controlled changes for the big stuff, too

Some changes go beyond a phone number. DockOps supports seniority assignment and reassignment as a controlled action, so a local can correct or restructure seniority when it needs to, with the change recorded rather than made quietly in a spreadsheet.

When administrators need to update many members at once, DockOps provides bulk profile editing through an inline grid. Bulk operations show a preview of the change before it's applied, and bulk status changes are written to the audit log.

The audit trail that backs it all up

Underneath the approval queue is a complete audit trail. DockOps writes changes to member records and operational data to an audit log, including who made the change, when, and the old and new values. Change history is viewable and filterable by date.

That's what makes the record usable when it really counts: in a grievance, a dues dispute or a review months or years later. "Who changed that?" stops being a mystery and becomes a lookup.

Better for members, not just the office

It would be easy to see an approval queue as purely an administrative control. But members gain just as much.

They can request updates from their phone instead of making a trip to the hall. They can see that their request is in the queue. They can upload documents and certifications by photographing them. And they can trust that their record won't change without the local's review.

DockOps also reports on members whose certifications have expired or are lapsing, and on members with incomplete onboarding, so administrators can act before someone is blocked at the hall. That's the kind of quiet help that makes a member's day go smoother.

Set up around your local's rules

Who can approve what, which fields need review, which documents your local requires: all of it is configured around how your local works. Permissions are set per module and per action, so a local can grant exactly the access each job requires and no more.

The shift

The old way: records change quietly, and nobody's sure who did it.

The new way: members request, the local approves, and every change has a name, a date and a reason attached.

Your local's record should be something everyone can trust. The approval queue is how it stays that way.

See the member-change approval queue in action. Book a demo at dockops.app/book.

— The DockOps Team