> 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.md).

# 建築履歷

- [驗屋項目管理指南（建築履歷版本）](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/yan-wu-xiang-mu-guan-li-zhi-nan-jian-zhulli-ban-ben.md): 自訂與管理所有驗屋檢測標準。您可以依照實務需求，建立獨立的驗屋空間、設定對應的工種分類，並定義詳細的驗收規範，以確保驗屋人員的檢測標準一致。
- [驗屋訂單作業（新增與匯出）](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/yan-wu-ding-dan-zuo-ye-xin-zeng-yu-hui-chu.md): 介紹驗屋訂單的新增、管理與報告匯出。所有現場檢驗行動皆須由後台建立「訂單」。透過訂單內的戶別資料、圖面空間與派工邏輯，系統將產生對應的 App 檢測單，並將任務派發給指定的檢驗人員。
- [App 驗屋檢驗操作](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/app-yan-wu-jian-yan-cao-zuo.md): 驗屋人員使用App進行現場驗屋檢驗。系統將後台建置好的空間、圖面與驗收規範，轉化為行動裝置上的檢測單。驗屋人員在此完成狀態判定、拍攝檢測照片、圖面標註與最終的客戶簽認。
- [建築履歷 - App 新增照片／影片自動儲存至媒體庫設定](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/jian-zhulli-app-xin-zeng-zhao-pian-ying-pian-zi-dong-chu-cun-zhi-mei-ti-ku-she-ding.md)
- [線上圖文編輯工具](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/xian-shang-tu-wen-bian-ji-gong-ju.md): 使用者可直接將 PDF 轉換為圖片並進行線上編輯（包含標註、裁切與預存文字等），大幅節省將檔案下載至電腦進行繁雜編輯的時間；同時也提供圖片規格與張數的後台限制功能，以符合建築履歷報告的標準。
- [缺失改善管理](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/que-shi-gai-shan-guan-li.md): 本系統提供系統式紀錄與自動歸檔功能，讓各戶別的履歷資料與缺失狀況一目了然，方便搭配查驗單位（如：UL方）進行審查與跨部門共用作業。無論是使用 WEB 網頁端或 APP 行動端，皆可隨時進行查驗照片的檢視與狀態更新。
- [報告即時預覽/匯出](https://quteng.gitbook.io/ke-hu-wen-da-ji/jian-zhulli/bao-gao-ji-shi-yu-lan-hui-chu.md)


---

# 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.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.