← All articles

Your Hall Runs on Rules. Your Software Should Too.

August 24, 2026 · 5 min read · By DockOps

Every local has a rulebook. Some of it is written in the bylaws and the contract. Some of it lives in decades of practice: how the shape-up runs, how gangs are built, how seniority is applied, how dues are handled when work is slow.

Now think about the software most locals have been offered over the years. Generic HR systems. Payroll tools built for a different industry. Spreadsheets someone built years ago that only one person understands. Each one, in its own way, asked the hall to bend to fit the tool.

That's backwards. Your hall runs on rules. Your software should run on the same ones.

Why generic systems don't fit the waterfront

Union workflows are unique, and longshore workflows even more so. Off-the-shelf software usually assumes a fixed employer, a fixed schedule and a fixed set of roles. A hiring hall has none of those. It has a call-back list, seniority classes, certification requirements by gang, membership windows, casual access rules, headers and subheaders, and a daily rhythm built around ships.

When a system doesn't understand those things, the hall ends up working around it. Staff keep a spreadsheet on the side. Dispatchers keep their real list on paper. The "system" becomes one more place data has to be copied into, instead of the place work actually happens.

Built around your local, not the other way around

DockOps starts from the opposite direction. It's configured around each local's existing rules: seniority order, eligibility and certification requirements, gang structure, dues categories, roles and permissions.

It enforces the rules the local already has rather than replacing them. The local keeps control of what those rules are and who can override them.

That flexibility goes all the way down:

Roles fit how your local is actually staffed. DockOps ships with roles for members, headers, dispatchers at more than one level, timekeepers and administrators, and locals can define their own. One person can hold more than one role.

Permissions are as precise as you need. Every area of the system can be granted independently for create, read, update, delete, list, menu visibility, download and view-your-own-records-only. Changing a work order's status is its own permission, so a dispatcher can edit a work order without being able to advance it.

The system looks the way you expect. Locals can set organization-wide appearance settings, including the palette that distinguishes members from non-members.

This isn't customization as an afterthought. It's the whole design.

Built by people who've lived it

There's a reason DockOps fits the hall. It was built by veteran software engineers working shoulder to shoulder with ILA leaders whose roots on the waterfront go back generations.

Dispatch rotations, shape-up procedure, seniority enforcement and grievance workflow weren't learned from a requirements document. They were run, every day, along with the unwritten rules and the human dynamics of the hall. Every workflow gets checked against the waterfront side before it ships.

The goal was never to automate longshore workers out of their own processes. It was to give the hall better tools for what it was already doing.

Replacing the old tools without breaking the work

The biggest fear any local has about new software is disruption. The hall can't stop working while a system gets installed. Members still need to go out tomorrow morning.

DockOps is built to modernize without breaking the structure members rely on.

It connects to what you have. DockOps has an API for connecting existing payroll and operational systems, plus automated and manual reports for recurring or on-demand exports. Where a local has an existing system it wants to keep for now, DockOps can work alongside it.

It meets members where they are. Members can use the app, tap a member card, or be checked in on their behalf by an authorized dispatcher. The hall display board shows what's happening for everyone. Nobody is forced onto a phone on day one.

Data comes with you. Exports cover timesheets, member profiles and certifications, with column selection, so records can be shaped for whoever needs them.

Scope is agreed up front. Implementation starts with a proposal built around your local's workflows, with scope, payment schedule and delivery milestones agreed before work starts.

Spreadsheets were never the problem. Silos were.

Spreadsheets got a lot of locals through a lot of years. The issue isn't that they're spreadsheets. It's that each one is an island. Dispatch in one file, dues in another, member records in a third, payroll in a fourth. Reconciling them is manual, error-prone and dependent on whoever built them.

DockOps connects those islands. Dispatch, timesheets, payroll reconciliation, dues, member records and administration live in one system, working from the same records. The member record isn't duplicated per department; it's one record used everywhere.

That's what makes everything else possible: same-day hours for members, weekly closing reports for the secretary-treasurer, a real-time dashboard for the board, and an audit trail for everyone.

For ILA and ILWU locals alike

Hiring halls differ from port to port and coast to coast. That's exactly why a system built around each local's own rules matters. Whether your local is an ILA longshore local, a clerks and checkers local, or one of the ILWU locals with its own registration and dispatch rules, the starting conversation is the same: how does your hall already run?

The shift

The old way: buy software, then change how the hall works to fit it.

The new way: start with how the hall works, and configure the software to fit.

Your local's rules took generations to build. They deserve a system that respects them.

Start with how your local already runs its hall. Book a demo at dockops.app/book.

— The DockOps Team