Task dependencies are what turn a list of tasks into a schedule. Maverick supports four link types — FS, FF, SS, and SF — each controlling a different kind of sequencing relationship. Most projects use mostly Finish-to-Start links, but knowing all four gives you the tools to model any workflow accurately.
1. Finish-to-Start (FS) — The Default Link
A Finish-to-Start link means the successor task cannot start until the predecessor finishes. It's the most common dependency in project management: construction can't begin until permits are approved; testing can't start until development is complete. Maverick draws an arrow from the right edge of the predecessor bar to the left edge of the successor bar. When the predecessor slips, the successor moves right automatically. FS links are the right choice for the vast majority of sequential work.
2. Finish-to-Finish (FF) — Synchronized Endings
A Finish-to-Finish link means the successor task cannot finish until the predecessor finishes — but both tasks can run simultaneously. This is useful for parallel work that must land at the same time: documentation must finish when software testing finishes, or client procurement must complete when internal engineering design completes. The two tasks overlap in the schedule; only their end dates are synchronized. If the predecessor extends, so does the successor's finish date.
3. Start-to-Start (SS) — Synchronized Starts
A Start-to-Start link means the successor task cannot start until the predecessor starts. Both tasks then run in parallel. This is common in fast-tracked schedules where you want to begin downstream work as soon as upstream work kicks off — without waiting for it to finish. Starting unit testing as soon as the first module of development begins is a classic SS scenario. The predecessor's start date controls when the successor can begin; the two tasks then run concurrently until each finishes on its own terms.
4. Start-to-Finish (SF) — The Rare Reverse Link
A Start-to-Finish link means the successor task cannot finish until the predecessor starts. It's the least common link type and easy to misuse — it describes a reverse dependency where the end of one task is gated by the beginning of another. A real-world example: a night shift cannot end until the day shift has started (handover). In most project management scenarios, an SF link can be replaced by a clearer FS or FF link. Use SF only when the reverse sequencing genuinely reflects how the work operates — and document why, since it will surprise any team member who reviews the schedule later.