> For the complete documentation index, see [llms.txt](https://compassly.gitbook.io/compassly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://compassly.gitbook.io/compassly-docs/core-modules/clients/programs/why-isnt-a-program-ready-for-mastery.md). # Why Isn't a Program Ready for Mastery **Page type:** Troubleshooting / FAQ\ **Status:** Draft (Noah Edit)\ **Owner:** Compassly Documentation Team\ **Last verified:** 2026-04-06 (Noah Edit: 2026-07-06)\ **Audience:** Super Admin, Admin, Supervisor, Clinician ## What This Section Covers This material covers why a Client Program did not achieve "Ready for mastery" status or why mastery progress appeared to reset. ## Common Reasons 1. **Baseline is not complete** * Mastery starts only after Baseline is calculated. If a Program was created with an "Automatic" Baseline information data set, then all initial observations will go towards calculating *Baseline value* until the days with observations matches the *Baseline period*. 2. **The required number of team members was not met** * The program may have observations logged for a day that meet the *Target* criterion, but if the number of team members doesn't match the *Team members* criterion, then the cycle will reset. The same team members do not need to appear every day. However, each day still needs enough team members to satisfy the *Team members* criterion. 3. **A day of observations did not meet criteria** * In order to achieve mastery, a Program must have enough successful days of observation to match the *Number of days* criterion. Days of observations that meet criteria do no have to be sequential, and if a day occurs without any observations then the current mastery cycle will continue on the next day of observations. However, if a day of observation that fails to meet criteria occurs during the cycle, mastery will be reset. 4. **Mastery criteria have not been established** * If mastery criteria have not been established for the Program, than observations will be logged, but will not contribute to Program mastery. Once criteria are established, previous obeservations will still not be considered. New observations must be logged. 5. **The mastery criteria were changed** * Any changes to a mastery criterion (*Target*, *Target value*, *Team members*, etc) will cause the mastery cycle to be reset. If you noticed changes to the mastery criteria or suspect that a Program has been altered, confirm with your supervisor. 6. **The Program was archived** * Archiving a Program doesn't erase it's observations, but it does reset the mastery cycle. If a Program was recently un-archived it might appear to have met all mastery criteria, but some observations might not be contributing to the current cycle. ## Tips for Troubleshooting 1. **Review the Client Program details, particularly the Baseline information and Mastery criteria.** * If *Baseline period* value exceeds the days of observations, or if it's value combined with the *Number of days* value exceeds the days of observations, then some days of observations are being used to calculate *Baseline value* and you haven't fulfilled the *Number of days* crtierion for mastery. * If Mastery criteria fields are empty, then observations are not being considered for mastery progress. Fill out the Mastery criteria (or have a qualified user do so) and continue to log observations. 2. **Review the Program's Data tracking & graph page.** * Scroll to the bottom of the page and review the table of observations. Compare values to the Mastery criteria, and confirm that there are a sufficent number of observations that satisfy the *Target*, *Team members*, and *Number of days* fields. Keep in mind that the successful days must be unbroken by a day of observations that failed to meet requirements. If any criterion is not met, then trace the observations back to the start of the current mastery cycle (the oldest day of observations that fulfilled requirements that does not have a failed day of observations following it) to assess how many more observations must be logged before "Ready for mastery" status is obtained. 3. **Consult your supervisor first.** * If you have confirmed that all Mastery criteria have been met and the Program status is still "In Progress", confirm with your supervisor that the Program has not been archived or reset recently. ## When To Contact Support If you have worked through the "Tips for Troubleshooting" section and cannot pinpoint the problem, reach out to the systems team on **Compassly Bugs / Feature Requests** Google chat to report the issue with details including but not limited to: * The Program Name * The Client Name * The exact dates for the observations you believe qualify the Program for mastery * Confirmation from your supervisor that to their knowledge the Program was not reset in any way ## Related Guides * [Understand Program Mastery](/compassly-docs/core-modules/clients/programs/understand-program-mastery.md) * [Master Program](/compassly-docs/core-modules/clients/programs/master-program.md) * [Master Programs in Batch](/compassly-docs/core-modules/clients/programs/master-programs-in-batch.md) * [Track Data and View Graph for Program](/compassly-docs/core-modules/clients/programs/track-data-and-view-graph-for-program.md) --- # 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://compassly.gitbook.io/compassly-docs/core-modules/clients/programs/why-isnt-a-program-ready-for-mastery.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.