Docs

Project & scenario fields

Every field on a bluprnts project and scenario — the layer's name, colour and toggle, and the eleven scenario levers with their ranges.

Reference for both what-if objects. For the walkthroughs, see Add or edit a project and Create a scenario.

Project fields#

FieldWhat it is
NameWhat the initiative is
DescriptionAn optional line on what it covers
ColourAccent colour on timelines
Start dateOptional. A marker on the timeline — the items inside carry their own dates
EnabledWhether the project is layered onto the forecast

A project holds no child records of its own. Each product, sale, employee, cost and financing entry carries the project it belongs to; an unset project means the base plan.

Every company has exactly one base project, always on, which is your plan as it stands.

Scenario fields#

FieldWhat it is
NameWhat the scenario models. Defaults to Untitled scenario
DescriptionShown under the name in the scenario picker
ColourAccent colour, assigned on save
LeversThe eleven adjustments below
Targeted adjustmentsScoped overrides on specific products, channels, departments, roles or costs

The levers#

LeverUnitRange
Sale volume%±100
Sale price%±100
Production cost%±100
Storage & distribution%±100
Shipping%±100
Overheads%±100
Headcount%±100
Average salary%±100
Customer pay delaydays±90
Supplier pay delaydays±90
New funding£0 – 1,000,000, in 25,000 steps

Percentages are relative to base — centre is no change. New funding is received in full in the first forecast period.

Targeted adjustments#

Each carries a metric, a dimension it's scoped by, the value it targets, and a multiplier.

MetricScoped by
Sale volume, sale price, production cost, storage & distribution, shippingProduct or channel
Headcount, average salaryDepartment or role
Fixed costsCost or cost type

Where several rules match one entity for the same metric, the most specific wins: product → role → cost → channel → department → cost type.