# Construction Operations Report

*Compiled: 2026-02-06 | Sources: work-logs, daily memory, plans, glossary, topic files*

---

## 1. Michael's Day Job Context

### Who He Is
- **Name:** Michael "Rocky" McLoughlin — everyone on site calls him Rocky
- **Trade:** Steelfixer / Formworker — 30 years in construction
- **Background:** Irish, in Sydney ~2 years
- **Employer:** LF Construction Services (Liam's company; Jo handles payroll — accounts@lfcs.com.au / admin@lfcs.com.au)
- **Current Project:** Ford Civil, Parramatta (working at Arncliffe site, Sydney)
- **Crew Partner:** Mike (German lad) — both steel fixers

### Daily Schedule (When On Site)
| Time | Activity |
|------|----------|
| 4:15 AM | Gym (Greyskull / 5-3-1 BBB / SVR II cycles) |
| 5:30 AM | Commute to site |
| ~7:00 AM | Site start |
| 12:00–12:30 PM | Lunch break (reads Telegram, voice notes) |
| ~4:30–5:30 PM | Knock off |
| 6:00–6:30 PM | Commute home (reads longer messages) |
| 6:30–11:00 PM | Coding / prompting / RateRight work |

**Health note (early Feb 2026):** Off sick for part of the period — not on site some days but still actively working on RateRight from home.

### Physical Considerations
- Hip issues from years of steelfixing — prioritises longevity in training
- Uses 0.25 kg microplates for gym progression
- On-site: can't type with gloves, prefers voice input
- Phone usage limited to 2–5 minute windows between tasks

---

## 2. Site Work Log — Current Project

### Project Details
| Field | Value |
|-------|-------|
| Project | Ford Civil, Parramatta |
| Site Location | Arncliffe, Sydney |
| Client/Builder | Ford Civil |
| Employer | LF Construction Services |
| Role | Steel Fixer |
| Crew | Rocky (Michael) + Mike |

### Week 5 (26 Jan – 2 Feb 2026) — 44 hours
| Day | Hours | Work |
|-----|-------|------|
| Mon 26 Jan | 8 | Australia Day (Bank Holiday) |
| Tue 27 Jan | 8 | Day off (hours owed) |
| Wed 28 Jan | 10 | Steel fixing & shuttering (7am–5:30pm) |
| Thu 29 Jan | 10 | Steel fixing & shuttering (7am–5:30pm) |
| Fri 30 Jan | 8 | Day off (hours owed) |

### Week 6 (3 Feb – 9 Feb 2026) — 9 hours logged (partial)
| Day | Hours | Work |
|-----|-------|------|
| Wed 5 Feb | 9 | All cages in. 2 cages to be altered (surveyor wrong marks). Morning delayed — no edge of kerb from groundworks; got going ~8:30am. Engineers gave wrong heights ~10:48am — all morning work redone. |
| Thu 6 Feb | — | Plan: Get material, build 2 shutters, position conduits on last 2, drop 2 links, cut 8 bars. Concrete pour at 11am. |

### Known Site Issues
- Groundworks crew sometimes slow to provide edge of kerb (reference line)
- Engineer has given wrong marks at least twice (heights on 5 Feb; 2 cages)
- New foreman started recently (name unknown)
- Engineer name unknown
- Day work (paid by the day), so rework from wrong marks is less financially painful

### People at Site
| Role | Name | Notes |
|------|------|-------|
| Steel Fixer | Rocky (Michael) | — |
| Steel Fixer | Mike | German, crew partner |
| Foreman | Unknown | New, started recently |
| Engineer | Unknown | Gave wrong heights 5 Feb |

---

## 3. Construction Glossary (Learned from Rocky)

| Term | Meaning | Example |
|------|---------|---------|
| Links | Steel reinforcement links (stirrups/ligatures) | "Drop 2 links" = install link bars |
| Conduits | Electrical conduit pipes embedded in concrete | "Position conduits" = place before pour |
| Cages | Pre-assembled reinforcement steel cages | Lowered into position before pour |
| Shutters | Formwork panels that hold concrete shape | "Build 2 shutters" = assemble formwork |
| Aids | Foundation elements / pile caps | Aids = pile cap reinforcement |
| Pour | Concrete placement | "Concrete at 11" = pour at 11am |
| White Card | Mandatory safety induction card (all AU site workers) | — |
| Edge of kerb | Reference line/level from groundworks crew | — |
| EDM | Electronic Distance Measurement (surveying) | — |
| Pedestals | Concrete columns with holding down bolts | "Struck 3 pedestals" |
| Day work | Paid by the day (not piece rate) | — |

---

## 4. Site Logging System — Notion Job Page Concept

### Status: **IDEA STAGE** — documented, not built

### Core Vision
Michael wants a **lean construction project management system** for personal use:
- Every job gets its own page in Notion
- Daily logs written throughout the day
- Photos uploaded to each job page
- Daily reports posted to Lean (construction management tool) + company work groups
- Build a personal knowledge base spanning his entire construction career

### Planned Notion Structure

**Database 1: Sites** (one entry per job site)
- Site Name, Client/Builder, Address, Status (Active/Complete/On Hold)
- Start Date, End Date, Foreman, Engineer, Site Contact
- Notes (rich text), Cover Photo

**Database 2: Daily Logs** (one entry per day worked, linked to Sites)
- Date, Site (relation), Crew (multi-select)
- Start Time, Finish Time, Break, Hours
- Work Description, Day Works Y/N, Issues, Tomorrow's Plan
- Photos

**Database 3: Contacts** (people at each site, linked to Sites)
- Name, Role (Foreman/Engineer/Supervisor/Labourer/Subbie/Client)
- Company, Phone, Site (relation), Notes

### Planned Views
- **Sites:** Gallery view (cover photos + status), Active sites filter
- **Daily Logs:** Calendar view, table filtered by site, "this week" view
- **Contacts:** Table grouped by site or role

### Open Questions (For Michael)
1. What info goes in daily logs? (hours, tasks, issues, weather?)
2. Photo organisation — tagged by trade/phase?
3. Report format — template or freeform?
4. Integration with RateRight? (workers on jobs, crew tracking)
5. Mobile-first? (needs to work on site with gloves)

### Technical Considerations
- Notion as backend (already using it for RateRight ideas)
- Could add Telegram bot for quick logging from site
- Voice input would be huge (can't type with gloves)
- Photo upload from phone camera → auto-attach to today's log
- WhatsApp integration discussed — post site reports directly to work groups (eSIM idea, not actioned)
- **Blocked on:** Notion API key / workspace access sharing

### Current Interim System
- Work logs stored in git: `memory/work-log/2026-W05.md`, `2026-W06.md`
- Site notes in: `memory/work-log/sites/arncliffe-ford-civil.md`
- Timesheet template: Excel (LF Construction Services format)
- Timesheet cron: Monday 7am compile, Wednesday 7am reminder

---

## 5. Lean Methodology Notes

### What We Know So Far
Michael has referenced **lean construction methodology** in the context of his personal logging system:
- "Lean construction methodology — minimal waste, continuous improvement"
- Daily reports to be posted to "Lean" (a construction management platform/tool)
- Purpose: capture learnings, reduce repeat mistakes, build institutional knowledge

### Lean Principles Applied to His Work
Based on site observations and logged issues:

1. **Waste Identification (Muda)**
   - Engineer wrong marks → rework waste (5 Feb: entire morning redone)
   - Groundworks delays → waiting waste (no edge of kerb, 30+ min delayed start)
   - Surveyor errors → defect waste (2 cages need altering)

2. **Continuous Improvement**
   - Logging issues systematically (wrong marks tracked twice)
   - Tomorrow's plan written at end of each day
   - Glossary maintained to standardise terminology

3. **Knowledge Capture**
   - Career-spanning knowledge base vision
   - Photo documentation per job
   - Contact networks maintained per site

### Lean Construction — Industry Context
- Lean construction adapts Toyota Production System principles to building sites
- Focus on flow (materials, information, work), pull scheduling, and reducing variability
- Michael's daily log system aligns with "Last Planner System" concepts (tomorrow's plan, issue tracking, constraint identification)
- The logging of engineer errors and groundworks delays is classic constraint analysis

### Status
- **Not formally implemented** — lean methodology is an aspiration for the logging system
- The daily note-taking and issue-tracking habits are already lean-adjacent
- Full lean implementation would come with the Notion system build

---

## 6. Construction UX Research (RateRight Platform)

### Key Findings for Construction Marketplace Design
Research completed across Hipages, Airtasker, ServiceSeeking, and international comparisons:

**Glove-First Design (Non-Negotiable)**
- 48px minimum touch targets (64px optimal)
- High contrast ratios (7:1 minimum for text)
- Bottom-tab navigation in thumb-friendly zones
- Voice input for hands-free operation
- Offline capability for remote sites

**Speed Over Features**
- Each additional tap reduces conversion 15–20%
- Core flows: 3 steps maximum
- App load under 3 seconds on 3G
- Smart defaults from user history increase conversion 34%

**Trust Signals for Construction**
- License number display with verification badge
- Insurance verification
- ABN validation (modulus-89 checksum, ABR API integration)
- Binary ratings (thumbs up/down) outperform star ratings
- Photo evidence in reviews

**Competitor Landscape**
- No dominant player in AU construction labour marketplace
- ServiceSeeking: most quotes, no commission
- Hipages: good verification, complicated UX
- Airtasker: fast but perceived low quality for skilled trades
- Workmate: pivoted away from construction (no longer a threat)
- **Nobody does flat-fee crew hire** — RateRight's differentiator

### Crew Hire Market Opportunity
- $3.8B addressable market in Australia
- 96.7% cost reduction vs traditional labour hire ($100 flat fee vs $3,040/day agency costs for a 6-person crew)
- No competitor currently offers flat-fee crew hire
- Legal considerations: workers comp mandatory, labour hire licensing required in QLD/VIC/ACT
- 300,000 worker shortfall projected by 2027

---

## 7. Connections: Day Job ↔ RateRight

Michael's 30 years of construction experience directly feeds the RateRight product:

| Day Job Reality | RateRight Feature |
|----------------|-------------------|
| Can't type with gloves | Voice-first job posting, voice signup |
| 2–5 min app windows between tasks | One-tap flows, minimal screens |
| Outdoor screen glare | High contrast, large fonts |
| Engineer wrong marks = rework | Issue logging in Notion system |
| Knows crew dynamics | Crew hire feature (biggest differentiator) |
| Steelfixer crew compositions | Realistic crew templates (formwork crew, concrete crew, etc.) |
| Paid by the day / piece rate | Understanding of worker pay models |
| White Card mandatory | Verification feature design |
| Works with Irish/British backpackers | Worker target market insight |
| Knows foreman, engineer, subbie roles | Contact/role taxonomies |

---

## 8. Pending / Blocked Items

| Item | Status | Blocked On |
|------|--------|-----------|
| Notion site logbook build | Idea stage | Michael's availability + Notion API key |
| WhatsApp work group posting | Discussed, not actioned | eSIM purchase |
| Lean methodology deep-dive | Not started | Michael to clarify which "Lean" tool he uses |
| ABR API registration | Form submitted | ~1 day approval wait |
| Work journal auto-sync to Notion | Planned | Notion API key sharing |
| Timesheet auto-generation | Cron set up | Template confirmed working |

---

*This report consolidates all construction-related context from Michael's work logs, daily notes, system plans, and research files. Update as new site work is logged or the Notion system gets built.*