> For the complete documentation index, see [llms.txt](https://archi-here.gitbook.io/construct-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archi-here.gitbook.io/construct-guide/contractor/announcement/result.md).

# 입찰 결과

입찰이 마감되면 의뢰인이 선정한 미팅 대상자 여부를 즉시 확인할 수 있습니다.

### 미팅 대상자 선정 결과 확인

프로젝트 대시보드 및 상세페이지에서 '미팅할 건설사'로 선정되었는지 알 수 있습니다. 

<figure><img src="/files/zSOmc5Mah21UNak93D0G" alt=""><figcaption></figcaption></figure>

#### 선정된 건설사

의뢰인의 연락처를 열람할 수 있으며, 상호 간의 일정 조율을 통해 대면 미팅을 진행하게 됩니다.&#x20;

#### 미선정된 건설사

해당 프로젝트의 미팅 대상에서는 제외되지만, [경쟁사 입찰 보고서](/construct-guide/contractor/announcement/report.md)를 통해 탈락 원인을 분석하고 다음 입찰을 준비할 수 있습니다.&#x20;


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://archi-here.gitbook.io/construct-guide/contractor/announcement/result.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.