A prepared draft still needs a responsible reviewer
Hawk Lane’s configured automation can prepare reviewable drafts from supported PDFs and authorized emails. A user or dispatcher with the relevant permission, assigned by the admin, can see a draft and make edits. The review step keeps a document-reading result separate from the operational decision to use that load.
The checklist below is an office review process. It does not claim that Hawk Lane automatically detects every duplicate, identifies the latest revision or completes every field. Confirm the fields and controls in your configured workflow. For the broader reason to connect inboxes and load records, see Gmail-based load handling.
First confirm the document and the work it belongs to
Open the source document or authorized email beside the draft. Establish which booking or load reference it represents and whether a newer instruction has arrived. A well-read earlier document can still produce the wrong operational record if a rate confirmation has since changed.
Use the latest instruction your team has confirmed. If two documents conflict, ask the responsible contact to clarify before releasing the draft. Treat an unclear document as an exception to resolve, rather than filling a blank with a guess.
Use this field-by-field review checklist
| Check | Compare with the source |
|---|---|
| Document / version | Source file or email, issue date, booking reference and any revised instructions |
| Parties | Correct customer, broker or carrier for this workflow; do not match on a similar name alone |
| Pickup / delivery | Stop sequence, full addresses, dates, appointment windows and applicable time zones |
| Rate / currency | Agreed amount and currency, with separately stated charges checked individually |
| Shipment details | Equipment, commodity, weight, units and relevant special instructions |
| References | Customer load, pickup, delivery and purchase-order references where supplied |
| Missing / conflicting data | List the question, source and person responsible for resolving it |
| Existing record | Check whether the work is already represented before creating another live load |
Not every source contains every field. A missing appointment time is different from an open appointment: ask what applies. A numeric value without a clear currency or unit also needs clarification. Review required information for your operation rather than relying on a single generic completeness score.
Example: the delivery time changed
In this fictional example, a PDF says delivery is at 08:00, while a later email says 10:00. The draft contains 08:00 because it came from the earlier PDF. The reviewer checks which instruction is current, confirms the applicable date and time zone, edits the draft where permitted, and keeps the reason for the change with the team’s working record.
This is an example of human review, not a claim that the system automatically reconciles PDF and email revisions. If the change cannot be confirmed, leave the draft out of live use until the responsible person resolves it.
Handle revisions, duplicates and gaps deliberately
- Revised source: identify the changed fields and compare them with any existing load before deciding which record needs updating.
- Possible duplicate: search the relevant reference, parties and work dates. Confirm whether this is a revision or a separate shipment before creating another record.
- Incomplete source: list the missing information, who is obtaining it and what must be resolved before use.
- Conflicting instructions: get a confirmed decision from the responsible contact and record the basis for the edit.
These are recommended review actions for the team. How the application flags, stores or resolves each exception depends on the configured workflow and permissions; verify those controls during setup.
Make permission and handoff clear
The admin should identify who may view and edit drafts and who is responsible for the final operational check. Before using the record for assignment, documents or billing, confirm that the required fields agree with the accepted source and that open questions have been resolved.
When discussing setup, bring a masked source file, the fields you need, the reviewer’s role and one exception you regularly encounter. That gives the team a practical acceptance example to test instead of a broad promise to read every document.
Buyer questions
Can every user edit a draft?
Draft access and editing require the relevant permission assigned by the admin. Confirm the roles your company needs during setup.
Does every PDF or mailbox work without setup?
No. Supported layouts, authorized inputs, required fields and review steps need to be agreed. Hawk Lane workflow automation is configured and quoted separately from monthly TMS plans and the Pro standard integration.
Can this checklist replace dispatcher judgment?
No. It helps an authorized reviewer compare the draft with the accepted instructions. It does not establish that a load is safe, commercially agreed or ready to run simply because fields were extracted.
Discuss your draft-load workflow
Discuss your workflow and confirm the right product, configuration or project scope with Hawk Lane.