Weekly Preview & Calendar Audit
Weekly planning template conducting proactive calendar audits, time-defenses, and strategic sprint commitments in Markdown.
Template Overview
Preventing reactive weeks requires proactive Sunday or Monday morning calendar audits. The Weekly Preview & Calendar Audit template structures weekly high-impact commitments, ruthless meeting pruning, scheduled focus blocks, and personal replenishment rituals in sovereign Markdown.
Markdown Template Structure
Copy the block below or click Download .md File to add this template directly to your personal vault:
---
title: "Weekly Preview: [YYYY-WXX / Week Commencing Date]"
date: [YYYY-MM-DD]
week_number: "Week [XX]"
primary_weekly_theme: "Product Architecture Milestone Delivery"
planned_deep_work_hours: 18.0
tags: [daily-notes, weekly-review, calendar-audit, planning, productivity]
---
# Weekly Preview & Calendar Audit — Week [XX]
## 1. The Big 3 Outcomes for This Week
1. **[[Outcome 1]]:** Complete and merge the Core ML INT8 quantization PR.
2. **[[Outcome 2]]:** Deliver final architecture presentation to the Executive Board.
3. **[[Outcome 3]]:** Conduct quarterly career growth check-ins with 4 Staff engineers.
## 2. Ruthless Calendar Audit & Defense
- **Audit Total Meeting Load:** [Current: 14.5 hours | Target: ≤ 12.0 hours]
- **Meetings Pruned / Cancelled / Converted to Async:**
- Cancelled Tuesday operational sync (Converted to async Slack thread).
- Shortened Thursday design review from 60 minutes to 30 minutes.
- **Deep Work Focus Blocks Defended:**
- *Monday Morning:* 09:00 - 12:00 (Compiler benchmark coding).
- *Wednesday Morning:* 08:30 - 11:30 (Board deck authoring).
- *Friday Morning:* 09:00 - 12:00 (Architecture RFC writing).
## 3. High-Priority Stakeholder Alignments
| Stakeholder | Key Objective for This Week | Scheduled Interaction | Desired Outcome |
|---|---|---|---|
| [[CEO Robert Sterling]] | Review Q4 engineering capital budget | 1-on-1 Wednesday | Budget approved |
| [[Dr. Elena Rostova]] | Finalize ANE Core ML kernel specifications | Pairing Thursday | Spec signed off |
| [[Marcus Vance]] | Coordinate infrastructure runner procurement | Async check-in | PO submitted |
## 4. Personal Resilience & Recovery Safeguards
- **Daily Physical Movement:** 4 workouts scheduled and blocked on calendar.
- **Digital Shutdown Target:** Computer closed by 18:30 each evening.
- [ ] Weekly preview complete; Daily notes scaffolded for Monday through Friday.
Filled Real-World Example
Here is a realistic example demonstrating how this template captures actual deliberations:
---
title: "Weekly Preview: Week 41 (Oct 12 - Oct 16, 2026)"
date: 2026-10-10
week_number: "Week 41"
primary_weekly_theme: "Benchmark Asset Launch & Blog Release"
planned_deep_work_hours: 19.5
tags: [daily-notes, weekly-review, calendar-audit, planning, productivity]
---
# Weekly Preview & Calendar Audit — Week 41
## 1. Big 3 Objectives
1. Ship Blog Wave 4 technical articles.
2. Verify all 24 SEO gates pass with zero regressions.
3. Deploy updated browser tools to Cloudflare Workers.
## 2. Calendar Pruning
Declined 3 recurring status updates, saving 3.5 hours for focus blocks.
## 3. Weekly Readiness
All daily note scaffolds generated. Ready for execution Monday morning.
When to Use and When to Avoid
When to Use
- Use on Friday afternoons or Sunday/Monday mornings to plan the upcoming work week.
- Use to audit your calendar, decline unnecessary meetings, and defend deep work blocks.
- Use to select your top 3 high-impact outcomes for the week.
When to Avoid
- Avoid for end-of-day daily reflections (use the Evening Reflection template).
- Avoid for multi-year corporate strategy plans.
On-Device AI Integration
Summarize your recording in Oyma with this local instruction:
Summarize the weekly planning voice recording:
1. Extract the Top 3 Big Outcomes planned for the upcoming week.
2. Outline calendar audit decisions, pruned meetings, and defended deep work blocks.
3. List key stakeholder alignments and personal health/resilience commitments.
Output in clean, structured Markdown.
Your data remains securely on your Mac with zero cloud exposure.
Frequently Asked Questions
What is the purpose of a Weekly Preview & Calendar Audit?
To review the upcoming week's calendar before it begins, eliminating low-value meetings, protecting deep work blocks, and aligning time with high-impact goals.
How does Markdown support weekly planning?
Markdown links your weekly goals via wikilinks to project PRDs, meeting agendas, and daily notes, maintaining complete continuity across your vault.
How does Oyma assist weekly planning reviews?
Oyma transcribes spoken weekly planning reflections on-device, organizing your spoken goals into structured Markdown agendas.
Write weekly preview & calendar audit in plain Markdown.
Store notes in your local vault, transcribe meetings on-device, and retain 100% data sovereignty.