Simplify and optimize team schedules.
A schedule can look full while leaving the wrong people unavailable at the wrong moment. Have AI find the constraints behind your team’s calendar or roster, compare workable alternatives and prepare a timetable that makes the work easier.
Try it now
Copy the prompt into your AI tool of choice, then answer its questions as they come.
Paste it into any AI chat to start. For most people, this is all you need.
Everything on this page in one paste: the prompt plus the full plan, every step and what to check. Use it for longer moves, to plan ahead, to share with a colleague, or if your AI can't open links.
How it goes
What the AI will do
- Investigate team calendars, coverage requirements, handoffs and scheduling discussions to find the real constraints.
- Build and compare feasible schedules against the improvements you choose, using evidenced availability and preferences.
- Prepare the selected schedule in a usable format, check conflicts and apply authorized calendar or roster changes where supported.
What to have ready
- The team and schedule to improve: meeting calendars, shift rosters or another recurring timetable.
- Access to current schedules and relevant staffing or handoff records; rough notes can help fill gaps.
Where you come in
- Confirm the people, hard requirements and what should improve.
- Resolve unconfirmed availability or tradeoffs, choose the schedule and authorize any changes that affect others.
What you'll get
A checked, usable team schedule with its coverage and tradeoffs explained, plus an accurate account of any changes applied or confirmations still pending.
You're done when
The selected schedule is prepared in a usable format and checked against the agreed requirements. Authorized changes are verified; unconfirmed availability, unapplied changes and pending team responses remain explicit.
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result. ### Start with the activity and the user's context Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear. Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them. ### Check the capabilities needed for this work Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit. When useful access is missing: - Explain what you cannot reach and how that material would help. - Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot. - If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response. - Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available. ### Ask focused questions and respect the answers Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful. Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements. ### Keep evidence and independent contributions distinct Distinguish evidence, inference, and missing information. Check your work against the source material. Use independent agents when your system actually supports delegation and independent investigation or review would improve the work: - Give each agent a bounded brief and the context appropriate to its role. - Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations. - Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately. ### Produce, check, and revise the result Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them. Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result. Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized. Help me simplify and improve a team's schedule. Establish the work it must support, compare feasible alternatives and prepare the chosen timetable for use. Do the investigation, schedule construction and conflict checking yourself. ### Identify the schedule and the people Start from the team or timetable I supplied. Establish whether this is a shift or coverage roster, a recurring meeting calendar, project coordination or another scheduling problem. Do not assume every busy calendar calls for fewer meetings. Inspect and try access to team calendars, current rosters, role assignments, staffing requirements, service hours, handoff records and relevant project deadlines. Search scheduling emails, chats and meeting transcripts for why the current arrangement exists, recurring clashes, expressed preferences and earlier attempted changes. Use the roster and invitations to establish who is actually involved, their roles, locations and time zones. Calendar occupancy alone does not establish someone's willingness or ability to take an assignment. Show the team and time period you have identified for correction. Confirm consequential uncertainty before planning around it. If access is missing, investigate permitted connection or export options and help obtain the current timetable and key requirements. Rough accounts are usable but keep unverified availability or coverage rules explicit; do not present a provisional reconstruction as a checked operating roster. ### Separate requirements from preferences Build a concise account of what the schedule must achieve. Establish hard requirements from actual records or the responsible person's confirmation: coverage by role or capability, minimum staffing where applicable, fixed events, dependencies, leave, time zones, travel and handover time, and applicable company work/rest rules. Use current authoritative sources if a specific legal scheduling requirement needs checking; do not invent one from a general recollection. Identify preferences separately: protected focus time, fewer fragmented days, consistent shifts, shared collaboration windows, equitable inconvenient hours or less travel. Attribute a preference to a person only when supported by their statements or confirmation. One manager's description of what everyone likes is not direct evidence from everyone. State the most useful improvement goal and ask me to confirm it along with material constraints. Where goals compete, explain the tradeoff in concrete terms—for example, a common meeting window may reduce fragmentation but repeatedly inconvenience one time zone. Wait for choices that change which schedule is acceptable. Continue analyzing unaffected requirements while a specific person's availability remains unconfirmed. ### Diagnose the current timetable Map the existing schedule against the requirements. Identify real overlaps, uncovered periods, unnecessary handoffs, isolated short appointments, duplicated attendance and constraints that force otherwise puzzling arrangements. Quantify lost or improved time only when supported by the schedule and stated assumptions. Do not treat an empty hour as automatically available work capacity. Look for simplification before elaborate optimization: combine compatible events, move a flexible event, stagger coverage, protect a stable collaboration window or shorten a transition. Check what each event or shift produces and who must actually participate before removing or consolidating it. Use relevant outcome and handoff records to avoid breaking work that is invisible in the calendar title. ### Build and compare feasible schedules Construct a small number of materially different alternatives when there is a useful tradeoff; a clear single repair does not require artificial options. Preserve hard requirements and show how each alternative changes the agreed goals relative to the current timetable. For every proposed schedule, check each person's overlapping commitments, required capability coverage, time-zone conversion, relevant date changes, breaks and handoffs. Check recurring events beyond the first occurrence, including exceptions and daylight-saving changes when relevant. Keep proposed availability distinct from confirmed availability. Use a spreadsheet, scheduling tool or calculation to verify a substantial roster rather than relying on a prose description. If agents help, assign bounded constraints or schedule alternatives with the same roster, evidence and common evaluation criteria. Require an explicit schedule and failed-constraint list, then reconcile centrally. Use a separate checker for complex schedules where available; give it the actual timetable and requirements, not a claim that it is optimized. If requirements cannot all be met, identify the actual conflict and the smallest decisions that could resolve it. Do not quietly relax a staffing rule or assign someone work they have not agreed to cover. Present the best feasible alternatives and let me choose which tradeoffs to accept. Describe improvement against the chosen criteria; do not claim a globally optimal schedule without a method that establishes that. ### Prepare and apply the selected timetable Turn the selected alternative into the format the team can use: a roster, calendar import, editable schedule or supported scheduling-system draft. Include dates, local times and time zones, people or roles, handoffs and exceptions. Prepare a concise explanation of what changed and any response needed from affected people. Ask for confirmation of unresolved individual availability through the permitted route. You may draft the specific request, but do not send it on my behalf without authorization. Hold affected assignments provisionally until actual responses arrive or the responsible person establishes the constraint. Do not call a proposal adopted by the team. If I authorize calendar or roster updates, inspect the supported action and apply the exact selected changes, preserving exceptions and avoiding duplicate invitations. Check the resulting events or roster entries. Inspect whether editing an event will notify participants and include that consequence in the concrete authorization when it is not already covered. Otherwise deliver the prepared schedule without changing others' calendars. ### Verify and hand over Recheck the final artifact against every hard requirement and agreed preference after revisions. Open the actual file or calendar representation and inspect representative dates plus known exception periods. Repair formatting or import problems that would change how the team uses it. Deliver the chosen timetable, a short explanation of improvements and tradeoffs, and the few confirmations still pending. State precisely whether it is prepared, imported or communicated. Invite corrections from the actual trial or team response and revise affected parts when those responses return. Finish with a usable schedule, not merely advice to reschedule things. These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
View full AI instructions
Simplify and optimize team schedules.
What the AI will do
- Investigate team calendars, coverage requirements, handoffs and scheduling discussions to find the real constraints.
- Build and compare feasible schedules against the improvements you choose, using evidenced availability and preferences.
- Prepare the selected schedule in a usable format, check conflicts and apply authorized calendar or roster changes where supported.
What you can provide
- The team and schedule to improve: meeting calendars, shift rosters or another recurring timetable.
- Access to current schedules and relevant staffing or handoff records; rough notes can help fill gaps.
Where you'll take part
- Confirm the people, hard requirements and what should improve.
- Resolve unconfirmed availability or tradeoffs, choose the schedule and authorize any changes that affect others.
What you'll get
A checked, usable team schedule with its coverage and tradeoffs explained, plus an accurate account of any changes applied or confirmations still pending.
Activity context
A schedule can look full while leaving the wrong people unavailable at the wrong moment. Have AI find the constraints behind your team’s calendar or roster, compare workable alternatives and prepare a timetable that makes the work easier.
For the user
Tell the AI which team and timetable you mean. It will search for the reasons behind the current arrangement before proposing changes. You confirm consequential constraints and choose among workable alternatives; the AI prepares the chosen schedule and makes only the calendar or roster changes you authorize.
Guidance for the AI
These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result.
Start with the activity and the user's context
Read the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear.
Begin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them.
Check the capabilities needed for this work
Inspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit.
When useful access is missing:
- Explain what you cannot reach and how that material would help.
- Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot.
- If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response.
- Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available.
Ask focused questions and respect the answers
Ask questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful.
Confirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements.
Keep evidence and independent contributions distinct
Distinguish evidence, inference, and missing information. Check your work against the source material.
Use independent agents when your system actually supports delegation and independent investigation or review would improve the work:
- Give each agent a bounded brief and the context appropriate to its role.
- Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations.
- Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately.
Produce, check, and revise the result
Do the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them.
Check the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result.
Preserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized.
Your AI prompt
Help me simplify and improve a team's schedule. Establish the work it must support, compare feasible alternatives and prepare the chosen timetable for use. Do the investigation, schedule construction and conflict checking yourself.
Identify the schedule and the people
Start from the team or timetable I supplied. Establish whether this is a shift or coverage roster, a recurring meeting calendar, project coordination or another scheduling problem. Do not assume every busy calendar calls for fewer meetings.
Inspect and try access to team calendars, current rosters, role assignments, staffing requirements, service hours, handoff records and relevant project deadlines. Search scheduling emails, chats and meeting transcripts for why the current arrangement exists, recurring clashes, expressed preferences and earlier attempted changes. Use the roster and invitations to establish who is actually involved, their roles, locations and time zones. Calendar occupancy alone does not establish someone's willingness or ability to take an assignment.
Show the team and time period you have identified for correction. Confirm consequential uncertainty before planning around it. If access is missing, investigate permitted connection or export options and help obtain the current timetable and key requirements. Rough accounts are usable but keep unverified availability or coverage rules explicit; do not present a provisional reconstruction as a checked operating roster.
Separate requirements from preferences
Build a concise account of what the schedule must achieve. Establish hard requirements from actual records or the responsible person's confirmation: coverage by role or capability, minimum staffing where applicable, fixed events, dependencies, leave, time zones, travel and handover time, and applicable company work/rest rules. Use current authoritative sources if a specific legal scheduling requirement needs checking; do not invent one from a general recollection.
Identify preferences separately: protected focus time, fewer fragmented days, consistent shifts, shared collaboration windows, equitable inconvenient hours or less travel. Attribute a preference to a person only when supported by their statements or confirmation. One manager's description of what everyone likes is not direct evidence from everyone.
State the most useful improvement goal and ask me to confirm it along with material constraints. Where goals compete, explain the tradeoff in concrete terms—for example, a common meeting window may reduce fragmentation but repeatedly inconvenience one time zone. Wait for choices that change which schedule is acceptable. Continue analyzing unaffected requirements while a specific person's availability remains unconfirmed.
Diagnose the current timetable
Map the existing schedule against the requirements. Identify real overlaps, uncovered periods, unnecessary handoffs, isolated short appointments, duplicated attendance and constraints that force otherwise puzzling arrangements. Quantify lost or improved time only when supported by the schedule and stated assumptions. Do not treat an empty hour as automatically available work capacity.
Look for simplification before elaborate optimization: combine compatible events, move a flexible event, stagger coverage, protect a stable collaboration window or shorten a transition. Check what each event or shift produces and who must actually participate before removing or consolidating it. Use relevant outcome and handoff records to avoid breaking work that is invisible in the calendar title.
Build and compare feasible schedules
Construct a small number of materially different alternatives when there is a useful tradeoff; a clear single repair does not require artificial options. Preserve hard requirements and show how each alternative changes the agreed goals relative to the current timetable.
For every proposed schedule, check each person's overlapping commitments, required capability coverage, time-zone conversion, relevant date changes, breaks and handoffs. Check recurring events beyond the first occurrence, including exceptions and daylight-saving changes when relevant. Keep proposed availability distinct from confirmed availability.
Use a spreadsheet, scheduling tool or calculation to verify a substantial roster rather than relying on a prose description. If agents help, assign bounded constraints or schedule alternatives with the same roster, evidence and common evaluation criteria. Require an explicit schedule and failed-constraint list, then reconcile centrally. Use a separate checker for complex schedules where available; give it the actual timetable and requirements, not a claim that it is optimized.
If requirements cannot all be met, identify the actual conflict and the smallest decisions that could resolve it. Do not quietly relax a staffing rule or assign someone work they have not agreed to cover. Present the best feasible alternatives and let me choose which tradeoffs to accept. Describe improvement against the chosen criteria; do not claim a globally optimal schedule without a method that establishes that.
Prepare and apply the selected timetable
Turn the selected alternative into the format the team can use: a roster, calendar import, editable schedule or supported scheduling-system draft. Include dates, local times and time zones, people or roles, handoffs and exceptions. Prepare a concise explanation of what changed and any response needed from affected people.
Ask for confirmation of unresolved individual availability through the permitted route. You may draft the specific request, but do not send it on my behalf without authorization. Hold affected assignments provisionally until actual responses arrive or the responsible person establishes the constraint. Do not call a proposal adopted by the team.
If I authorize calendar or roster updates, inspect the supported action and apply the exact selected changes, preserving exceptions and avoiding duplicate invitations. Check the resulting events or roster entries. Inspect whether editing an event will notify participants and include that consequence in the concrete authorization when it is not already covered. Otherwise deliver the prepared schedule without changing others' calendars.
Verify and hand over
Recheck the final artifact against every hard requirement and agreed preference after revisions. Open the actual file or calendar representation and inspect representative dates plus known exception periods. Repair formatting or import problems that would change how the team uses it.
Deliver the chosen timetable, a short explanation of improvements and tradeoffs, and the few confirmations still pending. State precisely whether it is prepared, imported or communicated. Invite corrections from the actual trial or team response and revise affected parts when those responses return. Finish with a usable schedule, not merely advice to reschedule things.
Done when
The selected schedule is prepared in a usable format and checked against the agreed requirements. Authorized changes are verified; unconfirmed availability, unapplied changes and pending team responses remain explicit.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.
These instructions were written in September 2026 using the frontier models available at the time. You may now have better tools or models, or restrictions that make some tasks harder. Your AI should adapt to the tools and access you actually have and find the best available way to help. Everything here is a starting suggestion for you and your AI, not a proven best practice for every setup. Feel free to rewrite any of it to better meet your needs.