Analisis insiden dan kemalangan

Was It Fatigue?

Analisis berstruktur selepas insiden untuk menentukan sama ada keletihan menyumbang kepada sesuatu kejadian, dan melalui laluan apa.

A Was It Fatigue? finding on a phone: a Fatigue Accident Likelihood Score of 3.2, between Possible and Likely, with how to record it.

Masalahnya

Insiden serius mesti disiasat. Sedikit sahaja siasatan yang bertanya tentang keletihan dengan sewajarnya.

Keletihan mudah didakwa tetapi sukar dibuktikan selepas kejadian. Siasatan cenderung sama ada terlepas pandang atau terus menyalahkannya tanpa menguji penjelasan alternatif.

Was It Fatigue? memberi penyiasat anda cara yang konsisten dan boleh diulang untuk bertanya, serta rekod yang menunjukkan penjelasan alternatif telah diuji.

See how Was It Fatigue? works Watch the video · 0:33
Presented by Professor Drew Dawson

The size of the problem

National figures for Singapura, from published research. They are modelled, not measured in your workforce.

  • 13%of workplace injuries are linked to sleep problems2014
  • 27.6%have inadequate sleep2022 (SMHS 2016, fieldwork 2016-2018)
  • S$2,312lost productivity per affected employee each year
Sources
  1. Uehli K, et al. Sleep problems and work injuries: a systematic review and meta-analysis. Sleep Medicine Reviews, 2014.
  2. Lee YY, et al. Sleep quality of Singapore residents: findings from the 2016 Singapore Mental Health Study. Sleep Medicine: X, 2022.
  3. Rosekind MR, et al. The Cost of Poor Sleep: Workplace Productivity Loss and Associated Costs. Journal of Occupational and Environmental Medicine, 2010;52(1):91-98, applied to average earnings in Singapore (MOM, mean gross monthly income from work of full-time employed residents, 2Q 2026 preliminary, excluding bonuses).

Kisah

The biggest incidents fatigue played a part in

Findings from investigators, coroners and courts in Singapura dan Australia that fatigue contributed, the most harmful first.

Kes dipaparkan dalam bahasa Inggeris.

  • Jun 2023 · New South Wales, Australia

    Charter bus crash that killed 10: operator and directors fined $674,000 incl. fatigue management failures

    • Keselamatan
    • Undang-undang
    • Kewangan

    After a charter bus crash in regional New South Wales killed 10 people and seriously injured 25, the National Heavy Vehicle Regulator prosecuted the bus company and its two directors. They pleaded guilty to Heavy Vehicle National Law safety duty breaches covering inadequate driver recruitment, failure to manage overspeed in a timely way, and fatigue management failings. The court fined the company $650,000 and each director $12,000, with proceedings against two managers still pending.

    Kes AU-transport-23Laporkan masalah

Lihat semua berita tentang keletihan

Cara ia berfungsi

A structured answer to “was it fatigue?”

After an incident or near miss, investigators work through a structured method: was fatigue present, and was the error the kind fatigue produces once other explanations are tested? It sits at the last level of defence, after something has gone wrong, and feeds each finding back into the levels before it: rosters, sleep and in-shift controls.

  1. Step 01

    Kejadian

    Penyiasat membuka penilaian bagi sesuatu insiden tertentu.

    The Was It Fatigue? investigations list on a phone, each with its Fatigue Accident Likelihood, and a button to begin a new investigation.
  2. Step 02

    Adakah keletihan wujud?

    Fatigue Likelihood Score (skor kebarangkalian keletihan), daripada empat soalan: tertidur sejurus sebelum kejadian, simptom tingkah laku dalam lima belas minit sebelumnya, sejarah tidur dan jaga terdahulu, dan peluang tidur dalam jadual giliran.

    A new Was It Fatigue? investigation on a phone: the date of the incident, then whether there is clear evidence the person fell asleep immediately before it.
  3. Step 03

    Adakah ia kesilapan jenis keletihan?

    Fatigue Error Likelihood Score (skor kebarangkalian kesilapan akibat keletihan) menguji penjelasan alternatif pada setiap tahap sebelum mengaitkan kesilapan itu dengan keletihan.

    Expert guidance in Was It Fatigue?: the behaviours that would support questionable evidence of fatigue in the 15 minutes before the incident, with a button to confirm the response.
  4. Step 04

    Dapatan gabungan

    Fatigue Attributable Likelihood Score (skor kebarangkalian boleh dikaitkan dengan keletihan) pada jalur 1–5 dengan laluannya dinamakan, yang disalurkan kembali ke kawalan jadual giliran, tidur dan semasa syif.

    A Was It Fatigue? finding: a Fatigue Accident Likelihood Score of 5.0, Almost Certain, with what the score means and how to record it.

After an incident, fatigue is either missed or blamed without testing the alternatives. Neither helps the people involved, and neither tells you which control failed. I wanted investigators to have a consistent way to ask the question properly, and a record that shows they did.

Daniel PlattPengasas Bersama dan Ketua Pegawai Eksekutif

Rollout

How we roll it out

  1. Scope

    Agree which events call for an assessment, and who investigates.

  2. Set up

    Investigator access, fitted to your existing incident process.

  3. Train

    Investigators learn the method and work a first case together with us.

  4. Review

    Findings feed back into roster, sleep and in-shift controls.

Apa yang dilihat oleh pelanggan

Siapa melihat apa

Setiap rekod menamakan laluan keletihan dan mendokumentasikan penjelasan alternatif yang telah diuji. Harganya berdasarkan jumlah siasatan, bukan bilangan pekerja: satu-satunya produk dalam rangkaian ini yang berharga mengikut kejadian.

Harga berdasarkan prevalens, bukan bilangan pekerja. Cara harga ditetapkan.

  • Your investigators

    The full record

    • Every answer and score
    • The alternative explanations tested
    • The fatigue pathway named
  • The employer

    One record per event

    • A structured, repeatable investigation record
    • Findings to feed back into roster, sleep and in-shift controls

Bukti

Apa yang dapat kami tunjukkan

Reka bentuknya memerlukan kedua-dua kehadiran keletihan dan kesilapan yang mempunyai ciri khas keletihan, serta menguji penjelasan alternatif sepanjang proses. Itulah yang menghalangnya daripada membuat kesimpulan sebab-akibat berdasarkan keletihan semata-mata.

Ia satu-satunya produk dalam rangkaian ini yang meneliti semua tahap, termasuk kecukupan jadual giliran, secara retrospektif selepas sesuatu kejadian.

Apa yang tidak dibuktikannya

Ia bersifat retrospektif. Ia tidak meramalkan kejadian, tidak menganggarkan saiz populasi, dan satu siasatan tidak membuktikan sesuatu corak. Ia bukan instrumen yang disahkan dan tiada dakwaan pengesahan dibuat untuknya. Rekod yang dihasilkan boleh tertakluk kepada pendedahan dalam prosiding undang-undang.

In practice

Rail · North America

A Class I railroad uses Was It Fatigue? to determine whether fatigue contributed to an incident or near miss.

Its investigators ask the same structured questions after every event, so each record assesses how likely it is that fatigue was present and that the error was the kind fatigue produces, and shows which other explanations were tested.

FAQs

Questions we’re often asked

Who uses it?

Your investigators, who open an assessment against a specific incident or near miss.

How does it avoid blaming fatigue by default?

It requires both the presence of fatigue and an error of the kind fatigue produces, and tests alternative explanations at every level before attributing an error to fatigue.

What does the finding look like?

A Fatigue Attributable Likelihood Score on a 1–5 band with the fatigue pathway named, which feeds back into roster, sleep and in-shift controls.

Is it a validated instrument?

No, and no validation claim is made for it. It is a structured, repeatable method. It is retrospective: it does not predict an event, and one investigation does not establish a pattern. Records produced are discoverable.

How is it priced?

On investigation volume, not headcount: it is the only event-priced product in the suite.

How is investigation data protected?

The platform is certified to ISO/IEC 27001:2022.

Laluan

Langkah seterusnya

Was It Fatigue? dan peraturan merentas 33 industri di Singapura

33 / 33

Menyokong kewajipan berjaga-jaga am anda

Lihat bagaimana Was It Fatigue? sesuai dengan peraturan dalam industri anda, dan apa lagi yang kami cadangkan untuk bermula.

Semua 33 industri

Penyelesaian lain yang berkait dengan Was It Fatigue?

Interested in Was It Fatigue? for your organisation?

Tell us a little about your organisation and which solutions you’re looking at, and our team will be in touch.

A Was It Fatigue? finding on a phone: a Fatigue Accident Likelihood Score of 3.2, between Possible and Likely, with how to record it.