Work out what happened with last night’s shed alarm
After a night alarm, nobody’s sure who went, when they got there, or how long the shed ran hot. That’s what the vet, the processor and the insurer will ask, and it’s also how you find out the call-out didn’t work.
The Shed climate watcher rebuilds the alarm timeline from the readings, the texts sent and who replied, works out how long the shed was out of range and logs the incident.
- When · On demand
- “Shed 2 alarm went off overnight. Did anyone go?”
- You get
- Timeline from alarm to reset; how long the shed was out of range and how far; who was texted and who answered; incident logged and a gap in the call-out flagged
- Approval level
- Act and tell. Does it and logs it. You hear about it after. You can change it.
What it reads
- Shed temperature and ventilation readings overnight
- Alarm texts sent and replies received
- Mortality logged that morning
- On-call roster
What you get
- A timeline: alarm, texts, first reply, arrival, reset
- Minutes out of range and the peak reading
- An incident note filed on the shed record
- A flag if the on-call person didn’t get or answer the text
When it stops and asks you
- There’s a gap in the readings and it can’t say what the shed did
- Someone went but didn’t reply to the text
- Mortality is up and the cause needs the vet
How often
After any night alarm
Who uses it
OwnersManagersFarm staff
What it uses
SMS and voice notes
Text the team, send a voice note or a photo, or forward a message. There’s no new app to learn.
Nothing official leaves the farm without your yes.This job runs at Act and tell: does it and logs it. You hear about it after. You can change that any time.
The conversation
How the job plays out, step by step.
Shed climate watcher
Started 7:12am · On demand
- Start to done
- 6 min
- Agent actions
- 6
- Needed you
- 3×
[AGENT NAME]For the Shed climate watcherShed 2 alarm went off overnight. Did anyone go?
You · 7:12am

Shed climate watcher
Pulled the overnight readings and the alarm messages

Alarm at 2:14am, high temp. [on-call] got two texts and didn’t reply. [manager] answered at 2:31 and the shed was back in range by 2:58. It peaked at 31.5°C, out of range for 44 minutes. Fan bank 2 dropped out at 2:12.
[AGENT NAME] · 7:12am
[on-call]’s phone was on silent. 60 dead this morning in that end.
You · 7:14am

Shed climate watcher
Logged the incident and the mortality against Shed 2 and flagged the call-out gap

Logged. I’ve made a job to get fan bank 2 checked. The alarm could go straight to [manager] if the on-call doesn’t answer in 10 minutes. Worth setting on every shed?
[AGENT NAME] · 7:15am
Yes, I’ll set that on every shed.
You · 7:17am
Done · 7:17am4 saved
- A timeline: alarm, texts, first reply, arrival, resetSaved
- Minutes out of range and the peak readingSaved
- An incident note filed on the shed recordSaved
- A flag if the on-call person didn’t get or answer the textSaved
Behind the scenes
7:12am
You ask
“Shed 2 alarm went off overnight. Did anyone go?”
7:12am+13 sec
Shed climate watcher works on it · 3 steps
Pulled the overnight readings and the alarm messages
climate.readShed 2 high temp alarm 2:14am, 31.5°C at peak 2:40am- Text to [on-call] 2:14am, no reply; second text 2:24am; [manager] replied 2:31am
- Back under 28°C at 2:58am
7:12am+2 sec
[AGENT NAME] messages you
“Alarm at 2:14am, high temp. [on-call] got two texts and didn’t reply. [manager] answered at 2:31 and the shed was back in range by 2:58. It peaked at 31.5°C, out of range for 44 minutes. Fan bank 2 dropped out at 2:12.”
7:14am+3 min
You reply
“[on-call]’s phone was on silent. 60 dead this morning in that end.”
7:14am+13 sec
Shed climate watcher works on it · 3 steps
Logged the incident and the mortality against Shed 2 and flagged the call-out gap
records.log_readingincident, 44 min out of range, 60 mortalitiesjobs.createelectrician to check fan bank 2memory.remembersuggest [manager] next if no reply in 10 min
7:15am+2 sec
[AGENT NAME] messages you
“Logged. I’ve made a job to get fan bank 2 checked. The alarm could go straight to [manager] if the on-call doesn’t answer in 10 minutes. Worth setting on every shed?”
7:17am+3 min
You reply
“Yes, I’ll set that on every shed.”
7:17am+3 sec
Shed climate watcher Done
Incident report on Shed 2 with timeline and mortality; fan bank 2 job created; you’re setting the 10-minute escalation to [manager] on every shed
memory.rememberescalation rule, all sheds
An example with made-up data. Names and figures in [brackets] are placeholders.
The agent behind it
Shed climate watcherPigs & poultryThe Shed climate watcher keeps an eye on shed temperature, ventilation and alarms.
What it won’t do
- Change the controller settings
- Ignore an alarm because it’s the middle of the night
- Make up a reading
More jobs the Shed climate watcher does.
- Act early on a hot shedDaily
- Check the generator test got doneScheduled
- Flag ammonia climbing in a shed late in the batchDaily
- Check the creep heat before a cold night in farrowingDaily
- Run the pre-summer fan, pad and alarm test on every shedScheduled
- Work out if a quiet tank sensor means no water in the shedDaily
Put [AGENT NAME] to work on your farm.
We’re taking a small number of pilot farms in Australia. Start with one or two agents and add more as you go.
See it on a farm like yours.
30 minutes with Thomas, our founder, on records like your own.
Livestock, paddocks, visitors and tanks, in one place.
The farm management software comes with every plan. Keep the software you already use, or use ours.
Not ready yet? Start with a free calculator.
The sums you do every week, for stock, pasture, crops and the books. No sign-up.
Watch a job before you commit.
Pick a playbook and see it play out, step by step.

