<?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>Core-Hours on GuardCal</title><link>https://guardcal.com/tags/core-hours/</link><description>Recent content in Core-Hours 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/tags/core-hours/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>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>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>