← All articles

Whose Numbers Are These, Anyway?

February 16, 2026 · 5 min read · By DockOps

Ask a simple question at your next board meeting: when a member's hours, dues or seniority are questioned, whose record settles it?

At a lot of longshore locals, the honest answer is uncomfortable. The record that settles it started somewhere else. It came in a payroll file, a remittance register, a spreadsheet a former officer built, or a legacy system nobody in the hall fully understands anymore. The local is expected to answer for those numbers, but it didn't create them, can't easily check them, and often can't find them quickly.

That's the paradigm DockOps was built to change. The idea is simple: the record should start with the local.

The old way: answering for numbers you didn't make

Think about how information has traditionally moved through a hall. A shape-up happens. Gangs go out. Work gets done. Then, days or weeks later, the paperwork comes back: hours, wages, dues withheld. The local's job becomes checking what someone else recorded, usually by hand, usually under time pressure, and usually with incomplete information.

When the numbers line up, nobody thinks about it. When they don't, the local is stuck reconstructing events from memory, phone calls and binders. Officers who weren't there have to defend or question records they never saw being made. Members who feel shorted have nowhere to look except the office window.

None of this is anyone's fault. It's just what happens when the local's own activity isn't captured as it happens.

The new way: the local's record comes first

In DockOps, the work order begins in the local's system. Members check in from the dock, by phone or with a member card at a tap station. Gangs are staffed on the flow board by the local's own seniority and certification rules. Check-off is recorded with a timestamp. When the work order is finalized, the timesheet is built from that recorded activity rather than typed in separately afterward.

That means by the time any payroll information comes back, the local already has its own account of what happened: who checked in, which gang, which job code, which date, how many hours. Reconciliation becomes a comparison between two records instead of a guessing game about one.

This is what "single source of truth" really means for a local. It isn't a slogan. It's the difference between asking "is this right?" and being able to show what's right.

Control means deciding who sees what

Owning the record isn't only about where data starts. It's about who controls access to it.

In DockOps, your local decides what is held about its members and who may see it. Access comes through accounts the local issues. Permissions are set per module and per action, so a local can let someone read a record without letting them export it in bulk. Members can be limited to seeing only their own records. When another office or system needs to connect, it gets only the access your local authorizes.

DockOps operates the software on the local's behalf, but it doesn't decide how member records are used. That's the local's call. DockOps doesn't sell member information or use it for advertising.

That's a real shift from systems where the local is a guest in someone else's database.

Accurate records protect everyone

There's a misconception that a local keeping its own records is somehow confrontational. It isn't. Accurate, timestamped records protect everyone who relies on them.

When a question comes up about a shift, a clean record answers it quickly. When a discrepancy appears between what was worked and what was reported, it can be caught early and reviewed calmly, with the source evidence attached, instead of turning into a months-long argument. Most discrepancies have ordinary explanations: a setup error, a late correction, a missing line. Finding them early is how they get fixed without drama.

The goal isn't to win arguments. It's to make sure there's nothing to argue about.

Built around how your local already works

Here's where many software projects go wrong: they hand a local a generic system and ask the hall to change how it operates. DockOps does the opposite.

DockOps is configured around each local's existing rules: its seniority order, its eligibility and certification requirements, its gang structure, its dues categories and its roles. It enforces the rules the local already has rather than replacing them, and the local keeps control of what those rules are and who can override them.

That matters for control, too. A system that forces your local into someone else's process isn't really yours. A system shaped around your bylaws, your hall and your people is.

What this looks like day to day

For officers, it means answers on demand instead of digging. A real-time dashboard shows active work orders, check-in and check-off activity, vessels, terminals and worker counts, with drill-down into gang and member detail.

For the secretary-treasurer, it means weekly closing reports that compare what the local expected to receive with what actually came in, with exceptions tied to their source.

For members, it means seeing their place on the call-back list, their hours and their certifications from their own phone, and being able to flag a problem while the work is still fresh.

For everyone, it means an audit trail. Changes to member records and operational data are logged with who made the change and when, so the history is there years later.

The question worth asking

Every local has records. The question is whether those records belong to the local's daily operations or arrive from somewhere else after the fact.

Locals already running DockOps at longshore ports have made that shift: the record starts at the hall, the rules are the local's own, and the numbers can be checked against something solid.

If your board has ever asked "whose numbers are these?", it might be time to make them yours.

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

— The DockOps Team