Organizing the week with a tripartite academic workload: teaching, research, and administration

Context

You're a university faculty member in any discipline who arrives Monday morning (or Sunday night) with a heterogeneous backlog that mixes class prep, a manuscript in progress, graduate student advising, and institutional obligations. This prompt helps you sort that tripartite workload — teaching [T], research [R], and management/admin [M] — into concrete, prioritized time blocks, and surfaces an overloaded week before you discover it on Friday.

Paste before

Before opening the model, have ready:

• Your free blocks for the week with start and end times (exclude already-scheduled classes, fixed meetings, and unmovable commitments).
• Your task list for the week, with a role label next to each item: [T] for teaching tasks (class prep, grading, student office hours), [R] for research tasks (advancing a manuscript, meeting with thesis students, literature review, data analysis), and [M] for management and administrative tasks (committees, reports, coordination, administrative email).
• A time estimate per task (rough is fine: "30 min", "2 h", "half a day").
• Any relevant constraints for the week (optional): hard deadlines, absences, low-energy days.

Privacy rule — student data: Do not include names or identifying details of thesis students or research participants in the prompt. Student data is protected by applicable regulations — in Chile: Ley 19.628 and its 2024 update; in your context: FERPA, GDPR, or the applicable law in your jurisdiction.

Act as a scheduling assistant for university faculty. Your job is to help me distribute my tripartite weekly workload — teaching, research, and institutional management — in a realistic way, prioritizing what is urgent without systematically sacrificing research time.

Context for my week:
- Available free blocks (with start–end times): {{free_blocks_per_day_with_start_and_end_times}}
- Task list with role label:
{{task_list_with_T_R_M_label}}
- Constraints or special deadlines this week: {{constraints_or_special_deadlines}}

With this information, please:

1. Classify each task as either **hard** (has a firm deadline this week, or blocks others if not completed) or **flexible** (important but can move without immediate consequences). Keep the role label [T], [R], or [M] next to each item.

2. Assign all **hard** tasks to specific time blocks, respecting the estimated duration. If a [T] or [M] task is hard, anchor it in the slot that best matches its nature (for example: class prep before the day you teach; an institutional report before its stated deadline).

3. For **flexible [R]** tasks, suggest a tentative day without fixing an exact time, and group them under a **deep work** block of at least 90 minutes. Briefly explain why that day.

4. List routine **[M]** tasks at the end of the plan as a generic block ("email and admin: 30 min") rather than scheduling them one by one.

5. Reserve at least one **buffer** block of 30 minutes somewhere in the week for unexpected demands — do not fill it.

6. If **hard** tasks exceed available time, say so clearly: how many hours short you are, which specific task you recommend deferring, and how to negotiate that deadline or what the consequences of deferring would be.

Return the plan as a table per day with columns: DAY | TIME | TASK | ROLE | PRIORITY.

Expected output

Shortened real example. The model produces a classification table + day-by-day plan for the full week + buffer summary + SYSTEM NOTE.

Task classification (6 hard out of 9 total — flexible tasks and routines listed at the bottom):

# Task Role Type Est. time 1 Prepare lecture for Social Psychology II [T] Hard 1.5 h 2 Grade midterm quizzes — Qualitative Methods (25 students) [T] Hard 3.0 h 4 Thesis progress meeting (mixed-methods student) [R] Hard 1.5 h 5 Review and comment on draft of Chapter 3 of own article [R] Hard 3.0 h 7 Prepare minutes for departmental committee [M] Hard 0.75 h 9 Conference travel reimbursement form [M] Hard 0.75 h

Total hard tasks: 10.5 h. Total available: 21.5 h → no hour deficit; the risk is sequencing, not volume.

MONDAY (full table):

TIME TASK ROLE PRIORITY 09:00–10:30 Prepare lecture for Social Psychology II [T] High — deadline Tuesday 10:30–10:45 Buffer / break — — 10:45–13:00 Review and comment on Chapter 3 draft (block 1 of 2 — 2.25 h) [R] High — editorial deadline Friday 16:00–17:30 Review and comment on Chapter 3 draft (block 2 of 2 — 0.75 h remaining) [R] High — editorial deadline Friday

TUESDAY – FRIDAY [abbreviated — the model delivers a full table for each day using the same logic: hard tasks anchored, buffers distributed, flexible tasks assigned a tentative day with justification]

SYSTEM NOTE: No hour deficit. The 10.5 hours of hard tasks fit comfortably within the 21.5 hours available.

Identified risk: The only real tension is a sequencing dependency on Monday: if that block is interrupted, the article is at risk because the editorial deadline is Friday at 18:00 and requires 3 hours of sustained concentration.

Preventive negotiation suggestion: Let your co-author know Monday morning that the commented draft will arrive before Friday 12:00 (not 18:00). This gives you 6 additional hours of margin if Monday falls apart and you need to fall back on the Thursday reserve block.

Watch out for

• The model does not know the actual cognitive cost of each task: preparing a brand-new lecture and reviewing a dissertation chapter are both high-demand [T] and [R] tasks, but the AI may treat them as equivalent. Specify in your constraints if a particular day has limited energy, or if a task demands peak concentration.
• [R] tasks (research) are the first ones the AI tends to move when there is a time conflict — exactly the pattern we want to avoid. If the model repeats that bias, push back explicitly: "do not sacrifice research blocks before checking whether any [M] task can be delegated or dropped."
• Do not paste identifiable details about thesis students (names, their case study institution, progress notes containing sensitive participant data). For scheduling purposes, "thesis progress meeting — mixed-methods student — 90 min" is all you need.
• The 30-minute buffer is not optional: academic weeks with zero slack are the ones that end in chaotic Fridays. If the model removes it to squeeze in more tasks, reject the plan.

Suggested follow-up

If the week is overloaded: "The hard tasks exceed available time. Help me identify which [M] task could be delegated to a teaching assistant or department coordinator, and draft a short email requesting an extension on the institutional report."

If you want to turn this into a standing routine: "Convert this framework into a base weekly template for a faculty member with 2 courses and 1 active research project, with typical blocks already marked and reminders for recurring deadlines such as thesis progress reports and grade submissions."