GA2 weekly examinations — what site teams need to know
Quick summary
Weekly GA2 examinations keep lifting equipment and site plant safe and demonstrably maintained. This guide explains what must be recorded, who is responsible, and how digital workflows reduce missed checks across busy construction sites.
If you manage plant on a construction or infrastructure project in Ireland, GA2 — the Report of Weekly Examination — is part of everyday compliance. It is not a one-off certificate you file away; it is an ongoing record that specific equipment was examined within the required interval and found fit for use (or taken out of service until rectified).
Site teams that treat GA2 as “paperwork at the end of the week” often struggle when an audit asks for continuity: last month’s excavator checks, who signed them off, and what happened when a defect was found. Teams that build GA2 into a clear weekly rhythm—and store results in one place—pass those questions in minutes.
What GA2 covers in practice
GA2 applies to equipment that falls under thorough examination and reporting regimes for lifting plant and related site machinery. On site, that typically includes items your team already tracks closely:
- Excavators, telehandlers, and site dumpers used daily
- Lifting accessories and attachments where examination is required
- MEWPs, cranes, and other specialised plant where your safety file defines weekly checks
Your statutory obligations sit alongside PUWER (Provision and Use of Work Equipment Regulations) expectations in the UK and equivalent plant safety duties in Ireland. GA2 is the weekly layer: did someone competent look at this machine this week, and is there a signed record?
What a good weekly record includes
Auditors and client safety teams look for consistency more than perfection. Each weekly entry should make these points obvious:
| Element | Why it matters |
|---|---|
| Asset identity | Serial number, fleet ID, or QR-linked register entry |
| Date and time of examination | Proves the check happened inside the required window |
| Examiner | Name or role of the competent person |
| Outcome | Fit for use, restricted use, or out of service |
| Defects and follow-up | What was wrong, and evidence it was closed out |
Photos, notes, and “failed then fixed” history are especially valuable when the same asset is questioned months later.
Common gaps that cause audit friction
These patterns show up on almost every multi-site contractor at least once:
- Checks done but not recorded — work happened on a clipboard that never reached the master file.
- Records scattered by project — GA2 for Site A lives in a folder; Site B uses a spreadsheet; head office has neither.
- No link between weekly check and certificates — thorough examination or LOLER paperwork exists, but weekly continuity is missing.
- Contractor handovers without history — a sub leaves and takes their inspection log with them.
Digital plant registers solve the first three by giving every asset one timeline. QR access on site means an examiner can open the right form from the cab in seconds—no app install, which matters when turnover is high.
Building a weekly rhythm that sticks
A workable process usually looks like this:
- Monday or post-weekend: rolling weekly GA2 for equipment that ran over the break
- Fixed day per site: same supervisor slot so checks are not “when we remember”
- Dashboard review: plant manager scans for overdue items before client walks or internal audits
- Escalation rule: any “out of service” asset is removed from hire/internal use until signed back in
SlánDocs includes GA2 templates you can run as-is or adapt for GA3, vehicles, temporary works, and custom plant types—so you are not maintaining five different paper systems.
Moving from paper GA2 to digital without disruption
You do not need to digitise your entire fleet on day one. Most teams start with:
- High-risk or high-hire equipment (excavators, telehandlers, MEWPs)
- One pilot site with a named plant coordinator
- QR labels on those assets linking to the live register
Within a few weeks, supervisors stop chasing PDFs in WhatsApp because inspection history, certificates, and weekly GA2 sit on the same asset record.
Quick summary
- GA2 is ongoing weekly proof—not a one-time document.
- Audits reward clear identity, dates, outcomes, and defect closure on every asset.
- Scattered paper and spreadsheets create gaps multi-site teams cannot afford.
- Digital registers, mobile-friendly forms, and QR access keep weekly examinations visible across Ireland and UK projects.
Want to see GA2 and PUWER workflows on your own plant types? Book a demo and we will walk through templates, dashboards, and audit exports with your team.
