DockOps is workforce management software for ILA longshore union locals. It connects dispatch and shape-up, payroll reconciliation, union administration, and member records in one system that members, headers, dispatchers and administrators all work from.
62 questions across 10 categories
What DockOps is, who it is for, and who builds it.
DockOps is workforce management software for ILA longshore union locals. It connects dispatch and shape-up, payroll reconciliation, union administration, and member records in one system that members, headers, dispatchers and administrators all work from.
DockOps is built for ILA longshore union locals and the people who run daily operations at the port: members who work the ships, headers who run gangs, dispatchers who staff them, timekeepers who handle payroll, and the administrators who keep member records, dues and grievances in order. It is not a consumer app — access comes through a participating local.
DockOps runs dispatch and shape-up with seniority-based staffing, maintains the call-back list, records check-in and check-off from the dock, turns that activity into review-ready timesheets, reconciles payroll against dispatch records to surface pay shortages, tracks dues, moves grievances and discipline through role-based review, and keeps one current record per member covering seniority, hours, certifications, documents and status.
DockOps is organized into four connected suites. Port Flow handles dispatch and operations — shape-up, the call-back list, check-in, gang staffing, work orders and timesheets. Ledger handles finance — dues and payroll reconciliation against dispatch. Bridge handles administration — grievances, discipline, documents, surveys and approvals with role-based access. Seafarer holds member records — seniority, hours, certifications, history and status.
DockOps is built by veteran software engineers working alongside ILA leaders — people with deep roots on the waterfront and decades of history running longshore operations, from the union hall to the berth. It grew out of that firsthand experience on the docks of Florida rather than from a requirements document.
Both, and that is the point. DockOps records dispatch and attendance as the work happens, then uses those same records to verify payroll, so a pay shortage can be traced back to the shift that created it. Locals running separate dispatch and payroll tools have to reconcile them by hand; DockOps connects them.
No. DockOps enforces the rules the local already has rather than replacing them. Seniority order, eligibility and certification requirements are applied automatically during staffing, and the local keeps control of what those rules are and who can override them.
Getting an account, what each role can do, and how sign-in works.
Members sign in with the account their local issues them. There is no public sign-up: a local has to be using DockOps first, and the local controls which role each person has and what that role can see. If a local is not yet using DockOps, its officers can request a walkthrough through the DockOps contact page.
DockOps ships with roles covering the way a local is actually staffed — members, headers, dispatchers at more than one level, timekeepers, and administrators — and locals can define their own. Each role is built from per-module permissions rather than a fixed template, so a local can grant exactly the access a job requires.
Permissions in DockOps are set per module and per action. Every area of the system — work orders, timesheets, documents, grievances, dues, the status board, audit logs and the rest — can be granted independently for create, read, update, delete, list, menu visibility, download, and view-your-own-records-only. Some actions are separated deliberately: changing a work order status is its own permission, so a dispatcher can edit a work order without being able to advance it.
Yes. DockOps supports users holding more than one role, and permission checks combine them, so someone acting as both a dispatcher and a timekeeper gets the access both roles allow without needing a second account.
Members sign in with the credentials their local issues. DockOps supports SMS-based authentication, and the mobile app supports biometric sign-in on devices that offer it, so members are not typing a password on the dock every shift.
Yes. DockOps includes a check-in on behalf capability for situations where a member cannot check themselves in, such as an authorized call-in. It is access-controlled, so only the roles a local grants it to can use it, and the action is recorded.
The call-back list, check-in, the flow board, gangs and work orders.
DockOps maintains the call-back list in seniority order so members can see exactly where they stand before leaving home. Dispatchers work the list from the same view, and when a gang needs a replacement DockOps draws from the call-back list. If the list is exhausted, dispatchers can record an alternative rather than being blocked.
The flow board is the live status board for the day. It shows who has checked in to each gang on each vessel, with seniority at a glance and certification abbreviations against each member, so headers and dispatchers can see staffing levels as they fill. It can be displayed on a screen in the union hall as well as on the web and in the mobile app.
Members check in and check off from the dock through the DockOps app, and locals can also use badge-based check-in. Check-in respects membership windows, casual access rules and authorized call-in overrides. Where a gang requires a certification, members without a valid, active credential are blocked from checking in to it automatically.
Gangs are configured with headers, subheaders and the roles the job requires, then staffed from the board. DockOps applies seniority order and checks certification eligibility as members are assigned, so an ineligible member cannot be placed into a role that requires a credential they do not hold.
Finalizing a work order in DockOps closes out the day for that job: the timesheet is completed from the recorded dispatch and attendance activity, checked-in members are notified by text message and push notification, and the record is written to the audit log. The flow board keeps its members after finalizing, so the finished record stays intact.
Yes. DockOps holds records for vessels, terminals and stevedoring companies, and work orders are tied to them. Vessel assignments connect a job to the ship it is being worked, which is what lets timesheets and payroll reconciliation trace back to the specific vessel and terminal.
DockOps has fallback and enforcement behaviour for missed deadlines, including auto-submit, dispatcher edits and approvals, timekeeper notification, and a no-show toggle a local can enable. The intent is that a shift is never lost because a form did not get filled in.
Morning Shape-Up · East Berth
Live workforce board
47 checked in
Badge, call-in, and mobile confirmations
From dispatch records to payroll analysis and employer payment accountability.
Timesheets in DockOps are generated from the dispatch activity itself rather than entered separately. Check-in, gang assignment and check-off records build the timesheet as the day runs, and finalizing the work order completes it. Header selection timers, overage queue handling and certification-based eligibility are applied along the way.
Yes. DockOps includes a timesheet adjustment workflow so corrections go through review rather than being made silently. Adjustments are recorded in the audit log with who made them and when, which is what makes the record defensible later in a grievance or a dues dispute.
DockOps compares employer payroll and remittance records with dispatch and timesheet records to identify what was due, what was paid, and what remains outstanding. The focus is money shipping companies, cruise lines, and stevedores owe members, locals, the ILA, and the Pension & Welfare office. Supporting records help the local review differences and pursue payment.
Members, their locals, the ILA, and the Pension & Welfare office. The goal is to identify underpayments by the companies responsible for wages and remittances. This also supports review of benefit amounts owed to families and eligible heirs. Dispatch, member profiles, and union administration remain core parts of DockOps alongside this financial work.
Timekeepers get a download built for their workflow, kept separate from the end-of-day record so the two do not interfere with each other. Timekeepers can be granted create and update rights on work orders where a local wants them to, and the timesheet export stays complete after the board clears for the day.
Yes. DockOps keeps dues and strike fund records alongside payroll reconciliation. The employer accountability focus is on dues withheld through payroll that must be remitted to the local: comparing amounts due with payments received and documenting any shortfall for collection follow-up.
Yes. DockOps includes record exports covering timesheets, member profiles and certifications, with column selection so an export can be shaped for whoever is receiving it. Exports are permissioned separately from viewing, so a local can let someone read a record without letting them download it in bulk.
Employer Payroll Analysis
Interactive ExampleStill Owed by Employers · All Years
$1,197,150
All companies · All recipients
Choose a Year · Select to Drill Down
| Who Owes | Still Owed |
|---|---|
| $299,247 | |
| $239,387 | |
| $215,433 | |
| $179,522 | |
| $143,599 | |
| $119,962 |
Fictional companies and amounts for illustration. Payroll weeks end on Sunday and belong to the month and year of their ending date. No actual findings or recovered payments.
The DockOps API, automated and manual reports, and DockOps: Pension & Welfare, with access controlled by the local.
Yes. The DockOps website has a fictional employer contribution walkthrough showing source hours, a sample rule, investigation and confirmation, partial receipts, settlement, and separate office/member evidence views. The integrations page includes illustrative manual and recurring CSV reports. These are review examples; office contribution rules, payment allocation, API mappings, report delivery, and member-facing evidence are configured and validated for the agreed implementation.
Yes. DockOps has an API for connecting existing payroll, benefit, and operational systems. It also provides automated reports for recurring delivery and manual reports generated on demand, with exports of approved records. API updates depend on the connected system’s supported interfaces. For the most complete, real-time pension and welfare integration, an office can use DockOps: Pension & Welfare within the same platform. The local controls the data each office can access.
Yes. A Pension & Welfare office can connect its existing system through the DockOps API, receive automated reports, or generate manual reports on demand. It can also use the DockOps: Pension & Welfare module for the most complete, real-time integration of approved member records, work hours, employer contributions, reconciliation, and reporting. Pension & Welfare is treated as one office. The local controls which records that office can access and export.
Yes. DockOps supports Vacation & Holiday Fund offices as a distinct group alongside Pension & Welfare. Their workflows can use hours, employer contribution records, and reporting through direct API connections, automated or manual exports, or DockOps modules. The local approves access to its records and the information shared with the fund office.
Yes. DockOps supports clerks and checkers locals through its dispatch, timesheet, payroll analysis, administration, and member-record modules, configured around the local’s roles and rules. Related locals and offices can connect through approved integrations or use DockOps modules, with each local controlling access to its own records.
Dispatch check-in records provide operational context and may include estimates. DockOps keeps recorded authoritative hours and their source distinct from those estimates. Each fund defines its qualifying hours, reporting year, and final eligibility decisions. Work performed outside DockOps still needs the appropriate authoritative records or imports.
The local union controls access to its DockOps records. It decides which offices and users can connect, what they can view, and what they can export. Direct integrations and shared modules use only the access the local authorizes, so connecting another system does not grant unrestricted access to member information.
Profiles, certifications, document approval and change requests.
A DockOps member record holds seniority, member type and status, hours worked, certifications with their expiry dates, uploaded documents, assignment and work history, and the contact and emergency information the local maintains. It is one record per member, used across dispatch, payroll and administration rather than duplicated per department.
Certifications are held on the member record with expiry dates, shown as abbreviations against members on the flow board, and enforced at check-in and gang assignment — a member without a valid, active credential cannot be placed into a role that requires it. DockOps also reports on certifications that have expired or are lapsing so a local can act before a member is blocked.
Documents members upload go into an approval queue for administrator review rather than straight onto the record. A member 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 is a trail of what was submitted and what happened to it.
Members can submit an information change request from their profile, which goes to the local’s administrators for approval. The member does not edit the record directly — the local stays in control of what its records say, and the request and its outcome are recorded.
Yes. DockOps includes bulk profile editing through an inline grid, so fields like years and hours can be updated across many members without opening each record. Bulk operations preview the change before it is applied, and bulk status changes are written to the audit log.
Yes. 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.
Yes. DockOps reports on members with incomplete onboarding and on expired certifications, so administrators can see who is missing something before it becomes a problem at the hall.
Member record
Current across web and mobile
Phone
(904) 555-0142
Home port
Jacksonville
Primary role
Crane operator
Emergency
Contact on file
Grievances, discipline, member voice, announcements and the audit trail.
Grievances are submitted, categorized by grievance type, and moved through role-based review in DockOps — from submission to assignment, hearing and resolution. Each step is recorded, so the local has a defensible history rather than relying on who remembers what.
Yes. DockOps includes a disciplinary referral workflow with role-based access, so referrals are submitted and reviewed inside the system and the record is retained with the member’s history. Locals can also define enforcement policies that the system applies.
DockOps includes Voice Your Concern, a channel for members to raise issues to the local through the system rather than catching someone in the hall. DockOps also supports employee surveys where a local wants to gather feedback more broadly.
Administrators post announcements in DockOps and members are notified. Announcements reach members in the app and by push notification, and notification routing respects roles, so gang-type notifications can be directed to administrators and dispatchers rather than going to everyone.
Yes. DockOps writes changes to member records and operational data to an audit log, including who made the change and when. Bulk flow-board status changes are recorded as well. Change history is viewable and filterable by date, which is what makes the record usable in a grievance, a dues dispute or a compliance review.
Yes. DockOps holds calendar events such as dispatcher rotations and vessel dates, and members can add them to the calendar on their own device from the mobile app.
Locals can set appearance settings across the organization, including the palette used to distinguish members from non-members, so the system reads the way the local expects rather than forcing one fixed presentation.
Bridge · Case workflow
Grievance GR-1048
Grievance
A. Rivera · Updated just now
Machinery check
D. Nelson · Updated just now
Time adjustment
J. Marshall · Updated just now
What members and staff can do from a phone.
Yes. DockOps has native apps for iPhone and Android, free to download from the Apple App Store and Google Play. The app gives members the call-back list in seniority order, work orders and start times, the flow board, check-in and check-off, push alerts, calendar entries, and their own profile and certifications.
Yes. Dispatchers and administrators use the same DockOps app as members, with their own role’s access. Gang management, timesheet adjustments, moving work orders through dispatch and finalize, and sending announcements can all be done from the phone.
DockOps sends push notifications to the mobile app and in-app notifications for events that matter: a work order created, a status change, a start time announced, an announcement posted, and call-back activity. Checked-in members are also texted when a work order is finalized. Routine check-in and check-off activity is deliberately kept out of the mobile alerts feed so the feed stays useful.
Yes. Push notifications can be turned off in your device settings, and DockOps keeps working without them. You would then be checking the app for work orders and status changes rather than being told about them.
Either. DockOps runs as a full web application as well as native iOS and Android apps, on the same records. Members generally use the phone, while leadership and administrative work tends to happen on the web where there is more room on screen.
Who can see what, and how member information is protected.
DockOps holds the employment records a local already maintains — name and contact details, role, membership type, status, seniority and hours — plus documents and certifications members upload, and the check-ins, assignments and timesheet changes that using the system creates. The local decides what is held and who may see it; access is enforced by role on the server, and changes to member records are written to an audit log.
Access to DockOps requires an account issued by the local and is enforced on the server for every request, not only in the interface. Traffic is encrypted in transit, data is encrypted at rest, and changes to member records are written to an audit log. Members can be limited to viewing only their own records where that is the appropriate level of access.
DockOps does not sell member information, use it for advertising, or track members across other companies’ apps or websites. There is no advertising identifier in the app. Information is shared with the local, with offices and systems the local authorizes through controlled access or exports, with the service providers needed to run the system, and where the law requires it.
The local. Your union local decides what is held about its members and who may see it. DockOps operates the software on the local’s behalf but does not decide how member records are used, which means requests to change or remove information are the local’s to grant.
The DockOps app asks for notifications, to tell you when a work order is posted or a start time is announced; calendar access, only when you tap to add an event, and only to write the event you chose; and photos or camera, to let you upload or photograph documents and certifications. Only the files you choose are uploaded, and DockOps does not read your existing calendar.
What it costs, and what bringing DockOps to a local involves.
DockOps offers implementation and licensing, or managed monthly access, under an agreed contract. Infraxio retains ownership of DockOps and its intellectual property. Pricing depends on the local’s size, workflows, integrations, customization, and support needs. Request a proposal through the DockOps contact page. The mobile app is free to download.
Infraxio owns DockOps and its intellectual property. Your local receives the internal-use license or managed access specified in its contract, with configuration and customization for the agreed workflows. The agreement defines hosting, support, data access, and deployment responsibilities. Licensing or hosting DockOps does not transfer ownership of the software.
No. The DockOps mobile app is free to download from the Apple App Store and Google Play under either commercial model. Members sign in with the account their local issues them.
Officers at a local that is not yet using DockOps can get in touch through the DockOps contact page and ask for a walkthrough. DockOps is configured around a local’s existing rules — seniority, eligibility, gang structure and roles — so the conversation usually starts with how that local already runs its hall.
Still have a question? Contact the DockOps team, see pricing, or read the privacy policy.