> For the complete documentation index, see [llms.txt](https://docs.softwaresecured.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.softwaresecured.com/planning/overview-page.md).
# Overview Page
An overview of each card and timeline step on the Portal Overview tab.
The **Overview** tab in space.vars.product\_name acts as a central dashboard for your pentest project. It gives you a real-time snapshot of where you are in the testing process, how your vulnerabilities are tracking against your SLAs, and a log of everything that has happened in the project.
## Project Timeline
This card gives you a full roadmap of your pentest, from the initial scheduling phase to the retesting period after report delivery. It is designed to make the pentest process as transparent as possible, so you are never left wondering what is happening with your pentest.
The active step displays contextual guidance and quick actions for your current stage. All other steps show a brief description of what to expect when you get there.
### Timeline Steps
{% stepper %}
{% step %}
### **Scheduling**
Confirm the dates for the test or reschedule as required. For more information, see [Pentest start date and rescheduling](/planning/kickoff-call/pentest-start-date-and-rescheduling.md).
{% endstep %}
{% step %}
### **Pentest Checklist**
Your checklist gives the engineers testing your environment the context they need for a thorough, well-scoped assessment. For more information, see [Pentest checklist](/checklist/pentest-checklist.md).
{% endstep %}
{% step %}
### **Active Testing**
Your environment undergoes a full suite of manual testing to uncover vulnerabilities across your agreed-upon scope. For more information, see [During the active pentest](/planning/during-the-active-pentest.md).
{% endstep %}
{% step %}
### **Testing End**
Active testing closes here. Your findings are then analyzed and compiled into your security report. Keep your environment active until the report is delivered.
{% endstep %}
{% step %}
### **Report Delivery**
You'll receive a detailed report covering every vulnerability found, its severity, and step-by-step remediation guidance. Want to walk through the results? Book a read-out call. For more information, see [Viewing and downloading reports and executive summaries](/reports-and-certificates/viewing-and-downloading-reports-and-executive-summaries.md).
{% endstep %}
{% step %}
### **Retest Window**
After you remediate, a retest confirms your fixes work and that nothing new was introduced along the way. When your active step is the Retest Window, the timeline updates as your retest progresses, from scheduling through checklist completion, active retesting, and report delivery. For more information, see [Retesting your vulnerabilities](/after-testing/retesting-your-vulnerabilities.md).
{% endstep %}
{% step %}
### **Your Next Pentest**
Regular pentests keep you ahead of new threats, cover your evolving product, and show customers your security maturity.
{% endstep %}
{% endstepper %}
***
## SLA Summary
This card shows a breakdown of your vulnerabilities by SLA status: compliant, at risk, or overdue. There are two views:
* **Simple:** An at-a-glance count by SLA status.
* **Detailed:** The same breakdown grouped by vulnerability severity.
For more information about SLAs and how to customize them, see [Service Level Agreements (SLAs)](/vulnerabilities/service-level-agreements-slas.md).
## Open Vulnerabilities
This card shows a bar graph of open vulnerabilities broken down by severity. You can filter this view by:
1. Compliance
2. Project Components
3. SLA Status
## Pentest History
Each row in this card displays a past pentest or retest, sorted by date with the most recent at the top. For each retest, you can see how many vulnerabilities were closed. For each pentest, you can see how many vulnerabilities were found and how many have been remediated.
## Project Activity
This card shows a history of events that have occurred in your project, such as retests being completed, pentest reports being delivered, and pentest checklists being submitted. The following events are tracked:
* Pentest & Retest Scheduling
* Pentest Checklist Submission
* Pentest & Retest Report Delivery
