Coordination Card

The coordination card is a set of package-wide kneeboard pages: every flight's timing, codes and plan on one sheet, for pilots, the mission commander and GCI. It's off until the package turns it on; then every flight's kneeboard carries it, after the Package page.

Turning it on

Open the package's master design and pick the COORD tab. The kneeboard preview beside it shows only the card's pages, so you see what each edit prints, even before the card is on. On Card, tick Print the card on the package flights' kneeboards, and untick any of the four pages you don't want. Release line and Change print in the card's title bar. To hide a single table, edit the pack's coord pages in the Template Builder.

To keep the card off one flight's kneeboard, untick Card in that flight's row on Flights & VUL.

What it shows

| Page | Sections | | ---------------- | ------------------------------------------------------------------------------------------------------------ | | 1 · Coordination | Header (package, date, MC, DMC, element leads), flights, ATO targets, aimpoints, threats, air OOB, CSAR | | 2 · Roll call | Admin timeline, timing and VUL per flight, mission timeline, phases, contracts, codewords · SPINS · bullseye | | 3 · Comm plan | Comm matrix (every net and each flight's channel on it), AAR plan, altitude deconfliction ladders | | 4 · Flow | Launch plan, target flow, package gameplan, remarks |

Most of it comes from what the package already holds, so nothing is typed twice:

• Flights — callsign, aircraft, crew count, task (the flight's ATO mission when it has one), A/A TACAN, STN range, interflight and Mode 3 from each flight's Flight Members tab. POD numbers every aircraft across the package in package order.
• Timing — takeoff from the start point; hold point, altitude and push from the flight's ingress-hold waypoint; TOT from its task waypoint; egress and recovery from the route. Times print on the mission clock (Z or L, as the TIMES box says), each flight's own late activation included. Taxi is the flight's admin-timeline row named TAXI (Misc tab).
• VUL — each flight's task window: its task waypoint's ToT to its Push. Type a time in the flight's VUL start or VUL end on Flights & VUL to override it. The package VUL runs from the earliest flight start to the latest flight end.
• Altitude blocks on the deconfliction ladder come from the altitude blocks on each flight's route waypoints: the ingress hold, the leg in, the target (task through task end) and the way out.
• Comm plan — every net any flight's comm plan carries (the package plan for linked flights, their own rows otherwise), with each flight's channel on it.
• Element leads — the first flight of each task.
• Targets and aimpoints from the Targets tab, threats and enemy air OOB from OPFOR, the admin timeline and codewords from Misc, tankers from Support, bullseye from the package. Bullseye bearings are magnetic.

The COORD tab holds only what no flight knows: MC and DMC, lead changes or extra roles, VUL overrides, phases, contracts, tanker on-station and boom frequencies, target priority/TLE/CDE/DWE, SPINS blocks, IR safe altitude, CSAR, minimum force and remarks — plus each flight's Mode 1, ALR and tanker. Flights & VUL and Comms & AAR show the derived taxi, blocks, planned VUL and comm matrix so you can check them; change them where they live.

Roster export

The COORD tab's Roster section gives one row per aircraft across the package — flight, position, callsign, pilot, aircraft, modex, task, Mode 3 and more. Pick the columns (the choice is kept in your browser), then Download or Copy as CSV or JSON. Modex numbers your squadron's aircraft-number standard assigns are filled in.

A published package's public link carries each seat's modex and aircraft too, so an external tool can read the roster without a download.

Briefing slides

On a package master, the briefing tool's Generate adds package slides from the same data: gameplan, launch plan, hold and push plan, tanker plan and contracts.