Get Your Team to Align Tasks with Shared Calendar Blocks
Move from individual calendar planning to team-wide time allocation that actually sticks
Your team agrees calendar blocking sounds smart but everyone implements it differently. Meetings still land on supposed focus time because there is no shared system for protecting work blocks.
That is the gap this drop closes. It is a operations skill built for Gemini, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Team leads managing 3-12 people who need coordinated work blocks
How it works
The skill file does five things, in this order.
1. Map your team's standard week template together. Ask Gemini to analyse your team's typical recurring commitments and propose colour-coded block categories everyone will use.
2. Create protection rules for different block types. Have Gemini draft specific guidelines for when each block type can be moved or interrupted and by whom.
3. Build a team onboarding checklist for the system. Get Gemini to produce a step-by-step setup guide new team members follow to configure their calendar the same way.
4. Set up weekly sync prompts to spot conflicts early. Use Gemini to generate a standard pre-week review that flags when team blocks clash with planned meetings or deadlines.
5. Document what to do when the system breaks. Have Gemini write recovery protocols for common failures like emergency meetings or schedule overruns that affect multiple people.
What comes back
A documented calendar system your whole team operates the same way with clear escalation paths when blocks need changing
The mistake to avoid
Run a pilot with two team members for two weeks before rolling out widely. Their friction points will reveal which rules need adjusting before you train everyone else.
Running it
Save the prompt as a Gem so it is reusable, or paste it into Gemini with your files attached. If the task touches Sheets, Docs or Gmail, run it from the Workspace side panel so it can read the file you already have open.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are helping a team leader implement shared calendar blocking across their team.
Team size: {number_of_people}
Main work types the team does: {work_types}
Current recurring meetings or commitments: {recurring_commitments}
Typical urgent interruptions: {common_interruptions}
Task 1: Propose 4-6 standard block categories this team should use, with a colour and clear definition for each. Make them specific to the work types listed.
Task 2: Draft protection rules for each block type. Specify which roles can reschedule each type, how much notice is needed, and what counts as a valid reason.
Task 3: Create a 10-step onboarding checklist for new team members to set up their calendar using this system. Include technical steps and conceptual understanding.
Task 4: Design a weekly 15-minute team sync agenda focused only on identifying calendar conflicts for the coming week. Keep it concrete and fast.
Task 5: Write protocols for three common failure scenarios: {failure_scenario_1}, {failure_scenario_2}, and an emergency that requires immediate schedule changes for multiple people. Each protocol should have clear decision points and communication steps.
Task 6: Suggest three leading indicators the team lead should track monthly to know if adoption is actually working or just performing compliance.
Format as a implementation guide the team lead can share in a team channel.