⚠️ Select your experience
The steps to view and understand framework readiness depend on your interface version. Select a link to skip to the instructions for your version.
Customers who joined Drata on or after Feb 24, 2026 are automatically on the New Experience.
Instructions for the New Experience ⬇️
What framework readiness shows
Framework readiness shows the current status of each in-scope framework in your environment. It reflects whether the requirements and controls in that framework meet the conditions for being Ready.
Use readiness to:
Track progress toward compliance
Identify gaps in evidence or approvals
Focus efforts on what's needed to reach audit readiness
Readiness is layered:
A framework is ready when its requirements or controls are ready (depending on how you choose to measure)
A requirement is ready when all its mapped controls are ready
A control is ready when all of its readiness conditions are met
View framework readiness
You can measure readiness by Controls or Requirements:
Controls (default): Based on the number of in-scope controls that are Ready
Requirements: Based on the number of in-scope requirements that are Ready
To switch the readiness view:
Go to Frameworks.
Use the Controls / Requirements toggle at the top of the page.
Choose how you want to measure readiness: Controls or Requirements.
Your selection applies only to your user account; it does not affect other users.
When a requirement is Ready
A requirement is considered Ready when all of its mapped controls are ready. If any mapped control is not ready—or if there are no mapped controls—the requirement is Not Ready.
Only in-scope requirements contribute to framework readiness. Out-of-scope requirements are excluded from readiness calculations.
When a control is Ready
A control is considered Ready when it meets all required approval conditions, its mapped evidence is valid, and it is in scope for at least one in-scope requirement.
SOC 2 readiness
SOC 2 readiness uses the same readiness logic but is often more sensitive to how you choose to measure. When measuring by Requirements, a requirement is Not Ready if any of its mapped controls are Not Ready, which can significantly lower the score. Use the toggle on the Frameworks page to compare both views.
Instructions for the Classic Experience ⬇️
Framework readiness shows the current status of each in-scope framework in your environment. It reflects whether the requirements or controls that make up a framework meet the conditions for being "ready."
Use the readiness status to:
Track progress toward compliance.
Identify gaps in evidence or approvals.
Focus your efforts on what's needed to reach audit readiness.
Readiness is dependent on the others:
A framework is ready when its requirements or controls are ready.
A requirement is ready when all its mapped controls are ready.
A control is ready when all conditions for readiness are met.
SOC 2 Readiness
SOC 2 readiness is a critical part of preparing for compliance with the SOC 2 standards. It involves tracking and evaluating the readiness of your organization's controls or requirements to ensure they meet the necessary Trust Services Criteria (TSC). The readiness score indicates how prepared your organization is to successfully complete a SOC 2 audit.
View Framework Readiness
You can measure readiness by Controls or Requirements.
Controls (default): Readiness is based on the number of in-scope controls that are ready.
Requirements: Readiness is based on the number of in-scope requirements that are ready.
Use the toggle at the top of the Frameworks page to switch between these two options.
When is a Requirement Ready
A requirement is considered ready when all of its mapped controls are ready.
Common Challenges and Troubleshooting Readiness Issues
Users sometimes encounter specific challenges when tracking framework readiness, particularly with SOC 2 compliance.
Why Does My Readiness Score Show 0%?
This issue often arises when using the requirement-based measurement. Since all controls mapped to a requirement must be ready for the requirement to be considered ready, even slight progress might not reflect in your score unless all related controls are marked as ready. You can troubleshoot this issue by switching between control-based and requirement-based perspectives to understand the discrepancy.
Actions Based on Readiness Status
Follow these steps to resolve and understand readiness discrepancies:
Verify Dependent Evidence: Ensure all controls tied to a failing requirement have valid evidence, which may include monitoring tests, ready policies, and manually uploaded evidence.
Adjust Viewing Lens: Go to the Frameworks Tab in Drata and switch between "Control" and "Requirement" readiness percentages to identify focus areas.
Review Metric Dependencies: Analyze the "Readiness Summary" in individual framework details to locate incomplete or failing requirements.