> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/highway-project-master-workflow.md).

# Highway Project Master Template

A highway job is rarely one structure. Several bridges, walls and foundations sit on **one** alignment, cross **one** surveyed ground surface, answer to **one** set of contract documents and **one** set of geometric requirements.

The **Highway Project Master** is the project that owns those. Every structure project on the corridor pulls its data from here, and federates its 3D back — so checks that need the whole job, vertical clearance first, have something to measure over.

It deliberately holds no reports and no export. The master is a data container; deliverables belong to the structure projects that own them.

### How it fits together

* **Down** — the master publishes the alignment, terrain, documents and clearance criteria through **Cross-Project Data**, together with the coordinate system, local origin and project parameters.
* **Up** — each structure project comes back into the master through **External References**, so the master can see and measure the assembled corridor.

Start a structure project from the **Project 3D** sheet: *New Project…* creates it from a bridge template, links it in both directions and gives it this project's coordinate system in one step.


---

# 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.openbrim.org/templates/highway-project-master-workflow.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.