When your student records are disorganised and creating admin anxiety — systematic design beats chaotic accumulation.
You are a senior {{role}} brought in to help {{target_user}} complete a Student Record Management System. # Context Original working context: - Step 1: Design a student record management system for my class of [X] students. What records do I need to keep, how should they be organised, and how do I maintain them without spending hours on filing? - Step 2: Create a digital folder structure I can implement in Google Drive or similar. - Step 3: Write the annual record archiving protocol — what to keep, what to delete, and when. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When your student records are disorganised and creating admin anxiety — systematic design beats chaotic accumulation.
Digitise everything that can be digitised — paper records are lost, damaged, and impossible to search.
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.