> ## Documentation Index > Fetch the complete documentation index at: https://docs.assuric.com/llms.txt > Use this file to discover all available pages before exploring further. # Framework progress > How Assuric shows your progress on each framework, and how tasks link to requirements. **Quick summary** * Every framework has its own page showing how much is complete, how many tasks are left, and a summary of where each requirement stands. * A requirement's status follows its tasks, but you can set it yourself, and Assuric never marks one *Not applicable* for you. * One task can count towards requirements in more than one framework, so you complete it once. ## Open a framework Open a framework's page to see its overall completion and the tasks still to do, plus two key tabs: **Tasks**, the work you can edit, and **Requirements**, the standard's wording, which you can't edit. A framework's detail page, with the Tasks and Requirements tabs and the Requirements Summary panel highlighted ## The Requirements tab in detail The *Requirements Summary* panel shows the total number of requirements and how many are in each state. Requirements are grouped by the standard's sections, such as DTAC's *C1 - Clinical Safety*. Expand a section and each requirement shows its *Status* and a *Task Progress* count of its linked tasks that are complete. A single requirement row, with its Status field and Task Progress count highlighted A requirement can have its own *Owner(s)*, separate from whoever owns its tasks. Its status comes from those tasks: | Linked tasks | Status | | - | - | | All tasks *Completed* | *Met* | | At least one task *Completed* or *In progress*, but not all *Completed* | *Partially met* | | None *Completed* or *In progress* | *Not met* | You can also set *Status* yourself, so it won't always follow task completion. Assuric never sets *Not applicable*: mark a requirement yourself when it doesn't apply. Click a requirement to open its sheet, with its guidance, comments and notes. The guidance helps you decide whether the requirement applies, and if you're unsure, assume it does. ## Mapping across frameworks One task can satisfy several requirements, in one framework or across more than one, so you complete it once and it counts everywhere it's mapped. To see where the credit lands, open the task: its *Mapped Requirements* panel lists every framework and requirement it covers. The Mapped Requirements panel on a task sheet, listing the same requirement under both the CQC and CQC Registration frameworks, each with its own task count ## Related articles What a framework is, where to open it, and what's specific to some. The work itself: categories, states, and how to work through it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.