> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/standards/edit-standards/occupations.md). # Occupations Occupations are just a type of Framework Standard. Occupations are just a type of Framework Standard. **Step 1** Create an Occupations Standard **Step 2** Add the Occupations you want **Step 3** Open the Occupation you want to work on and create Containment relationships between that occupation and the Competencies or Standards that satisfy that Occupation. *Note: Multiple Occupations can map to the same Standard. E.G. you may want to configure your data so that EVERY Occupation contains the “Maintains Safe Work Environment” Standard.* --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.shiftiq.com/help/standards/edit-standards/occupations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.