Skip to main content

Delegated Calendar Booking SOP

Overview​

  • What: Book, hold, and move events on a principal's business calendar on their behalf, without needing to ask what any given event is worth.
  • When: Any time someone other than the principal is arranging their meetings. Standing arrangement, and the default mode during travel.
  • Who: Scheduler runs it. Principal owns the calendar, completes the one-time setup, and answers escalations.
  • Time Required: About 5 minutes per booking once set up.

Two roles are used throughout and mean exactly one thing each:

RoleWho it is
PrincipalThe person whose calendar this is, and who attends the meetings
SchedulerThe person arranging the meetings on their behalf

The boundary between them is the whole point of this SOP. The scheduler owns logistics: offering slots, creating invites, confirming, reminding, and keeping the calendar classified. The principal owns the relationship: who is worth meeting, what gets said, and anything commercial. A scheduling message that turns into a commercial conversation is the main failure mode, and it is the reason the guardrails in §13 exist.

This procedure is a delegation artifact. It exists so booking runs without founder time, which is the second of the two goals in SC Goals. The bump rule in §7 is the first goal made operational.


Prerequisites​

Principal — one-time setup, before any handover​

None of these are the scheduler's to do, and the system does not work until all five are done.

  1. Grant the scheduler Make changes to events on the business calendar. Not Make changes and manage sharing, which is more than this job needs, and not See all event details, which puts the principal back in the loop for every booking. This specific level is what makes the principal the organizer on every invite the scheduler creates, so the client sees the principal's name rather than the scheduler's.
  2. Share the personal calendar as See only free/busy (hide details). Never at full detail.
  3. Set personal events that must block to Busy. An event marked Free transmits nothing through a free/busy share, so a personal calendar of Free events shares as an empty calendar. The share will look like protection and provide none. This is the step most often skipped and the only one whose failure is invisible.
  4. Color every existing recurring event to its category per §5, so the palette reads correctly from day one. Automated booking tools write their own color on sync and routinely get it wrong.
  5. Confirm the hours snapshot in §4 still matches the canonical preferences.

Scheduler — before the first booking​

  • Access to the principal's business calendar at Make changes to events, confirmed by the checks in Verification.
  • The principal's personal calendar visible as opaque Busy bars.
  • A named list of who is to be contacted, with one line of agenda per meeting. This SOP does not decide who gets met.
  • For outreach mail, the Travel Visit Scheduling Email Template.

Procedure​

Booking one meeting, start to finish. Each step points at the rule that governs it.

  1. Confirm which hours profile is live. Look for an all-day travel-window event on the business calendar. If one covers the target date, the travel profile in §4 applies. If not, the home profile does.
  2. Find candidate slots inside the Open window for that profile. Skip anything that collides with an existing event or with a gray Busy bar from the personal share. Treat every gray bar as immovable: do not book over it, and do not ask what it is.
  3. Check the slot against §8 sizing. A physical meeting consumes travel either side, so two physical meetings at different places can never be adjacent.
  4. Place a tentative block on each slot being offered, per §11. This is what stops the same slot going to two clients at once.
  5. Send the outreach email per §13, offering two or three named slots with the time zone stated.
  6. On reply, create the event on the principal's calendar per §12, classified and colored per §5, named per §9, with the timezone set per §10. Delete the tentative blocks that were not taken.
  7. If the reply proposes a slot that is not on offer, do not accept it. Take it back to the principal.
  8. If nothing fits without displacing something, walk the bump ladder in §7. If the ladder runs out, escalate per §14. A ladder that runs out is information, not a puzzle.

Verification​

Per booking, before considering it done:

  • The event sits on the principal's calendar, with the principal shown as organizer, not the scheduler.
  • It carries a color, and the color matches the category.
  • The title follows §9, with a time zone token if the booking crosses zones, and no trailing space.
  • The event's timezone is set to where the principal will physically be, not where the scheduler is.
  • The description block is filled per the Templates section, with any figure or reference number present.
  • A Google Meet link is attached for virtual meetings and absent for physical ones.
  • Every tentative block created for this client that was not taken has been deleted, and anyone who knew about it was emailed first.
  • No two physical events at different locations are adjacent.

Setup verification, once, and after any access change:

  • The scheduler appears on the business calendar's sharing list at Make changes to events.
  • An event created by the scheduler shows the principal as organizer.
  • The personal calendar renders to the scheduler as opaque Busy bars, and a known personal commitment actually appears. A free/busy share looks identical whether or not the underlying events are set to Busy, so this has to be checked rather than assumed.

1. What the scheduler can see​

Two calendars exist.

  • Business. The scheduler manages this. Everything in this SOP applies to it.
  • Personal. The principal manages it. It reaches the scheduler as a free/busy share: opaque gray Busy bars with no title, location, or guests.

Treat every gray Busy bar as immovable. Do not book over it, do not ask what it is. That is the whole protocol for personal time.

2. The system in six lines​

  • Every event gets one category, which sets its color, its movability, and its naming.
  • Seven colors, one per category, one color word each: red, orange, yellow, green, blue, purple, gray. An uncolored event is an unclassified event.
  • Four tiers of movability, from fixed to freely movable.
  • A new revenue opportunity takes from the lowest tier first and stops when the ladder runs out. Running out is an escalation, not a puzzle.
  • A block covers travel as well as the meeting, and the title carries the real start time.
  • When it cannot be solved, escalate rather than improvise.

3. Color is set at creation, never in a cleanup pass​

An uncolored event is an unclassified event, and the moments when classification matters most are exactly the moments before a weekly tidy-up would run. Color the event when you create it.

Automated booking tools color their own events. Leave what a tool generates unless the color contradicts the category, in which case recolor it. This is not optional politeness: a client call left gray reads as a personal hold that nobody may move, which is the opposite of the truth.

4. Where the scheduler may book​

Two profiles. The all-day travel-window event on the business calendar tells you which one is live. If one covers the date you are booking, use the travel column.

ClassHome (IST)Travel (local time at destination)What it means
Closed07:00–11:00, 14:00–15:0012:00–13:00Never book. Not even for revenue
Protected11:00–14:00noneDeep work. No recurring meetings, ever. A one-off external booking needs the principal's yes, asked each time
Occupied15:00–15:30stood down for the tripDaily sync
Open15:30–18:0009:00–17:00Book freely, subject to the ceiling below
Undefinedafter 18:00, weekendsevenings, weekendsAsk before booking

Density ceiling. Under the home profile, blocked time across the working week caps at roughly 40 percent. Check it once a week, not per booking. The ceiling is suspended under the travel profile, because a trip is a compression event and the ceiling would read as a stop sign on exactly the days density is the objective.

The daily sync under the travel profile. A sync that sits at 15:00 at home lands in the middle of the night at most destinations. It stands down for the duration rather than moving, and the overlap window in §14 replaces it.

Snapshot taken 2026-08-14. The principal's canonical productivity preferences are the source of truth for these values and win any disagreement. They are held outside this repository. If this snapshot is more than a month old, confirm the values with the principal before relying on them.

5. Every event gets one category​

Category sets the color, the movability, and the naming. Pick one when you create the event.

Colors are Google Calendar's own, named as they appear in the event color picker. id is the colorId the Calendar API takes, for anything automated.

ColoridSayCategoryUse it forTier
Tomato11redRevenue at stakeA sum or a signature is live: prospect, demo, proposal, collection, renewal, rate change, at-risk account1
Tangerine6orangeClient standingRoutine contact with a healthy paying account: delivery, onboarding, support2
Banana5yellowNetworkRoom value, not deal value: chapter meetings, lodge, mastermind, industry events2
Peacock7blueInternalTeam, contractor, vendor, tooling, ops, admin, errands, and internal tentative blocks3
Basil10greenFocusNo counterparty: deep work, prep, thinking time3
Grape3purpleLockedCannot move at any price: flights, filing deadlines, legal, medical procedures0
Graphite8grayPersonal holdPersonal commitment, no detail shown. Created by the principal only0

Seven distinct hues, one word each. If two people describing the same event would both say "the red one," the palette has failed. Google offers four more colors — Flamingo, Blueberry, Sage, and Lavender — each a near-duplicate of one above. Do not use them. An eighth color degrades every color, not just its own.

A category can be overridden by the principal. It cannot be overridden by the scheduler. That asymmetry is deliberate.

6. What each tier permits​

TierWho moves itHow
0 FixedNobodyDo not move it, do not propose moving it
1 Principal onlyPrincipalFlag the conflict, name the options, wait
2 Ask the other sideSchedulerOnly with the counterparty's yes in writing. Their silence is a no
3 Scheduler's callSchedulerMove or drop it, mention it at the next sync

7. The bump rule​

When a new revenue opportunity needs a slot that is taken:

  • Take from tier 3 first.
  • If tier 3 has nothing, ask the counterparty on a tier 2.
  • Never take from tier 1 or tier 0 to make room.
  • If the only slot that fits is tier 1 or 0, stop and escalate. That is the principal's decision, not a scheduling problem.

The focus floor. At most one Focus block per week may be taken. Focus is the pressure valve, so it must not be drained. The weekly no-inputs thinking block is not Focus at all: it is Locked, colored Grape, and cannot be taken.

8. Sizing a block​

  • Virtual: the block is the meeting.
  • Physical: the block runs from leaving to being back. The title carries the real start.
  • Two physical events at different places cannot be adjacent. Put the travel between them. Adjacency in a calendar asserts teleportation, and every later booking inherits the error.

9. Naming​

<Counterparty or subject> - <what it is> - starts <h:mm am/pm>

The starts suffix appears only when the block opens before the real thing begins, because travel is inside the block. No suffix means the block start is the real start. That is the whole convention.

  • Always name the counterparty. Never initials, never a bare noun with no owner.
  • Add a time zone token whenever the booking crosses zones: starts 12:00pm ET. A time without one, read from another country, is a guess.
  • Sentence case. No trailing spaces.
  • Put the joining link, address, phone number, and any reference number in the description, not the title.
YesNo
Greater New Haven chapter - visitor meeting - starts 12:00pm ETBNI
Michael Grieder - catch-up callcall MG
NMG Digital - product demoProduct demo
Branford PMB - collect mail - starts 12:00pm ETcheck mailbox

10. Timezone and recurring events​

  • Set an event's timezone to where the principal will physically be, not where the scheduler is when creating it. Most calendars default new events to the calendar's own zone, which will be wrong for the whole of a trip. Change it per event.
  • When the principal travels, suspend location-anchored recurring blocks instance by instance. Never edit the series to handle a temporary absence.
  • Mark a trip with an all-day event set to Free, so the window is visible without consuming bookable time. This event is also what tells the scheduler which hours profile is live.

11. Tentative blocks​

When two or three slots go out to a client, those slots are spoken for until the client replies. Without a record of that, the same slot gets offered to two people, or real time gets blocked for a meeting that never happens.

Create one tentative block per offered slot, tier 3, set to Busy, colored Tangerine when the slot is for a client and Peacock when it is internal:

Tentative Block for <Client> - Start <h:mm AM/PM>

The Start time is when the meeting itself begins. The block opens earlier, because travel sits inside it. See §8.

What: slot offered to <Client>, awaiting reply
Who: <name> / <email>
Offered: <all slots sent, with time zone>
Release: <date the slots are released if no reply>
Booked by: <role, date>

Minimum durations. An in-person meeting gets 30 minutes of travel before it, inside the block. On top of that, the meeting itself runs at least an hour, and longer where the account or the distance calls for it. The current per-client minimums are trip-specific and live with the trip's own availability sheet, not here.

  • On a yes, convert the taken slot into the real event and delete the other tentative blocks for that client.
  • Email the other party before deleting a tentative block that they know about, whether it was offered directly or is a recurring commitment being stood down. Deleting quietly reads as a no-show later.
  • On a no, or at the release date, delete all of them. A tentative block that outlives its offer is worse than none, because it blocks real availability with a meeting nobody is having.
  • They are tier 3, so they never block a genuine revenue opportunity. If one has to go, it goes.

12. Creating the invite​

  • Create the event on the principal's calendar, not the scheduler's. This is what makes the principal the organizer, so the client sees the principal's name.
  • Add the client contact as a guest, plus any additional stakeholder the principal named. Do not add anyone the principal did not name.
  • Google Meet link: virtual only. A physical meeting with a Meet link attached invites the client to join the wrong way.
  • Moving or canceling an event with guests emails all of them. Before changing a confirmed meeting, decide whether the guests should be notified, and expect that they will be by default.
  • Reminders: leave the calendar default unless the principal asks otherwise.

13. Sending the outreach email​

Use the Travel Visit Scheduling Email Template, which carries the variants and the sending-account decision. The rules that matter most here:

  • Send from the scheduler's own named mailbox, with the principal on cc. Not a shared alias, and not the platform operations address. Asking a business owner for an hour of their time is a named-person act.
  • The scheduler does not send client mail from the principal's mailbox, even where mailbox delegation exists. Delegate access is for triage: the principal labels what needs attention, the scheduler works that label, and every reply goes out from the scheduler's own address so the client always knows who they are talking to. The invite carries the principal's name because of the calendar permission, which is the narrower and correct instrument for that.
  • No money. No invoices, balances, pricing, or contract terms. The principal raises those in the room.
  • No scope commitments, and no agenda beyond the single line supplied.
  • Offer only the slots that have tentative blocks. If the client proposes something else, take it back to the principal rather than accepting it.
  • Do not renegotiate any recurring call unless the task explicitly says to.
  • Keep it short. Three or four sentences. Anything longer is a sign the ask is unclear.
  • Voice, spelling, and signature follow the working rules for client mail: email-writing-style, client-facing-content-locale, and gmail-drafts-no-signature-block.

14. When something does not fit​

Escalate rather than improvise.

SituationWhere it goesExpect
Day to day, anything not blockingSlackThe default channel. Covered at the next sync if it can wait
Blocking a live revenue decisionDirect message to the principal on SlackAn answer the same working day. Under the travel profile, inside the overlap window below
Cannot wait for the next working dayWhatsAppReserved for genuinely time-sensitive matters. Using it for routine questions costs it its meaning
Anything that needs a recordEmailSlack and WhatsApp are not the archive

The overlap window. When the principal is traveling across a large time difference, "same day" is ambiguous and the sync has stood down. Agree one window per trip where both are reliably awake and treat it as the answer slot. For India-to-US Eastern travel that is roughly 8:30–10:30 AM at the destination, which is early evening at home.

An escalation says four things, in this order:

  • What the opportunity is, and what is at stake if it slips.
  • Which slots would fit it.
  • What currently sits in each of those slots, with its tier.
  • What the scheduler recommends.

Do not resolve a tier 0 or tier 1 conflict without the principal, and do not move a tier 2 without the counterparty's yes in hand.


Templates

Copy-paste patterns per category. Angle brackets mark what to replace. Times shown illustrate the naming format; they are not scheduling guidance.

Every template has the same three parts: title, color, description.

The description block​

Same fields for every category. Drop any line that does not apply. Do not reorder them, because a fixed order is what makes it scannable.

What: <one line on why this meeting exists>
Who: <name, role, company> / <phone> / <email>
Where: <full address, or the joining link>
Travel: <door-to-door each way, and from where>
Prep: <what must be ready, and where it lives>
Ref: <account, quote, invoice, or confirmation number>
Booked by: <role, and on what date>

Revenue at stake​

Color: Tomato (red, id 11). Tier 1, only the principal moves it.

<Company or person> - <collection | renewal | proposal | demo | rate change> - starts <h:mm am/pm ET>

Drop the starts suffix when the meeting is virtual or has no travel inside the block.

What: <the specific sum or signature that is live>
Who: <name, role> / <phone> / <email>
Where: <address or link>
Travel: <each way>
Prep: <the document that has to exist before this call>
Ref: <invoice or proposal number>
Booked by: <role, date>

Always name the amount or the decision in the What line. This is the category that outranks everything else, and it earns that only if the reason is visible without opening a second system.

Client standing​

Color: Tangerine (orange, id 6). Tier 2, move only with the client's written yes.

<Company> - <onboarding | support | delivery review | monthly check-in>

Automated booking tools generate their own title, commonly <Name> <> Symphony Core. Leave it. Recolor if the tool's color contradicts the category, which for client calls it usually does.

Description: standard block. Prep should name the open items from last time, since the value of a standing call is continuity.

Network​

Color: Banana (yellow, id 5). Tier 2.

<Chapter, lodge, or event name> - <visitor | member | guest> - starts <h:mm am/pm ET>
What: <what attendance is meant to produce>
Where: <venue name and full address>
Travel: <each way, from where>
Prep: <who to look for, what to bring>
Booked by: <role, date>

These are nearly always physical and early, so the block runs from leaving to being back and the title carries the real start. Say visitor or member plainly, because the two grant different rights in the room and that changes what the hour is worth.

Internal​

Color: Peacock (blue, id 7). Tier 3, the scheduler's call.

<Team, vendor, or system> - <what is being decided or done>

Description: standard block, usually just What and Prep.

This is the first place the bump rule takes from. Keep it honestly classified. Filing an internal item as something weightier removes the slack the whole system depends on.

Tentative block​

Color: Tangerine (orange, id 6) for a client slot, Peacock (blue, id 7) for an internal one. Tier 3. Set to Busy. Always temporary.

Tentative Block for <Client> - Start <h:mm AM/PM>
What: slot offered to <Client>, awaiting reply
Who: <name> / <email>
Offered: <all slots sent, with time zone>
Release: <date the slots are released if no reply>
Booked by: <role, date>

See §11. Every tentative block has a release date, none survives its offer, and the other party is emailed before one they know about is deleted.

Focus​

Color: Basil (green, id 10). Tier 3, with a floor: at most one per week may be taken.

Focus - <the specific piece of work>
What: <the one thing that gets touched>
Prep: <document, file, or link, named>

Name the work. A block called Focus alone is indistinguishable from free time and will be treated as free time. Set the event to Busy.

The weekly no-inputs thinking block is the exception in every respect:

Focus - weekly thinking block - no inputs

Color it Grape (purple, id 3) and treat it as tier 0. No agenda, no email, no calls. It is the one block the bump rule may never touch.

Locked​

Color: Grape (purple, id 3). Tier 0, nobody moves it.

<What it is> - <reference or identifier>
What: <what happens if this is missed>
Where: <full address, terminal, room, or portal>
Travel: <each way, plus the arrival buffer the venue requires>
Ref: <confirmation, docket, or case number>

The What line states the consequence, not the activity. A deadline whose cost is written down does not get quietly rescheduled.

Personal hold​

Color: Graphite (gray, id 8). Tier 0. Created by the principal only.

Personal hold

No detail in the title, none in the description. The scheduler sees an opaque Busy bar and treats it as tier 0 without asking what it is.

Most personal commitments need no hold at all, since the free/busy share surfaces them automatically. This is only for something that has to be visible in the business view.

Travel window​

All-day event, set to Free, no color required.

<Person> in <place>

Free rather than Busy, so the window is visible without consuming bookable time underneath it. This event is also the switch that tells the scheduler which hours profile in §4 is live. The individual commitments inside the trip get their own blocks in the usual way.


Document History​

VersionDateAuthorChanges
1.12026-08-14Symphony Core Systems TeamRenamed the Hold convention to tentative block and adopted the naming already in use on the calendar. Added minimum durations and the 30-minute travel buffer to §11, and the rule that the other party is emailed before a tentative block they know about is deleted. Corrected §13: mailbox delegation exists and is used for triage, so the section now says client mail is still sent from the scheduler's own address rather than that delegation is unnecessary. Added WhatsApp and email to the §14 channel table.
1.02026-08-14Symphony Core Systems TeamInitial version. Adapted from a personal calendar execution guide into a role-shaped SOP. Added the travel hours profile, the Hold convention for offered-but-unconfirmed slots, the one-time access setup as Prerequisites, invite and guest-notification mechanics, an escalation channel and overlap window, the outreach-email section, and a Verification block.