Coaching Calendar & Booking Policy SOP Writer

Most coaches don’t lose hours to bad clients. They lose them to a vague calendar. No stated buffers, so calls run into each other. No written reschedule rule, so every change becomes a polite negotiation in the DMs. A no-show that you eat because there was never a policy to point to.

This prompt fixes that in one pass. You describe how you actually want to work, and it writes a clear coaching booking policy your clients can read in 30 seconds, plus an internal calendar SOP that tells you exactly which scheduler settings to flip. By the end of this page you’ll also understand why the prompt produces a usable policy instead of generic boilerplate, so your next ops prompt is sharper.

When to use this

• You keep renegotiating your hours, reschedules, or cancellations in one-off messages.
• You’re setting up Calendly, Acuity, or TidyCal and don’t know what buffers and limits to set.
• Calls run back-to-back with no breathing room and you end the day fried.
• A client no-show cost you a slot and you had no policy to fall back on.
• You want one consistent set of rules across your scheduler, welcome email, and client agreement.

The prompt

Copy this whole block into ChatGPT, Claude, or Gemini:

You are an operations consultant who designs scheduling systems and booking policies for solo coaches. Your job is to turn my preferences into a clear, professional booking policy and a matching calendar SOP I can put into use today.

Before writing, ask me up to 3 clarifying questions if anything below is unclear or contradictory (for example, if my buffers don't fit my stated hours). Otherwise, proceed.

CONTEXT
- What I coach and my session format: {{COACHING_TYPE}}
- My availability (days, hours, timezone): {{AVAILABILITY}}
- Buffers and daily limits I want: {{BUFFER_RULES}}
- Booking, reschedule and cancellation notice windows: {{NOTICE_WINDOWS}}
- My late-arrival and no-show rule: {{NO_SHOW_RULE}}
- My scheduler and where the policy will live: {{TOOLS}}
- Tone: {{TONE}}

TASK
Produce two deliverables.

1. CLIENT-FACING BOOKING POLICY
   Write a short policy my clients will actually read, with these labeled sections:
   - When you can book me (hours and timezone, stated plainly)
   - How to book and reschedule
   - Cancellation and notice windows
   - Late arrivals and no-shows
   - One friendly closing line that frames the rules as protecting their results.

2. INTERNAL CALENDAR SOP
   Write a step-by-step standard operating procedure for ME, covering:
   - Exact scheduler settings to configure (available hours, buffers, daily limits, minimum notice) based on my tools above.
   - A checklist for what to do when a client requests a reschedule or cancels.
   - What to do after a no-show.

CONSTRAINTS
- Match my tone. Plain English, no legalese, no buzzwords like 'unlock' or 'in today's fast-paced world'.
- Keep the client-facing policy under 250 words.
- Use only the rules I gave you. Do not invent fees, refund terms, or hours I didn't state. If something I need is missing, flag it in a short 'Gaps to confirm' note at the end instead of guessing.
- Format both deliverables so I can copy-paste them directly into my scheduler and a document.

How to customize it

Replace the seven {{VARIABLES}} before you send it:

See it in action (full example)

Here is the exact prompt, filled in for an executive coach. This is the whole input, nothing hidden:

You are an operations consultant who designs scheduling systems and booking policies for solo coaches. Your job is to turn my preferences into a clear, professional booking policy and a matching calendar SOP I can put into use today.

Before writing, ask me up to 3 clarifying questions if anything below is unclear or contradictory (for example, if my buffers don't fit my stated hours). Otherwise, proceed.

CONTEXT
- What I coach and my session format: 1:1 executive coaching, 60-minute video calls
- My availability (days, hours, timezone): Tue-Thu, 9am-3pm Eastern (US)
- Buffers and daily limits I want: 15-min buffer between calls, max 4 sessions per day, no back-to-backs over my 12-1pm lunch
- Booking, reschedule and cancellation notice windows: book at least 24h ahead, reschedule with 24h notice, cancel with 48h notice
- My late-arrival and no-show rule: session is forfeited after a no-show; if a client is 10+ minutes late, the call is shortened, not extended
- My scheduler and where the policy will live: Calendly + Google Calendar; policy shown on the booking page and in the welcome email
- Tone: warm but firm, plain English, no legalese

TASK
Produce two deliverables... [rest of the prompt unchanged]

And here is the complete output the model returns:

A quick note before I write: your three rules all fit your stated hours, so no blockers. Drafting now.

---

1. CLIENT-FACING BOOKING POLICY

When you can book me Coaching calls run Tuesday through Thursday, 9:00am-3:00pm Eastern (US). Sessions are 60 minutes by video.

How to book and reschedule Grab a time on my Calendly link. Please book at least 24 hours in advance so I can prepare for our session. Need to move it? Use the reschedule link in your confirmation email with at least 24 hours’ notice and pick any open slot.

Cancellation and notice windows If you need to cancel, let me know at least 48 hours before our call. That gives the time to someone on my waitlist and keeps our work on track.

Late arrivals and no-shows Life happens. If you’re running late, jump on when you can, but the call still ends at our scheduled time so I can stay on track for the next client. If a session is missed with no notice, it’s counted as used.

These few rules aren’t about being rigid. They protect the focused, on-time sessions that get you results, and they let me give you my full attention every time.

---

2. INTERNAL CALENDAR SOP

A. Scheduler settings to configure (Calendly) 1. Set event type to a 60-minute “Executive Coaching Call.” 2. Availability: Tuesday, Wednesday, Thursday only, 9:00am-3:00pm, timezone Eastern (US). 3. Add a 15-minute buffer after each event. 4. Block 12:00pm-1:00pm daily as unavailable (lunch) so no call backs onto it. 5. Set a daily limit of 4 events. 6. Set minimum scheduling notice to 24 hours. 7. Turn on the reschedule/cancel links in confirmations. 8. Confirm Calendly is two-way synced with Google Calendar so personal blocks show as busy.

B. When a client requests a reschedule or cancels 1. Reschedule with 24h+ notice: approve, let Calendly handle it, done. 2. Reschedule with under 24h notice: offer the next open slot manually; note it in the client’s file. 3. Cancel with 48h+ notice: release the slot and message the waitlist. 4. Cancel with under 48h notice: log it; the session counts as used per policy.

C. After a no-show 1. Wait 10 minutes on the call, then mark the session as used. 2. Send a brief, warm check-in: “Missed you today, hope all’s well, here’s the link to book our next one.” 3. Log the no-show in the client’s file. If it’s a second one, flag it for a conversation.

---

Gaps to confirm – You didn’t mention any fee for late cancellations or no-shows. Right now the policy treats a missed session as “used.” If you ever sell single sessions rather than packages, you may want a stated fee. – No refund terms were given, so I left them out on purpose.

That is ready to use. Paste the policy into your Calendly page and welcome email, follow the SOP to set up the calendar, and decide on the two flagged gaps.

Why this works

Three LLM principles are doing the heavy lifting. Learn them and every ops prompt you write gets better:

1. Role priming. Opening with “You are an operations consultant who designs scheduling systems for solo coaches” tells the model which knowledge to pull from. “Write me a booking policy” returns generic legal-sounding filler; an operations-consultant role returns concrete scheduler settings and a usable SOP. Always assign a role that matches the job.
2. Specificity in, specificity out. The model can only be as precise as your inputs. “Be flexible with timing” produces vague mush. “15-minute buffer, max 4 sessions a day, block 12-1pm” produces exact Calendly steps. Your {{BUFFER_RULES}} and {{NOTICE_WINDOWS}} are what turn the output from advice into a checklist.
3. Constraints as quality control. The lines that say don’t invent fees or hours and flag missing rules in a ‘Gaps to confirm’ note are the most important in the prompt. Left alone, models cheerfully fabricate a cancellation fee or refund clause you never agreed to, and you’d paste it into a client agreement without noticing. Telling the model what NOT to do, and to ask instead of guess (the “up to 3 clarifying questions” line), is the single biggest fix for confident-but-wrong AI output.

Do this now

1. Copy the prompt above into ChatGPT or Claude.
2. Fill in the seven variables with how you actually want to work, not how you think you “should.”
3. Send it. If it asks clarifying questions or flags a gap, answer honestly.
4. Paste the client-facing policy into your scheduler and welcome email, then follow the SOP to set your buffers and limits today.

Pro tips

• Write your rules as if you mean them. The policy is only as firm as your inputs. If you say “24h notice, but I’m flexible,” you’ll get a wishy-washy policy. State the rule you’ll actually hold.
• Keep the ‘Gaps to confirm’ note. It surfaces the decisions you’ve been avoiding (late fees, refunds) instead of letting the model paper over them.
• Generate a short and a long version. Ask for a one-paragraph version for your booking page and the full version for your client agreement, from the same inputs.
• Re-run it each season. When your availability changes, update {{AVAILABILITY}} and regenerate so your policy and calendar never drift apart.

Related

• Client Session Cancellation & Reschedule Response Scripts
• Standard Operating Procedure Writer for Coaching Tasks
• Weekly Time-Block Planner for Solo Coaches
• Client Intake & Onboarding SOP Builder for Coaches