Built around the Australian standards that matter.
EMAction is designed to support AS 3745, align with AS 4083, meet WHS duty-of-care obligations, and — via the Command addon — align with AIIMS-5.
Request a procurement pack
EMAction is designed to support AS 3745, align with AS 4083, meet WHS duty-of-care obligations, and — via the Command addon — align with AIIMS-5.
Request a procurement packAS 3745:2010 is the Australian standard for emergency planning in facilities. It covers the Emergency Planning Committee, the Emergency Control Organisation, the warden structure, incident categories, drills and records.
EMAction supports AS 3745. It does not and cannot certify your organisation’s compliance with AS 3745. Compliance depends on your Emergency Planning Committee, your documented procedures, your warden training and your drill programme. EMAction is a tool that supports those activities; it is not a substitute for them.
AS 4083:2010 is the Australian standard for emergency planning specifically for healthcare facilities. It sets the framework for the colour-code system (Code Red for fire, Code Blue for medical emergency and so on), procedures and warden structure specific to healthcare.
EMAction aligns with AS 4083. It does not and cannot certify your facility’s compliance with AS 4083 or with clinical governance frameworks that cite it. Compliance depends on your Emergency Planning Committee, your clinical leadership, your staff training and your documented procedures. EMAction provides the digital surface for response behaviour; it is not a substitute for the clinical response itself.
The Work Health and Safety Act and the corresponding state and territory regulations place a duty of care on the PCBU (the person conducting a business or undertaking) — the employer, the building owner, the principal contractor — to workers, contractors and visitors. Emergency response planning is part of that duty.
EMAction is a tool. Duty of care remains with the PCBU. EMAction provides evidence of response behaviour — when an incident was activated, who was accounted for, what instructions were broadcast, what refusals were recorded. That evidence supports WHS obligations; it does not discharge them.
AIIMS-5 — the Australasian Inter-service Incident Management System, maintained by AFAC (Australasian Fire and Emergency Service Authorities Council) — defines the principles, functions and artefacts used by Australian emergency services to manage incidents. It is increasingly expected of upper-market facility operators — hospitals, universities, airports, mine sites, councils — whose incidents may span extended periods, multiple agencies, or heightened regulatory scrutiny.
AIIMS-5 alignment is available via the EMAction Command addon only, not the base platform. The features listed below require the Command addon to be enabled for your tenant.
Aligned, not certified. No software certification scheme exists for AIIMS. EMAction Command produces a per-tenant alignment statement PDF suitable for procurement responses — a mapping of AIIMS-5 principles, functions and artefacts to enabled EMAction features. This is alignment documentation, not a certification claim. Any vendor claiming “AIIMS certified” should be asked to name the certification body. AIIMS-5 alignment requires the Command addon; compliance with AIIMS-5 expectations for your organisation remains with your Incident Management Team and training provider.
Depending on your sector, additional compliance regimes apply. EMAction helps you evidence response behaviour under these regimes, but does not certify compliance with them.
Requires effective emergency management systems as part of organisational governance. Aged care context →
Most states mandate emergency management plans and regular drills for schools, usually citing AS 3745. Education context →
Children’s Health and Safety requirements for early childhood education and care services. Education context →
Higher education and VET providers carry their own emergency management expectations. Education context →
NSW Resources Regulator, Qld Resources Safety & Health and equivalents impose incident management obligations beyond WHS. Construction & field-site context →
Under state WHS construction regulations, the principal contractor carries explicit emergency planning responsibilities. Construction & field-site context →
Operational excellence reporting often references incident and drill data. Office & commercial context →
EMAction is a tool. Sector-specific compliance remains with your organisation and its regulator. EMAction provides incident records, drill evidence and audit-trail exports that support these regimes; it does not certify compliance with them.
These are the honest boundaries. Every procurement document we produce makes them explicit.
EMAction is not a fire detection or alarm system. It integrates with the response, not the detection. Smoke detectors, sprinkler systems, duress alarms and sensor networks remain with your existing fire and building systems.
EMAction does not issue Emergency Warden Instructions. It supports the response; it does not author the instructions document that drives it. The Emergency Planning Committee writes the instructions; EMAction carries the response behaviour against them.
EMAction is not AIIMS certified. No such certification exists. The Command addon aligns with AIIMS-5 and produces alignment statement documentation — not certification. Any vendor claiming “AIIMS certified” should be asked to name the certification body.
The base platform’s security and data-handling controls that sit under every compliance surface above.
OTP login for all roles with role-based redirects. Email/password fallback where the tenant requires it.
12-hour absolute session timeout across every role. Sessions cannot be extended beyond that window without re-authentication.
QR check-in pages gate incident data behind authentication. A QR code shown publicly cannot by itself leak incident details — the user still authenticates before seeing any data.
No cross-tenant data access. Each client’s uploads, database and sessions are isolated; a user on one tenant cannot see another tenant’s incidents, wardens or PEEP records.
Client data — uploads, database, sessions — is never overwritten by deployments. Platform upgrades preserve tenant state.
All dates stored in UTC, displayed in the building’s configured timezone. Per-building timezone setting supports tenants with operations across multiple states or countries.
EMAction produces documentation that slots into standard AS 3745, AS 4083 and AIIMS-5 tender questions.
Per-clause mapping of EMAction features to AS 3745 requirements. Produced by EMCorp for base-platform deployments on request, sized to the specific clauses named in your tender.
Available on request — base platform
Per-tenant document generated via the Command addon. Maps AIIMS-5 principles, functions and artefacts to enabled EMAction features. Alignment documentation, not a certification claim.
Available via Command addon — per tenant
We scope exactly which features are live for your tenant. The feature-flag configuration is itself documentation for your procurement review — you can see precisely what the tenant is licensed to use.
Standard, every tenant
Send us the specific tender questions, the clauses, the regulator scrutiny you’re under. We’ll tell you what EMAction covers, what it doesn’t, and what you’ll need to run alongside it.
Request a demo