Manage your end-of-semester workload

Context

A teacher at any level — primary, secondary, or higher education — entering the end-of-semester period with a pile of simultaneous high-demand tasks and immovable institutional deadlines: final grades, reports, parent/guardian meetings, minutes, and assessment review meetings. The prompt organizes that workload into a realistic weekly plan, identifying overallocation before the final Friday reveals the collapse.

The end of semester is the period of highest shared workload for school and university teachers alike: both face mass grading, simultaneous hard deadlines, and the need to communicate results to students and families before closing records.

Originally written for Chilean classrooms. References to SIGE (Chile's school management system), MBE Domain D, and Ley 19.628 are specific to the Chilean context. Substitute your school's grading system, your school's teaching framework, and your national data protection law as applicable.

Paste first

Before opening the model, have ready:

• Your institution's concrete deadlines: grade submission in your school management system, report delivery to your curriculum coordinator or academic secretary, dates for parent/guardian meetings or group feedback sessions.
• Your to-do list, with a type label next to each item:
  • [G] grading (tests, essays, semester projects, oral defenses)
  • [A] administrative (system entry, formal reports, minutes)
  • [F] families / group feedback (parent/guardian meetings, sending results, at-risk notifications)
  • [M] management (assessment review meetings, committees, team coordination)
• A rough time estimate per task (coarse is fine: "3 h", "half a day"). For [G] items, note how many pieces per hour you can realistically grade.
• The free blocks available until the close date, excluding classes and immovable commitments.

Privacy rule: Do not include students' names, ID numbers, individual grades, learning support diagnoses, or psychopedagogical reports in the prompt. To plan volume it is enough to write "48 students with a descriptive report pending" or "6 students at risk of failing." Identifiable data should not pass through an external language model.

Act as a planning assistant for teachers during the end-of-semester period. Your job is to help me distribute all my end-of-semester tasks realistically across the weeks I have left, assigning each task to a specific time block and warning me if there is more work than fits in the available time.

**My context:**
- Role and level: {{role_and_school_level}}
- Students to assess: {{approximate_number_of_students_to_assess}}
- Available time: {{weeks_available_with_start_and_end_dates}} — {{free_blocks_per_week_in_hours}}

**My end-of-semester to-do list, with type labels:**
{{to_do_list_with_labels_[G]_grading,_[A]_administrative,_[F]_families,_[M]_management}}

**Concrete deadlines:**
{{deadlines_with_description_and_time_if_known}}

With this information, please:

1. Classify each to-do item as **hard** (immovable deadline or blocks other people if not done) or **soft** (urgent but with some real flexibility).

2. Estimate the total time required for **hard** items and compare it to the available time. If there is overallocation, flag it immediately: how many hours short and what the consequence of each possible deferral would be.

3. Assign **hard** items to specific weeks with estimated hours. **[G]** mass-grading items must land in contiguous blocks of at least 2 hours: fragmentation destroys grading rhythm and increases actual time.

4. Propose an attack order that allows completing feedback cycles with students **before** recording final grades, when possible.

5. Identify which **[A]** and **[M]** items can be handled in 20–30 minute fragments so they do not consume deep-work blocks with tasks that do not require them.

6. Reserve at least 30 minutes of buffer per week, unassigned.

Return the plan as a table by week with columns: **Week | Task | Type | Est. hours | Priority**.

Expected output

Real example (trimmed):

Overallocation alert: 28.4 h of hard work for 28 h available. Without buffers, deficit of ~25 min; with buffers (3 × 30 min), deficit of ~1.9 h. Oral defenses represent 63% of total time; if pace drops from 8 to 7/h, deficit rises to ~3.4 h. Recommendation: reduce buffers to 15 min/week and accept that W2 will have no real margin.

Week Task Type Est. hours Priority W1 Parent/guardian meetings — Grade 11 + Grade 10 F 3.0 h High W1 Grade oral defenses — Grade 11 (76 students, blocks ≥2 h) G 9.5 h High W2 Grade remaining oral defenses (67 students) G 8.4 h High W3 — first block Enter grades + upload averages to grade system G/A 0.8 h Critical — before Oct 15 17:00 W3 Descriptive reports — Grade 10 A (48 students) A 3.2 h High — Oct 17 23:59 W3 Assessment review meeting (prep + attendance) M 3.0 h High

Items fragmentable in 20–30 min: entering grades into the digital grade book and written at-risk communication. Do not fragment: grade system upload (irreversible deadline), descriptive reports, or meeting preparation.

Watch out for

• The model does not know how much deep grading actually costs. 143 oral defenses are not 143 × 5 minutes. If you estimate grading time poorly, the whole plan collapses. Be explicit: "I grade 8 oral defenses per hour" or "each descriptive report takes me 4 minutes." AI tends toward optimism in teacher grading estimates.
• Do not include identifiable student data. Names, ID numbers, individual grades, or diagnoses are protected by your national data protection law. The model does not need to know who each student is to help you plan your time.
• The model will tend to underestimate [F] and [M] items. Preparing a meaningful parent/guardian meeting or gathering evidence for an assessment review takes more time than it appears. If the plan leaves these for "the free slot on Friday," ask it to reschedule them with a realistic estimate.

Suggested iteration

If the week is overallocated: "The hard items exceed the available time by {{X}} hours. Help me identify which [A] or [M] task can be delegated to a coordinator or colleague, and draft a brief message explaining the context."

If you want to generate the content of reports or feedback once you have the plan: use a separate prompt specifically for drafting descriptive reports or group feedback — the model will work better with one task at a time.