> For the complete documentation index, see [llms.txt](https://quteng.gitbook.io/ke-hu-wen-da-ji/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/que-shi-gai-shan-guan-li.md).

# 缺失改善管理

本系統提供系統式紀錄與自動歸檔功能，讓各戶別的履歷資料與缺失狀況一目了然，方便搭配查驗單位（如：UL方）進行審查與跨部門共用作業。無論是使用 WEB 網頁端或 APP 行動端，皆可隨時進行查驗照片的檢視與狀態更新。

## 1. 缺失項目總覽與篩選

系統將所有檢驗項目集中管理，方便人員快速掌握整體進度與缺失狀況。

**操作步驟**：

1. 進入系統後台，先選擇指定的「組別」。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2Ftltu1gcMD5WjK7EtjXFd%2Fimage.png?alt=media&amp;token=9e7fcfc0-62f6-4ec3-b0e2-e462f37acd51" alt="" width="563"><figcaption></figcaption></figure>
2. 於列表中找到您要檢視的目標「戶別」，點擊該筆資料右側的「查看驗屋明細」按鈕，進入詳細頁面。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FFKIBHC1vpW9g34hTPo9C%2Fimage.png?alt=media&amp;token=a023f2e4-241a-4ff0-a59a-9ace3ea2f2bb" alt="" width="563"><figcaption></figcaption></figure>
3. 在明細列表上方，點擊下拉選單並選擇「顯示全部」。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FnE6oa4ngJYZH4V5ydFQA%2Fimage.png?alt=media&amp;token=a9dbd18d-fec9-4a44-8127-e19014cdb2fb" alt="" width="563"><figcaption></figcaption></figure>
4. 列表將會完整展開，讓您一眼看清所有項目的目前狀態，包含：「未檢驗」、「不適用」、「合格」以及「缺失」。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FE4cBCfPB92ugHjsSMvcE%2Fimage.png?alt=media&amp;token=f709ad1c-eda2-4782-85a3-c27af142fc93" alt="" width="563"><figcaption></figcaption></figure>

## 2. 檢驗狀態操作與留言板功能

檢驗人員可以直接在同一個作業畫面上完成所有的狀態判定與備註，大幅提升審核效率，且支援跨平台操作。

**操作步驟**：

1. **狀態判定**： 在明細列表中，找到對應的檢驗項目。檢驗人員可直接在「檢驗項目是否有缺失」的狀態欄位中，點擊切換該項目的檢驗結果（例如：標記為「未檢驗」、「不適用」、「合格」或「缺失」）。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2F45RwblfpC9g83mcDuBE2%2Fimage.png?alt=media&amp;token=c023d3c0-f45c-4cec-b134-bece471f74e1" alt="" width="563"><figcaption></figcaption></figure>
2. **留言板功能**： 針對有疑慮或需要特別說明的項目，可在列表最右側的「備註」欄位點擊，直接輸入留言或改善建議。這些紀錄將完整保存於系統中，方便後續追蹤。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FXsEUAJjQB43GN8aDYttT%2Fimage.png?alt=media&amp;token=f14986eb-553e-40f6-a184-f2907bcd21e3" alt="" width="563"><figcaption></figcaption></figure>
3. **跨平台作業**： 上述的所有檢視、狀態切換與留言操作，不僅能在 WEB 電腦端上完成，現場檢驗人員也可直接使用 APP 端進行同步操作，達到即時記錄與改善回報的目的。


---

# 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://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/que-shi-gai-shan-guan-li.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 `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.
