# Scope Development **Purpose of this step**\ Scope development translates inspection findings into a clearly defined plan of work.\ The scope exists to document *what will be done, how it will be done, and what is included or excluded* before pricing is finalized. **How inspection findings translate into scope**\ Inspection documentation is reviewed to determine: * Required work to address observed conditions * Installation methods aligned with manufacturer requirements and applicable codes * Access, sequencing, and protection considerations * Constraints that affect material selection or labor approach Only conditions that were observed or reasonably inferred are included in the scope. **Repair vs. replacement scopes**\ Scope recommendations may vary depending on condition, risk tolerance, and long-term goals. * **Repair scopes** address specific, isolated issues and assume surrounding materials are serviceable * **Replacement scopes** address system-level performance, age, or compatibility concerns When multiple responsible paths exist, they may be presented as options rather than a single directive. **How options may be presented**\ If applicable, Cupcake may present more than one scope option to reflect different priorities, such as: * Performance vs. cost * Short-term remediation vs. long-term solution * Material or system alternatives Options are presented to inform decision-making, not to force selection. **Assumptions and limitations (disclosed)**\ All scopes are developed based on visible conditions and non-destructive inspection. Unless stated otherwise, scopes assume: * No concealed damage beyond what was observed * Existing structures meet minimum conditions required for the proposed work * Manufacturer specifications will govern installation methods Any assumptions made due to limited visibility are disclosed rather than implied. **What this step does not do**\ Scope development does not: * Require commitment * Guarantee unseen conditions * Substitute for structural or engineering evaluations **What comes next**\ Once the scope is defined and documented, pricing can be developed accurately and transparently. --- # 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/scope-development.md?ask= ``` 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.