> For the complete documentation index, see [llms.txt](https://guide.mymodone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mymodone.com/how-do-i.../use-the-dashboard/modone-culture-index.md). # modONE Culture Index The modONE Culture Index (the "MCI") is a monthly snapshot of overall program performance.

modONE Culture Index Tile

The modONE Culture Index (MCI) is a single monthly score, from 0 to 150, of how healthy your safety program is. It updates on the 1st of each month. It helps to be clear about what the MCI measures. It scores the *leading indicators* of a safety program — how consistently you communicate, how engaged your team is, how well they comprehend the content, and, on the Pro plan, how you keep up with inspections. These are the things modONE can observe directly, and the things you can act on. The MCI is a measure of what your program is *doing* — the habits that build a strong safety culture — not a measure of injury or claim outcomes. That's what makes it useful month to month: it tracks the work you control and rewards consistency, rather than waiting on results that take much longer to show up. The MCI also lets you benchmark. It shows how your program's activity and engagement compare with other modONE customers, so you can see where you stand and how much room there is to climb. ### Reading your MCI tile MCI updates on the 1st of each month. From top to bottom, the tile shows: * **Performance tier** — Emerging, Advancing, Performing, or Outperforming. * **Standing among modONE customers** — the share of customers in your tier and your rank within it. * **Points** — points earned versus points available this month. * **Three gauges** — Safety Program, Engagement, and Inspection. Inspection appears on the Pro plan only. Your lowest gauge is usually the fastest place to gain points. Open **MCI Details** to turn the score into a checklist of completed items and available points, then pick one or two actions to work on. ### MCI Pillars Your score is built from three pillars. Knowing what each one reflects tells you where to focus. #### Safety Program Reflects a consistent, proactive program — communicating regularly and keeping your safety content active rather than sporadic, so the fundamentals stay in place month to month. #### Engagement Reflects team members actively taking part: opening content, responding, completing quizzes, and giving feedback. This is the pillar your frontline crew moves directly. #### Inspection Reflects keeping up with audits and compliance checks. This pillar appears on the Pro plan. Each gauge on your tile maps to one of these pillars, so your lowest gauge points to the pillar with the most available points. ### Performance Tiers MCI performance falls into one of four tiers. They're maturity bands — most organizations begin in the lower tiers and climb as their program habits become routine:\ \ **Emerging (0-30 points)**\ Early stage of development with room for growth.\ \ **Advancing (31-75 points)**\ Progressing and showing potential, but there's still room to improve.\ \ **Performing (76-120 points)**\ Performing well, meeting expectations, and demonstrating a strong safety culture.\ \ **Outperforming (121-150 points)**\ Excelling and achieving at a high level beyond typical expectations. ### Improving your MCI The MCI is built to be improved, not just watched. Start with your lowest gauge — that's usually where the most points are available. Open **MCI Details** to see the score as a checklist of completed items and points still on the table, pick one or two to work on, and your progress shows up in next month's update on the 1st. Steady, small improvements compound: the tiers reward consistent habits more than one-time pushes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guide.mymodone.com/how-do-i.../use-the-dashboard/modone-culture-index.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.