> ## Documentation Index
> Fetch the complete documentation index at: https://docs.energy.nlead.ch/llms.txt
> Use this file to discover all available pages before exploring further.

# n:lead Scheduling Bridge

> Deliver your portfolio data — n:lead handles the balancing groups

The scheduling bridge is the interface between your portfolio and the
German balancing groups n:lead operates for you as Balance Responsible
Party (BRP).

You deliver data. n:lead does the rest: aggregating the position per
control area, handing the open position to your trader for the EPEX
day-ahead auction, and submitting the balancing-group schedules to the
German TSOs.

```mermaid theme={null}
flowchart LR
    Y[Your portfolio data<br/>forecast or master + metered data] -->|API| B(n:lead Scheduling Bridge)
    B --> P[Position per<br/>control area]
    P --> T[Your trader<br/>EPEX day-ahead]
    P --> S[Balancing-group schedules<br/>to the German TSOs]
```

## What you send

<CardGroup cols={2}>
  <Card title="A portfolio forecast" icon="chart-line" href="/data-delivery#option-a-portfolio-forecast">
    Production and consumption per quarter-hour and control area, for one
    delivery day. The direct route if you already forecast your portfolio.
  </Card>

  <Card title="Or your customer data" icon="database" href="/data-delivery#option-b-master-and-metered-data">
    Market-location master data, metered data and rolled-out profiles — the
    bridge then builds the consumption forecast for you.
  </Card>
</CardGroup>

## Get started

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Send your first forecast in a few minutes.
  </Card>

  <Card title="Data delivery" icon="upload" href="/data-delivery">
    What to send, in which unit and resolution, and how often.
  </Card>

  <Card title="Background" icon="bolt" href="/concepts/domain-model">
    Control areas, balancing groups and quarter-hours — the market context.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    Endpoints, authentication and error semantics.
  </Card>
</CardGroup>

<Note>
  Everything downstream of your data — positions, trader handoff and TSO
  schedule submission — is operated by n:lead. You do not need to trigger
  it; it runs automatically once your data arrives.
</Note>