> For the complete documentation index, see [llms.txt](https://docs.buildertek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildertek.com/index.md).

# Walk Through Module

## Overview

The Walkthrough process is the starting point of the preconstruction phase and is designed to help you evaluate, estimate, and plan a project before it is officially created in BuilderTek.

Unlike traditional workflows, where a project must be created first, BuilderTek allows you to create and manage a Walkthrough independently or with a Project as soon as an opportunity is created. This gives your team the flexibility to begin gathering requirements, building estimates, requesting vendor pricing, and preparing customer proposals before committing to a full project setup.

Whether an opportunity comes from your website, a contact form, an email inquiry, a phone call, or an existing customer, you can immediately create a Walkthrough and begin documenting all project-related information in one centralized location.

The Walkthrough serves as the foundation for the entire preconstruction process. From a single record, your team can collect project details, request vendor bids, compare pricing, build customer-facing quotes, and track approvals. Once the customer approves the final proposal, the Walkthrough can be used to seamlessly transition into the project execution phase.

In this guide, you will learn how the Walkthrough process connects with other BuilderTek modules and how information flows between them to create a structured and organized preconstruction workflow. While the process involves multiple steps and modules, BuilderTek is designed to keep everything connected and easily accessible through quick links, related records, and intuitive navigation.

The goal of this user guide is to provide a clear, step-by-step process for managing a project from the initial inquiry through preconstruction planning, vendor pricing, customer approval, and project creation.

### What This Guide Covers

In this guide, you will learn how to:

* Create a new Walkthrough from an opportunity 
* Capture and organize project requirements 
* Create and send RFQs (Request for Quotes) to vendors for pricing
* Review vendor responses and compare submitted bids
* Award the selected vendor
* Generate a Purchase order
* Build a customer-facing Quote using vendor pricing and project costs
* Apply markup and profit margins to create the final customer proposal
* Share the Quote with the customer for review and approval
* Convert the approved Quote into a new project and move into the construction phase

By following this workflow, you can manage the entire process within BuilderTek while maintaining complete visibility, accurate records, and a seamless transition from planning to project execution.

### When to Use It

Use a Walkthrough when you need to:

* document a site visit or customer request;
* organize scope before a project is approved;
* estimate quantities and costs;
* request vendor pricing;
* prepare work for project execution.

![Walk Through record](/files/FOpoqTQRCr0s9NnP1XIg)

{% hint style="info" %}
A Walk Through can be linked to a BT Project, but it can also be created before the project record exists. This supports early estimating and preconstruction work.
{% endhint %}


---

# 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.buildertek.com/index.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.