01Field reports into inspectable summaries
Prepare drafts from approved notes and attachments while preserving the source, location reference and timestamp. Highlight missing asset identifiers and conflicting observations. The reviewer should see what the system could not establish and remain responsible for deciding whether the summary is ready for the next handoff.
02Purchasing documents with explicit checks
Extract proposed vendor, order and line-item fields, then match them against approved records. Treat units, quantities and repeated attachments as validation problems. Ambiguous items should go to a reviewer with the source text rather than become a guessed transaction in the purchasing or accounting system.
03Service requests with shared ownership
Create structured drafts with a site, issue, responsible team and next action. Show what has been acknowledged and what still awaits clarification. Preserve the message trail so colleagues in another location can understand the request without reconstructing a conversation from separate phone calls and inboxes.
04Recovery when a handoff fails
Record the last successful integration step and expose failed runs in a visible queue. Use duplicate checks and bounded retries where supported. A coordinator needs a practical way to resume work after a connection fails, including an agreed manual path when systems are temporarily unavailable.