<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Team Policy on GuardCal</title><link>https://guardcal.com/categories/team-policy/</link><description>Recent content in Team Policy on GuardCal</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 25 Oct 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://guardcal.com/categories/team-policy/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Your Meeting Policy Died in Week Six</title><link>https://guardcal.com/posts/why-meeting-policies-die/</link><pubDate>Sun, 25 Oct 2026 09:00:00 +0200</pubDate><guid>https://guardcal.com/posts/why-meeting-policies-die/</guid><description>Why meeting policies fail is diagnosable from the calendar. The four causes, the tell for each, and whether relaunching is worth it or not.</description></item><item><title>Meeting Budgets: Capping Hours per Team</title><link>https://guardcal.com/posts/meeting-budgets/</link><pubDate>Sat, 24 Oct 2026 09:00:00 +0200</pubDate><guid>https://guardcal.com/posts/meeting-budgets/</guid><description>A meeting budget caps a team&amp;#39;s recurring person-hours, not each person&amp;#39;s diary. How to set the number, who has to enforce it, and what breaks first.</description></item><item><title>Core Hours for a Team Across Four Time Zones</title><link>https://guardcal.com/posts/core-hours-across-time-zones/</link><pubDate>Fri, 23 Oct 2026 09:00:00 +0200</pubDate><guid>https://guardcal.com/posts/core-hours-across-time-zones/</guid><description>A core hours policy across four time zones is mostly arithmetic. Work out the real overlap first, then write the narrow version that survives.</description></item><item><title>Rolling Out a No-Meeting Day Without It Dying</title><link>https://guardcal.com/posts/rolling-out-a-no-meeting-day/</link><pubDate>Sat, 17 Oct 2026 09:00:00 +0200</pubDate><guid>https://guardcal.com/posts/rolling-out-a-no-meeting-day/</guid><description>A no-meeting day dies from exceptions nobody counted. The list you write before launch, the announcement message to send, and the decision you make in week six.</description></item><item><title>No-Meeting Days: What the Evidence Actually Says</title><link>https://guardcal.com/posts/no-meeting-days-evidence/</link><pubDate>Thu, 15 Oct 2026 09:00:00 +0200</pubDate><guid>https://guardcal.com/posts/no-meeting-days-evidence/</guid><description>One real study sits behind the no meeting day, and it is weaker than the figures quoted from it. What it found, what it omits, why Zoom ended its own.</description></item><item><title>A Meeting Policy That Survives Month Three</title><link>https://guardcal.com/posts/meeting-policy-that-survives/</link><pubDate>Tue, 13 Oct 2026 09:00:00 +0200</pubDate><guid>https://guardcal.com/posts/meeting-policy-that-survives/</guid><description>Most meeting norms hold six weeks, then quietly stop being true. The policy document, the rollout sequence, and the four ways it dies.</description></item></channel></rss>