Calendar dates and contract track numbers

Schedule missions by calendar month and year, with separate track numbers within each contract.

Schedule a dated mission

Open Operations → Scheduled tracks → Schedule a track. Enter a mission name and template, choose the month and year, and select its shared contract. For example, May 3049, Track 3, Breakthrough.
Enter the track number within the selected contract, or leave it blank for the next number after that contract’s saved scheduled tracks. Numbers must be unique within a contract; different contracts can each have Track 3. Several tracks can occur during the same calendar month. Historical spreadsheet track numbers are not guessed: enter the correct number when continuing an imported contract.
Choose Standalone mission (no contract) for an independent mission; leave its contract track number blank. Narrative and Dobless scheduling use the same date and numbering fields. Scheduling does not advance the calendar or post payments.
Session date (real world) is an optional date picker for when you will play. Scheduling notes is a separate optional text field. This session date does not change the in-universe mission month/year. Existing free-text session information remains in Scheduling notes; dates are not guessed from old notes.

Scheduled tracks lists Date, Track, Mission and Status. Open a mission and choose Edit mission date and track number. The GM can associate older missions with their shared contract and save their correct number. Existing missions without recorded numbers display Not assigned.
Dates and names can be changed before roster lock, completion or unit reporting. Locked historical missions retain their dates and financial history while their contract numbering can be corrected. Changes are audited.
Calendar, contract dates, company summaries, ledger rows, OpFor, briefing choices and printed unit reports display calendar dates using the campaign’s starting date. Calendar target dates and contract date fields use named months and years. Changing the campaign starting date still relabels the existing timeline; use Calendar to advance play.
Internal accounting and CSV imports retain campaign month indexes for compatibility. A date display change does not renumber financial records, replay payments, or alter historical balances.

New league campaigns keep independent company dates and merchant stock. Mission roster submissions save the company operational month for rewards and aftermath accounting. A shared scheduled mission label does not move other company calendars. The campaign starting-date reference remains common; use Target date to correct a company date. See Travel methods, arrival and league calendars for one-action journey processing.