SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Separate readiness from completion
A prerequisite makes work eligible to begin. A subtask contributes to finishing the parent deliverable. Mixing both meanings into one checklist creates a dangerous ambiguity: completing a prerequisite can be mistaken for completing the whole project. This guide describes a lightweight coordination model for teams willing to maintain links and explicit rules.
What Trello documents
Atlassian describes dependencies through linked cards, checklists and Automation rather than a built-in dependency-management engine. Its recommended representation uses one card per task, separate checklists for prerequisites and subtasks, links from dependent checklist items to dependency cards, and return links in attachments. Automation can then update checklist state or move cards when conditions are met. This representation alone should not be treated as automatic critical-path planning or a guarantee that someone cannot start blocked work.
Example: launch approval and launch preparation
A campaign launch waits for brand approval. Brand approval becoming complete should make launch preparation ready; it should not mark the campaign launched. Writing the email and checking the landing page are separate outputs contributing to preparation. Name the first checklist Prerequisites and the second Deliverables. Document which state means permission to start and which means the parent outcome is actually accepted.
Build a small acceptance matrix
Use three sample cards before applying the design to a real campaign. With one prerequisite incomplete, the dependent card must remain waiting. With all prerequisites complete but one deliverable incomplete, it may become ready but must not become complete. With every required deliverable accepted, the owner can close the parent according to the agreed policy. Write these expected states down before creating any rules so that rule behavior has a measurable purpose.
Prevent ambiguous matching
Use explicit card links in the maintained relationship record. Reused titles such as Approval are ambiguous to a human and can also make title-based rule configuration hard to audit. Give sample cards unique names during the rehearsal, inspect the actual linked destinations and open the return links. When moving work to a different board, verify that the relevant people can still read the linked cards; a visible title is not evidence of usable access.
Plan for reopening
Completion is not always permanent. Decide who must review dependent work when a prerequisite is reopened or rejected after approval. Test that scenario separately instead of assuming the forward completion rule automatically reverses itself. Start with a manual owner review for exceptions, then automate only the transitions that have a clear expected outcome. Use the automation log to diagnose a failed transition before adding another rule that may duplicate it.
Continue with the Trello implementation guides.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.