figran

A change register for an invented teaching flowchart

By Figran Team

What this exercise is for

A design review can approve a layout change while accidentally changing what a figure says. This exercise separates the requested edit, the information that must stay the same, and the reviewer's reason for accepting or rejecting a revision. It is a suggested teaching activity, not a classroom trial or a measured learning result.

The reference specification

Use an invented handout with three boxes, in this reading order:

  1. Draft
  2. Review
  3. Handout

There is one arrow from Draft to Review and one from Review to Handout. In this example, an arrow means the next step in a proposed workflow. It does not establish elapsed time, movement of material, causation, a biological mechanism, or a measured quantity. There are no data values or scientific sources attached to the invented example. Keep this specification beside the work.

Four revision requests to sort

Request What a reviewer should check Suggested decision for this example
Increase the space between the three boxes. The labels, reading order and two connections remain the same. Accept as a layout edit if those checks pass.
Replace the arrow from Review to Handout with a two-way arrow. A two-way connection adds a return relation that is absent from the reference specification. Ask for clarification; do not approve it as a spacing change.
Rename Review to Verified result. The new label asserts verification that this invented workflow does not establish. Reject the unsupported label and retain Review.
Put the boxes in a vertical column for a narrow handout. The reading order still follows Draft, Review, Handout, and the arrow meaning remains stated in nearby text. Accept the arrangement only after checking the sequence and text companion.

The suggested decisions apply only to the specification above. A different real source can justify a different decision. This table is not a rule that all two-way arrows or all verification labels are wrong.

Keep one register entry for each change

Copy these six fields for a proposed revision:

  • Requested edit: [one concrete change]
  • Information to preserve: [labels, relations and boundaries]
  • Possible change in meaning: [what a reader could infer after the edit]
  • Decision: [accept / clarify / reject]
  • Reason: [point to the reference specification or the real source]
  • Follow-up check: [what to read or compare in the next version]

Worked register entry

Requested edit: Put the boxes in a vertical column.

Information to preserve: Draft, Review and Handout in that order; two forward connections; arrows mean next step only.

Possible change in meaning: A reader might treat vertical position as rank, or miss the second connection if the handout is cropped.

Decision: Accept after a check of the complete narrow layout.

Reason: The reference permits a proposed sequence and does not assign rank. A vertical arrangement can preserve that sequence, but position alone is not a replacement for the stated arrow meaning.

Follow-up check: Read the text companion without the visual: Draft is followed by Review, then Handout. This is an invented proposed workflow; the arrows do not show time, amount or causation. Compare this sentence with every label and connection in the revised handout.

This is an illustrative review entry, not a report that a design tool produced or validated a particular revision.

Try it with a peer

Each person selects one request, writes a register entry, and gives it to a peer. The peer marks one field clear, missing or needing clarification and explains why. Revise the entry using that comment. Do not turn the number of accepted changes into a score for scientific accuracy or accessibility certification.

For a real teaching figure, replace the invented specification with your actual source, approved label list, arrow meanings and known limits. A change that alters meaning needs a source-based decision, even when the layout looks better.

About and reuse

Figran Team is affiliated with Figran, a tool for scientific and teaching visuals: https://figran.net/ . This original text was prepared with AI assistance and reviewed for the limits stated above. No use of Figran or any particular tool is required. This activity does not report an experiment, classroom test, product comparison or learning gain.

The original text is offered under CC BY 4.0: https://creativecommons.org/licenses/by/4.0/ . Attribute Figran Team and link to this resource. This text licence does not license Figran software, logos, trademarks or third-party materials.

Public contact: support@figran.net