# Working with Project Briefs

<div align="left"><figure><img src="https://1953986935-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fa6RFTjyYzjLt399Tjt7N%2Fuploads%2FZ5n8BnGNrmLCj61i42lI%2FProject%20Brief.png?alt=media&#x26;token=55652d39-84a1-4032-af1e-cc70fc6c0daa" alt="" width="188"><figcaption></figcaption></figure></div>

Architects need to look out for the following in project brief from clients:

1. **Project scope and objectives**: Overall goals and objectives of the project, including the type and size of the building, the number of floors and rooms, and any specific features or amenities that are required.
2. **Site information**: Details about the location of the building, including the address, zoning regulations, and any environmental or historical considerations that may affect the design.
3. **Budget and timeline**: Established budget for the project and timeline for completion, including milestones for each phase of the project.
4. **Design requirements**: Specification of any design requirements or preferences that the client has, such as architectural style, materials, and color palette.
5. **Approval and permitting process:** Outline of the approval and permitting process that will be followed, including any relevant city or state codes and regulations.
6. **Consultants or contractors:** List the consultants or contractors that will be working on the project, including architects, engineers, and builders.
7. **Client's contact information**: Look out for the client's contact information, so that the architect can reach out with any questions or concerns throughout the project

List is non-exhaustive and can be added on if there is need to have more constraints and criteria of successful design and construction of the building.


---

# Agent Instructions: 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:

```
GET https://docs.archlogbook.co/01-industry-basics/working-with-project-briefs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.