What goes wrong with manual dockets.

  • Quantities or part references typed in by hand and not matching the order
  • Dockets created from an old version of the job
  • No quick way to prove what was delivered, and when
  • Partial deliveries tracked in notes instead of against the order
  • Paper copies lost, so a dispute starts without evidence

What delivery docket software should do.

  • Create the docket from the job or work order, so items and quantities come from the record
  • Support partial and multiple deliveries against one order, with what remains shown
  • Include customer references, delivery address, job number and revision
  • Capture a signature or confirmation of receipt, on paper or on a device
  • Attach related documents, such as certificates, when the customer requires them
  • Keep an issued, searchable copy linked to the job

Connecting it to the rest of the flow.

A delivery docket is most reliable when it comes from the same data as the quote, the work order and any certificates. That way a change made earlier in the chain is reflected in the docket.

See the guides on BOM-linked work orders, compliance certificates and client communication for the surrounding steps.


Getting started.

  1. Collect three recent dockets and note every field and correction made by hand
  2. Decide how partial deliveries are recorded
  3. Choose how receipt will be confirmed
  4. Build the docket for one customer or product group first
  5. Compare it with the paper version for a few weeks, then switch over

Frequently asked questions


Practical checklist

  • Gather recent dockets and mark the hand-typed fields
  • Decide how partial deliveries are tracked
  • Agree how receipt is confirmed
  • Pick one customer or product group to start with
  • Plan a short parallel run with paper

If you would like to talk it through, you can contact pyes.software. A conversation about your current workflow is the starting point, with no obligation.

This content is for informational purposes only and does not constitute legal, financial, or compliance advice.

Related:

pyes.software by A-Vision Software is a B2B industrial software engineering practice and is not affiliated with the PyES chemistry software project.