> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/access/local-governance-stack/property-tax/pt-master-data-templates/construction-type.md).
# Construction Type
## Introduction
The Construction Type refers to the list of Building construction types in the ULB limits considered for tax calculation.
DIGIT Property Tax system has certain pre-defined categories namely :
* Pucca
* Semi Pucca
* Kuccha
## Data Table
| Sr. No. | Construction Type Code\* | Construction Type (In English)\* | Construction Type (In Local Language)\* |
| ------- | ------------------------ | ----------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| 1 | PUCCA | Pakka Building With R.C.C. Roof or R.B. Roof | पक्का भवन, आर0सी0सी0छत या आर0बी0 छत सहित |
| 2 | SEMIPUCCA | Any Other Pakka Building | अन्य पक्का भवन |
| 3 | KUCCHA | Kuccha building that is all other building not covered in clauses (a) and (b) | कच्चा भवन अर्थात समस्त अन्य भवन जो (एक) और (दो) में अच्छादित नही है |
The data described in the above table is a sample.
## Attachments
> [](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation* ](https://egov.org.in/)*is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*
---
# 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.digit.org/local-governance/access/local-governance-stack/property-tax/pt-master-data-templates/construction-type.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.