Neural LogDocumentation
Logs

Weekly Scheduling: Distribute Spots Across Days and Weeks

Configure weekly quantities, run-week patterns, and program day weights for broadcast order lines, then generate daily logs with retained weekly allocation and proceed through reconciliation to charging.

Neural Log weekly scheduling distributes a fixed weekly spot count across eligible days using probability-based weighting. After you set quantities, run weeks, and optional program day weights, the system generates a retained weekly allocation and creates daily draft logs for each scheduled day.

Before you start#

You need a role that grants access to Traffic > Broadcast Order Browser and Logs > Commercial Logs, with permission to edit order-line schedules. Weekly configuration requires that the order, station, and line are saved and active.

  • Program day weights are configured per radio group under Program Options > Program Day Weights.
  • Changing program weights or station membership after a weekly allocation is saved can invalidate the retained week. A fresh preview or generation for that week then refuses.

Set weekly quantities#

1

Open the order line#

In Traffic > Broadcast Order Browser, locate the order and open its line detail.

2

Edit Weekly Quantities#

Choose Edit Weekly Quantities. The dialog shows the current schedule mode.

3

Enter weekly values#

Enter an explicit weekly quantity. Zero is distinct from blank. Select the allowed ISO weekdays for distribution. Choose the first interval and partial-week treatment.

4

Apply#

Choose Apply to update the parent draft. The parent line becomes dirty and Save is enabled. If you choose Cancel, the parent remains unchanged.

5

Save the line#

On the parent line, choose Save to persist the weekly configuration. The line advances its revision. Returning to daily mode restores the original daily values.

Result#

  • The line stores a canonical weekly schedule document with quantity, allowed days, seed, interval, and partial-week policy.
  • All seven original daily identities remain inactive and are preserved for future reversal.
  • No logs, occurrences, allocations, or charges are created by configuration editing alone.

Configure run-week patterns#

Run weeks limit which calendar weeks the line may run. They are independent of the weekly quantity mode.

1

Open Edit Run Weeks#

On the order line, choose Edit Run Weeks.

2

Select the pattern#

Choose All Weeks, Every Nth Week, or Specified Weeks.

- **Every Nth Week**: enter the anchor date and an interval from 2 to 13.
- **Specified Weeks**: enter explicit start dates. Duplicate or overlapping intervals are rejected.
3

Apply and save#

Choose Apply to update the draft, then Save the parent line to persist the pattern. The revision advances once.

Result#

  • The line stores a canonical run-week payload alongside the daily schedule revision.
  • Demand previews and production orders use the frozen pattern to compute requested dates and monthly totals.
  • Restoring All Weeks clears the stored pattern without losing daily counts.

Set program day weights#

Program day weights adjust the relative probability of each weekday for front-loaded weekly schedules.

1

Open Program Day Weights#

Go to Program Options > Program Day Weights and select a saved radio group.

2

Enter signed values#

Enter a signed integer for Monday through Sunday. Zero means Normal (equal probability). Values must be between -90 and +90.

3

Save weights#

Choose Save weights to persist the configuration. The group advances its revision. Choose Cancel to discard changes.

Bind program weights to a weekly line#

When editing weekly quantities, you can choose how weights are applied:

  • Keep saved weighting (default): retains the existing independent settings or the current program binding.
  • Normal: disables front-loading and removes any program binding.
  • Current program day weights: enables front-loading and binds the line to the freshly resolved radio group. The group is resolved from the saved order/station scope; all stations in the order must belong to the same configured group.

Apply rechecks the source. A changed or inaccessible source refuses before persistence.

Generate saved weekly logs#

1

Preview weekly demand#

From the order or station view, run the demand preview. The preview refreshes saved quantities through a clean permission scope and respects weekly mode, run weeks, and program weights. Review the per-date requested spots and cost.

2

Preview placement#

Run Preview Daily Placement to see how weekly and daily demand compete for slots. The preview shows placed and bumped occurrences for the selected station and date.

3

Save draft log#

Choose Save draft log to generate a sealed draft for the selected day. The system creates the log, its occurrences, and a weekly ledger that retains the complete week's allocation.

4

Review Draft Log#

Open Review Draft Log to inspect placed and bumped items, weekly attribution, and frozen diagnostics.

Result#

  • A sealed daily log is created with ordinary and, if configured, filler occurrences.
  • The weekly ledger stores the exact allocation bytes for the week.
  • Replaying the same receipt returns the same log. A conflicting generation request for the same week is refused.

Weekly financial handoff#

Once daily logs are generated, the weekly workflow continues through the same financial steps as daily scheduling:

  1. Reconcile with Play-Log: match as-run evidence for each day of the week.
  2. Charge Log: create invoice drafts from reconciled airings. Bumped occurrences are not billed.
  3. Review Charged Log: verify the charged result and open Invoice Drafts.
  4. Issue invoices: finalize the invoice from the draft.

Days with no chargeable spots still use explicit retained station-ID as-run evidence. An empty CSV is not proof that nothing aired.

Recover from stale context or lost response#

If a preview closes, reopen it from the saved order or station and review the current inputs. If Save draft log was submitted but its result is uncertain, inspect the saved log before starting another generation. Use a retained recovery option only when the panel explicitly offers the original request. If charging has already completed, refresh the parent log to display Review Charged Log or Invoice Drafts.

Do not recreate an uncertain financial submission. A changed weekly allocation, program weighting or station membership requires a fresh review of the current data.