Messy Notes to SOP

Example inputs

Paste rough process notes: Each weekday, open the shared Orders tracker. Filter rows marked Ready. Match each to the shipping confirmation in the shared folder. If the order ID and shipped quantity match, record the confirmation filename and mark Shipped. If quantities differ, leave status unchanged and send the row to Maya, the ops manager. Record what was checked in the Notes column. Old informal note says delete duplicate rows; we now need to preserve them.

Who will use this procedure?: New operations assistant. Can edit Orders tracker and read shipping confirmations. No refund or account-admin access.

Completion standard and restrictions: Never delete records. Maya must approve exceptions before a status change. Completion means every Ready row is either verified Shipped or documented as an unresolved exception. No customer emails should be sent.

Generated example

SOP: Daily Order Shipment Verification

Purpose and ready check

Intended result: Every Ready-marked row in the Orders tracker is either verified and marked Shipped (with confirmation filename and Notes entry) or documented as an unresolved exception routed to Maya.

When to use: Each weekday, as part of daily order processing.

Responsible role: Operations assistant (edit access to Orders tracker; read access to shipping confirmations folder).

Required access/materials: Shared Orders tracker (edit), shared shipping confirmations folder (read), Maya's contact channel for exception approval. If access is missing, obtain it through the approved access-request channel — do not proceed with workarounds.

Procedure

1. 1.Open the shared Orders tracker and filter rows marked Ready. *Completion check:* filtered view displays only Ready rows, using each row's stable row ID (not row count) as the reference.
2. 2.For each Ready row, locate the matching shipping confirmation in the shared folder by order ID. *Completion check:* a confirmation file with matching order ID is found.
3. 3.Compare shipped quantity on the confirmation to the tracker's ordered quantity. *Completion check:* quantities recorded as match or mismatch.
4. 4.If quantities match: record the confirmation filename in the tracker and mark the row Shipped. *Completion check:* filename visible in the row, status changed.
5. 5.In the Notes column, record what was checked (order ID matched, quantity matched, confirmation filename). *Completion check:* Notes field is non-blank for the row.
6. 6.If quantities differ, leave status unchanged, send the row to Maya for review, and note "quantity mismatch — pending Maya review" in Notes. *Completion check:* Maya notified; Notes reflects pending state; status untouched.
7. 7.Repeat for all Ready rows in the batch. *Completion check:* every row from step 1 is either Shipped-with-filename or logged as pending Maya review — none deleted or skipped.

Exceptions and stop points

• Quantity mismatch: Do not change status. Record mismatch in Notes, send row to Maya (escalation owner: Maya). Preserve the original row and both quantity values.
• No matching confirmation found: Do not mark Shipped. Note "confirmation not found" in Notes and flag to Maya for approval before any status change. Preserve the row untouched.
• Suspected duplicate row: Per current hard restriction, never delete. Note "possible duplicate — flagged, not removed" and route to Maya for review. Do not act on the old informal "delete duplicates" note — it is superseded and marked obsolete below.

Handoff checklist

• [ ] All Ready rows (by row ID) accounted for — none deleted.
• [ ] Matched rows show Shipped status + confirmation filename + Notes entry.
• [ ] Mismatched/unresolved rows remain unchanged in status, logged in Notes, and sent to Maya.
• [ ] Maya has been notified of all pending exceptions (notification sent ≠ resolved).
• [ ] No customer emails sent during this process.

Confirm before adoption

• Obsolete step for review: "Delete duplicate rows" contradicts the no-deletion restriction and must not be followed; confirm this instruction is formally retired.
• Maya's approval channel/turnaround is not specified — confirm how exceptions are submitted and tracked to closure.
• Proposal (not policy): consider a shared exceptions log tab for Maya's review queue, separate from the main tracker — optional improvement, not currently documented.

Provisional note: This SOP assumes the operator already has the edit/read access described in Audience. Please supply: Maya's exception-submission method, and confirmation whether Notes-column format is standardized.