# Inspection Process

**Purpose of this step**\
The inspection process exists to document existing conditions so recommendations and pricing are based on observed facts rather than assumptions.

Inspection always precedes scope development and pricing.

**What is inspected**\
Depending on the project type, inspections may include:

* Roofing systems (surface condition, penetrations, flashing, ventilation indicators)
* Windows and doors (operation, frame condition, installation quality, visible water or air intrusion)
* Siding and exterior trim (material condition, attachment, moisture indicators)
* Gutters and drainage components (flow paths, attachment, discharge locations)
* Interior areas relevant to the concern (ceilings, walls, openings, attic access when applicable)

Only areas relevant to the proposed work are inspected.

**Visual vs. physical inspection limits**\
Inspections are non-invasive unless otherwise agreed in advance.

This means Cupcake does **not**:

* Remove finished materials
* Cut into walls or ceilings
* Perform destructive testing
* Guarantee the absence of concealed damage

If conditions cannot be verified visually, this uncertainty is documented rather than assumed.

**Use of photos, measurements, and documentation**\
During inspection, Cupcake may collect:

* Photographs of observed conditions
* Measurements required for material and labor planning
* Notes related to code, manufacturer requirements, or installation constraints

This documentation is used internally to develop an accurate scope and estimate.

**Why inspection precedes pricing**\
Pricing without inspection relies on averages, assumptions, or exclusions.

Cupcake does not price work this way.

Inspection ensures:

* The scope reflects actual conditions
* Recommendations align with manufacturer requirements
* Pricing accounts for complexity rather than surprise

This reduces change orders, disputes, and incomplete solutions.

**What comes next**\
Once inspection findings are reviewed, Cupcake determines whether a defined scope of work can be responsibly developed.

If so, scope development and pricing follow.\
If not, limitations are communicated clearly.


---

# 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://cupcake-home-improvements.gitbook.io/cupcake-home-improvements-documentation/our-process/inspection-process.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.