Budgeting
You know what a work phase and a milestone are, what TD and WD mean, and why every date on the timeline depends on First Shooting Day.
The timeline holds the production schedule of a budget as work phases and milestones. Formulas and cash flow rules can take their numbers and dates from it, so you enter each date once. When you change the schedule, those formulas and rules use the new values. To open the timeline, click  **Timeline**.
The timeline shows milestones in the lane **Milestones** and work phases in the lane **Work Phases**, both on one axis of days. A legend lists every milestone and every phase.
Preparation, the shoot and wrap are examples of work phases. A phase has a start date, an end date and two figures for its length:
- **Total Days (TD)**: the days from the start date to the end date. KOSMA calculates TD and does not count the end date itself. - **Work Days (WD)**: the days people work in the phase. You enter WD yourself. KOSMA does not subtract weekends or breaks.
For a new phase, KOSMA proposes 5 WD for every 7 TD. WD can never be higher than TD. If you raise WD above TD, KOSMA moves the end date later.
A budget needs both figures because some costs are billed per calendar day, such as a rented van, and others per work day, such as a crew member. Every phase gives two numbers that any formula can use without further setup. `<name>_duration` is the TD of the phase, and `<name>_workdays` is its WD. The short forms `<name>_TD` and `<name>_WD` give the same numbers. For the details, see [use phase durations in formulas](/kb/article/use-phase-durations-in-formulas).
Contract signature, picture lock and delivery are examples of milestones. You place a milestone a whole number of days before or after First Shooting Day. You can attach a cash flow rule to a milestone instead of a fixed date. When you move the milestone, by dragging it or by changing its date, KOSMA moves the payment with it. A payment on a fixed date stays where it is.
A milestone has no payment delay of its own. If a payment is due some days after a milestone, such as 30 days after delivery, you set this in the cash flow rule: see [use milestones in cash flow rules](/kb/article/use-milestones-in-cashflow-rules).
Every budget has one milestone that every other date depends on. In a budget created with **No Template**, it is called **First Shooting Day** in every interface language. A template can give it another name, and you can rename it. This article calls it First Shooting Day. It is the starting point: every other milestone and every phase lies a number of days before or after it. You cannot delete or drag First Shooting Day. Its date changes only in its own dialog: see [set up milestones](/kb/article/set-up-milestones). When you change the date, KOSMA moves every milestone and every phase by the same number of days. Their distance from First Shooting Day stays the same.
If First Shooting Day has no date, no other milestone or phase has a calendar date either:
- The axis shows day numbers instead of dates. - The phase and milestone dialogs ask for a number of days instead of a date. - **Today** is disabled. - Cash flow rules on milestones or phases pay nothing.
When you change the length of a phase, in its dialog or by dragging it, KOSMA recalculates every formula that uses its TD or WD, and with it every quantity built on that formula.
Phases and milestones are not linked to each other. Moving or lengthening a phase moves no milestone, and moving a milestone changes no phase. If you add a week to the shoot, the quantities built on the shooting phase change, but a milestone at the end of the shoot stays on its day. Move that milestone yourself, so that the payments attached to it move too.
Before you build a formula or cash flow rule that uses a phase or a milestone, set it up: see [set up work phases](/kb/article/set-up-work-phases) and [set up milestones](/kb/article/set-up-milestones). To use a phase in a payment cycle, see [use phases in payment cycles](/kb/article/use-phases-in-payment-cycles).
Markdown