Allotment Admiral

Reads

my texted readings, GP's target range

Runs on

Claude, run by a scheduler

Ask first
- What limit did the doctor give? (default 140/90)
- Who else should know about a high week? (default nobody)

Needs
- A way for the person to send readings (a text or note in any format).
- A sheet with date, time, top and bottom numbers and pulse.

Build
1. Each evening read any new readings and write them to the sheet with the time.
2. Work out the 7-day average.
3. If it is above the limit and no warning was sent in the last 7 days, text the person with the average and any pattern by time of day.
4. Never give medical advice beyond pointing to the next appointment.

Check
- Enter a week of test readings above the limit: one text arrives, not two.

Reads

my voice notes, events calendar, plot reports from members

Runs on

Claude, run by a scheduler

Ask first
- How long should it be? (default 6 short items)
- Anything always included? (default dates for the next fortnight)

Needs
- The person's notes for the week in any form, and the group's events calendar.

Build
1. Thursday 4pm read the week's notes and the next two weeks of events.
2. Ask the model to write 6 short items in the person's plain voice, dates first.
3. Save as a draft to the mailing list. The person sends.

Check
- Add one test event: it appears with the correct date.

Reads

work-day sign-in sheets, plot inspection notes, member list with ages and contact detail

Done when

Closes when the member replies or is seen again; no reply in 2 weeks goes on my call list.

Runs on

Claude, run by a scheduler

Ask first
- How long away counts as quiet? (default 6 weeks)
- Who should get a phone call rather than a message? (default members over 80 or without email)

Needs
- Sign-in sheets or attendance lists. Paper sheets are often the only record; a photo of each week's sheet works if someone takes it.
- Plot inspection notes, which show an untended plot even when nobody signs in.

Build
1. Read: Sunday 6pm load the last 8 weeks of sign-ins and the latest inspection notes.
2. Decide: a member is quiet if not signed in for 6 weeks and their plot is marked untended or worse. Keep: signed in weekly to August, nothing since, plot overgrown. Drop: away for a fortnight with a neighbour watering.
3. Deliver: email the person the list with a warm two-line draft for each; members who should be phoned go on a call list instead.
4. When a member replies or signs in again, take them off the list. After 2 weeks with no reply, move them to the call list.

Check
- Mark a test member absent for 7 weeks with an untended plot: a draft appears.
- A member away with a note on file is not listed.

Reads

plot inspection notes, waiting list, tenancy rules

Done when

Closes when the new tenant signs; a plot offered and refused goes to the next name.

Runs on

Claude, run by a scheduler

Needs
- Inspection notes with plot number and condition, the waiting list with date joined and size wanted, and the tenancy rules on when a plot can be taken back.

Build
1. On the first Monday read the last two inspections.
2. Keep plots marked untended both times where the rules' notice letters have gone out.
3. Match each to the longest-waiting person who wants that size.
4. Email the committee the list with an offer letter drafted for each. Nothing goes to applicants until the committee replies agreed.
5. When an offer is refused, draft for the next name.

Check
- A test plot untended twice with letters sent is matched to the top of the list.

Reads

medication list with doses, last pharmacy collection dates

Runs on

Claude, run by a scheduler

Needs
- A list of medicines with daily dose, pack size and last collection date. Ask the person to reply with the date each time they collect.

Build
1. Sunday 10am work out days left for each medicine.
2. Text the reminder plus any medicine under 10 days.
3. Update the collection date when the person replies collected.

Check
- Set a test medicine to 7 days left: it is in the text.

Reads

weather forecast, route notes

Runs on

Claude, run by a scheduler

Build
1. Monday 7am read the forecast for the week's mornings.
2. Pick the driest calm morning, avoiding any route marked muddy after rain.
3. Text the person with a draft for the group chat. The person posts it.

Check
- The suggested day matches the driest morning in the forecast.

Reads

society bank statement, subs list, receipts folder

Runs on

Claude, run by a scheduler

Needs
- The group's bank statement, the subs list with amounts due, and receipts for spending.
- Payments often arrive with no clear reference; match on amount and surname, and list anything unmatched for the person.

Build
1. On the first of the month read last month's transactions.
2. Match subs payments to members and spending to receipts.
3. Email a summary to the person and the treasurer, with reminder drafts for unpaid members. Never send.

Check
- Remove one test payment: that member appears as unpaid.

Reads

bank statement, expected income list

Runs on

Claude, run by a scheduler

Reads

energy bills, public tariff prices

Runs on

Claude, run by a scheduler

Needs
- The last 12 months of energy bills for usage and current rates, and access to public tariff comparison pages.

Build
1. Each quarter read the latest bill and annual usage.
2. Compare with the three cheapest public tariffs for that usage.
3. If a deal is cheaper by a set amount (default 50 a year), draft an email to the supplier. The person sends.

Check
- The note quotes the current unit rate from the latest bill.

Reads

past applications, society accounts, membership numbers

Runs on

Claude