Field note 43

Test a card template before reuse

A blank red master card above two separate off-white cards on a charcoal surface, illustrating a template and new task instances.
Test the template before reuse

Before reusing a Trello web card template, inspect its source card’s completion state, create an authorized test instance, and check the instance rather than trusting the master’s appearance. Give each real task its own agreed date. Treat later master edits as changes for future cards, not updates to cards already created. These checks prevent a reusable description from being mistaken for a ready-to-run task.

In this fictional design studio, Omar is the human studio operations owner. He approves the candidate template content and proposed board changes. Actual task creation and board modification still require the board owner’s separate permission. The preparation sheet below is an illustrative plan, not an executed board test or authorization to change a board.

What Trello documents—and what the studio proposes

Trello’s template documentation identifies three behaviours worth testing. Completion status is hidden when a card becomes a template; if the source card was marked complete, new cards from it will automatically be marked complete. Start and due dates are hidden on the template and are not copied. Editing the template does not update cards already created from it. [1]

The studio’s proposed operating rules are separate: use an explicitly not-complete source, inspect a fresh instance, agree each instance’s timing and record a decision about older instances when the master changes. These are local safeguards, not extra Trello guarantees.

The Dates documentation explains how to open a card and select Dates to add or edit dates, and how to mark a card complete. It also says a due-date reminder must be set to receive a due-date notification. Choose a reminder explicitly, or choose None; a due date alone is not a reminder configuration. [2]

Filled proposed master

Title: Equipment photo preparation - ITEM

Description: Prepare a working photo set for the approved internal asset EQ-17, the studio’s portable light stand, showing its full front view and folded storage view. Use only the photographs authorized in the internal equipment-photo brief for EQ-17; that brief identifies the source folder. Do not search for substitute pictures. Named task owner: Priya, equipment coordinator. Required output: two clearly named working image files, one per requested view, handed to Omar for review. If the brief, source location, asset identity or requested view is missing or contradictory, stop preparation and ask Omar to resolve it before continuing. This task prepares internal review material, not approved publication assets.

Proposed checklist:

For reuse, ITEM and the asset-specific description must be replaced with the next approved brief’s details. The example supplies concrete content to review; it does not claim that a template automatically assigns Priya or executes any work.

Example acceptance card

Every board observation remains untested. Expected results combine the documented behaviours with the proposed safeguards identified above.

Test/input Expected result Current observation or status Action/owner
Old completed source card proposed as master Inspect the normal source and explicitly set it not complete before making it a template; hidden completion must not be trusted Not run - owner-authorized test required Board owner inspects and corrects source state under permission; Omar reviews evidence
Fresh test instance from candidate template Instance is verified not complete before reuse is accepted Not run - owner-authorized test required Board owner creates and inspects test instance; hold any unexpected completion
New instance needs timing No inherited start/due dates; set its own owner-agreed date through Dates and select reminder explicitly Not run - owner-authorized test required Omar agrees timing; board owner checks Dates and records selected date and reminder
Master description changed after earlier instance exists Earlier instance remains unchanged; no automatic retrospective update Not run - owner-authorized test required Board owner compares descriptions; Omar decides whether the earlier instance needs a separately authorized edit

Run the test in order

First, obtain permission for the test’s actual board changes, including the temporary source, new instance and description edit. The board owner should inspect the source as a normal card and establish its not-complete state before selecting Make template. If an existing template hides the feature needing inspection, Trello documents disabling the template, making the change and turning it back into a template. [1]

Second, create a clearly identified test instance from that candidate. Inspect its completion state, description and checklist directly. Record what is present rather than assuming checklist state or task ownership copied correctly. An unexpected or uninspected result stays held; it is not a pass.

Third, inspect Dates before setting the test instance’s own agreed date. Record the date and time selected, whether a start date is needed, and the explicit reminder choice. Check the saved settings again. Do not infer a reminder from a coloured due-date badge. [2]

Fourth, retain the earlier instance’s description, make the permitted master description change, and compare the earlier instance again. Record the unchanged text. Omar then decides whether that older task needs an individual amendment; any actual edit requires the board owner’s authorization. [1]

Finally, Omar reviews the evidence and separately approves the candidate content for reuse or requests changes. A technically expected result does not establish that the brief, output or review handoff is good enough. Likewise, marking task work complete is not editorial or business acceptance of the photos.

Reuse checklist

An assistant can prepare this description, checklist and test record from supplied material without claiming Trello access. It cannot turn an offline acceptance sheet into permission, assignment or completed work.

Sources

  1. Create a template card
  2. Add a due date or start date to a card

Discuss the process with MAJLS ↗