Start with the existing board's meaning of a card. A team that tracks one customer request per card needs a different split from a team that tracks one release deliverable.
Split outcomes before turning notes into checkboxes
This original fictional team uses one card per independently reviewable event deliverable. Its existing card is called “Prepare open-house materials.” The notes contain:
- Approve the one-page visitor map.
- Check entrance labels on that map.
- Check the accessible route on that map.
- Prepare the volunteer briefing.
- Confirm the briefing's arrival instructions.
The map and briefing can be reviewed independently. Under this team's stated rule, a clearer proposal is a “Visitor map approved” card and a “Volunteer briefing approved” card. The two map checks belong under the map card; the arrival-instructions check belongs under the briefing card.
That is a proposed work breakdown, not proof that either deliverable is approved. “Check accessible route” is a review action; completing the checkbox should refer to an actual check and an accepted result.
| Proposed card | Checklist item | Evidence needed before checking it |
|---|---|---|
| Visitor map approved | Check entrance labels | Reviewer compared labels with the approved venue details |
| Visitor map approved | Check accessible route | Responsible reviewer confirmed the route against current venue information |
| Volunteer briefing approved | Confirm arrival instructions | Coordinator accepted the stated meeting location and arrival time |
The fixture intentionally leaves people and deadlines unspecified. ChatGPT should not assign either from job titles or the order of the notes.
Request a board-compatible proposal
Propose a Trello card/checklist breakdown. Do not modify the board.
What one card means on our existing board: [ENTER]
Existing card titles/descriptions and relevant checklist items: [PASTE]
Distinct deliverables and their acceptance rules: [PASTE]
Confirmed owners/deadlines, if any: [PASTE OR UNCONFIRMED]
Work already completed with evidence: [PASTE OR NONE]
For each proposed card, state one outcome and the evidence needed to
mark it complete. Put supporting steps in its checklist. Identify any
item that needs independent tracking under our board rule and explain
why it should be a separate card. Preserve completed work and its
evidence. Do not mark proposed checks complete, infer owner acceptance,
invent dates, duplicate the same task across cards, or add automation.
Return a reviewable text proposal using our existing terminology.
OpenAI's prompting guidance supports supplying the intended result and the constraints. Here, the team's card rule prevents a generic task list from becoming a mismatched board structure.
Keep checklist completion distinct from outcome acceptance
Atlassian's Trello checklist documentation, checked October 24, 2026, describes managing checklist items and converting an item into a card. Those operations provide a way to represent the agreed split. They do not establish that a deliverable met its acceptance criteria.
All map checks might be complete while a reviewer is still deciding whether to approve the map. Keep that outstanding decision visible in the card's description or the team's established review convention. Do not rename it “Approved” solely because the checklist reaches its end.
If an item becomes a separate card, retain its context and connect it to the original work using the board's existing linking convention. Review what remains in the original checklist so the same action is not accidentally tracked twice.
The project-management guide helps when the source notes themselves contain unresolved dates or assignments. This narrower exercise starts after the team has decided what it tracks. Have the people doing the work review the proposed split, then transfer the accepted card titles and checklist items into the maintained board without resetting completed work.