As of 13 August 2026, AI can only partly create a stock receiving procedure.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open your current stock system, purchase order records, delivery paperwork and any existing goods-in notes, then gather the names of the people responsible for receiving and discrepancy approval.
   2. Walk through one ordinary delivery and record each action from arrival at the site to stock being accepted, stored and entered into the system, including the documents and screens used.
   3. Record three recent exceptions such as shortages, damage, wrong items or missing paperwork, and note who decided what happened in each case.
   4. Paste the gathered facts, existing notes and company rules into the prompt, replacing every bracketed slot and leaving unknown details clearly marked.
   5. Ask the model to produce the procedure, then remove or resolve every [CONFIRM] item before treating the document as final.
   6. Give the draft to the receiving operative and the person responsible for stock records, and have them test each step against a real delivery without relying on memory.
   7. Compare the tested procedure with the purchase order, delivery note, stock system entry and discrepancy record, then amend the SOP and send it to the accountable manager for approval and issue control.

   Prompt

   Create a stock receiving procedure for a UK business using the information below. Use British English and write it as a practical SOP that a new member of staff could follow.
   
   Business and site: [describe the business, site and receiving area]
   Products or stock received: [describe products, including any special handling or traceability needs]
   Typical deliveries: [suppliers, delivery frequency, packaging and expected documents]
   Systems and records: [purchase order system, stock system, goods received note, delivery log or other records]
   People and responsibilities: [who receives, who checks, who resolves discrepancies and who approves stock adjustments]
   Current process: [paste any existing notes or procedure]
   Known problems: [late deliveries, shortages, damage, wrong items, temperature issues, paperwork or other problems]
   Relevant company rules: [paste approved policies or controls]
   
   Produce:
   1. Purpose, scope and definitions, including what counts as a discrepancy.
   2. Roles and responsibilities.
   3. Required equipment, documents and system access.
   4. A numbered receiving process from delivery arrival to stock being accepted, recorded and stored.
   5. Separate instructions for shortages, overages, wrong items, damaged packaging, rejected deliveries, missing paperwork and suspected contamination or other unsafe conditions.
   6. The records to complete, who completes them and when.
   7. Escalation points and approval requirements.
   8. A short checklist for the receiving operative and a short audit checklist for a manager.
   
   Do not invent supplier terms, legal requirements, system names, approval limits, storage conditions or safety controls. If information is missing, write [CONFIRM] next to the relevant step and list the question that must be answered. Do not claim that the procedure meets a law or standard unless that requirement is included in the supplied information. Keep the final procedure specific to the details provided, and make assumptions explicit.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.