One Trip, Three Portals: The Agent That Logs Into eLandings and the Dealer Report So the Dock Manager Stops Re-Keying

5:10 a.m., the tender is alongside and the same weights get typed three times

The tender came off the grounds at ten past five and the offload is done by half past six. The scale printout is in the dock manager's back pocket, already damp. By eight o'clock those same numbers — species, grade, delivery weights, price, permit and vessel details — will have been typed into a landing report in one system, carried across into the dealer's own accounting so the crew settlement is right, and squared against the quota or allocation record that somebody in the office keeps in a spreadsheet because the two official systems do not talk to each other.

Same numbers. Three keyboards. During the peak of the run, that is not a nuisance; it is a full-time job that also happens to be the job where an error is most expensive, because a mistyped landing report is what a state biologist and a federal auditor will both read later.

This post is about the thing that changed in 2026: an AI agent can now drive those screens the way your office manager does — open the site, sign in, pick the right menu, fill the fields, hit submit and read the confirmation number back — in the many corners of this industry where there is no connection to build because nobody ever built one.

Why the connection you assumed existed was never built, and what changed this year

Fisheries reporting runs on web portals, and the portals were built for people, not for other software. Alaska's eLandings brings the state, the federal service and the halibut commission onto one landing report. On the East Coast, dealer reports and harvester trip reports move through the Atlantic Coastal Cooperative Statistics Program's systems, and permit holders sign in through the federal regional office's online services for electronic trip reports and permit business. Gulf and South Atlantic quota-share holders sign into a separate federal account system to file landing notifications and debit their shares.

Each one works. None of them was ever designed to hand its screens to your bookkeeping software, and no vendor is going to build a connection for a fleet of nine boats. So the connection has always been a human with two windows open and a printout on the desk.

Computer use means the agent operates the same screen a person does — signing in, clicking through the menus, filling the fields and reading back what the site said — instead of needing a special connection that nobody is ever going to build for a fleet your size.

Through 2026 the browser-driving ability of these agents crossed from party trick to something you can put on a daily job. It reads the page, finds the field, types, submits, and — the part that matters for a regulated filing — takes a picture of the confirmation screen and writes the confirmation number somewhere you can find it in eighteen months when somebody asks. It does not change the rules. Deadlines are still deadlines; the reports are still yours, filed under your permit, with your name on them. The agent is not a new legal category. It is a fast, literal clerk who does not get distracted at the peak of the run and does not go on the water in July.

flowchart TD
  A["Offload finished, scale printout in hand"] --> B["Agent opens the landing report and starts the ticket"]
  B --> C["Enters species, grade, weights, price, vessel"]
  C --> D{"Do the weights match the scale printout?"}
  D -->|No| E["Hold for the dock manager"]
  C --> F["Agent files the dealer report in the state system"]
  F --> G{"Portal rejects a code or a permit?"}
  G -->|Yes| E
  G -->|No| H["Confirmation numbers written into the trip folder"]

A Tuesday in July, run by the agent

The dock manager photographs the scale printout and the deck tally into the trip folder on the shared drive. That is his whole involvement until something needs a decision.

The agent opens the folder, reads the printout, and starts the landing report: vessel, permit, gear, statistical area, species and grade lines, delivery weights, price per pound. It fills what it can read and stops on what it cannot — an illegible grade line goes into a hold list rather than getting a best guess. It then moves to the second portal and enters the dealer side of the same landing, then updates the allocation spreadsheet with the pounds landed and what remains.

At the end of the run it writes one message to the office manager: nine landings filed, confirmation numbers attached, two held — one because the tally sheet grade line was unreadable, one because the portal refused a permit number that expired last week. That second one is worth the whole exercise; a permit problem found at 7 a.m. on the dock is an annoyance, and the same problem found in November during a renewal review is a much longer conversation.

The office manager clears both holds before her second coffee. What used to be five hours of typing across the week became forty minutes of exception handling.

The real risk is not the typing, it is the late filing

Every fishery has its clock. Trip reports carry short submission windows measured in days after the trip ends; dealer reports run on a weekly cycle; quota-managed landings need advance notification before the fish come over the rail. Miss enough of them and the consequence is not a fine in the mail, it is a hold on the thing you cannot operate without: your permit renewal, your quota transfer, your ability to declare into a trip.

Late filings almost never happen because someone refused to do the work. They happen because the work landed on the one week the office manager was covering the dock, or her kid was sick, or the run came all at once. An agent that files the same day, every day, removes the failure mode that actually bites: the backlog nobody noticed until it was three weeks deep.

Keep the confirmation numbers. Whatever the agent files, it should write down what came back — the confirmation, the timestamp, the screen it saw. That record is your defence, and it is more complete than the one a clerk keeps, because a clerk does not photograph every confirmation screen.

Six and a half hours a week at the peak of the run

Assumptions, illustrative for a small dealer taking nine to fourteen landings a week in season: forty minutes of portal work per landing across the three systems, eleven landings a week, an office manager at $34 an hour fully loaded, and an eighteen-week season.

The dollar figure is the smaller half. The larger half is that the office manager gets her July back and spends it on the receivables that are genuinely aging, which on most docks is worth more than four thousand dollars.

Three places to keep a person in the chair

First, anything the agent could not read. A soaked tally sheet with a smeared grade line must go to a human, and the rule should be explicit: no guessing on species, grade or weight, ever. The whole value of the filing is that it is true.

Second, sign-in credentials and anything touching your permit identity. Give the agent its own access where the system allows it, keep multi-factor codes going to a person, and never let it change permit or account details on its own. Filing a report is routine. Changing who you are on a federal system is not.

Third, corrections. When a landing has to be amended after the fact — a re-weigh, a mis-sorted grade, a price adjustment agreed with the captain — that is a conversation between the dock manager and the captain that ends with a person hitting submit. An agent quietly amending an earlier filing is exactly the pattern you do not want in a regulated record.

Frequently asked questions

Is it allowed? These are government systems.

The reports are yours, filed under your permit, and you remain responsible for their accuracy whether a clerk or an agent typed them. Read the terms of use of each portal before you point anything at it, keep the sign-in tied to a named person in your office, and treat the agent as staff. If you are unsure about a specific system, ask your port agent or state licensing office — they field this question regularly now.

What happens when a portal changes its screens?

It breaks, and you want it to break loudly. Set it up so a failure raises a message to a person rather than retrying blindly, and expect a short period after any portal update where a human files while somebody adjusts the routine. This is the main ongoing maintenance cost and it is honest to name it.

Our office manager knows all the quirks. Doesn't this throw that away?

The opposite, if you do it right. Sit with her for two mornings and write down every quirk — the code the system expects for a mixed-grade delivery, the field that has to be blank rather than zero, the order the screens must be filled in. That list is the most valuable document your office produces, and right now the only copy is inside one person who will eventually retire.

Do we still need the paper?

Keep whatever your fishery and your state require, in the form they require. The agent's job is to stop the re-typing, not to change your record-keeping obligations. Most operations end up with better paper afterwards, because confirmation screens get filed automatically instead of ending up in a drawer.

Where to start on Monday

Pick the most repetitive filing you do — usually the dealer report — and have someone screen-record themselves doing three of them start to finish, narrating every quirk. That recording is the instruction sheet. Automate that one filing, watch it for two weeks with a person checking every submission, then add the second portal.

CallSphere builds AI voice and chat agents for the other side of that morning: the phone that rings while the offload is happening. Boats calling in ETAs, buyers asking whether the tender is in, a chef looking for tomorrow's availability — answered, logged and routed, so the office can stay on the filings instead of jumping between the handset and the portal.