Trello board cards: complete, archive or delete?

Before clearing a card, decide whether the owner wants a completion marker, a retained record off the active board, or permanent removal.

For an ordinary Trello Cloud board card on computer, first identify the exact board and card privately. Agree who may change it and what evidence establishes the underlying work. A similar title or a cleanup request does not resolve those questions.

Record completion

Atlassian documents Mark complete on the card front or beside the title when the card is open. Its new control supports cards without due dates. The documentation describes a rollout: if your controls differ, follow its linked date instructions rather than assuming the feature is present. Template and separator cards are excluded here. Completion can trigger automation, including moving or archiving a card; the actual board's rules remain unknown until checked. Mark a card as complete.

A completion marker records task state. It does not establish that a person delivered the requested work; keep that evidence separate.

Keep a record off the board, or remove it permanently

Archive card is available in the actions menu of an open card. Archived cards remain retained indefinitely unless a board member deletes or restores them; they are not automatically deleted. The documented return route is board menu → More → Archived items, find the card, then Restore.

For permanent removal, first archive the card; Delete then becomes available and requires confirmation. Atlassian describes deletion as permanent and unrecoverable. Use deletion only for agreed permanent removal. This procedure excludes the separate Inbox archive and list or board deletion. Archive or delete a card.

Check what still needs to happen

For a configured recurring due date, marking the card done advances to the next date matching its cadence from the current due date, and returns it to not done. Completing one occurrence therefore does not establish that the recurring work has ended.

Archiving suppresses notifications for actions related to that card, including due dates. A retained record is not a continuing reminder. If future work or an alert is still needed, resolve that requirement before choosing archive. Card dates: recurring due dates and reminders.

Write a short private handoff: selected card, intended state, record-retention need, remaining occurrence or reminder, required work evidence, and unresolved automation. If the intended result or permission is unclear, leave the state change pending. None of these preparation checks proves a notification arrived or a recovery succeeded.

Evidence: English Trello Cloud documentation checked at 2026-10-05T11:10:02Z; no update dates were displayed. Source inspection and manual decision checks only; no board, card, automation, notification, deletion or recovery actions. A distinct same-controller checker reopened all three sources at 2026-10-05T11:11:12Z and rechecked nineteen author decisions plus six additional boundaries at 2026-10-05T11:14:57.887617Z; no independent factual review is claimed. Recheck before use if controls, card type or board rules differ, and by 2026-11-05T11:10:02Z. This procedure follows the task-handoff standard [current article].