> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/schedule.md).

# Scheduling

## Overview

The Schedule keeps you on top of all your projects: historical, present and future. It's a calendar of your testing, showing projects, project requests and retest rounds, so every test window and retest sits on one schedule.

All projects are colour-coded, so you can quickly identify their status. You can view the schedule by month, week or day, look back in time to see historical projects, or look ahead to plan for upcoming ones.

Projects, project requests and retest rounds all appear on one calendar. View it by month, week or day, filter each source, and save the views you use. Project Coordinators and Administrators can also look up other users' schedules to plan who does what.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FHk4PU0Bp1sKlKUxpoRDH%2Fschedule-at-a-glance.svg?alt=media&amp;token=1f2d817c-3bb8-4456-b50a-00887f7fe306" alt=""><figcaption></figcaption></figure>

## Why it matters

* **See clashes before they happen.** Overlapping tests, retests and requests are easy to spot on one calendar.
* **Plan people, not just projects.** Project Coordinators and Administrators can see each person's schedule, so work goes to people who are free.
* **Know what's coming.** Project requests on the calendar show testing that's planned but not yet approved.
* **Keep the history.** Past projects stay on the schedule, which helps with planning repeat tests and answering "when did we last test this?"

## Who uses it

| Who                                         | To                                                          |
| ------------------------------------------- | ----------------------------------------------------------- |
| **Project Coordinators and Administrators** | Allocate testers, balance workloads and plan upcoming tests |
| **Testers**                                 | See which projects and retests they're on, and when         |
| **Clients and stakeholders**                | See when their testing and retests are scheduled            |
| **Security and programme managers**         | Plan the testing programme across the year                  |

Every application role can see their own projects on the schedule. Only Administrators can see all projects. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## Use the schedule

### View your schedule

1. Open **Schedule**.
2. Choose **Month**, **Week** or **Day**.
3. Move back in time to see historical projects, or forward to plan for upcoming ones.

All projects are colour-coded, so you can quickly identify their status.&#x20;

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fd02yuLMIHEfPlT7vzY0q%2FScreenshot%202026-11-10%20at%2010.55.32%E2%80%AFam.png?alt=media&amp;token=4eb9d5d2-36aa-494e-b591-7e7d6282b90e" alt=""><figcaption></figcaption></figure>

### Open a project from the calendar

Click a project or project request on the calendar to see key information about it.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FVbz1f3dVUUWF5wCL21C6%2FScreenshot%202026-11-10%20at%2010.56.08%E2%80%AFam.png?alt=media&amp;token=68d3adb7-e074-418d-9f90-a5519a270b0a" alt=""><figcaption></figcaption></figure>

From here, you can go to the `Project Overview` or `Project Tracking`.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FLP1uWncbsMe6Lg80DWeK%2FScreenshot%202026-11-10%20at%2010.57.10%E2%80%AFam.png?alt=media&amp;token=521fb9d2-29a3-4ff4-bdf2-a2f16b042429" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FuDGXOi6IddF5vod55Aw9%2FScreenshot%202026-11-10%20at%2010.57.21%E2%80%AFam.png?alt=media&amp;token=1108c238-a332-4ad5-acd0-a5bcb41423bd" alt=""><figcaption></figcaption></figure>

## What's on the calendar

The calendar shows three sources: projects, project requests and retest rounds.

### Project requests

You can filter the calendar on project requests, to help plan your upcoming tests. Requests show testing that's been asked for but not yet approved, so you can see what's coming and who might be needed. See [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project).

### Retest rounds

Your projects calendar shows retest rounds alongside projects and project requests, so every test window and retest sits on one schedule. You can see each round's title and status on the calendar, and filter retest rounds by project. See [Retesting](https://support.attackforge.com/app/getting-started/retesting).

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FkrVRuc2mcUZ25EGvyKzh%2Fimage.png?alt=media&amp;token=821e6649-17e3-4052-b86a-81ae2a9c6356" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fl9IPWQgBbcdpBOLpm3Oz%2Fimage%20(1).png?alt=media&amp;token=05f71c52-912b-4b60-917b-d4c321f2ca84" alt=""><figcaption></figcaption></figure>

## Manage a busy calendar

| Feature                     | What it does                                                                                                   |
| --------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Busy days, tidied**       | Collapse each day to a few events, with a "+ more" popover, or show them all. Jump back to today in one click. |
| **Filters for each source** | Filter projects, project requests and retest rounds separately                                                 |
| **Saved calendar views**    | Save your sources, filters and event limit as a custom view. Your existing calendar views carry over.          |

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FeQTB2Tf8LGCrvjZEFIlH%2FScreenshot%202026-11-10%20at%2011.03.19%E2%80%AFam.png?alt=media&amp;token=a3fe9d53-24f8-4731-85ca-76f94995eda6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FSONBd3xXulXoT6okLGLm%2FScreenshot%202026-11-10%20at%2011.03.43%E2%80%AFam.png?alt=media&amp;token=26ac5f79-ba95-46ac-bdf3-24c4bb093f42" alt=""><figcaption></figcaption></figure>

See [Custom views](https://support.attackforge.com/app/getting-started/custom-views) for more on saving views.

## Allocate resources

As a Project Coordinator or Administrator, you can view the schedules of other users, to help with resource allocation. For example, before you assign a new test, you can check who's free that week.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fs02hJWIq9Z2MOouyN4kH%2FScreenshot%202026-11-10%20at%2011.04.46%E2%80%AFam.png?alt=media&amp;token=f38e7f5a-6de3-4a5a-afd4-6226c0ab53e0" alt=""><figcaption></figcaption></figure>

1. Look up a schedule for a user, or filter by role.
2. To narrow it further, filter by the roles the user is assigned on projects. For example, show everything where this person was the *Pentest Lead*.
3. Switch to the list view to see more information about those projects.
4. Export the information to CSV to work with the data offline.

## Tips

* **Check the schedule before assigning work.** Look up the person's schedule, or filter by role, to see who's free.
* **Turn on project requests when planning.** They show testing that's coming but not yet approved.
* **Keep retests in view.** Retest rounds take people's time too, so plan them alongside projects.
* **Save the views you use often**, such as one for your team's projects and retests.
* **Collapse busy days** to keep the calendar readable, and use "+ more" to see the rest.
* **Export to CSV** for capacity planning or reporting outside AttackForge.

## FAQ

**What does the schedule show?** Projects, project requests and retest rounds, past, present and future.

**Can I see other people's schedules?** Yes, if you're a Project Coordinator or Administrator. You can look up schedules for each user, or filter by role.

**Can I see only the projects where someone was the Pentest Lead?** Yes. Filter by the roles the user is assigned on projects.

**Can I get the schedule into a spreadsheet?** Yes. Switch to the list view and export to CSV.

**Are retests on the calendar?** Yes. Retest rounds appear alongside projects and project requests, with their title and status.

## Related pages

* [Projects](https://support.attackforge.com/app/modules/projects)
* [Requesting a project](https://support.attackforge.com/app/getting-started/requesting-a-project)
* [Retesting](https://support.attackforge.com/app/getting-started/retesting)
* [Custom views](https://support.attackforge.com/app/getting-started/custom-views)
* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.attackforge.com/app/modules/schedule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.