> 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-one-and-moasure-2-series/your-moasure-device/measuring-technique/master-pace.md).

# Master Pace

Moving at the correct pace is one of the most important techniques for achieving accurate measurements with Moasure.

Watch this tutorial to learn how to move confidently between pause points, use the timer bar and audio feedback to guide your pace, and understand why measurement error increases with **time**, not **distance**.

{% embed url="<https://vimeo.com/1208748056?fe=ci&fl=sv&share=copy>" %}

## Why Pace Matters

Moasure measures continuously while you move. Each time you pause and place the device completely still, it captures a measurement point. We refer to these locations as pause points.

Moasure's accuracy depends on **how long the device remains in motion**, not simply how far it travels.

**Think about time rather than distance.** Whether your next pause point is close by or further away, reaching it sooner will generally produce a more accurate result because there is less time for measurement error to accumulate.

The goal isn't to rush. It's to move confidently between pause points, then place the device quickly but gently before continuing.

To achieve the best results:

* **Walk at a steady, confident pace.** Move briskly without rushing.
* **Rotate smoothly as you turn.** Avoid sudden or jerky movements.
* **Pause regularly.** Place the device while the timer remains in the **green zone**, or no later than the **amber zone**.

***

## Understanding the Timer Bar

The timer bar provides both **visual** and **audio** feedback to help you know when it's time to capture your next pause point.

#### 🟢 Green (0–6 seconds)

This is the ideal timing window. Aim to place the device while the timer remains in the green zone whenever possible.

#### 🟠 Amber (6–8 seconds)

You're approaching the recommended limit. Prepare to pause and place the device.

#### 🔴 Red (8+ seconds)

You've exceeded the recommended timing. Continuing to measure in the red zone increases the likelihood of inaccurate measurements. **Pause immediately.**

#### Audio Feedback

* A steady ticking sound begins as soon as you start moving.
* After approximately **6 seconds**, you'll hear beeping to remind you to prepare to pause.
* After approximately **9 seconds**, the beeping becomes faster, indicating that you've moved well beyond the recommended timing.

{% hint style="info" %}
**For the most accurate results, place the device while the timer remains in the green zone, or no later than the amber zone.**
{% endhint %}

***

## Correct Pace

<figure><img src="https://3108400965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH1SckI7Noi5Ipj4x33R7%2Fuploads%2FAfhhlMLQEjjEqBWYvrSm%2FPace%20GIF.gif?alt=media&amp;token=5d39be9e-3f73-41fc-a5d7-7c2dbc59cb84" alt=""><figcaption></figcaption></figure>

The example above shows the difference between moving at a confident pace and moving too slowly.

Walking confidently helps you reach the next pause point while the timer remains in the **green zone**.

Moving too slowly causes the timer to enter the **amber** and **red** zones, increasing the likelihood of measurement error.

***

## Longer Measurements

You don't need to complete the entire measurement within **8 seconds**.

Instead, simply break longer measurements into shorter sections by capturing regular pause points before continuing.

For example, if a section would take around **10 seconds** to walk, split it into two shorter movements with a pause point between them.

Think of each pause point as a marker along your measurement. Regular pause points help maintain accuracy over longer distances.

***

## Measuring Around Obstacles

Don't worry if you can't reach your next pause point within the recommended timing.

Simply pause before the obstacle, then continue measuring once you've moved around it.

You can capture as many pause points as needed to maintain accuracy.

{% hint style="info" %}
**Tip:** If you don't want these additional pause points to appear in your drawing, you can remove or ignore them afterwards. See [**Ignore Line**](/en/moasure-one-and-moasure-2-series/measure-and-edit/understand-path-types.md) and [**Ignore Tool**](/en/moasure-one-and-moasure-2-series/measure-and-edit/master-edit-tools/ignore.md)  for more information.
{% endhint %}

***

## Key Takeaways

* **Measurement error increases with time, not distance.**
* Move confidently between pause points - don't move slowly.
* Aim to pause while the timer remains in the **green zone**, or no later than the **amber zone**.
* Break longer measurements into shorter sections with regular pause points.


---

# 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-one-and-moasure-2-series/your-moasure-device/measuring-technique/master-pace.md?ask=<question>&goal=<user_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.
