HawkLine®

Visualise your whole operation. Live.

with

HawkLine® Bridge (RRTally)

RoRo Operation Command Center

HawkLine® Bridge — formerly RRTally — is the RoRo tally and operation command center for stevedores, terminals and vessel operators. From the manifest landing in your inbox to the unit leaving your yard — one live picture instead of a hundred records.

  1. Manifestany format
  2. Yardblock · row
  3. SurveyPDI
  4. Wharframp side
  5. Vesseldeck · hold
  6. Shiftingon board
  7. Dischargeverified out
  8. Yardplaced · found
  9. Customerhanded over

Every stage visible. As it happens.

The manifest

The Manifest Engine processes every format they send you.

Drop the files in exactly as they arrive — no reformatting, no re-typing, the engine does the rest. ISO 3779 World Manufacturer Identifiers built in: every manufacturer recognised on sight. Ports are UN/LOCODE.

As it arrives

  • PDFCargo manifestscanned document
  • XLSMaker format Adelivery list
  • XLSMaker format Bdispatch VIN list
  • IMGVIN sheetsphoto · scan · tiff
  • CSVBooking listagent spreadsheet

Different makers. Different agents. Different shapes. The engine takes them all.

Manifest engine

powered by HawkLine data pipeline

Captured once.

— no re-typing, no re-entry, ever. New formats are onboarded as configuration, not a software release.

One structured cargo record

  • VIN
  • WMI
  • Make
  • Model
  • POL → POD
  • Dims
  • Weight
  • + more

Hand every party the shape they ask for

  • Excel vehicle list
  • Voyage report PDF
  • Stowage-plan PDF
  • Transit pass — four per A4, QR

The same record powers the operation

  • Tally
  • Deck plan
  • Yard
  • Reports
  • Transit pass

Captured once at the manifest — no re-entry, ever.

The yard

Visualise the yard from placed to on board.

One record follows the unit through the yard — every step time-stamped, every step visible in the office. Nothing is written twice; nothing is lost between steps.

  1. 1

    Placed

    Block · row · column, GPS, keys and notes captured at the car.

  2. 2

    Surveyed

    PDI against your checklist — damage, photos, shipping marks.

  3. 3

    Ready

    Cleared for shipment; trouble flagged in the open — won't start, no key, damaged.

  4. 4

    To the wharf

    A move is a new event, never an edit — old and new position both kept.

  5. 5

    On board

    Verified at the ramp, placed on the deck — the yard record closes, the stowage record opens.

The office sees · units in the yard by POD

  • liveUSLAX · Los Angeles
  • liveDEBRV · Bremerhaven
  • liveSGSIN · Singapore
  • liveJPYOK · Yokohama
  • arrived, not yet placed
  • trouble
  • surveyed
  • double-claimed cells

Ask the yard

Where is …4821?
Block B · R2 · C3
What is ready for Bremerhaven?
surveyed · no trouble · by block
What came in and isn't placed?
pending list · live

The phone captures. The office sees. Illustration — not customer data.

The yard · live

Visualise your yard in real time.

Every placement is captured on the phone — block, row, column — and seen block by block in the office as the team works. What used to be a walk around the yard becomes a question you type.

Find any unit in seconds

Search a VIN, get its position — and everything recorded with it.

  • VIN search
  • GPS at placement
  • Keys · notes · trouble

Coverage that tells the truth

The office sees what the yard doesn't know, too — flagged in the open, never hidden.

  • Pending
  • No position yet
  • Double-claimed cell

Every move is a new record

A re-parked unit is a second event, never an edit — old and new positions both kept. When a dispute comes, the history is already there.

Survey (PDI)

Visualise every unit's condition before it moves.

PDI (cargo survey) is built in. The surveyor records damage, photos and shipping marks at the car against your own manufacturer-specific checklist — and every answer becomes a datapoint you can report on.

Your checklist, not a generic form

Manufacturer-specific PDI templates you build and modify yourself.

  • Checkpoints & logic
  • Multichoice · numeric · sums

Damage the way the claim needs it

Every damage is structured — VIN-linked, time-stamped, with photos — not a line in a notebook.

  • Damage + photos
  • Shipping marks
  • Unit & overall KPI

Filled at the car. Submitted from the office.

Surveyors work on the phone, offline if needed — drafts auto-save and sync. Supervisors review and submit from the web portal. Condition flags raised at the tally also surface on the live monitor and in the voyage report.

How you verify

Scan it. Or type it. Verified in seconds.

Scan the maker's label, or type the last few characters of the VIN. Every unit checked against the manifest the moment it crosses — on the phone and in the office.

Scan
13:00▮▮▮
Verifypending · live
▣ Scan⌨ Type

Point at the VIN barcode or QR

Tap the box for 2× zoom · torch

Reads every code type

  • QR code encoding 7147QR
  • Code 128 barcode encoding 7147Barcode
  • DataMatrix code encoding 7147DataMatrix
  • PDF417 code encoding 7147PDF417

Reads manufacturer-specific labels

  • VW PIN label7-digit PIN → matched to the manifest
  • +Your maker's labelonboarded on request

Sample codes — each one encodes 7147.

No label? Type the shortest unique tail of the VIN — 3 to 9 characters, never all 17.

  • Works offline on the ramp

    The tally keeps going without signal and syncs when it returns. Several clerks tally one port in parallel, with atomic dedup — never a double-count.

  • Wrong cargo is caught, not counted

    A unit with no pending line at that port raises a typed exception — wrong port, not on manifest, extra unit — and is held out of the verified count.

Type
13:00▮▮▮
Verifypending · live
▣ Scan⌨ Type

…F002659

Toyota · Camry · USLAX

…P800259

Tesla · Model Y · DEBRV

…A441359

BMW · X3 · SGSIN

Last 2 typed · progressive59
123456789Clear0⌫

The vessel

Visualise your vessel, deck by deck, as it loads.

The clerk verifies a unit and drops it onto the drawn deck — it snaps into its lane, facing the way it was parked. The office watches the stowage build up live; the discharge port knows which hold holds what before the ship berths.

Place it with a finger

  1. 1. Verify a unit — scan or type.
  2. 2. Drag it onto the drawn deck; it snaps into the lane, facing the way it was parked.
  3. 3. Look up — it is already on the office screen, with the hold's units and tonnes updated.
  • Deck 2

    loaded · units & tonnes

  • Deck 3

    loading · live

  • Deck 4

    HOLD FULL · never overlaps

Every unit drawn where it stands, labelled by VIN. Deck-plan placement is included and switched on per voyage; without a vessel drawing, position is still captured by deck and hold. Cargo weight and centre of gravity are indicative figures that feed the vessel's own stability check. Discharge is verify-only; stern and side ramp are first-class modes; a key receipt is issued on handover.

Experience live

  • Snap to lane
  • Facing & rotation
  • No-go zones
  • Lane sequencing
  • Ramps included
  • Every device, same plan
  • Live deck & hold panel
  • Units & tonnes per hold
  • Cargo weight & CG per deck
  • Drag · pinch · double-tap
  • Hold full — never overlaps
  • Stowage report per deck & hold
  • Discharge port knows before berthing

From day one

Not what you get. What you eliminate.

The words every port captain and stevedore knows — and the record that makes each one a thing that stops happening.

  • Over-landing

    A unit not on the list for this port is stopped at the scan — typed as an exception, held out of the count.

  • Short-landing

    What has not come off is visible as pending, live, before the ramp goes up — not discovered at reconciliation.

  • Mis-discharge

    Wrong port, not on manifest, extra unit — each caught at the ramp as a typed exception, never a silent accept.

  • Over-carriage

    The pending list for this port empties to zero on screen — nothing sails on by accident.

  • Double counts

    Several clerks tally one port at once; every event is de-duplicated at source.

  • Re-typing the manifest

    Read once from any format, captured once — the same record runs tally, deck plan, yard and reports.

  • Count disputes

    Every VIN carries an append-only history — who, when, where, and every move. Nothing to reconstruct days later.

  • Walking the yard to find a unit

    Type a VIN — block, row, column, with GPS from the moment it was placed.

  • Stowage surprises at berth

    Loading ends with a stowage report per deck and hold, so the discharge port plans before the ship berths.

None of these is a promise. Each is a record the operation now has — on the phone, in the office, the same second.

Privacy & trust

Your operation's data stays yours.

Manifests, tallies, surveys and reports are shared only where you send them — never to a third party, never without your authorisation.

Stevedore

your operation · your data

  • Manifests
  • Tallies
  • Surveys (PDI)
  • Reports

Nothing moves by default

You send ▸opens only when you approve
  • Terminal

    ✓ the operation you shared · nothing else

  • Vessel operator

    ✓ the call you shared · nothing else

  • Anyone else

    blocked — no send, no data

  • Access by role

    clerk · lead · view — scoped by port

  • Append-only record

    nothing is quietly edited

  • Offline on the ramp

    synced on your terms

  • Your clerks see only their operations

    assigned per port, per voyage

We comply with

  • ISO/IEC 27001

    Information security

  • ISO/IEC 42001

    AI management

  • EU GDPR

    Data protection

  • ISO 3779

    VIN & WMI

  • UN/LOCODE

    Port codes

Plug-ins

More than a tally. Plug-ins for the whole operation.

Switch on what your operation needs — each plug-in runs on the same cargo record, so nothing is entered twice.

  • + Advanced PDI

    Beyond the PDI checklists in every plan — the full survey engine: additional checklist kinds, a no-code template builder, and reporting down to every checkpoint.

    • Cargo survey
    • Your templates
    • Checkpoint reports
  • + MAFI stacking & handling

    Roll-trailers tallied as stacked piles up to four high, machinery paired — re-tally keeps the stack honest.

    • Stacking
    • Machinery pairs
    • MAFI fleet
  • + Training

    Worker certifications and competency tracked against the people on your ramp and in your yard.

    • Certifications
    • Competency
  • + Documents & approvals

    Requests routed through multi-step sign-off with an audit trail — permits, clearances, change and access requests.

    • Requests
    • Approvals
    • Audit trail
  • + Inventory

    The kit the operation runs on — jump-start units, tools, consumables — tracked as stock and assets.

    • Jump-start units
    • Tools
    • Stock & assets
  • + Damage & parts replacement

    A damage recorded at survey becomes a case to resolve — parts and stock tracked until the unit is made good.

    • Damage cases
    • Parts & stock
    • Closure
  • Start with the tally.

    Add plug-ins as the operation asks for them — the record underneath never changes.

    Planned next: Stevedore team management · Lashing checklists · Quality checklists · Special & used cargo — a unique ID and a pass for cargo with no VIN.

Who it's for

Built for your side of the operation. Whatever your role.

The same record, the same phone — but the operation is set up for what your port actually does: loading, discharging, passing cargo through, or running it all for someone else.

  • Load port

    You stow it.

    Yard to ramp to deck — the loading ends with a stowage report, not a count.

    • Yard block · row · column, keys, trouble.
    • Deck-plan placement — units and tonnes per hold, live.
    • Stowage report per deck and hold, ready before departure.
    • Key receipt on handover.
    • Loading
    • Yard
    • Ramp
  • Discharge port

    You verify it.

    Discharge is verify-only by design — cargo is leaving, not being stowed.

    • Know which hold holds what before the vessel berths — plan gangs and sequence.
    • Wrong-port units stopped at the ramp — wrong port, not on manifest, extra unit.
    • Recent-discharge panel live in the office.
    • Landed units into your yard, same record.
    • Discharge
    • Yard
    • Ramp
  • Transshipment port

    You pass it through.

    Every unit carries its POL → via → POD legs — the clerk sees where it came from and where it goes next.

    • The onward port visible on every yard cell.
    • Onward loading with its own stowage report.
    • Discharge
    • Yard
    • Loading
  • Agent for a principal

    You run it for them.

    Working the operation on behalf of a line or cargo owner — one voyage record across every port your principal calls.

    • Voyage hub: every port, every operation, one card.
    • Your clerks, your assignments, their cargo.
    • Same tally whichever port you are at that day.
    • All modes
    • Multi-port

Operation-specific, not one-size-fits-all. Each operation is set up for its mode — the phone shows only what that port needs to do.

Pricing

Priced by role, billed by activity.

Bridge runs the whole RoRo operation, so pricing follows the people who run it — stevedores at the ramp, terminals, vessel operators, and the cargo owners and dealers on the other end. All prices in USD, payable yearly only.

Start here

Find your plan

Answer three questions and we point you at the right plan. List prices in USD, payable yearly.

How many ports?

What do you tally?

Do you need yard management?

Our recommendation

Pick what you tally — your plan appears here.

HawkLine® Tally

For stevedores/agents — tally cargo for any vessel operators

Standard

$1,200/yr per port

effective $100/mo per active month

Discharge · under 5,000 units/yr

Pro

$3,000/yr per port

effective $250/mo per active month

Discharge · up to 15,000 units/yr

Enterprise

$6,000/yr per port

effective $500/mo per active month

Discharge · unlimited volume

Loadmaster

$12,000/yr per port

effective $1,000/mo per active month

Discharge + stowage + load + vessel deck placement · yard tally

Place cargo directly on each voyage's deck layout.

Per call

Full platform

$500

one port call · one-off

HawkLine® Yard

For terminals — yard and wharf tally, block · row · column, live in the office

Standard

$6,000/yr per terminal

effective $500/mo per active month

Yard and wharf tally · under 5,000 units/yr

Enterprise

$12,000/yr per terminal

effective $1,000/mo per active month

Yard and wharf tally · unlimited volume

HawkLine® Multiport

Running 2–10 ports? One price, all ports together

Tally Multiport

$30,000/yr all ports together

effective $2,500/mo per active month

Everything in Enterprise · up to 10 active ports

Yard Multiport

$30,000/yr all terminals together

effective $2,500/mo per active month

Everything in Yard Enterprise · up to 10 active terminals

More than 10 ports or terminals — or deck placement across your ports? Talk to sales

HawkLine® VesselFleet command

For vessel operators — live stowage, weight, and troubles across every port and voyage

$12,000/yr

effective $1,000/mo + $100 per active vessel per month

Whole fleet, whole planet — capped at $10,000/mo

HawkLine® Track

VIN-level visibility for cargo owners and dealers — their units, their status

$1,000/yr

Every plan includes

  • Manifest — every format, one cargo record
  • PDI — pre-delivery inspection
  • Trouble — condition flagging per VIN
  • Up to 10 users

Payable yearly only — monthly rates show the effective monthly cost

Unlimited volume runs on fair use — 250,000 units a year per plan. Moving more? We scale to 1 million units a year — talk to sales.

Payment gateway transaction fees may apply.

FAQ

Common questions.

Is HawkLine Bridge the same as RRTally or RoRo Tally?
Yes. HawkLine Bridge is the new name for RRTally, previously listed on this site as RoRo Tally. Same product, same team. The RoRo tally is now one stage inside Bridge, alongside the manifest, the yard, the survey (PDI) and vessel stowage.
Does it work without internet?
Yes. The mobile tally is offline-first. Verifies queue on the device and sync when the phone reconnects — no operator action needed. Atomic dedup means a verify re-sent after a dropped connection never becomes a double-count.
Do I need barcode-scanner hardware?
No. The phone camera reads the maker's label — QR, barcode, DataMatrix, PDF417 and the VW PIN label — or the clerk types the shortest unique tail of the VIN, 3 to 9 characters. Any modern phone works; there is no scanner hardware to procure, maintain, or replace.
What if a VIN isn't on the manifest?
It is caught, not counted. A unit with no pending line at that port raises a typed exception — wrong port, not on manifest, or extra unit — and is held out of the verified count for review. Supervisor review tooling is in development.
Who can see our operation?
Access is role-based — clerk, lead, and view — scoped by port. Your clerks see only the operations they are assigned. A view role reads everything and writes nothing, which is the usual fit for a shipping line or principal that needs live status.
Can we integrate with our TOS or BL system?
Not out of the box. Bridge ships its own exports — a styled Excel vehicle list, the voyage report PDF, the stowage-plan PDF and the cargo transit pass. A specific Terminal Operating System or bill-of-lading integration is scoped per engagement.
What if a unit has a problem — damaged, won't start, no key?
The clerk flags it at the car as a trouble, picked from a standard list — won't start, flat tyre, no key, damaged, and more — or attaches a note. Each marking is a VIN-linked, time-stamped record, kept separate from identity exceptions. Troubles surface live on the operations monitor and in the voyage report. For structured damage with photos and shipping marks, the PDI survey records it against your own checklist.
What does it cost?
Pricing follows your role, and every plan is payable yearly only — monthly rates show the effective monthly cost. Stevedores use HawkLine Tally — Standard $1,200/yr, Pro $3,000/yr, or Enterprise $6,000/yr per port (effective $100 to $500 per port per active month), Loadmaster $12,000/yr per port (effective $1,000/month) — discharge, stowage and load with direct cargo placement on each voyage's deck layout, unlimited volume, with yard tally included — or $500 flat for a single port call. Enterprise and Loadmaster are unlimited-volume plans with a fair-use threshold of 250,000 units a year (Standard covers under 5,000 units a year; Pro up to 15,000). Moving more — up to 1 million units a year, or more than 10 ports? Pricing is custom, so talk to sales. Terminals use HawkLine Yard for yard and wharf tally — Standard $6,000/yr per terminal for under 5,000 units a year, or Enterprise $12,000/yr per terminal for unlimited volume (effective $500 and $1,000 per active month). Running 2 to 10 ports? Multiport is one price across every port — Tally Multiport $30,000/yr (everything in Enterprise, up to 10 active ports) and Yard Multiport $30,000/yr (up to 10 active terminals), each effective $2,500/month. Vessel operators use HawkLine Vessel at $12,000/yr (effective $1,000/month) plus $100 per active vessel per month, capped at $10,000/month for the whole fleet. HawkLine Track — VIN-level visibility for cargo owners and dealers, their units and their status — is $1,000 per year. Every plan includes the Manifest, PDI (pre-delivery inspection), and Trouble flagging, with up to 10 users. All prices in USD.

HawkLine® Bridge · RoRo Operation Command Center

Ready to visualise your next voyage?

Tell us your port and the lines you handle. We'll walk you through a voyage with your own manifest — a real person responds within one working day.