> For the complete documentation index, see [llms.txt](https://docs.moasure.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moasure.com/en/moasure-lx1/measure-with-moasure-lx1/lx1-property-walkthrough.md). # LX1 Property Walkthrough Follow Simon as he uses Moasure LX1 to measure a property from the first room through to the completed floor plan. Across this five-part series, you'll see how the techniques and workflows covered in this User Guide are applied in a real property, including measuring rooms, connecting additional rooms, capturing doors, windows, stairs and wardrobes, working around obstacles, and reviewing the completed floor plan. ### Part 1 – Measuring the Living Room {% embed url="" %} Start with the first room and see the basic LX1 measuring workflow in practice, including Pace, Placement and Rotation. ### Part 2 – Measuring the Hallway {% embed url="" %} Continue into the hallway, including connecting the new room, capturing a closed door and measuring the staircase. ### Part 3 – Measuring the Office {% embed url="" %} Follow the measurement into the office, including a built-in wardrobe / closet, working around obstacles and using a temporary pause point. ### Part 4 – Measuring the Kitchen {% embed url="" %} Continue into the kitchen and see two different methods for capturing windows. ### Part 5 – Review and Edit Your Floor Plan {% embed url="" %} Review the completed multi-room floor plan and see how it can be edited and refined in the Moasure app. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.moasure.com/en/moasure-lx1/measure-with-moasure-lx1/lx1-property-walkthrough.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.