On this page 7 steps
GET READY
Before you start
- Included access
- Included with the AI products
- Trident product
- Insights or Automation (Act)
- What this does
- Reviews information without changing records
- A paired Trident connection with access to the job and relevant supporting activity.
- The job number and the required or delivery date you want assessed.
IN YOUR AI CONVERSATION
Start with this request
Using Trident, investigate why Job 12345 is late or at risk. Check operation progress, material availability, purchasing and shipment context. Separate confirmed blockers from possible causes and recommend the next checks. Do not reschedule or change records.
Adapt the example to your own records and outcome. The guide does not run the request.
FOLLOW THE WORKFLOW
One step at a time.
Read what happens, what you provide and the result to look for. Use the step reference when you need help.
- 01
LATEJOB-01
Identify the job and required date
Select the job and establish the required or delivery date being assessed.
Your part
Confirm which date matters when the job contains alternatives.
Look for this result
The investigation has one clear job/date basis.
Need help at this step?
A customer promise date and an internal production date may differ. Clarify the intended comparison first.
- 02
LATEJOB-02
Review operation progress
Review routing progress, remaining work, completed quantities and available scheduling information.
Your part
Read the progress summary.
Look for this result
You can see which operations appear complete, waiting or outstanding.
Need help at this step?
Identify scheduling or time-entry gaps before relying on the progress picture.
- 03
LATEJOB-03
Review material availability
Check requirements, inventory context, picks and possible shortages for the job.
Your part
Review the material items that may prevent progress.
Look for this result
Potential material blockers are identified.
Need help at this step?
Distinguish a confirmed shortage from availability that could not be verified. Ask which quantity and location support the finding.
- 04
LATEJOB-04
Review purchasing dependencies
Review open POs, due dates, receipts and externally sourced requirements relevant to the job.
Your part
Check the PO or supplier commitment associated with a blocker.
Look for this result
Purchasing dependencies are connected to this job, not just listed in isolation.
Need help at this step?
A late PO is not automatically the cause. Confirm whether the outstanding line is actually needed for the remaining work.
- 05
LATEJOB-05
Review shipping/order dependencies
Review order and shipment status where it affects the date or completion question.
Your part
Clarify the expected shipment when several deliveries are involved.
Look for this result
Downstream context is included where relevant.
Need help at this step?
Mark the step not applicable when no order or shipment dependency affects the job.
- 06
LATEJOB-06
Determine likely causes
Separate observed facts from likely contributing causes and rank the blockers by relevance.
Your part
Clarify business priorities when they change the interpretation.
Look for this result
A reasoned cause list, including unresolved questions.
Need help at this step?
Ask what evidence supports each cause. Keep unresolved causes visible instead of forcing a definitive explanation.
- 07
LATEJOB-07
Recommend next checks
Identify what to verify with production, purchasing or shipping next.
Your part
Choose a blocker for further review or take the findings to the process owner.
Look for this result
A practical follow-up list without automatically changing dates or commitments.
Need help at this step?
Reference the LATEJOB step where the investigation stopped or became unclear.
WHEN YOU FINISH
The expected result
A ranked list of observed blockers and possible contributing causes, with immediate follow-up checks. The investigation does not promise a new delivery date or change the schedule.
KEEP THE NEXT QUESTION FOCUSED
Where to go next.
← Back to Skills & TrainingSK-006 · Guide/draft Skill version 0.1 · Reviewed 2026-11-04. Confirm the installed Skill version when reporting an execution problem.