---
name: lfcs
description: LF Construction Services site operations — job tracking, correspondence, inspections, RFIs, dockets, EOD summaries, and pre-pour checks. All skills share the same job folder structure under lfcs.jobs_root.
version: 1.0.0
category: lfcs
tags: [lfcs, construction, site-operations, job-tracking, admin]
metadata:
  hermes:
    requires_toolsets: [terminal]
    config:
      - key: lfcs.jobs_root
        description: Root directory holding active LFCS job folders.
        default: "/home/ccuser/opsman-work/Jobs/Ongoing Jobs"
---

# LF Construction Services — Site Operations

All LFCS skills share the same job folder conventions. Every path below is relative to `<job>` = `<lfcs.jobs_root>/<Job>/`.

## Standard Job Folder Structure

```
<job>/
  00-brief.md                          ← contract price, type, start_date, target_completion
  _strategy.md                         ← profit-lever flags (optional)
  Job-Tracker.md                       ← hours table, materials table, costs-to-date
  04 - Programme and Scheduling/
    programme-24wk.md                  ← 24-week programme, current week number
  06 - Correspondence/
    06a - Emails/                      ← drafted emails (EML-YYYY-MM-DD-description.md)
    06b - RFIs/_REGISTER.md            ← RFI register (RFI-A1, VO-001 numbering)
  07 - Site Documents/
    07a - Dockets/                     ← signed dockets (YYYY-MM-DD-signed.*)
    07b - Photos/
    07c - Inspection Records/
      _inspection-log.md              ← inspection register
    07d - Daily Diary/                  ← daily diary entries (YYYY-MM-DD.md)
  08 - Variations/_REGISTER.md         ← variation register
```

## Standard Job Fields (00-brief.md)

| Field | Values | Notes |
|-------|--------|-------|
| `type:` | `price`, `dayworks`, `hybrid` | Determines docket/photo requirements |
| `contract_price:` | dollars | Used for budget variance in job-tracker |
| `start_date:` | YYYY-MM-DD | Jobs in Upcoming/ with start_date within ±7 days are active |
| `target_completion:` | date | |

## Skill Map

| Skill | When to use | Key file |
|-------|-------------|---------|
| `lfcs-job-tracker` | "where's [job] at", "am I over budget" | Job-Tracker.md |
| `lfcs-eod-summary` | "EOD summary", "wrap up", 17:00 cron | Daily Diary + Job-Tracker |
| `lfcs-docket-check` | "docket check", EOD cron auto-check | 07a - Dockets/ |
| `lfcs-pre-pour-check` | "pre-pour check", "ready to pour" | 07c - Inspection Records/ |
| `lfcs-rfi-status` | "RFI status", "open RFIs", "what to chase" | 06b - RFIs/_REGISTER.md |
| `lfcs-client-correspondence` | Formal emails, letters, RFIs, variations | 06 - Correspondence/ |
| `lfcs-tool-tracker` | Tool/vehicle register, WhatsApp check-in/out | Google Sheets + Transfer Log |
| `timesheet` | "do my timesheet", weekly payroll submission | Job-Tracker.md hours table |

## Active Job Identification

Check BOTH `<lfcs.jobs_root>/Ongoing Jobs/` AND `<lfcs.jobs_root>/Upcoming/`.
- A job in `Upcoming/` that has started site work is still active — do not skip it.
- Jobs with `start_date` within ±7 days of today are active.
- If there are multiple active jobs, handle each separately.

## Naming Conventions

- RFI numbering: `RFI-A1`, `RFI-A3`, etc. (Cat A = mobilisation blockers, Cat B = scope, Cat C = commercial)
- Variation numbering: `VO-001` upwards
- Email drafts: `EML-YYYY-MM-DD-short-description.md`
- Diary entries: `YYYY-MM-DD.md`
- Docket files: `YYYY-MM-DD-signed.*` (strict pattern — no false positives)

## Shared Pitfalls

1. Job-Tracker.md tables sometimes use `$` and `,` — strip both before parsing numbers.
2. For `dayworks`/`hybrid` jobs: dockets required. For `price` jobs: no docket needed.
3. Use Australia/Sydney timezone for all date comparisons.
4. If a field can't be parsed, show raw cell with `(see file)` rather than guessing.
5. Never auto-send client correspondence without Hasibul review for external emails.

## Subsection Index

- [Docket Check](./references/docket-check.md) — signed docket verification, at-risk revenue flags
- [EOD Summary](./references/eod-summary.md) — end-of-day report procedure and format
- [Job Tracker](./references/job-tracker.md) — mid-day status, budget variance
- [Pre-Pour Checklist](./references/pre-pour-check.md) — 8-item concrete pour walkthrough
- [RFI Status](./references/rfi-status.md) — open RFI register, priority sorting, chase actions
- [Client Correspondence](./references/client-correspondence.md) — email/letter drafting templates, tone rules, filing
- [Tool & Equipment Tracker](./references/tool-tracker.md) — system design, WhatsApp workflow, Google Sheets schema
- [Weekly Timesheet](./references/timesheet.md) — hours compilation and submission workflow