Resource Industry Network Safety Conference Checklist
Published by QHSE Directory Editorial Team • Oct 21, 2026
At 6:45 a.m. outside the MECC in Mackay, attendees check their badges, notebooks, and day plan before the first safety session begins. Coffee cups steam in the Queensland air. Boots, polos, and blazers cluster near the doors. If you are travelling to the resource industry network safety conference, that quiet minute before entry is when your real work should already be clear.
After 20 years in HSE roles across operations, projects, and consulting, I can tell you where value is usually lost. Not in the keynote. Not in the breakout room. It is lost on Monday morning, when useful notes sit under a hard hat on the passenger seat and nobody owns the next step.
You should treat this conference as a working day with a defined safety objective, not as a general industry outing. The event may be positioned as Regional Queensland's most anticipated day for advancing safety leadership and practices, but your site will only benefit if you return with decisions, contacts, and actions that fit your actual risk profile.
Pre-work checklist for the resource industry network safety conference
Define the outcome before you register
Start with the result you need. Safety Conference 2026 is scheduled for Friday 29 May 2026 at the Mackay Entertainment & Convention Centre, 258 Alfred St, Mackay, Queensland 4740, and its theme is “Learning from the Past. Shaping the Future.” Use that theme as a filter. You are not there to collect interesting ideas. You are there to bring back something that changes work.
- State the one safety problem you need to solve. Name one issue in plain language. Examples from resource and industrial settings are easy to find: isolation drift during shutdowns, contractor onboarding inconsistency, mobile plant interaction risk, fatigue controls that exist on paper but not in practice, or a rise in psychosocial complaints from front-line teams. One problem is manageable. Five problems create noise.
- Match the agenda to your site risks. Compare the program against your recent incident reviews, critical control verification results, and audit findings. If your last three internal audits raised supervision quality, permit discipline, and fatigue, those topics should drive your session choices. Do not let a polished title pull you away from your top exposure.
- Set a simple success measure for the day. Keep it operational. For example: leave with three control ideas to test, two peer contacts who solved a similar issue, and one legal or technical clarification for supervisors. That measure should fit on one line and be checked before you drive out of Mackay.
A conference day only matters if you know what problem you want it to help solve.
A short planning matrix helps. Build it before tickets are booked, not on the plane or in the hotel.
Site issueSession targetEvidence to captureSuccess measure by day’s endIsolation non-compliance during maintenanceOperational learnings or lawVerification step, field example, failure pointTwo changes to trial in permit checksPsychosocial risk escalationPsychosocial safety or mental healthSupervisor prompt, escalation trigger, support pathwayOne revised conversation guide for leadersWeak data from inspectionsTechnology or data-driven insightsData field design, reporting cadence, ownership modelOne metric to add to monthly review
Prepare the team and the logistics
Mackay is described as the epicentre of regional manufacturing and mining. That is not a throwaway line. It means you will be surrounded by people dealing with familiar pressures — shutdown windows, contractor interfaces, cost scrutiny, labour constraints, and the constant tension between production and protection. The conference promises presentations from leading experts, practical and cost-effective solutions, and inspirational stories. That mix only becomes useful if the right people are in the room and the right questions are already written down.
- Choose attendees who can influence safety decisions. If you can send two people, send one HSE lead and one operational decision-maker — a superintendent, maintenance manager, or production leader. If you can send only one person, choose someone who can brief both the toolbox room and the leadership meeting without losing credibility in either space.
- Build a question list from current incidents or audit gaps. Pull the last quarter of incident themes. Add open corrective actions. Add unresolved audit non-conformances. Turn each into a direct question: What changed first? How was worker uptake verified? What resistance appeared? What did the change cost in time or training? RIN’s program details emphasise real industry conversations and practical takeaways you can apply immediately, so bring questions that demand practical answers.
- Pack a follow-up template before you leave. Build a simple note sheet with six fields: issue, idea, owner, due date, success measure, and contact. Print it or place it in your tablet. This one step prevents the familiar problem of returning with pages of highlights and no action structure.
One caution is worth stating. The main event listing places the day at the MECC on Alfred Street, while a social post tied to program promotion also references Paget. Treat that discrepancy properly. Confirm the final venue and travel details from your booking confirmation rather than from a screenshot or forwarded message.
Registering is the easy part; preparing a question list is what turns attendance into value.
Execution checklist

Work the room and capture usable ideas. The breakout program has been described as covering on-site technical expertise, operational learnings, psychosocial safety, mental health, law, technology, and data-driven insights. That range is strong. It can also scatter your attention if you listen like a spectator instead of an investigator.
Attend breakout sessions with a note-taking brief
Walk into each breakout with a capture structure. Mine is simple after years of field debriefs: hazard, control, verification, and barrier. In other words, what risk was addressed, what changed, how was the change checked, and what got in the way. If the speaker cannot answer those four points, the idea may be interesting but not yet ready for site adoption.
The 2026 event is designed to equip attendees with skills and information they can take back to their workplaces. Hold each session to that standard. For a talk on mental health, do not settle for broad awareness messaging. Ask what line leaders actually said, what referral path was used, and how confidentiality concerns were managed. For a technical session on guarding, ask what maintenance trade-off followed the modification and how it was resolved.
Record names, methods, and exact language you can reuse
Capture more than the idea. Record the speaker’s name, organisation, operating context, and the exact words used to describe the problem. Exact language matters when you brief your site later. “Critical control drift” lands differently from “we had a paperwork issue.” “Field verification before sign-off” is stronger than “we improved compliance.” Words shape uptake.
Do the same in corridor conversations. If a maintenance manager from Moranbah tells you their team reduced handover confusion by changing permit close-out language, write that down before lunch. If a supplier explains a limitation on a respiratory product in humid conditions, record the limitation, not just the brand. Precision saves time later.
Turn Q&A into site-specific prompts for your team
A good question period should not end in the room. Convert each useful exchange into a prompt for your own site: How would this work in an open-cut environment? What would our contractors say? Which procedure would need amendment? Would procurement block this? Could supervisors verify it on night shift?
This matters because the conference is built around practical takeaways you can apply immediately. Immediate application does not mean blind copying. It means disciplined translation. The idea should be reshaped to fit your risk profile, your workforce, and your control framework before anybody issues a new instruction.
If you cannot explain a session’s takeaway in one sentence, you probably have not captured it clearly enough.
Validation checklist

Convert notes into workplace action before the momentum fades. The theme “Learning from the Past. Shaping the Future” should continue after the closing remarks. The lesson is not learned when it is heard. It is learned when it is tested, assigned, and verified.
Separate quick wins from larger projects
Sort every useful note within 24 hours. Quick wins are small, local, and low-friction: add a pre-start prompt about line-of-fire exposure, revise a toolbox discussion on psychosocial triggers, or change the order of a contractor induction slide deck. Larger projects require cross-functional ownership: fatigue management review, change to a critical control standard, procurement of new guarding components, or redesign of incident data fields.
If you do not separate these categories, everything goes stale together. In practice, a supervisor can implement a revised verification question next week. A broader procedure rewrite may need HSE, operations, legal review, and worker consultation. Different actions require different governance.
Assign owners, deadlines, and success measures
Be exact. If a note has no owner and no due date, it remains a note. Assign the action to a role, not to a vague team. “Operations superintendent” is usable. “Site leadership” is not. Then set a date and define what completion looks like.
Use evidence, not intent. For example: “Trial revised isolation field verification on ten permits by 15 June; evidence = completed permit sample and supervisor feedback.” Or: “Review contractor pre-qualification criteria for psychosocial risk controls by next monthly governance meeting; evidence = updated checklist and approval record.” Those statements can be audited. Good intentions cannot.
Report back to HSE and operational leaders
RIN frames the conference around sharing lessons, building capability, and strengthening safety outcomes across industry. Your report-back should mirror that. Keep it short. One page is enough if it is structured: what was learned, where it applies, what should change first, and who will decide.
Do not brief HSE in isolation. Bring operations into the conversation early. The conference brings together like-minded professionals and industry experts across regional Queensland, but internal alignment still determines whether anything changes on your own site. I have seen technically sound ideas stall because the superintendent heard about them three weeks too late.
Action typeExampleOwnerDue dateProof of completionQuick winAdd a field prompt on fatigue indicators to pre-start formsShift supervisor7 daysUpdated form in use on crew start-upProjectReview mobile plant separation control standardHSE manager and operations manager30 daysDraft standard and consultation recordExternal follow-upRequest technical demonstration after breakout discussionMaintenance manager14 daysBooked session and evaluation notes
If a note does not have an owner and a due date, it is still just a note.
Common misses
Most wasted value appears after the trip. I have watched capable teams spend money on travel, hear strong presentations, exchange cards with credible peers, and still change nothing at site because the discipline around follow-up was weak.
Don’t attend without a pre-brief from your site
Ask your site what it needs answered before you leave. That pre-brief should come from current operating pain, not from curiosity alone. Speak to the superintendent, the HSE adviser, the maintenance planner, and at least one front-line supervisor. In a manufacturing setting, ask which safety conversation keeps repeating. In mining, ask which control is most often verified late or poorly. Without that pre-brief, you will drift toward interesting commentary rather than risk-relevant learning.
Don’t leave networking contacts unlogged
The conference is promoted as an opportunity to connect with leading professionals across industry. Treat that as work, not as social surplus. Log contacts within 24 hours: name, role, company, issue discussed, promised action, and relevance to your site. Tag them by topic — law, psychosocial safety, contractor management, guarding, data, or verification. An unnamed phone number and a photo of a business card are not a contact management process.
Don’t return without a debrief and action review
The program is built around practical, cost-effective solutions rather than theory alone. Honour that by holding a debrief within 48 hours and an action review within 30 days. The first meeting decides what to test. The second meeting checks what actually changed. If nothing moved, say so plainly and decide whether the barrier was cost, authority, timing, or poor fit.
RIN’s social promotion stresses real industry conversations and practical takeaways you can apply immediately. Immediate only counts when evidence appears in the field — on the permit, in the pre-start, in the supervisor conversation, or in the critical control check. Anything less is conference theatre.
A good conference can produce ideas; a good process turns those ideas into change.
One well-run conference day can become a documented safety improvement plan.
Define the problem, target the right sessions, and assign actions before the notes go cold; then the resource industry network safety conference pays back in safer work, not just fuller notebooks.
When you walk back through the gate after Mackay, which lesson will you already have tied to an owner, a date, and a measurable site change?
Strengthen Safety Links With Qhsedirectory
This Connection platform helps safety manufacturers, distributors, HSE professionals, and organizations turn resource industry network safety conference contacts into usable QHSE supplier and resource pathways.