Inputs
- Original B/L or shipping instruction packet
- Cargo quantity, grade, parcel, receiver, and consignee details
- Voyage, vessel, load port, discharge port, and date references
- Split instructions, document templates, and review notes
Maritime Guides
How B/L splitting works in bulk shipping
B/L splitting takes source shipment and cargo information and produces multiple bill-of-lading outputs that still need review before use.
How the Work Holds Together
Inputs, checks, exceptions, and human review.
The useful result is not an isolated answer. The team needs to see what Chartera used, what it did, what can still go wrong, and where judgment is required.
Chartera
- Reduces repetitive document preparation by assembling split outputs from the original documents and instructions.
- Keeps source shipment data and split instructions close to the generated drafts.
- Preserves a maker/checker review pattern before documents are used outside the team.
Watch For
- A copied field changes across one split output and is not caught before release.
- The team can see the generated documents but not the instruction or source row behind each one.
- The workflow compresses drafting time but loses the checker queue and exception list.
Human Review
- A person still reviews document accuracy, external wording, missing values, and exception handling before release.
What the Team Reviews
B/L split output pack
Inputs
Shipping instruction, cargo details, receiver list, and B/L template
Split logic
Cargo parcels and receiver details mapped to draft outputs
Prepared drafts
B/L drafts assembled for checker review
Exception list
Missing, conflicting, or unusual fields surfaced before release
Review state
Maker/checker workflow remains explicit
The manual workflow
Teams gather source shipment data, cargo details, consignee or receiver information, and document instructions, then prepare and check multiple outputs.
Where time is lost
The repetitive work is context reconstruction, copying details across documents, and checking that each split output remains consistent with the source material.
What a good automated flow preserves
The right system reduces repetitive document handling while keeping source context and checker review in the loop before documents are released.
Common Questions
Does Chartera remove document review?
No. The B/L proof page emphasizes a reviewed flow with one person creating outputs and one person checking.
What result has Chartera shown publicly?
The public case study describes a 32-hour workflow compressed to 3 hours while retaining checker review.
Why does source context matter?
B/L outputs leave the desk. Teams need a clear path back to the data and instructions behind each output.