> 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/online-building-plan-approval-system-obpas/obpas-user-manual/residential-construction-permit-system-stakeholders-user-manual/submit-for-oc-plan-scrutiny.md).

# Submit For OC Plan Scrutiny

Click on the **OC Plan Scrutiny for new construction** option in the eDCR Scrutiny card.

![](https://lh3.googleusercontent.com/iEQHo0CZRkFr46KNgs_Mq62oVIm6g0PK3fpDUWwCcwQdVXp7bWT2L6A8IVZzrRZyfh4uzW6j60nu5hDCrFoLfipYViHX3yeirsHSuk4QX_4BI9RQS3oHsWJQkCYrQ_FrHlkpZDmW)

Check the list of required details to process the OC eDCR scrutiny.  

![](https://lh3.googleusercontent.com/UctwmGedCBxnVuZ1NPTI11M0A8u2JHeZx8rfRNoBD_yU1mzUidbrxabTXnG3sTS4AQ2r01mjo_OgdDOy4q9NQdk_20kHExcHIaVsUUTSmhqHF7P41knJmnV2zI5GkDh9uWvztkAj)

Enter the **Building Permit Number** and **Building Permit Date**. Click on the **Search** button

![](https://lh4.googleusercontent.com/sXsRMz5GBAHVS9wvmUoBH6XgZaDRtCPnndmg2dRZfAZkShXzNCKGYPnpRfhnltPRRhDSzExZOujJBNtDNQ2isOOrZW1mwuGoJm49d6KP8qoTWSY6OOzdxKr6xGlRuVZ9pyr2PB_c)

Your application details are visible on the screen. Review the details and then click on **Proceed for OC Scrutiny** button.

![](https://lh4.googleusercontent.com/3LxcTg4L_FGIf1lz9Cm6lLUU5abmavPD36QscRbvwAoEeyeLOgc7155TIcq0_j3j4cCoRhHeG2LYvwLyPW9pF8Wwf4DcCBwgXFW6xa1_CHM8KfenARiqQuTL_thrCPXQ9Uvza7qL)

Upload the OC Plan Diagram. Click on the **Submit** button.

![](https://lh5.googleusercontent.com/CcXwhqBKjcAN7LoJ_B4qJg30ATUR2H3v6NXBOBP46fxAK_Kb2mnhVMCrvdcqDDtNpY7e7S3wNntEk-OYrgK8Liby0WWJ2iPSGl_rVY8EOAhK1bpP-RO8DkWwdKAZAmQcBUfu5s_G)

The OC Building Plan eDCR Scrutiny process is successfully completed. Make a note of the Scrutiny Number. Click on the **Download Scrutiny Report** button to download and print the report.

![](https://lh3.googleusercontent.com/JZHdIjsQszhDyiJa8gwgbdS5lTbL7vV0eaLIfSPLvQymWwABNLwZEvJL9Zn3ef7er1QOi2KiuRFq4Kgpe4f8BUcxP4RiA2z6O41CL7R0L7OjwWA00IpF5vXjMhm37t3isDkrXZs4)

In case of any errors or lapses the plan scrutiny is rejected and the system displays a failure message. In such a case make the changes and resubmit for scrutiny.

![](https://lh5.googleusercontent.com/jHdc5Y-OzSUmdKMW-TBJgvdicPDJgmYrLYIOH1mCnLb9AGKxu0nrRYpo6wwVPgJ3BFmCSpJbebavfKlde4OnBNtrZkvm5_-dsWxUWcABDEJxDqMF1P2defZ1iJliQYSgQvDaRlwa)


---

# 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/online-building-plan-approval-system-obpas/obpas-user-manual/residential-construction-permit-system-stakeholders-user-manual/submit-for-oc-plan-scrutiny.md?ask=<question>&goal=<user_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.