Workflow column
Extracting through Complete. This is the board everyone shares. Signing and sealing change this column automatically; extraction finishing does too.
Portal guide
Ticket lifecycle
How a shipment ticket moves through six stages in Beagle — from document extraction to a sealed, verifiable Delivery Order.
Overview
Tickets live in client folders. Each ticket is a shipment intake package: shipping documents, Ticket details, a generated Delivery Order, and a six-column board. There is no separate approve, reject, or reopen button. You move the work by completing checks, signing, and dragging one neighboring column at a time.
Two concepts people confuse
Extraction health
How the uploaded files are reading: extracting, succeeded, failed, or partial. Adding documents later does not send the ticket back to Extracting.
Who you are and whether you created the ticket both matter. A manager who filed a ticket works as its creator. A manager named only as signatory can view it and sign it, but cannot edit the packet.
Stages
Drag only to a neighboring column. Extracting advances on its own. Complete does not move back.
Extracting
Stage 1 of 6
Uploaded files are being read. The ticket waits here until extraction finishes.
What is expected
- Every uploaded file finishes reading, including files that fail.
- No one edits the packet or moves the card while that read is still running.
What happens
- Every new ticket starts here. Create asks for at least one file, and dropping several files makes one ticket each.
- The board refreshes on its own. When every file has finished — even if some failed — the ticket moves to For review.
- You can open the ticket and watch document status.
What stays locked
- Ticket details, Delivery Order edits, client folder moves, and delete stay locked.
- Cards cannot be dragged, and nothing can be moved back into Extracting.
Before you advance
All 5 checks must pass before you can drag out of For review. The board explains the first problem it hits.
Before you leave For review
These checks also apply if you try to skip ahead into any later column.
5/5
01Ticket details
Select a consignee and a signatory. If that consignee has brokerage houses, choose a brokerage too. Shipping line is optional — it selects that line's Delivery Order templates. Without one, the packet is an Authorization Letter only.
02Document checklist
Use each checklist row’s Upload for the House B/L, Arrival Notice, or Inward Foreign Manifest. Arrival Notice and Manifest are optional — upload them or mark Not applicable.
03Manifest match
If you upload an Inward Foreign Manifest from the checklist, resolve mismatches on that row until it matches. A missing Manifest does not block leaving For review. A pending or mismatched one does.
04Delivery Order facts
Fill every required Delivery Order field, including at least one container number. Missing fields show as a count on the ticket.
05Field reviews
If anyone edited a printed field, an admin must Mark safe on each edit. Pending or Mark not safe reviews block Sign, board advances, and Complete downloads.
Role-based workflows
Select your role to see the steps and rules that apply to you.
Ticket creators
User · manager who created the ticket
File the packet, keep details accurate, and move the board once the checks are clear. This is the path for a regular user, and for a manager working on a ticket they created.
01File the ticket
Open Clients, open the client folder, then New ticket. Upload at least one file. You can drop several files to create one ticket per file.
02Wait out Extracting
If you uploaded files, stay on the board or ticket until the card moves to For review. Extraction runs in the background.
03Complete Ticket details
Set the consignee and the signatory who will sign. Add a brokerage when that consignee has brokerage houses. Shipping line is optional. Add Notes if the team needs context. Save while the ticket is still in For review.
04Upload and compare
On Document checklist, use Upload on each row for the House B/L, Arrival Notice, and Inward Foreign Manifest. Documents is for listing and preview only. If you upload a manifest, fix any mismatches on that checklist row.
05Review the Delivery Order
Use Preview and Edit to fill required fields. Overlay edits notify admins, who Mark safe or Mark not safe on those values.
06Advance one column at a time
Drag For review to For signature when the checks are clear. After Sign, move Ready for submission to Submitted once the packet has gone out, then Submitted to Complete.
Good to know
- You see tickets you created, plus any ticket where you are the assigned signatory.
- Only the ticket creator (or an admin) can edit Ticket details and the Delivery Order.
- If you created the ticket, you can drag it like any other creator — including as a manager.
- Moving a signed ticket back to For review or For signature clears the signatory stamp.
Verifying a completed Delivery Order
After Complete, the sealed PDF ends with a certificate page. That link is public — no Beagle login required.
01
Complete the ticket
Seal the Delivery Order so it includes a verification page with a QR code and certificate.
02
Scan the QR
Scan the QR on the last page, or open the verification link printed on that page.
03
Confirm the document
Check the document details and confirm the PDF against the stored packet. No Beagle account needed.
An unrecognized link usually means the QR was not from a completed Beagle Delivery Order, or the address was copied incorrectly.
If you are stuck
Common situations and how to resolve them.
Wait for every file to finish. Use Still extracting — refresh if the board has been sitting still. You cannot drag the ticket out of Extracting.
Open the ticket, check the document list, and Re-extract or upload a clearer scan. A failed or partial extraction does not by itself block For review work once the ticket has left Extracting.
Move one column at a time. Leaving For review also needs Ticket details, the House B/L, required Delivery Order fields, and no pending or not-safe reviews. An uploaded Manifest must match.
Confirm you are the assigned signatory, the ticket is in For signature, a signature specimen is saved on Profile, required fields are filled, and every edited field is marked safe.
On tickets they did not create, managers may only return For signature to For review. Creators and admins keep the normal neighbor moves.
A field marked not safe blocks the sealed packet download until an admin marks it safe.
Words we use
Key terms as they appear in Beagle.
- Client folder
- The customer workspace that holds tickets. Sidebar label is Clients. Every ticket belongs to one folder.
- Ticket
- A shipment intake package. The title is a Ticket No. such as PRO00001-TKT (series, then client code). House B/L is a separate field, not part of the title.
- Workflow status
- The six board columns. This is separate from extraction health on the documents.
- Extraction
- Background reading of uploaded PDFs and images. Health can be extracting, succeeded, failed, or partial even after the card has moved to For review.
- Ticket details
- Consignee, brokerage when needed, shipping line, signatory, house B/L, and optional Notes.
- Delivery Order
- The generated packet you preview, edit, sign, download, and eventually seal.
- Signatory
- A manager named on Ticket details. That person sees the ticket in the client folder and stamps page 1 in For signature.
- Mark safe / Mark not safe
- Admin review of an edited Delivery Order field. This is the approval step for overlay edits — tickets do not have a separate approve or reject action.
- Notes vs Activity
- Notes are optional remarks on Ticket details. Activity is a log of overlay edits, field markings, and signatures.
Need a client folder or a sign-in? Start from Sign in, or contact Beagle Cargo.