> 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-b-laws-policies-regulations-governing-land-assembly-acquisition-title-tenure/3.-idle-land-taxation-policy-2018.md). # 3. Idle Land Taxation Policy 2018 The proposed Policy sought to levy takes on idle land to deal with speculation of land which leads to artificially high prices of land. Quick Link: · The Ministry of Lands sought to introduce the Idle Land Taxation Policy 2018 which would in effect have introduced property taxes on idle land.\[1] The policy had incentives to promote the use and productivity of land while discouraging hoarding of land for speculation purposes through a package of disincentives, thereby leading to an increase in land prices which in turn leads to escalation of house/property prices. · The Policy was however not progressed, since it was not introduced to Parliament (National Assembly and Senate). There is a need to revisit this.
*** \[1] < > --- # 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-b-laws-policies-regulations-governing-land-assembly-acquisition-title-tenure/3.-idle-land-taxation-policy-2018.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.