> For the complete documentation index, see [llms.txt](https://dualguard.gitbook.io/dualguard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dualguard.gitbook.io/dualguard/security-reviews/protocol-teams/scheduling-process.md).

# Scheduling Process

DualGuard keeps scheduling lightweight so teams can lock review time without freezing code weeks in advance. After an initial assessment and a preliminary quote, scheduling follows a straightforward flow.

**Step 1: Reserve a slot**

The protocol reserves a review slot with a **25% deposit and proposes a preferred start date.**

DualGuard confirms staffing and the start date shortly after reservation. If the proposed date is not feasible, DualGuard will suggest alternatives and work with the team to select a new start date.

**Step 2: Deposit flexibility**

If DualGuard cannot accommodate the originally proposed start date, DualGuard returns the deposit to the protocol team.

**Scheduling notes**

Teams can often schedule on short notice, especially for narrower scopes and update reviews. For larger or higher-stakes releases, earlier scheduling gives more flexibility on dates and staffing and reduces the chance of timeline compression close to launch.