<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Duress blog</title>
    <link>https://www.duress.com/en-au/blog/</link>
    <atom:link href="https://www.duress.com/rss.xml" rel="self" type="application/rss+xml" />
    <description>Data-driven posts on workplace and lone worker safety from the monitoring data behind Duress.</description>
    <language>en-au</language>
    <item>
      <title>One in six: the community worker's 9pm problem</title>
      <link>https://www.duress.com/en-au/blog/community-workers-9pm-problem/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/community-workers-9pm-problem/</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
      <description>Between 9pm and midnight, 16.7% of community-sector duress activations are confirmed emergencies. A year of monitoring data on when outreach and support work actually turns dangerous.</description>
    </item>
    <item>
      <title>Retail's danger clock</title>
      <link>https://www.duress.com/en-au/blog/retail-danger-clock/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/retail-danger-clock/</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
      <description>Retail is the largest source of duress activations in our monitoring data, and its risk has a schedule: evening trade and the hours after midnight confirm as real emergencies at more than double the morning rate.</description>
    </item>
    <item>
      <title>Two kinds of danger</title>
      <link>https://www.duress.com/en-au/blog/two-kinds-of-danger/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/two-kinds-of-danger/</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
      <description>Retail workers press the button; government and community workers set timers. What a year of trigger data says about matching a safety system to the shape of the risk.</description>
    </item>
    <item>
      <title>What seven seconds actually buys</title>
      <link>https://www.duress.com/en-au/blog/what-seven-seconds-buys/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/what-seven-seconds-buys/</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
      <description>A 7-second median operator pickup sounds like a marketing number. Here's what the distribution behind it looks like, and why the tail matters more than the median.</description>
    </item>
    <item>
      <title>How people actually call for help</title>
      <link>https://www.duress.com/en-au/blog/how-people-call-for-help/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/how-people-call-for-help/</guid>
      <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
      <description>Nearly half of duress alarms are a long button press. A tenth are a fall detected. The full breakdown of how 20,433 alarms were raised, and what it means for choosing a device.</description>
    </item>
    <item>
      <title>After hours is when alarms get real</title>
      <link>https://www.duress.com/en-au/blog/after-hours-risk-lone-workers/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/after-hours-risk-lone-workers/</guid>
      <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
      <description>22% of duress activations happen between 6pm and 6am, but 34% of confirmed emergencies do. A year of monitoring-centre data on when lone workers actually need help.</description>
    </item>
    <item>
      <title>1 in 6 alarms was raised by nobody</title>
      <link>https://www.duress.com/en-au/blog/alarms-nobody-pressed/</link>
      <guid isPermaLink="true">https://www.duress.com/en-au/blog/alarms-nobody-pressed/</guid>
      <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
      <description>17.7% of duress activations in FY26 were automatic: fall detection, missed check-ins and expired safety timers firing when the worker couldn't press anything. What that means for how you design a safety system.</description>
    </item>
  </channel>
</rss>
