Call Schedule Builder

🛤️

Pipeline

Catalog & Rules → Capacity & Targets → Generation → Publication → Adjustment. Call and daytime responsibilities will share the same provider, activity, location, target, and constraint model.

📦

Import Baseline Configuration

Imports the reviewed external call-schedule-bootstrap.json into Firestore. This file is a one-time migration baseline only; active catalogs and effective-dated rule sets will be managed dynamically in Firestore through the Rules Builder.

📐

Minimum Retained Call

Sets the global hard minimum percentage of an eligible provider's default call allotment that must be retained. Changes are effective-dated by allocation year, preserve prior versions, and do not permit individual exceptions.

Effective allocation year

Minimum retained call

% of default

📋

Call Types

Not seeded yet.

📐

Rules

Not seeded yet.

ℹ️ Annual call volume per type is drawn from a real year of Qgenda "Calendar By Task" exports (Jul 2025 – Jul 2026), annualized to 365 days — not a formula guess. Weeknight counts are total covered nights; weekend counts are grouped into blocks (consecutive dates for the same person), not raw days. This still isn't the same as running a live allocation year end-to-end, so treat it as a solid starting point rather than gospel — re-pull this analysis periodically as practice patterns shift.

Allocation Year

Loading configured minimum retained-call rule…

Default = FTE-weighted equal share of your family's (category × pool) annual call volume — slowdown partners excluded, contract-provider reserved blocks excluded. Declare a percent of your default to buy more or sell some back. The configured minimum retained-call percentage is enforced as a hard rule. GEN call additionally accepts optional cross-category buy-in from INT/EP, matched only after GEN's own native demand is satisfied.

Loading roster…

CSB

Dashboard

Catalog & Rules

Call Allocation