← All articles

When an Officer Leaves, the Records Shouldn't Leave With Them

September 14, 2026 · 5 min read · By DockOps

Every local has that person. The one who knows where everything is. Which binder has the old seniority list. Why a member's status was changed back in a slow year. How dues were handled during that dispute. Which spreadsheet tab actually matters.

Then one day that person retires. Or loses an election. Or simply moves on.

And a surprising amount of the local's history goes with them.

Institutional memory is a risk you can't see

Turnover is part of union democracy, and it's healthy. New officers bring new energy. But when a local's records live in people's heads, personal files and one-off spreadsheets, every transition is a risk.

New officers inherit decisions they can't explain. Grievances come up about events nobody remaining can describe. Dues questions reach back into periods nobody documented. A seniority correction made years ago looks like an error because the reason was never written down.

None of this shows up on a balance sheet. But it shows up in disputes, in delays, and in members' confidence that the local knows what it's doing.

The old paradigm relied on memory. The new one relies on the record.

Replace memory with structure

DockOps was built around a simple idea from the waterfront: union administrators need defensible records for grievances, dues reporting and compliance, and structured, timestamped, role-based workflows are how you get them.

That means the important things a local does every day are captured as they happen, inside the system, not reconstructed later.

Dispatch decisions are on record. Every assignment, override, replacement and headcount change keeps who made it, the reason and the history.

Member records have a full history. Changes are written to an audit log with who made them, when, and the old and new values. Change history is viewable and filterable by date.

Seniority changes are controlled. Seniority assignment and reassignment are controlled actions, recorded rather than made quietly in a spreadsheet.

Dues and grace periods leave a trail. Requests, approvals and exceptions are recorded, along with the member's ledger history.

When a new officer asks "why is this the way it is?", the answer is in the system, not in someone's memory.

Grievances and discipline with a defensible history

Few things depend on institutional memory more than grievances and disciplinary matters. They can stretch across months and sometimes across administrations.

In DockOps, grievances are submitted, categorized by type and moved through role-based review, from submission to assignment, hearing and resolution. Each step is recorded. Disciplinary referrals are submitted and reviewed inside the system with role-based access, and the record is retained with the member's history.

So when leadership changes mid-grievance, the new officer picks up a complete file, not a handoff conversation and a box of papers.

Reconciliation that survives a change in office

Financial follow-up is especially vulnerable to turnover. A discrepancy flagged by one secretary-treasurer can easily be lost when the next one takes over.

In DockOps, reconciliation findings stay attached to their source evidence: the member, the work period, the source record and the running balance. What was verified, corrected or settled is tracked over time. Weekly closing reports export for follow-up and audits.

The work one officer started doesn't disappear when they leave. The next officer can see exactly where things stand and carry it forward.

Getting new officers up to speed

A new officer in a records-in-people's-heads local can spend months just learning where things are. In DockOps, they log in and see the local as it is.

The real-time dashboard shows active work orders, check-in and check-off activity, vessels, terminals and worker counts. Member records are one place, used across dispatch, payroll and administration. Reports surface expiring certifications and incomplete onboarding. Audit logs answer the "who did that?" questions.

And because permissions are set per role, a new officer can be granted exactly the access their position requires on day one, while a departing officer's access can be removed just as cleanly.

Protecting the local, not just the officer

There's an important point here about whose records these are. When records live in an individual's files, they can feel like that person's property, even when nobody intends it that way. When records live in the local's system, they belong to the local.

In DockOps, the local decides what's held about its members and who may see it. Access comes through accounts the local issues and controls. That's a structural protection for the local's continuity, independent of who holds office.

Continuity for members, too

Members feel turnover more than officers sometimes realize. A new face at the window who can't find a record. A question that used to get a quick answer now taking weeks. A sense that things are less certain than they were.

When the record is solid, members experience continuity. Their hours, their certifications, their standing and their history are all exactly where they were the day before the election. Their trust in the local doesn't depend on any one person still being there.

Built around how your local operates

Every local structures its offices differently: different titles, different responsibilities, different approval paths. DockOps is configured around how your local works, so the right records, approvals and permissions follow each role, whoever holds it.

The shift

The old way: the local's history lives with the people who made it.

The new way: the local's history lives with the local, structured, timestamped and ready for whoever comes next.

People will always change. The record shouldn't have to.

See how DockOps keeps your local's history in one place. Book a demo at dockops.app/book.

— The DockOps Team