> For the complete documentation index, see [llms.txt](https://docs.archlogbook.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archlogbook.co/01-industry-basics/working-with-consultants.md).

# Working with Consultants

<div align="left"><figure><img src="/files/6qP3oRJWjDWTYDIu6DT9" alt="" width="375"><figcaption></figcaption></figure></div>

An architect typically works with a variety of external consultants throughout the design and construction process of a building project. These consultants may include structural engineers, mechanical engineers, electrical engineers, and other specialists who provide specialized expertise in areas such as acoustics, lighting, and fire protection.

The architect is also responsible for coordinating the work of these consultants, **ensuring that their designs are compatible** with the overall design concept and that they meet all necessary codes and regulations.

{% hint style="info" %}
**Note:** Specialist design work needs to be checked by respective Qualified Person, who may or may not be the Architect. The Architect shall not be liable for any negligence on part of the Specialist.
{% endhint %}

*Learn more:*

[Specialist Design Items](/01-industry-basics/specialist-design-items.md)

Most importantly, the architect also acts as the primary point of contact between the consultants and the client, and is responsible for communicating the progress and any issues that arise during the project.


---

# 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://docs.archlogbook.co/01-industry-basics/working-with-consultants.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.
