ACRI - Australian Child restraint Resource Initiative – is the number one resource for training on child restraint use in Australia, offering specialised training programs and auditing solutions for specific workplace environments.
Authorised child restraint fitting stations ( often referred to accredited restraint fitting stations ) are everywhere it seems these days with many only promoting the child restraint installation aspect. A good service provider who provides an installation service does much more than that and call themselves a child passenger safety technician. The promotion of child restraint fitting stations in providing installations, over many decades in some states, has contributed to a bias in the understanding of what parents need to focus on everyday.
It has very little to do with an authorised fitting stations activities that will keep a child safe. All ACRI trainees are exposed to a completely different perspective than any other training system in Australia. We do not falsely create experts from a single training exposure, we train practitioners to bring new and wider perspectives to a family's everyday safe travel knowledge.
New South Wales, Western Australia, South Australia, Tasmania, Victoria, Northern Territory, Australian Capital Territory, Queensland are all catered for by our services. Family day care, automotive service, repair, new car sales, professional installation or fitting services, nannies, child care and Family and community services. The car rental industry is also catered for.
ACRI specialises in sharing solutions for easy understanding of child restraint use issues. Improving child restraint safety for all of our littlest road users and making it easier for parents to satisfy themselves that they are doing it right. Media articles from many stakeholders have been used to highlight that parents ‘Have to use’ child restraints, but have generally failed in making it a simpler process for everyone.
One example is that people have been told that they need to use a child restraint, (ie: Capsule, chair, booster, toddler car seat, infant restraint combination restraint, convertible restraint etc:) because of the road rules and to avoid a fine. That's not why we use them.
Child restraint products need to be used to provide a safer environment for our smaller passengers who may either be;
1. At risk when using an inappropriate restraint system, such as a ‘Seat belt’. Or....
2. They're under-developed physically and can benefit from specific injury protection devices and practices.
They are the reasons that child restraint systems need to be used. The Road rules are a ‘Big stick’ approach to force us to do something to protect our child passengers against the dynamics that we, as mere mortal road users are generally unaware. The road rules have never been the pinnacle of practices to aim for as they are the minimum safety approach.
Do we need child restraint road rules? Sadly yes, as they play a part in reminding us of what's important to focus on. It's just that we don't often know how important
Parents have received many poor messages over the years, including that they couldn't possibly do the installation themselves and that they must rely on an 'authorised' installer. Every parent/carer should start their child restraint experience by getting familiar with their restraint, gaining some understanding of how it should be used, which includes the installation. If they then have any doubt about the correct use of their child's restraint then they should seek out assistance from someone who's been trained on what the correct procedure is for helping others with the use of their restraint, which includes the installation. Correct child restraint use is not all about the installation. Secondly, it's largely irrelevant who carries out the initial installation aspect. If the day to day user hasn't been briefed on how to monitor the installation and how to correctly configure it, then it could become unsafe at any time.
ACRI providers are trained to empower parents and carers via their services and not create dependency. See our 'Code of Practice'.