Gaulett connects order data, documents and business rules with AI-assisted reading. Your team receives findings linked to their sources to review, request missing information and decide the next step.
See what is stopping this order from moving forward.
Compare the order with its attachments. Then see what changes when the team checks the missing document.
Both stages are shown below: before the missing document arrives and after the packing list has been checked.
Before the missing document arrives
3 issues to address
01Destination mismatchPending+
Two destinations. Confirmation needed.
Order and requirement
Order PED-042
Order · version 1
Destination
North
Expected packages
12
Reference recorded in the order.
Document received
Attachment to PED-042
ANX-042 · version 1 · page 1
Destination
South
Linked order
PED-042
Excerpt located by AI for the team to check.
What needs to be checked
The destination must be confirmed before dispatch. AI highlights the difference; it does not decide which information is correct.
The team’s next action
The responsible department confirms the correct destination and records the instructions in the order and the required documents.
02Packing listPending+
The order requires a packing list. It has not arrived yet.
Order and requirement
Checklist for PED-042
Order checking requirement
Required document
Packing list
Expected packages
12
The requirement comes from the company’s process.
Document received
Attachments received
Initial documents for PED-042
Packing list
Not attached
Pending issue
Missing document
The missing document is flagged for the team to confirm.
What needs to be checked
The packing list must match the order and allow the packages to be checked. Receiving a file alone does not close the issue.
The team’s next action
Confirm the requirement and request the packing list from the person responsible for the order.
03Illegible pagePending+
If the text cannot be read, the information remains unconfirmed.
Order and requirement
Checklist for PED-042
Order checking requirement
Document
Attachment · page 2
Required condition
Legible content
Only content that can be read can be checked.
Document received
Attachment to PED-042
ANX-042 · version 1 · page 2
Legibility
Insufficient
Content
Unconfirmed
AI flags the limitation. The content is not assumed.
What needs to be checked
The required fields on the page must be legible. There is no basis for filling in or confirming illegible content.
The team’s next action
Request a legible version and check its content before recording the next steps.
After checking the packing list
2 issues still open
01Destination mismatchPending+
Two destinations. Confirmation needed.
Order and requirement
Order PED-042
Order · version 1
Destination
North
Expected packages
12
Reference recorded in the order.
Document received
Attachment to PED-042
ANX-042 · version 1 · page 1
Destination
South
Linked order
PED-042
Excerpt located by AI for the team to check.
What needs to be checked
The destination must be confirmed before dispatch. AI highlights the difference; it does not decide which information is correct.
The team’s next action
The responsible department confirms the correct destination and records the instructions in the order and the required documents.
02Packing listChecked+
The packing list arrived. The team checked the order reference and contents.
Order and requirement
Checklist for PED-042
Order checking requirement
Required document
Packing list
Expected packages
12
The requirement comes from the company’s process.
Document received
Packing list LV-042
LV-042 · version 1 · received and checked
Linked order
PED-042
Packages listed
12
The team confirmed the identification and the list of packages.
What needs to be checked
At this stage of the example, the team has checked the packing list against the order. Only the missing-document issue has been closed.
The team’s next action
Record packing list LV-042, version 1, and the check performed. Continue addressing the destination mismatch and the illegible page.
03Illegible pagePending+
If the text cannot be read, the information remains unconfirmed.
Order and requirement
Checklist for PED-042
Order checking requirement
Document
Attachment · page 2
Required condition
Legible content
Only content that can be read can be checked.
Document received
Attachment to PED-042
ANX-042 · version 1 · page 2
Legibility
Insufficient
Content
Unconfirmed
AI flags the limitation. The content is not assumed.
What needs to be checked
The required fields on the page must be legible. There is no basis for filling in or confirming illegible content.
The team’s next action
Request a legible version and check its content before recording the next steps.
In this example, the excerpts represent the records for PED-042. The team checks the sources and authorizes the next steps.
Where business knowledge, processes and AI meet
Business
Understand the impact of an incorrect destination or unchecked packages.
Processes
Define requirements, responsibilities and the conditions for closing each issue.
AI
Locate information, highlight differences and prepare the summary with its sources.
When new information arrives
The order changes. The review keeps up.
The order, sources and versions stay linked so work can resume without losing the history.
The packing list has arrived. Is everything resolved?
The team checks the identification and contents of the new document and closes only that issue. The destination mismatch and unreadable page remain open. The record identifies who reviewed it and which version they received.
A message gives a different destination. Which one applies?
The responsible department checks the correct destination and, if the change is confirmed, updates the order before dispatch. A more recent message alone does not authorize a choice of destination.
The page is now readable. Has the data changed?
The contents can now be checked. The team identifies the valid version and retains the previous one. If the old file could not be read, there is no basis for claiming that the data changed.
How to assess value
The benefit needs to show in the team’s daily work.
Quality
What was found?
Issues detected, problems missed and unnecessary alerts, by type and severity.
Effort
How much work is still needed?
Time spent reading, reviewing, correcting and handling exceptions, including work by those who supply missing information.
Rework
How much back-and-forth?
Requests for corrections and repeat reviews per order. A new version does not count as a new order.
Compare against current practice, using equivalent orders and criteria defined before the test.
