> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/tracking-progress.md). # Tracking progress 📈 Progress trackers are determinate indicators to represent where a user is in a journey. They inform the user what they have completed, where they are currently, and what's left to complete. * [ ] Determine your type of progress tracker This tracker can be visible in many ways — a loading bar, a pie chart, numbered steps. An experience with large sections would utilise numbered steps, or "milestones". One overall journey that has incremental steps would utilise a loading bar or pie chart better, perhaps with an overall percentage. * [ ] Create your states A progress tracker with milestones needs to show 3 states: * What's been completed * What's currently being completed * What hasn't been completed yet * [ ] Assemble your tracker Final touches can include grouping your sections by milestone, and deciding how you want to label each milestone (by number or by title). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/tracking-progress.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.