---
name: site-lookahead
description: AM look-ahead and EOD site summary for LFCS. Reads programme, RFIs, subbie schedule, and job tracker; outputs a tight 4-6 line Telegram summary. Runs as a daily cron job.
category: ops
tags: [lfcs, daily, telegram, opsman]
recurrence: daily cron
---

# Site Look-Ahead Skill

## Trigger
- Scheduled cron job (daily ~6am)
- Rocky asks for "AM look-ahead", "morning summary", or "what's happening today"

## Input files (in order)

Always read from the **Ongoing Jobs** folder first. If files are sparse/empty, check the **Upcoming Jobs** folder — a job that just mobilised often has richer docs there still.

| File | Purpose |
|---|---|
| `00-brief.md` | Job type, client, start date, contract value |
| `04 - Programme and Scheduling/programme-24wk.md` | Today's week, tasks, pour areas |
| `06 - Correspondence/06b - RFIs/_REGISTER.md` | Cat A blockers still Pending |
| `10 - Subcontractors/_subbie-schedule.md` | Subbies booked for today |
| `Job-Tracker.md` | Planned activity, materials, hours |

### Two-folder lookup rule

```
# Find active job — check Ongoing first
ls "/home/ccuser/opsman-work/Jobs/Ongoing Jobs/"

# Programme may live in either Ongoing or Upcoming version
# Check Ongoing first, fall back to Upcoming:
ls "/home/ccuser/opsman-work/Jobs/Ongoing Jobs/<job>/04 - Programme and Scheduling/"
# If programme is empty (0–4 lines), check:
ls "/home/ccuser/opsman-work/Jobs/Upcoming/<job>/04 - Programme and Scheduling/"
```

A job in "Ongoing" may have been recently moved there — the Upcoming folder often has the complete programme, RFI register (with all 33 RFIs), and subbie schedule while the Ongoing copy is still sparse.

## Output: Telegram Summary

**Tight 4–6 line format:**

```
**Today (Wk N, DOW):** [one line — key task]
**Blockers:** [Cat A RFIs still Pending, or "none"]
**RFIs to chase:** [top 2-3 by critical path — include RFI number + one-liner]
**Deliveries:** [confirmed deliveries, steel, materials — or "none booked"]
**[CLAIM prep note if within 2 weeks of due date]**
```

**Rules:**
- Cat A RFIs are mobilisation blockers — always flag if any are still `Pending`
- Chase list: max 3, prioritised by what is blocking today's work
- If nothing notable: one line only
- Never use bullets in the Telegram output itself — plain sentences, short

## LFCS-specific context

- **Active job:** 01-2275 HPE Field of Play Hornsby (Solutions Plus, Joel Alvey)
  - Type: hybrid | Start: 30 Apr 2026 | Duration: 24 wks | Contract: $324,015 ex-GST
  - Programme: 6-day week, pour cycle N/N-1/N/N+1 (see `programme-24wk.md`)
  - LD: $250/day | Claim due dates: 25th each month
  - 33 total RFIs (10 Cat A blockers, rest Cat B/C)
- **Subbie schedule** lives in `10 - Subcontractors/_subbie-schedule.md` (Upcoming folder)
- **Daily diary** path: `07 - Site Documents/07d - Daily Diary/YYYY-MM-DD.md`
- **Job Tracker** lives at job root (not in a subfolder)

## Pitfalls

1. **Ongoing folder is sparse** — if programme is <5 lines in Ongoing, always check Upcoming. Don't assume the move was complete.
2. **Programme table is empty** — flag in summary; job may not have a loaded programme yet.
3. **No RFI responses** — this is the normal state before mobilisation. 10 Cat A RFIs pending is expected. Only escalate if today's planned activity is blocked by a missing answer.
4. **Claim date proximity** — if within 2 weeks of a claim due date, remind Rocky that CC needs to start drafting. Claim dates: 25 May, 25 Jun, 25 Jul, 25 Aug, 25 Sep.

## Logging

After output:
- Append AM look-ahead note to the daily diary at `07 - Site Documents/07d - Daily Diary/YYYY-MM-DD.md`
- Mark as `hermes - AM look-ahead` entry