# What a schedule checks

> What Geenius Newsletter checks before a send is scheduled: a current approval, the audience, the plan, the domain and a person.

Source: https://newsletter.geenius.io/docs/what-a-schedule-checks/

Only a signed-in person can schedule a send. Your own AI can prepare the issue and can pause or cancel a send. It cannot approve or schedule one.

## What has to be true

- The issue has an approval, and that approval is for the issue as it is now. An edit after the yes voids it.
- The audience is at most 10 % larger than the approved count. An approval of 100 still covers 110 readers. It does not cover 111. A larger jump needs a new approval.
- The workspace is not stopped.
- The plan still has room for this month's mails. The monthly limits are early-access placeholders.
- The sender identity is complete. See [Sender identity](/docs/sender-identity/).

On a live send, the publication's own sending domain also has to be verified. During early access, sends run in test mode and no mail leaves the app. A live send is not what early access does.

## After you schedule

The audience is fixed when the send starts. Each address is checked again for suppression and for still being active. An edit, a revoked approval or archiving the issue after you scheduled it cancels the send.

A test, sent before this, goes only to the signed-in account's own address, at most five times an hour, and is recorded. It is not the schedule.