3,500+ copy-ready AI prompts — filter by type, audience, or difficulty.
When curriculum documentation is required — structure ensures completeness without spending weeks on admin.
When workplace wellbeing concerns need to be formally raised — professional documentation and communication protect your interests.
When facing redundancies — legally sound process documentation that treats affected employees with dignity.
Use when documenting that informed consent was obtained, to ensure all medicolegally required elements are captured in the medical record.
Use when standardising ward handover documentation or training new staff on safe handover practices.
Use when working through a diagnostically challenging case and needing structured documentation of your clinical reasoning.
Use when generating medical certificates or statutory documentation, ensuring legal compliance and ethical standards.
After writing a function or module that others will use — documentation written at the time of coding is always better than documentation written later.
After writing a function or module that others will use — documentation written at the time of coding is always better than documentation written later.
When making a formal referral — thorough documentation strengthens the case and speeds the process.
When hiring documentation is inconsistent — formalised process before an employment dispute surfaces the gap.
When managing an underperforming employee — precise documentation that protects the business and supports the employee.
Use when assessing and documenting decision-making capacity for any significant clinical decision, particularly refusal of treatment.
When growth is limited by the owner doing everything and nothing being documented.
After designing or building an API that external or internal developers will consume.
After designing or building an API that external or internal developers will consume.
When valuable knowledge exists in your head but not anywhere else.
Create a complete Standard Operating Procedure (SOP) for the given process. Include purpose, scope, step-by-step instructions, decision points, and quality checks.
At year end — institutional knowledge transfer that prevents the next teacher starting from scratch.
Whenever building a public API, onboarding new engineers, or handover of a system or codebase
When curriculum documentation is required — structure ensures completeness without spending weeks on admin.
When workplace wellbeing concerns need to be formally raised — professional documentation and communication protect your interests.
When facing redundancies — legally sound process documentation that treats affected employees with dignity.
Use when documenting that informed consent was obtained, to ensure all medicolegally required elements are captured in the medical record.
Use when standardising ward handover documentation or training new staff on safe handover practices.
Use when working through a diagnostically challenging case and needing structured documentation of your clinical reasoning.
Use when generating medical certificates or statutory documentation, ensuring legal compliance and ethical standards.
After writing a function or module that others will use — documentation written at the time of coding is always better than documentation written later.
After writing a function or module that others will use — documentation written at the time of coding is always better than documentation written later.
When making a formal referral — thorough documentation strengthens the case and speeds the process.
When hiring documentation is inconsistent — formalised process before an employment dispute surfaces the gap.
When managing an underperforming employee — precise documentation that protects the business and supports the employee.
Use when assessing and documenting decision-making capacity for any significant clinical decision, particularly refusal of treatment.
When growth is limited by the owner doing everything and nothing being documented.
After designing or building an API that external or internal developers will consume.
After designing or building an API that external or internal developers will consume.
When valuable knowledge exists in your head but not anywhere else.
Create a complete Standard Operating Procedure (SOP) for the given process. Include purpose, scope, step-by-step instructions, decision points, and quality checks.
At year end — institutional knowledge transfer that prevents the next teacher starting from scratch.
Whenever building a public API, onboarding new engineers, or handover of a system or codebase