> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/engineering-metrics/deployment-metrics/time-to-build.md).

# Time to Build

Time to Build represents the average time taken by all the steps of each deployment to complete in the production environment.

By integrating with your CI/CD tool, Typo tracks all your production deployments across repos & workflows as configured by you. Then, the average time to run each step across all production deployments represents the Time to Build for the selected time.

<div align="left"><figure><img src="/files/nybBFm4v1hBsjkUxR0Ep" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/eyJx0Xv9K84u5eJhPCZq" alt=""><figcaption></figcaption></figure></div>

### **How does measuring time to build help in improving the Engineering teams' efficiency?**

Measuring time to build contributes to enhancing the efficiency of engineering teams in several ways:

1. **Performance Optimisation:** Tracking time to build helps identify bottlenecks and inefficiencies in the build process, enabling teams to optimize build pipelines and reduce build times.
2. **Streamlining Development Workflow:** Insights from deployment time metrics allow teams to streamline their development workflow by identifying areas where build times can be shortened or dependencies can be optimized.
3. **Enhancing Developer Productivity:** Faster deployment times enable developers to spend more time writing code and less time waiting for builds, leading to increased productivity and satisfaction.
4. **Meeting SLAs:** Monitoring deployment time metrics helps ensure that teams meet service level agreements (SLAs) for deploying changes, maintaining reliability, and meeting customer expectations.