Create work instructions with AI: from dictation to a usable procedure

A work instruction is valuable when a colleague can use it to take over a recurring task reliably. For the team leader, the result should be fewer basic questions while important exceptions still reach the right person. AI can help turn existing company knowledge from dictation into a readable procedure. It does not independently decide which rule should apply inside your business or who has authority to make an exception.

The most useful starting point is a small process with a visible beginning and end. Here, a spoken draft becomes a usable instruction for checking incoming delivery documents. The business, roles and quantities are fictional. The subject is internal matching and handover, not technical goods inspection or legal assessment. The result is a reviewed description you can prepare for colleagues and for recurring AI assistance with a clearly defined part of the work.

Choose a process somebody actually repeats

Begin with a task you regularly explain aloud. “Take care with deliveries” is too broad. “Match incoming delivery documents to an order and hand discrepancies to purchasing” describes observable work. Its start is receipt of the documents; its end is a traceable match with an accepted next action if something differs. That makes clear what the instruction is meant to achieve rather than leaving its completion to each reader’s interpretation.

Limit the scope. Our example concerns office handling after delivery information arrives for ordered presentation materials. It replaces neither the actual quantity report from the person receiving the goods nor a specialist inspection. Users must recognise which information they can check and which they need from someone else. Otherwise an administrative task can quietly become a decision for which they lack the necessary evidence and responsibility.

Identify who can explain the process and who can review it. An experienced office colleague may know the everyday shortcuts, while purchasing knows the boundaries for discrepancies. Both perspectives help. You do not need a long meeting about every possible business process. The normal case, its main exceptions and a recipient who will actually use the procedure are enough to prepare the first draft and test its usefulness.

webRichtung assist supports structuring your own dictation and creating stored, reusable documents. Explore assist and select a recurring process for your first work instruction. Bring a task whose result you can judge yourself. The first benefit appears when a colleague can carry out that process with less additional explanation and knows where any unresolved decision belongs.

Dictate the actual process, including its gaps

In the hypothetical business, office coordinator Lara explains: “When delivery documents for presentation materials arrive, I look for the corresponding order. I check supplier, order reference and reported quantity. The person who received the delivery tells me what actually arrived. If everything matches, I attach the documents to the order and record receipt. If there is a difference, I inform purchasing.” This gives an initial sequence rooted in how the work currently happens.

She adds: “Sometimes the order number is missing. I ask instead of choosing a similar order. If only part arrives, the rest remains outstanding. With two identical messages, I check whether they refer to the same delivery. I do not reorder or change the ordered scope myself. Purchasing decides the next clarification. At the end, I want to see the documents matched and any open discrepancy assigned to a responsible person.”

This dictation is useful even though details remain missing. “Inform purchasing” does not explain who accepts the case when the usual person is away. “Record receipt” does not yet identify the information colleagues need to read later. The draft should reveal these gaps as questions. It should not invent suitable names or company procedures merely to make the text look complete before the business has resolved those points.

An appropriate AI instruction is: “Create a draft from my dictation for a colleague unfamiliar with this process. Describe trigger, required information, normal case, exceptions and completion. Flag unclear ownership as questions. Add no automatic reordering or order changes. Use clear action sentences and separate factual checking from purchasing decisions.” This is your working request, not a claim that a preinstalled standard process already supplies the company-specific rules.

Add ownership and decision boundaries before use

Lara clarifies three points in the example. First, Ben in purchasing handles discrepancies; the designated purchasing substitute covers his absence. Second, the internal handover includes order reference, reported receipt quantity, the discrepancy and available documents. Third, a discrepancy is handed over only when the recipient accepts its handling. These decisions come from the business. AI can express them clearly but cannot establish their validity or confer authority on the people named.

Describe a separate route for missing order references. The employee searches using the information available and asks purchasing to check when the relationship is uncertain. They do not choose an order merely because the supplier name is similar. The state remains “matching unresolved”. That is a usable outcome for this exception if somebody accepts the next check. A forced, apparently complete match would be less useful than a clearly documented open question.

For quantity differences, keep the original ordered scope intact. Describe received quantity and outstanding remainder separately. A missing part is not a confirmed cancellation or an automatic instruction to reorder. Purchasing clarifies what happens next. The procedure should prevent somebody tidying documents from accidentally making a commercial decision outside their task simply because changing one number would make the records appear to agree more neatly.

For possibly duplicate messages, first establish whether they refer to the same delivery. A second email is not evidence of a second arrival. The receiver’s actual report and available documents define what can be checked. Here too, unresolved matching is passed on visibly. No extra quantities are created just because the same content reached the office twice through repeated messages rather than through two separately confirmed deliveries.

The developed instruction describes a usable route

The sample instruction awaiting approval begins: “This procedure covers internal handling of delivery documents for ordered presentation materials. Start when the documents and the receiver’s report are available. Find the corresponding order using the stated reference. Check that supplier and subject match the case. If the reference is missing or ambiguous, keep matching open and take the specific question to Ben or the purchasing substitute.” It defines the work’s scope and initial condition.

The normal route follows: “Compare the quantity actually reported as received with the order and delivery documents. When the information agrees, attach the documents to the case and record which quantity belongs to which receipt. Preserve the connection to the original order. Do not mark the whole order complete merely because a document is present; check whether other agreed delivery parts remain outstanding.” This connects an action to its intended result.

The exception passage says: “For a quantity discrepancy, document the order, reported receipt and difference separately. Do not change the ordered scope. Prepare a handover to Ben or the substitute containing reference, documents, reported quantity and open question. For a suspected duplicate, explain why it may concern the same delivery and ask for the relationship to be checked. Make no independent reorder, cancellation or other agreement with the supplier.”

Completion is described as: “The office step ends when the clear match is readable or the responsible person has accepted the unresolved matching question. A quantity discrepancy must also have an accepted next handler. Record who owns which next action. Sending a question without established ownership is not a completed handover.” This distinguishes the office task’s completion from the later resolution of the delivery itself, which may require further work from purchasing.

The sample deliberately uses continuous prose. In your own document, organise the steps as appropriate while preserving their sequence and conditions. More important than appearance is whether someone can act without hidden company knowledge. The instruction describes a business process. It does not promise that assist automatically handles stock, changes purchase orders or communicates with suppliers, and it should not be assessed as if those actions had already occurred.

Test with a colleague and concrete cases

Ask someone who did not write the text to work through the normal case. In the first fictional trial, ten presentation folders were ordered and ten reported received; documents and reference agree. The colleague should explain what they match and how they describe receipt. They must also check whether this order contains other outstanding delivery parts. The result is a traceable office position, not a blanket conclusion about every other order from the supplier.

In the second trial, ten folders were ordered but only eight actually arrived. The colleague records ten ordered, eight received and two outstanding. Eight plus two equals ten. They prepare the discrepancy for Ben and wait for his acceptance of the next clarification. They neither reduce the order to eight nor order two additional folders. This decision is precisely where you see whether the instruction’s boundary is understandable to its actual user.

In the third trial, the reference and an unambiguous match are missing. Two orders from the same supplier could fit. A correct attempt initially ends with the matching question accepted by the responsible person. If the colleague chooses the newer order without evidence, the wording is insufficient. Ask which passage led them there and improve that specific passage rather than adding an unrelated general warning to the end of the document.

Record the reader’s questions as well as mistakes. “Where do I find the actual quantity?” may show that the source is hard to access. “Who takes over when Ben is away?” may expose missing cover. Not every difficulty is a writing problem. Sometimes the team leader must clarify operations before a better sentence is possible. AI should not conceal that organisational gap through wording that makes an unavailable route sound fully established.

Prepare reuse through Skills with a defined scope

Only after testing should you describe which part assist will support repeatedly. In this example, the requested work can be to prepare an internal matching and discrepancy draft from supplied information. That is narrower than “manage deliveries”. Required inputs are order reference, ordered scope, actual reported receipt and relevant documents. If anything is absent, the draft should identify the question rather than claim that the review has already been completed.

assist Skills help apply your working method repeatedly and adapt it when practices change. For this pattern, you could say: “Prepare an internal review draft from the supplied information according to our approved procedure. Separate ordered quantity, receipt and remainder. Show missing matching and possible duplication. Name the responsible role for open questions. Change no order and prepare external communication only as a draft.” This defines the assistance around its intended result.

Carry over valid rules and roles, not the last example’s data. Ten folders ordered and eight received are test inputs. They must not appear as default facts in the next case. An employee’s name also needs maintenance when responsibility changes. The reusable method should structure new inputs without bringing old quantities, suppliers or unresolved questions into an unrelated case simply because that earlier example helped explain how the procedure works.

Check the boundary between instruction, result draft and performed action. A text may prepare handover to Ben; it does not prove he received or accepted it. The assist module page states that external effects require your approval. Describe clearly what is prepared and which real steps the team subsequently checks. A well-written procedure should make this distinction easier rather than hiding it behind an imprecise claim that everything is already done.

Maintain one valid version instead of parallel texts

Name an owner for the instruction. In the example, Lara and purchasing check whether sources, handover and cover remain correct. When the receipt report or responsibility changes, they update the relevant passage and test it on a suitable case. Maintenance is triggered by changed work, not merely by an arbitrary calendar date on which someone saves the same text again without checking its usefulness to the people applying it.

Ensure intended colleagues can find the valid version and do not accidentally reuse older drafts. A clear title naming the task and scope helps more than several files called “final”. Connect recurring AI instructions to the same valid rules so the document and its application do not diverge. This maintenance belongs to your process; saving a document once does not automatically keep its content aligned with every later organisational change.

Start with dictation of one recurring task and test the resulting route with a second person. Once normal case, exception and completion work, prepare recurring assistance deliberately. Explore assist and start your first usable work instruction through the module page. The benefit is a process the team understands and can take over while unresolved decisions remain visible with the people responsible for making them.