# Send the notice to Limited Partners

Once you have [approved the allocations](/for-general-partners/allocate.md), Gildi has generated a PDF notice for every LP. This page explains how to preview those notices, send them, and handle delivery issues.

## What gets sent to each LP

Each LP receives two artifacts simultaneously:

1. **Email notification** — a short, scannable email with the call amount, due date, and a download link for the PDF. Sent via the fund's configured email identity.
2. **Notice PDF** — the legal capital call document. Attached to the email and stored permanently in the LP's portal under **Documents → Capital Call Notices**. Conforms to ILPA Capital Call Notice Standard 2.0.

The PDF includes:

* Fund name and fund number
* Notice date and drawdown due date
* Total call amount (itemised by investment / fee component for combined calls)
* LP-specific: commitment, share %, gross allocation, adjustments, net call amount
* Payment instructions (bank account, IBAN/SWIFT, reference to include in the wire)
* Audit reference (Gildi call ID)

## Preview a notice before sending

> *\[Screenshot: the Allocations table on an approved call, with the PDF preview icon highlighted on one LP's row]*

To verify the PDF for one LP before sending to everyone:

1. On the approved call page, find the LP in the **Allocations** table.
2. Click the **Preview PDF** icon (⤓) on their row.
3. The PDF opens in a new tab. Review the figures and payment details.

If you spot an error, click **Revert to Draft** on the call page. This unlocks the call for editing. Note: reverting deletes the queued PDFs — they will be regenerated when you re-approve.

## Send all notices

> *\[Screenshot: the "Send notices" confirmation dialog showing the number of LP notices, email addresses, and the Confirm send button]*

When you are satisfied with the notices:

1. Click **Send notices** on the approved call page.
2. A confirmation dialog shows:
   * Number of LP notices to be sent
   * Email addresses on file (one per LP entity)
   * Send time (immediate, or scheduled — see below)
3. Click **Confirm send**.

Gildi sends all emails in a single batch. The call status changes to **Sent**. Each LP's portal immediately shows the call under **Upcoming payments**.

## Scheduled send

If you want the notices to go out at a future date and time (e.g., early morning on the first day of the notice period), toggle **Schedule send** before clicking **Confirm send**. Enter the date and time in the fund's local timezone. Gildi queues the send and shows **Scheduled** status on the call.

You can cancel a scheduled send at any time before it fires.

## Resend a notice to a specific LP

If an LP reports not receiving their email:

1. Go to the call's **Delivery** tab.
2. Find the LP in the delivery status table.
3. Click **Resend** on their row.

This sends a fresh copy to the email address on file. It does not change the notice PDF content or the LP's portal record.

## Delivery status

The **Delivery** tab shows the send status for every LP:

| Status        | Meaning                                                               |
| ------------- | --------------------------------------------------------------------- |
| **Delivered** | Resend server confirmed acceptance.                                   |
| **Opened**    | LP opened the email (requires tracking pixels not blocked).           |
| **Bounced**   | Email address rejected the message. Update the LP's email and resend. |
| **Pending**   | In queue (within the first few minutes after send).                   |

A bounce does not affect the LP's legal obligations — the drawdown due date still applies. It is the GP's responsibility to ensure the LP receives the notice; Gildi surfaces bounces prominently so you can act immediately.

## After sending

Proceed to [Reconcile payments](/for-general-partners/reconcile.md) once the drawdown due date approaches.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gildi.io/for-general-partners/send-notice.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.