> For the complete documentation index, see [llms.txt](https://cahf.gitbook.io/kenya-legal-policy-and-institutional-review/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cahf.gitbook.io/kenya-legal-policy-and-institutional-review/annex-c-laws-policies-regulations-governing-physical-planning/12.-physical-planners-registration-act-no.-3-of-1996.md). # 12. Physical Planners Registration Act, No. 3 of 1996 This statute seeks to provide for registration of physical planners Quick Link: . · Section 3 establishes the Physical Planners Registration Board which is responsible for regulating the activities and conduct of registered physical planners. The Board also sets and conducts examinations for purposes of registration of members; verifies qualifications and eligibility of persons seeking registration; and enquires into professional misconduct of members and institutes disciplinary action. · Sections 6, 7 and 8 provide for the issuance of a certificate of registration for registered planners and publication of a register containing the members. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://cahf.gitbook.io/kenya-legal-policy-and-institutional-review/annex-c-laws-policies-regulations-governing-physical-planning/12.-physical-planners-registration-act-no.-3-of-1996.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 `build a script that syncs our docs to a CMS` 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.