> 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/yan-wu/yan-wu-liu-cheng/ru-he-cha-kan-yu-hui-chu-chang-shang-que-shi-pc-cao-zuo.md).

# 如何查看與匯出廠商缺失？（PC操作）

#### **路徑：** 

驗屋系統 > 廠商缺失 > 廠商缺失項目彙總

***

#### **操作方式：**

1. 前往 **廠商缺失項目彙總** 頁面：選擇建案後，進入 **驗屋系統 > 廠商缺失 > 廠商缺失項目彙總。**

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2F0JSaOdoAYpWtGij41TFy%2Fnote%20(39).jpg?alt=media&amp;token=c50d8aa6-f554-446c-a4b8-33d82da3f185" alt="" width="563"><figcaption></figcaption></figure>
2. 前往 **廠商缺失項目彙總細項** 頁面：點擊廠商列表右側 查看（![](https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FwiHIA4z5XMOiIo99fW8W%2F%E6%88%AA%E5%9C%96%202025-09-17%2011.37.24.png?alt=media\&token=356678c8-6b6f-4c93-b987-1627d7b917f2)）按鈕，畫面上會列出該廠商的所有缺失。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FkWcw7HMg0mgt1dfJcBjf%2Fnote%20(40).jpg?alt=media&amp;token=f3cb21a8-4af5-47ee-8865-f6bc67cd0bfb" alt="" width="563"><figcaption></figcaption></figure>
3. 匯出廠商缺失報告：提供PDF與Excel格式下載。
   1. 點擊 **廠商缺失項目彙總細項** 頁面右上方綠色的 **匯出PDF** 及 **匯出Excel** 按鈕
   2. 進行匯出設定，按照需求選擇以下條件，修繕狀態、棟別、項目、驗屋階段、修繕截止日
   3. 點擊視窗右下綠色 **確認送出** 按鈕，即可完成檔案下載。

      <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2F5ahzrGIleQ5N3zziyM9g%2Fnote%20(42).jpg?alt=media&amp;token=d925a708-6fbf-466c-a25b-0f702de528bc" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/yan-wu/yan-wu-liu-cheng/ru-he-cha-kan-yu-hui-chu-chang-shang-que-shi-pc-cao-zuo.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.