Quick answer
There is no single universal certificate that, by itself, proves a person or company is competent to perform every Quantitative Risk Assessment. Clients should verify the proposed team’s relevant engineering qualifications, major-hazard experience, modelling competence, software access, regulatory knowledge, independent checking process and traceable project evidence.
The phrase “QRA certification” can refer to professional training, software courses, process-safety credentials, internal competency approval or a client’s vendor-qualification requirement. These are useful evidence, but none should replace a technical assessment of the team proposed for the specific facility.
For the full engineering scope of a study, visit Elion’s Quantitative Risk Assessment service. For the underlying calculations and workflow, see the QRA methodology guide.
What should “QRA qualified” mean?
A competent QRA team should be able to convert process and site data into a defensible chain of evidence: scenario selection, frequency analysis, consequence modelling, risk integration, ALARP evaluation and practical mitigation. Qualification therefore depends on the assignment.
- Relevant engineering or science education
- Experience with comparable hazardous materials and facilities
- Demonstrated understanding of fires, explosions and toxic releases
- Competence in frequency, event-tree and consequence analysis
- Experience producing individual-risk contours and societal-risk F-N curves
- Knowledge of the applicable approval and technical framework
- An independent checking and revision-control process
Seven areas to verify before appointing a QRA practitioner
1. Facility-specific experience
Ask for examples involving comparable inventories and operations—not merely a list of unrelated safety audits. LPG bottling, LNG, petroleum terminals, chemical manufacture, toxic-gas storage, pipelines and occupied-building studies require different modelling judgement.
2. Named team and responsibilities
The proposal should identify who leads HAZID, prepares the scenario register, performs frequency analysis, operates the modelling tools, checks the calculations and approves the report. Confirm that the named personnel will remain assigned.
3. Modelling capability
Verify the tools proposed for dispersion, fire, explosion and risk integration. Software may include PHAST, SAFETI, ALOHA or specialist models as appropriate. Ask for evidence of legitimate access, version control, training and recognition of model limitations.
4. Frequency-analysis competence
A full QRA is not only a set of consequence distances. The practitioner should be able to justify failure data, event trees, ignition probabilities, weather distributions, safeguard credit and occupancy assumptions.
5. Regulatory and standards knowledge
The team should identify the current requirements applicable to the installation, which may involve OISD, PNGRB, PESO-administered rules, MSIHC obligations, MoEFCC Terms of Reference, API, CCPS, NFPA or client criteria. No consultant should claim that one generic standard applies to every facility.
6. Independent technical review
Ask how the scenario register, model inputs, frequencies, contour drawings, F-N results and recommendations are checked. The checker should be sufficiently independent of the original calculation.
7. Decision-ready deliverables
Competence is demonstrated in the audit trail. Require data and assumption registers, scenario lists, calculation outputs, model basis, risk maps, dominant-contributor analysis, ALARP evaluation and a prioritised action register.
QRA competency evidence checklist
| Evidence | What to examine |
|---|---|
| Qualifications | Relevant engineering, process-safety or risk-analysis education |
| Project record | Comparable facilities, substances, pressures and decision objectives |
| Software capability | Appropriate licensed tools, training and model-limit awareness |
| Method statement | Scenario, frequency, consequence, risk and ALARP workflow |
| Quality assurance | Named checker, revision control and comment close-out |
| Sample deliverables | Traceable calculations rather than only contour images |
| References | Clients able to confirm technical performance and review support |
Training and certifications that may support competence
Depending on role, useful evidence may include formal process-safety education, recognised functional-safety or risk qualifications, hazard-study leadership training, consequence-modelling software training and continuing professional development. The value of any credential depends on its syllabus, assessment method, recency and relevance to the proposed work.
A software attendance certificate does not prove that the practitioner can select credible scenarios, validate input data or interpret risk results. Likewise, a general safety qualification does not automatically establish competence in major-accident frequency and consequence modelling.
Warning signs during vendor qualification
- A claim of being “QRA certified” without naming the credential or issuing body
- No named modeller or independent checker
- No distinction between consequence analysis and full QRA
- Risk contours offered without frequency or population methodology
- Generic regulatory claims not tied to the facility
- No model files, calculation trail or assumption register
- An unrealistically short schedule with no client-input milestones
Recommended technical evaluation approach
Score technical proposals before comparing price. Weight scope understanding, relevant team experience, methodology, modelling and data controls, quality assurance, deliverables and schedule realism. Commercial comparison should then be made among technically acceptable bidders with exclusions normalised.
Frequently asked questions
Is QRA certification mandatory in India?
There is no single credential universally mandated for every QRA assignment. The applicable authority, project Terms of Reference, client procedure or tender may specify qualifications, experience, software or third-party requirements. Confirm these for the particular project.
Can one person complete the entire QRA?
Small studies may use a compact team, but material assignments benefit from separate scenario, modelling and independent-check responsibilities. The required structure should reflect complexity and consequence potential.
How can a client verify a consultant’s claims?
Request named personnel, comparable project references, a sample methodology, evidence of software capability, the QA plan and examples of reviewable deliverables. Contact references before award.
Elion can provide a project-specific team structure, methodology and deliverable matrix for technical evaluation. Share the facility brief to request a scoped proposal.