Site Mobilization: Don't Build the Whole Mega-Project in Week 2
"Good morning—and good afternoon to our colleagues joining from Australia! Welcome Cohort 2 across Australia, Vietnam, Malaysia, Taiwan, and the UK to Bi-Weekly Sync #1!
Over the past two weeks since our Core Workshop on 6 October—whether you're delivering rail & civil works in Australia, developing Gamuda Land townships in Vietnam, or supporting engineering, QS, safety, or corporate teams in Malaysia—many of you jumped into Antigravity and tried to automate your entire department SOP in one giant prompt, and watched the app stall halfway.
Across Gamuda, we never pour the entire bridge deck or metro station roof on Day 1. We drive 1 Test Pile first. Today is Site Mobilization & Setting Out: slicing your project down from a 12-module dream ERP to 1 high-value job that works cleanly end-to-end."
"1 Working Test Pile > 10 Half-Dug Trenches." Whether in Sydney, Ho Chi Minh City, or KL—prove 1 single form, claim row, or safety check first before adding 10 tabs.
"Type in the Google Meet chat: Where are you dialing in from (AU / VN / MY), and what is the ONE document, form, or check you are slicing down to for Week 2?"
"Once we pick that 1 pain point, how do we map it out before touching code? Let's look at the Surveyor's 3-Peg Blueprint on Slide 2."
The 3-Peg Setting-Out Blueprint
"Before any excavator digs a single bucket of earth on a site in Sydney, Ho Chi Minh City, or Kuala Lumpur, our surveyor hammers 3 boundary pegs into the ground. Every reliable Gamuda DevForge app follows this exact 3-Peg Setting-Out Blueprint:
• Peg #1 (Raw Input): What is the 1 thing the user drops in? (e.g., 1 progress claim CSV row, 1 Gamuda Land unit handover form, 1 WHS/EHS safety photo, or 1 vendor invoice/CV).
• Peg #2 (AI Worker & Rule Check): What are the 3 to 5 specific rules the AI checks?
• Peg #3 (Verified Output): What decision table or action card comes out?
Golden Rule: If you cannot write your 3 Pegs in 1 sentence each on a napkin, do not prompt Antigravity to write code yet!"
Peg 1: Subcon Claim / Site Diary CSV → Peg 2: Check contract schedule rate (AUD/MYR) & missing docket ref → Peg 3: 5-column Variance Hold Table.
Peg 1: Unit defect note or site hazard photo → Peg 2: Check quality warranty or WHS/HSE safety clause → Peg 3: Rectification Action Card.
Peg 1: Vendor invoice, travel receipt, or CV → Peg 2: Verify policy cap & mandatory criteria → Peg 3: Pass / Flag Scorecard.
From 'Wish-List Prompt' to a 3-Part Site SOP
"Whether you're in Sydney, HCMC, or KL, why does a prompt like 'Please check this document and tell me if it's okay' give you a generic essay every single time? Because that's a wish-list, not a Standard Operating Procedure!
On Slide 3, we upgrade Peg #2 using the 3-Part Site SOP Prompt:
1️⃣ [ROLE — WHO]: Appoint a specific Gamuda specialist (e.g., 'You are a Senior Gamuda Commercial / WHS / Property / Finance Specialist').
2️⃣ [NUMBERED RULES — HOW]: Give 3 to 5 strict pass/hold inspection rules.
3️⃣ [HANDOVER FORM — OUTPUT]: Specify the exact table columns (whether in AUD, VND, or MYR) and instruct the AI: 'If any field is missing, write [MISSING DATA]—never guess!'"
[ROLE] You are a Senior Gamuda Project Commercial & Compliance Auditor (supporting AU, Vietnam & Malaysia operations). [INSPECTION RULES] 1. Verify Reference / PO number matches standard project format (e.g., "GAM-AU-", "GL-VN-", or "GAM-MY-"). 2. Flag any claimed line item where Claimed Qty > Verified Site Qty or variance exceeds 5% of the schedule rate. 3. Flag any item missing a valid Delivery Docket / Handover Reference. 4. If any field or currency (AUD / VND / MYR) is missing or unclear, output "[MISSING DATA]" — never invent figures. [HANDOVER TABLE] Return ONLY a Markdown table with columns: | Item | Claimed (AUD/VND/MYR) | Verified | Status (PASS / HOLD) | Action Required |
One Trade Per Worker: When to Split Steps
"A common question we get is: 'Eddie, do I need 1 prompt or 2 prompts?'
Here is the rule of thumb: 80% of your Week 2 prototypes only need 1 single step! If the input is already a clean form or short text, 1 well-written Site SOP prompt handles it easily.
Only split into Worker A (Extractor) → Worker B (Inspector) if you are dealing with messy, unstructured multi-page text AND complex math/compliance rules at the same time—just like we don't ask the crane operator to weld rebar while lifting a precast beam."
The Front-Gate Guardhouse (Stopping 'Garbage-In')
"Every Gamuda project site has a Security Guardhouse at the front gate. If a lorry arrives without a Delivery Order, the guard stops it before it enters the site.
Build these 3 Guardhouse habits into your prototype today:
1️⃣ Front-Gate Input Check: Block empty clicks! Check that required fields are filled before calling the AI.
2️⃣ No Guessing Allowed: Tell your AI to output [MISSING DATA] instead of hallucinating numbers.
3️⃣ Add a 'Load Sample Data' Button: Put a 1-click button that pre-fills a realistic Gamuda test case so you and your colleagues can test your app in 2 seconds!"
Live Blueprint Clinic & Action Item Before Sync #2 (Wed, 4 Nov)
"Let's spend our final 12 minutes doing a live Blueprint Clinic! Who in Cohort 2 wants to unmute or drop their idea in the chat so we can map your Peg 1 → Peg 2 → Peg 3 together right now?
And before our Cohort 2 Sync-Up #2 on Wednesday, 4 November 2026 (09:00 – 10:00 MYT)—where we appoint the AI Foreman and modularize your UI like IBS Prefab Pods—complete your 5-point Mobilization Checklist and drop a screenshot of 1 working input-to-output run in our Cohort 2 Google Chat space!"