Prompt: Convert technical training meeting into high-context SOP documents (AI-ready)
Act as an operations and technical documentation specialist for Uptake Digital.
You are converting a Microsoft Teams technical training session into one or more high-quality Standard Operating Procedure (SOP) documents.
This output will be fed into additional AI systems for refinement and expansion, so depth, clarity, and context are critical. Do not optimise for brevity. Optimise for completeness and accuracy.
Do not produce a meeting recap.
Extract and convert all relevant procedural knowledge from the meeting into structured SOP documentation that can be:
- followed by a technician
- understood without attending the meeting
- safely expanded by another AI system without losing intent
- Identify each repeatable process described and create separate SOPs where appropriate
- Capture explicit steps AND implied logic, even if not fully spelled out
- Preserve technical nuance, reasoning, and intent behind actions
- Include supporting context that explains why steps are performed, not just what to do
- Expand shorthand or verbal explanations into clear written instructions
- Where presenters skip steps due to assumed knowledge, reconstruct them where reasonably inferable
- Do not remove detail for the sake of conciseness
If something is unclear:
- Do not guess
- Mark it as Needs confirmation
- Provide the most likely interpretation if helpful, clearly labelled
Where available, incorporate:
- Tools, platforms, and systems used
- Permissions or roles required
- Configuration details and settings
- Decision points and conditional logic
- Dependencies between steps or systems
- Common mistakes or pitfalls mentioned
- Verbal tips or operator judgement shared during training
- Any references to standards, policies, or best practices
- Order of operations and sequencing rationale
Purpose Clear explanation of what this procedure achieves and when it should be used.
Context / Background Explain why this process exists, including business or technical rationale where available.
Scope Who this applies to, and any inclusions or exclusions.
Prerequisites Access, permissions, tools, licences, environment requirements, or prior knowledge required.
Inputs / Required Information All data, credentials, or references needed before starting.
Procedure Numbered steps with:
- Clear, actionable instructions
- Expanded detail (avoid shorthand)
- Relevant configuration values or examples
- Decision points (e.g. “If X, then Y”)
- Explanations where needed for clarity
System Behaviour / Expected Outcomes What should happen at key stages so the operator knows they are on track.
Exceptions / Edge Cases Variations, known issues, or alternative paths.
Validation / Completion Check How to confirm the process has been completed successfully.
Escalation When to escalate, who to escalate to, and what information to include.
Notes / Risks Warnings, dependencies, assumptions, or important considerations.
- Start with SOPs created (list of SOP titles)
- Then provide each SOP in full
- Maintain consistent formatting
- Use plain English and British spelling
- Keep tone practical and instructional
If the meeting does not provide full coverage:
- Still produce the SOP using available detail
- Add a final section:
Gaps requiring confirmation
- List missing details clearly
- Be specific about what needs validation
Prioritise completeness over brevity.
Assume the reader:
- was not in the meeting
- does not have implicit knowledge
- will rely on this document to execute the task or feed it into another AI system
Now convert the meeting content into SOP documentation.