Schedule an event

Create a one-time control event with targets, actions, and a time window

Texture supports two ways to create an event:

Path	What you do
Manual	Create and schedule the event yourself in Programs → Program Events.
Partner signal	A connected partner (for example Leap) creates the event; you review and release it. Signal events.

Before scheduling, confirm enrollment health and device readiness.

Event windows originate outside Texture

The date and time you enter should match the window from your grid operator signal or internal planning. Texture executes that window; it does not choose it for you.

Read the events list#

Open Programs → Program Events and select the program. Each row shows the event (date and number of actions), a status badge, an optional Signal badge when a partner created the event, the Scheduled Time (window in your local time), and a ⋯ menu for per-event actions.

Every event moves through a status lifecycle:

Status	Meaning
Draft	Created but not yet scheduled; still being configured. Hidden from the list until you turn on the Drafts filter.
Scheduled	Configured and queued to run at its window.
In Progress	Window is active; commands are going out.
Completed	Finished. Results are available in Reports.

The status filter chips (In Progress, Scheduled, Completed) are on by default; Drafts is off, so turn it on to find events you haven’t scheduled yet. A date range narrows long histories.

Partner-created events show a Signal badge. Signal events.

Create the event#

Open Programs → Program Events.
Select the program (Program Events requires a program).
Click Schedule Event.

Texture creates a draft and opens Configure Event.

Targets#

Choose who the event applies to:

Selection method	Targets
Enrolled sites	All sites currently enrolled in the program.
Tags	Only sites that carry the tags you select. Use this for a subset of the fleet.
Collection	A specific enrollment collection. Only available when collections exist for the program.

If the program has both batteries and EV chargers enrolled, pick the device type for this event (Battery or EV Charger). Actions and operating modes follow that choice.

Actions#

Click Add Action for each phase of the event. An event can include several actions in sequence. The overall event window is derived from the earliest start and latest end across those actions.

Schedule (per action)#

Field	Notes
Date	Required.
Start time / End time	Required. End must be after start, and the window must not be in the past. Actions cannot overlap.

Times follow your browser locale

Date and time fields use your local timezone. There is no separate program-timezone picker. Convert to the program’s operating timezone yourself before you enter times.

Battery control#

When the device type is battery:

Operating mode	Effect
Discharge	Send energy to the grid. Set Minimum battery reserve (percent) so discharge does not go below that state of charge.
Charge	Charge from the grid.
Idle	Hold: neither charge nor discharge.
Reset to Default	Return to normal pre-event behavior.

Charging control#

When the device type is EV charger:

Operating mode	Effect
Stop Charging	Prevent charging during the window.
Start Charging	Allow charging to resume.

Event preview#

As you add actions, the Event curve preview shows an illustrative shape of how the event would move fleet storage over the window (charge up, idle flat, discharge down). Treat it as a sanity check on the sequence, not a forecast of energy delivered.

Confirm#

When at least one action exists, every action has devices targeted, and timing is set, click Schedule Event and confirm. The event moves to Scheduled (queued to run at its window). Drafts you no longer need can be deleted from the events list or Configure Event page.

Signal events#

A signal event is created automatically by a partner integration (for example Leap) when it sends Texture an event notification. You don't create or configure these; the partner sets the window and targets. Your job is to review the event and release it when you're ready to dispatch.

Signal events appear on the Program Events list with a Signal badge. They arrive as drafts, so turn on the Drafts filter to find them if none appear in the default view. Signal events are read-only — the partner-set window and targets cannot be edited.

What to check before releasing#

Open the event to review:

Check	What to look at
Time window	Confirm the partner-set window matches the signal you received or are expecting.
Targets	Verify the device count and selection look right for this dispatch.
Device readiness	If you haven't already, confirm enrolled devices are connected: Check device readiness before an event.

Release the event#

When everything looks right, use Stage & Release — in the ⋯ menu on the list row, or as the primary button on the event detail page. The event moves from Draft to Scheduled and runs at its partner-set window.

If the window looks wrong or you're not ready to dispatch, leave the event in Draft and follow up with your partner contact before releasing.