One system. Every part of the business.

THE GRID — Help & Training Guide

Everything you need to work in The Grid, step by step. If it's not on The Grid, it doesn't exist — and this guide shows you how to put it there. Find your module in the left menu, or search it.

1System
20+Modules
200Of us on it
0Spreadsheets
GO

Getting Started

Signing in, staying secure, and finding your way around. Five minutes here saves a week of asking.
Sign in — step by step
Open https://thegrid.nzWorks on any device — desktop, phone, iPad. Bookmark it. Field techs live at field.thegrid.nz (see Field App).
Sign in with your work email + passwordYour login is your email address. No account yet? Your manager creates one in Staff & Permissions.
First time / after a reset: use the temporary passwordIt arrives by email from The Grid (or your manager reads it to you). It works once — The Grid immediately makes you choose your own.
Choose a strong passwordAt least 10 characters with a letter and a number. A short phrase beats a fancy word: orange fence 42 is stronger than P@ssw0rd!. Your own name, email or "clarksons" won't be accepted.
Set up 2FA if askedSome accounts require two-factor. The Grid walks you through it: install Google or Microsoft Authenticator on your phone → scan the QR → type the 6-digit code → save your backup codes. At sign-in, tick Trust this device 30 days on your own computer so it only asks monthly.
Sign out with the power buttonThe small button next to your name at the top of the sidebar. The Grid also signs you out after 15 idle minutes (60-second warning first); sessions last 12 hours max.
🧭 The sidebarEvery module lives in the dark menu on the left, grouped by area. What you see depends on your role — if a module's missing, you don't have access (ask your manager).
🔐 My Security (2FA)Under Tools & Resources. Set up or manage your authenticator, check backup codes. Lost phone? An admin resets your 2FA in Staff & Permissions and you re-enrol.
💬 Feedback buttonTop of every page. Broken, missing, confusing? 30 seconds, straight to David. Found a gap? That's not a complaint — that's exactly the feedback we need.
📖 This guideHelp Guide button on every topbar. Search the left menu, or Ctrl+F anything.
Golden ruleIf it's not on The Grid, it doesn't exist. Calls, jobs, quotes, hours, stock — log it where it belongs and the whole team can see it. Don't ask — look it up.
⚡

The Big Picture

One flow runs the whole business. Every module is a station on this line — know where your work sits and what happens either side of you.
Customer calls / emailsTriage
→
Quote if neededQuoting
→
Job createdJob Management
→
Scheduled to a techDispatch Board
→
Work done on siteField App
→
Reviewed & completedJob Management
→
Invoice raisedInvoicing
→
Paid & reportedAP/AR · Finance
Everything is linkedA job knows its customer, site, quote, tickets, hours, materials and invoice. Fill things in properly and the links do the work for you.
Stages tell the truthJobs move new → scheduled → in progress → complete → review → invoiced. Reports, the field app and the customer portal all read those stages — keep them honest.
Recurring work feeds itselfPM/Recurring schedules auto-create jobs. Contracts group them. Assets record what was serviced. You maintain the setup; The Grid does the repetition.
TRI

Triage

The front door. Every phone call, email, alarm and customer-portal request lands here as a ticket. Nothing gets forgotten, because nothing lives in someone's head.
Ticket typesPhone · Email · BMS/CTRL Alarm · Portal (customer raised it themselves) · Walk-in.
PrioritiesUrgent/high tickets sort to the top and carry a tighter SLA clock. Alarms show red until acknowledged.
Where tickets goA ticket either becomes a job, becomes a quote, or gets resolved with a note. Closing without one of those means it never needed us — say why.
Take a customer call
Open Triage → + New TicketDo it while they're on the phone, not after — the form is the call script.
Pick the customerStart typing — it searches existing customers. New customer? Create them in CRM first (30 seconds), then the ticket. Never free-type a name that already exists.
Title + what's happeningTitle = what a tech would want to read: "Carwash bay 2 not starting — Z Albany" beats "carwash problem". Add the caller's name and number.
Set priority honestlyUrgent means someone's standing there waiting or something's unsafe/losing money. Everything can't be urgent.
Action it: Create Job or Create QuoteThe ticket links to whatever it becomes — the customer's history builds itself. Portal tickets ("Customer approved quote…") work exactly the same: action them, and the customer sees progress in their portal.
On the toolsAcknowledge alarms before you assign them — an unacknowledged alarm stays red for the whole team and eats the SLA clock. Ack means "a human has seen this".
CRM

CRM — Customers & Sites

Who we work for and where. Every job, quote, invoice, asset and ticket hangs off a customer and a site — so getting these right is the foundation for everything else.
CustomerThe company we bill: "Z Energy Ltd". Holds contacts, terms, and the full history across all their sites.
SiteA physical place work happens: "Z Albany". One customer, many sites. Jobs and assets always belong to a site.
Portal switchesCustomers can be given portal access with per-customer switches (assets, quotes, invoices…). See Customer Portal.
Set up a new customer properly
CRM → + New CustomerSearch first! Duplicates poison reporting and history. If they exist under a slightly different name, use the existing record.
Fill the billing basicsLegal name (what goes on invoices), accounts email, phone, physical address. A customer without an accounts email can't be emailed invoices.
Add their sitesCustomer record → Sites → add each location with its address and site contact. "Head office" is a site too.
Check the history tab as you workEvery ticket, quote, job and invoice for this customer shows in one timeline. Before you call them, read it — walking in knowing their story is the difference.
Watch outOne customer, one record. "CBRE", "CBRE Ltd" and "CBRE Limited" as three records means three part-histories and wrong statements. If you spot a duplicate, tell your manager — don't just pick your favourite.
QTE

Quoting

Price the work before we do it. Quotes carry cost centres and line items (labour, materials, other), roll up to a sell price, and convert to jobs when accepted — carrying everything across.
Build and send a quote
Quoting → + New QuotePick the customer and site (from CRM — see above). Give it a name the customer will recognise.
Add cost centresOne per chunk of work ("Switchboard upgrade", "Carwash repairs"). Small quote = one is fine.
Add line items to eachLabour lines (hours × rate — rates come from Rate Cards), material lines (search the Products catalogue — 50,000+ items with live cost prices), and other/disbursements. Sell price = cost + markup, or set it directly.
Review the totalsThe quote shows cost, sell and margin as you build. Over $10k? Get it approved before it goes out.
Send it — Status: SentEmail it from the quote (Grid-branded email from quotes@). Customers with portal access can view and approve it online — approvals land back in Triage automatically.
Accepted → Convert to JobOne click. Lines, site, customer and pricing carry to the new job. Declined? Mark it declined with a reason — that's sales intelligence, not failure.
On the toolsQuotes someone else is editing show a read-only lock so you can't tread on each other. If a quote looks locked and shouldn't be, the other person probably just left the tab open.
JOB

Job Management

The centre of The Grid. A job is a piece of work at a site — everything else (hours, materials, forms, photos, invoices) attaches to it. Master this module and the rest makes sense.
StageMeansWho moves it
NewCreated, not yet scheduledOffice
ScheduledOn the Dispatch Board with a tech and dateDispatcher
In ProgressTech has started on siteTech (field app)
CompleteWork finished, signed off on siteTech (field app)
ReviewOffice QA — hours, materials and paperwork checkedOffice
InvoicedInvoice raised — job locks (no more edits)Invoicing
Create a job (when there's no quote)
Job Management → + New JobOr straight from a Triage ticket — that keeps the link to the original call.
Customer, site, descriptionDescription is the tech's brief: what's wrong, where exactly, access notes, who to see on site.
Set branch/division and due dateThese drive every report and the dispatch view — don't leave them blank.
Add known materials & estimated hoursFrom the Products catalogue and labour lines. Job costing compares estimate vs actual later — a job with no estimate can't tell you if it made money.
Save → it appears in DispatchThe dispatcher takes it from here. You can watch its whole life from this screen.
Review & complete (office, after the tech finishes)
Open jobs in ReviewThe tech's notes, photos, signature, hours and materials are all on the job.
Check hours and materials are realMissing timesheet lines or van stock not recorded? Fix now — after invoicing the job locks.
Move to Complete → raise the invoiceSee Invoicing. The job stage flips to Invoiced automatically and disappears from the field app.
Golden ruleEverything on the job. Photos, extra work, customer conversations, delays — log them on the job while they're fresh. Six months later, that job record is the only witness.
DSP

Dispatch Board

The week at a glance: every tech, every day, every job. Drag, drop, done — the field app updates instantly.
QueueUnscheduled jobs wait on the left. Drag one onto a tech's day to schedule it.
Late tabJobs past their due date that still aren't done. This should be empty. It won't be — work it daily.
Duration intelligenceThe board suggests how long a job will take from the quote, history on similar jobs, and AI — trust it as a starting point.
Site bundlingMultiple jobs at one site? The board flags them so one visit covers all — travel time is money.
Schedule the day
Start in the queue, priority firstUrgent tickets and overdue PM jobs float up. Clear those before the nice-to-haves.
Drag the job to a tech + dayPick by skills, licence and geography. The tech's day fills visually — overruns cascade so you can see the pile-up before it happens.
Multi-tech jobs: assign a crewBig jobs take multiple techs — the Gantt view shows them side by side.
The tech sees it immediatelyTheir field app schedule updates live. No phone call, no printout.
Rework as the day changesCallouts happen. Drag things later, tomorrow, or to another tech — the app follows.
FLD

Field App (iPad / phone)

The tech's whole day in one app: schedule, jobs, hours, stock, forms and expenses. Works offline — everything queues and syncs when coverage returns.
Set it up once
Safari → field.thegrid.nz → sign inSame email + password as the desktop Grid.
Share button → Add to Home ScreenIt installs like an app — red Grid icon, full screen, offline support. Open it from the icon from now on.
Work a job, start to finish
Check Schedule in the morningToday's jobs in order, with addresses, briefs and site contacts.
Open the job → StartStage flips to In Progress — the office sees you're on site without ringing you.
Log as you goPhotos (before/during/after), notes, materials used from van stock, and your hours. Ten seconds now beats twenty minutes of remembering on Friday.
Extra work found? Say so before doing itAdd it to the job notes and flag the office — that's a variation or a new quote, not free work.
Finish: signature → CompleteCustomer signs on the glass. Job goes to office Review, and drops off your list once invoiced.
OfflineNo signal on site? Keep working — everything you do queues on the device and syncs the moment you're back in coverage. Don't re-enter things twice.
PPM

PM / Recurring Jobs

Planned maintenance that generates itself. Set up the schedule once — The Grid creates the jobs on cadence, forever, until you stop it.
Set up a recurring schedule
PM/Recurring → + New ScheduleCustomer, site, and what the visit involves (this becomes each job's brief).
Set the cadenceMonthly, quarterly, 6-monthly, annual — and the start date. The next-due date shows immediately.
Link assets being servicedTie the schedule to the client assets it maintains — their service history then writes itself (and shows in the customer portal).
Jobs appear automaticallyAs each due date approaches, the job is created and lands in the Dispatch queue like any other. Generate Now forces the next one early if needed.
Watch outDon't manually delete an auto-created PM job because "we did it early" — complete it against the real visit or the schedule's history develops holes and compliance reporting lies.
AST

Client Assets

The equipment we look after at customer sites — switchboards, dispensers, carwash plant, HVAC, fire systems. Each asset carries its identity, condition, test schedule and full service history with dollars.
Asset recordMake/model, serial, install date, expected life, replacement cost, condition grade, critical flag, location at site.
Test/PM plansEach asset can carry scheduled tests ("calibration every 6 months"). Overdue tests glow red — here and in the customer portal.
Service historyEvery visit logged with labour/materials/travel dollars, result (pass/fail) and the tech. This is what customers pay to see.
Register a new asset on site
Client Assets → + New AssetPick customer + site, then describe the unit: name, type, location at site ("Plant room, rear wall").
Capture the plateMake, model, serial, install date. Photograph the nameplate while you're standing in front of it.
Grade it and cost itCondition (Excellent→Very poor), expected life, replacement cost. These feed the customer's capital plan — honest grades make honest forecasts.
Attach its test planWhat needs checking, how often. It'll surface on the compliance dashboards automatically.
Why it mattersCustomers see their own assets in the Customer Portal — compliance rate, overdue tests, capital plan, spend per asset. The register is a product we sell. Treat data quality accordingly.
CTR

Contracts

Standing FM agreements — the customers we serve continuously (CBRE, Foodstuffs-style relationships). A contract groups sites, rates, recurring schedules and every job under one umbrella, so you can see whether the whole relationship makes money.
Working with contracts
Open the contract recordValue, term, sites covered, agreed rates and response times live here — read it before promising a customer anything.
Link work to the contractJobs and quotes for contract customers should carry the contract tag — that's how spend rolls up.
Watch the margin viewEach contract shows revenue vs cost to serve across all its jobs. A busy contract isn't automatically a profitable one.
RenewalsExpiry dates surface ahead of time — renegotiate before it lapses, with the margin history in front of you.
STK

Stock Control

What we hold and where: the head-office procurement store (with bin locations), branch stores, and every van. Four movements explain everything: receive, transfer, consume, adjust.
MovementWhen
ReceiveGoods arrive from a supplier (usually against a PO)
TransferStock moves between locations — store → van, HQ → branch. At cost, no invoice.
ConsumeStock used on a job (bills through the job) or sold externally
AdjustStocktake correction — always with a reason
The habits that keep counts true
Receive against the PO, same dayGoods in the door = received in The Grid. Check quantities against the PO as you book them in.
Record what leaves your vanTechs: materials used on a job get logged on the job in the field app — that's the consume. Skip it and the job's profit is fiction and the van count drifts.
Low stock alerts → raise a POItems falling below minimum flag themselves. Reorder through Purchase Orders, not a phone call.
Stocktakes: adjust with a reasonCount, enter, and let the adjustment record why. Repeated shrinkage on one item is a signal, not an accident.
Head office supplyThe procurement store (with bin locations like sub-racks) is also what feeds the B2B Portal below — one pool of stock, visible to staff and trade customers alike.
B2B

B2B Portal & B2B Orders

Two halves of one flow. The B2B Portal is the shop — browse head-office stock by category, cart, order. B2B Orders is the office fulfilment screen — confirm, pick, pack, dispatch, invoice.
Ordering (portal — staff, field techs, trade customers)
Sidebar → B2B Portal (or b2b.thegrid.nz)Front page shows categories — PPE, Workwear, Carwash/Transport, QSR, Safety, Tech. Tap one, or search everything.
Add to cartLive availability per location shows on each item. The 🛒 in the header follows you around.
Cart → check the details → Send order requestCompany defaults from your login (staff orders auto-flag as internal). Say where it's going — pickup or which branch.
Fulfilment (office — B2B Orders under Stock Control)
Work the pipeline: Requested → ConfirmThe dashboard strip shows what's awaiting action. Confirming tells the customer it's real.
Start picking → print the Pick ListSorted by bin location with tick boxes — walk the racks once.
Pack: enter serials on serialised linesSerial numbers are captured at pack — they print on the packing slip and register warranties automatically on warrantied gear.
Dispatch — courier ref or branch transferExternal orders consume stock; internal (Clarksons) orders transfer at cost to the chosen branch. Print the Packing Slip (no prices) for the box.
Complete — invoice preview for external ordersA full invoice preview pops up for a visual check → "Looks right — raise invoice" creates the real AR invoice (B2B-INV-…). Internal transfers never invoice. Print the Tax Invoice from the completed order.
Warranty registerDispatched serials on warrantied equipment create warranty records automatically — searchable from B2B Orders. When a customer rings about a failed unit, the serial tells you if it's on us.
CAT

Products, Price Books & Rate Cards

The pricing engine behind quotes and jobs. Get familiar — you'll touch it every time you price anything.
ProductsThe master catalogue — 50,000+ supplier items with cost prices, updated from supplier imports (JA Russell etc.). Search by code or description when adding materials anywhere.
Price BooksCustomer-specific pricing: agreed discounts or fixed prices for contract customers. A quote for that customer picks up their book automatically.
Rate CardsLabour rates by role (tech / lead / supervisor) and time (standard / after-hours). Quotes and job costing read these — nobody should hand-type an hourly rate.
Rule of thumbIf you're typing a price from memory, stop — search the catalogue or the rate card. Memory prices are how margin leaks.
PO

Purchase Orders

Buying anything = raising a PO first. It commits the cost to a job (or overhead), gives the supplier a reference, and gives AP something to match the bill against. No PO, no purchase.
Raise a PO
Purchase Orders → + New POPick the supplier and — critically — the job it's for. No job means it's overhead, and overhead needs a reason.
Add lines from the catalogueCodes, quantities, agreed prices. Free-text lines are the exception, not the habit.
Approval limits apply automaticallyOver your limit? It routes to a supervisor/manager for approval — and you can't approve your own. That's deliberate.
Send to the supplier, then receive against itWhen goods arrive, book them in against this PO (see Stock). Quantity and price mismatches surface in AP's three-way match instead of slipping through.
INV

Invoicing

Turning completed work into money. Invoices raise from jobs (so nothing invoices twice or never), support progress claims and credits, and email out Grid-branded from invoices@.
Invoice a completed job
Open the completed job → Raise InvoiceLines build from the job's labour, materials and other costs at sell prices.
Preview before you commitA full visual preview shows exactly what the customer gets — bill-to, lines, GST, total. Check it like the customer will.
Confirm → the job locksThe invoice gets its number, the job flips to Invoiced and can't be edited. That's why Review (the stage before) matters.
Email it from the invoiceGrid-branded, with the payment details block (BNZ account + reference). Portal customers also see it in their portal.
Record payments as they landFull or part payments against the invoice — the status runs sent → partial → paid, and overdue flags itself from the due date.
Progress claimsBig jobs bill in stages — claim by % or $ against the contract value, with a final-claim lock so you can't overclaim.
CreditsGot it wrong? Raise a credit against the invoice (full or partial) — it nets off properly in AR and the reports. Never delete an invoice.
Consolidated invoicesMultiple small jobs for one customer can bill on a single invoice, split per job underneath.
A/R

AP / AR

Both sides of the money. AR: what customers owe us (invoices, payments, overdues, statements). AP: what we owe suppliers (bills matched against POs and receipts before they're approved to pay).
AP — process a supplier bill
Enter the bill against its POThe three-way match compares bill ↔ PO ↔ goods received. Green = pay it.
Mismatch? Chase it before approvingWrong price or short delivery is the supplier's problem to fix now — not finance's problem after payment.
Approve for the payment runApproval limits apply, same as POs.
AR — keep the money coming in
Watch the overdue laneOverdues sort by age. 60+ days escalates — statements and a call, not hope.
Send statementsPer-customer statements roll up everything outstanding. Portal customers see the same numbers live in their portal — one version of the truth.
EXP

Expense Claims

Out-of-pocket spend, Xero-Me style: snap the receipt, AI reads it, office approves it, it lands in the books as a real cost. No shoeboxes.
Claim an expense (everyone)
Open Expenses (field app or expense.thegrid.nz)+ New claim → photograph the receipt. The scanner pre-fills supplier, date and amount — check it, don't trust it blindly.
Say what it was forCategory and, if it belongs to a job, the job. "Parking — job 61234" gets approved fast; "misc $80" gets questions.
Submit and trackYou'll see it move submitted → approved (or queried, with a reply you can answer) → paid.
Approve claims (office)
Expense Claims screen → work the queueReceipt image side-by-side with the claim. Re-code the category if it's wrong — don't bounce it for coding.
Approve or query with a noteApproved claims post to AP as an overhead bill (or to the job) and hit the real P&L — no month-end journal mystery.
FIN

Finance Dashboard, Reports & Budget

The money picture, live from the same data everyone else is entering — which is exactly why data discipline in every other module matters.
Finance DashboardP&L, balance sheet view, AR/AP position, WIP — real figures from jobs and invoices, filterable by branch and division.
Financial ReportsThe report pack — margins by job/customer/contract, revenue by division, exportable and printable for the board.
BudgetFY budget by branch/division, actuals tracking alongside. Variance conversations happen here, not in a spreadsheet.
Management ReportThe monthly PDF pack, generated from live data — one click, no copy-paste.
RememberFinance screens are read-only mirrors of operational truth. If a number looks wrong here, the fix is almost always on a job, invoice or timesheet — trace it back.
T&P

Timesheets & Payroll

Hours drive two things: what jobs really cost, and what people get paid. One entry, both outcomes — which is why hours go against jobs, daily.
Hours, start to paid
Techs: log hours daily against jobsIn the field app as you finish each job. Office staff enter theirs in Timesheets. Friday-afternoon reconstruction is how hours get lost.
Supervisors: approve weeklyCheck the week reads true — right jobs, right hours, overtime where it's real (8+/day, 40+/week).
Approved hours flow to payrollThe pay run picks up approved timesheets — no re-typing. Leave (from HR) folds in automatically.
Payroll runs the pay cycleReview the run, handle exceptions, finalise. Queries about the numbers go back to the timesheet, not the payslip.
CUS

Customer Portal

What our customers see at customers.thegrid.nz: their jobs, their assets with compliance and capital planning, their quotes (with approval), invoices and statements, and a request button that lands in our Triage. Their window into The Grid — powered by the data you enter.
My Assets — the showpieceTheir register: compliance rate, overdue tests, per-site health, capital plan with a 10-year forecast, click-in per asset to service history with dollars, and four printable reports.
Quotes with approvalThey approve a quote online → a high-priority ticket lands in Triage → we convert it. No email tennis.
Requests"Request a job / quote" creates a Triage ticket (type: portal). They watch its status through to the job number.
Per-customer switchesEvery section (assets, capital plan, reports, quotes, approval, invoices, requests) toggles per customer — our control, enforced server-side.
Preview as a customer (staff)
Sidebar → Customer Portal (test)Quick-pick a company (CBRE, Nestle, Z Energy, Waitomo) or search any customer.
You see exactly what they'd seeTheir data only — a CBRE login physically can't see Z Energy's world. Use it before a customer demo or when they ring about "what the portal says".
⚙ on the picker = their switchesTurn sections on/off per customer. Off means invisible and blocked, not just hidden.
ComingReal customer logins are next — you'll flick a portal-access switch on the customer and they get their own credentials. Until then it's staff-preview only.
CLS

Classroom

Training lives in The Grid too — courses with videos and documents, assigned by role, branch or division, with completion tracked. This guide gets you started; Classroom makes it stick.
Take a course
Classroom → Assigned to meCourses assigned to you show with due dates. Multi-part courses (episodes) track per part.
Watch / read → Mark CompleteVideos stream in the page (up to 750MB, they play and seek fine). Completion is recorded against your profile.
Browse & self-enrolThe library below your assignments is open — upskilling is encouraged, not gated.
Run training (managers)
Manage & Assign → create the courseUpload the video or document (Manage → Edit → Upload file), write the description.
Assign by audienceRole, branch or division filters — "all techs in Auckland" is three clicks. Set a due date and watch completion roll in.
RPT

Reporting

Operational dashboards over everything: jobs, revenue, margins, staff utilisation, contract performance — all filterable by branch and division, all exportable.
Pick the view, then filterBranch and division filters sit on every report — your numbers, not the whole company's, unless you want the whole company's.
Trust the drill-downA number that surprises you should be clicked, not argued with — it traces to the underlying jobs or invoices.
Export what you needPrint/PDF/CSV from each report. But before rebuilding a spreadsheet empire — ask, the report you want probably exists or can.
ADM

Staff & Permissions (managers+)

Where logins live: create accounts, set roles and branches, reset passwords, control 2FA, and gate module access. You can only manage people below your own level.
Set up a new starter
+ New Staff MemberName, work email (this is their login), role, branch, phone. The role decides what they can see and approve.
Password: min 10 characters, letter + numberOr skip it and use Reset Password to generate a temp they'll replace at first login (better).
Tick Require 2FA if their role warrants itMoney, admin and management roles should have it. They'll be walked through enrolment at next login and can't skip or disable it.
Check module accessThe Permissions tab gates modules per person, plus spend limits for approvals.
The three rescue buttons
Reset PasswordGenerates a readable temp password — email it from the popup (Grid-branded) or read it out. One use, then they set their own.
Reset 2FA (lost phone)Wipes their authenticator pairing and backup codes; they re-enrol at next login.
DeactivateLeavers get deactivated, never deleted — history stays intact, login stops working immediately.
TLS

Everyday Tools

The supporting cast under Tools & Resources.
🗒️ Forms LibraryDigital eForms — job forms, checklists, sign-offs. Fill on any device; submissions attach where they belong.
🤖 Ask DavidThe built-in AI assistant. Ask how something works, where something lives, or who to talk to — in plain English.
📧 Email LogEvery email The Grid has sent — invoices, quotes, password resets — with status and a preview. "Did they get it?" lives here.
🕐 Activity LogWho did what, when. Great for "who changed this?" questions — the answer is always logged.
📥 Import CentreBulk data in (admin). Supplier catalogues, customer lists, historical data.
✈️ Travel PlannerPlan multi-site NZ trips — routes, times, distances between jobs.
🎉 Shout OutsPublic recognition wall. Someone nailed it? Say so where everyone can see. Use it often.
🔐 My SecurityYour own 2FA setup and backup codes — see Getting Started.
…

Coming Soon to This Guide

🦺 Health & Safety — SMILE, HAHA, SWMS and site inductions. The module's live but evolving; the training chapter lands when it settles. Interim rule stands: report hazards and incidents immediately, and at least one H&S report per person per month.
🏗 Construction — projects, RFIs, variations, payment claims. In active build — chapter to follow.
🧑‍🤝‍🧑 HR Hub — leave, skills matrix, employee records. Chapter to follow. Leave requests still go in via HR Hub → your supervisor approves.
THE GRID — Clarkson's Electrical · Tomorrow's solutions today Questions or corrections? Use the 💬 Feedback button — it goes straight to David.