How Cladograms Activity C Actually Works
The Gizmo Cladograms Activity C asks you to construct a cladogram from a data table of characteristics across a set of organisms. It sounds straightforward until you open it and realize the trait matrix is messy. You get a mix of shared derived characters, ancestral traits, and a few characters that don't cleanly map onto any branch. That is where most students get stuck. I have walked through this activity enough times that I can tell you what trips people up and what the intended path looks like. The activity typically gives you organisms like a lamprey, shark, lizard, dove, crocodile, and leopard, or a variation of that set. Each organism has a list of traits—vertebrae, jaws, four limbs, amniotic egg, hair, backbone, and so on. Your job is to order them by which traits they share and in what sequence those traits appeared in evolutionary history. The tool has a drag-and-drop interface for placing organisms on branches and a sidebar for defining what each node represents. The core mechanic is that every branching point, every node, corresponds to a shared derived character. You start from the bottom. The root node is the most basal trait, usually something like a backbone or vertebrae. You move upward one trait at a time. Each time you add a trait to a node, the organisms that carry that trait get grouped together on the branches that come after it. Organisms that do not carry the trait stay on the earlier branches. You keep doing this until the tree is fully resolved.
Here is the step-by-step I actually use instead of guessing: Step 1: Open the Character Table. Look at which organism has the fewest traits. In almost every version of Activity C, the lamprey or its equivalent is the outgroup. It lacks the most derived traits. Place it on the branch closest to the root. This establishes your baseline. Step 2: Identify the trait that splits the fewest organisms from the rest. That trait belongs on the next node up. If only one organism has hair, hair goes on the node right before the leopard. Do not put hair at the root. That is the most common mistake. Hair is a derived trait, not an ancestral one.
Step 3: Move upward trait by trait. Each node should have exactly one trait label. The gizmo sometimes lets you leave nodes unlabeled, but that is not the goal. Every branching point needs a justification. If two traits seem to appear at the same time, check whether one is actually nested inside the other. An amniotic egg depends on a jaw, for example. They are linked in the hierarchy. Step 4: Verify by checking each organism. Trace its path from the root to its final branch. Does every trait it has appear at or below its placement node? If a trait is missing from the path but the organism has it, your tree is wrong. Go back and adjust the node. I once spent nearly twenty minutes on a version where the gizmo had swapped a trait into the table unexpectedly, and my cladogram kept getting flagged as incorrect even though it was logically sound. The problem was a trait labeled as "backbone" that was placed above "vertebrae" in the data table, which made the gizmo's answer key treat them as different nodes. The workaround was to ignore the gizmo's pre-filled labels and build the tree purely from the organism trait presence/absence grid, then compare. If the structure matched but the node labels were slightly off, you could swap the labels to align with the key. It was a data entry quirk in that version, not a conceptual error on my part.
Get the Full Details
The more counter-intuitive thing beginners miss is that the order of branches on the same node does not matter. A lizard and a dove can switch positions on their shared branch without changing the meaning of the tree. The gizmo sometimes flags this as wrong if it expects a specific visual layout, but in cladistics the topology is what counts, not the left-to-right ordering. If your tree is correct but the gizmo marks it wrong, rotate the sub-branches and resubmit. Another nuance people overlook is trait reversals and convergence. The activity data is simplified and usually avoids these, but if you encounter an organism that seems to lack a trait it should have based on its closest relative, the likely explanation in a school context is incomplete data in the table, not a real evolutionary reversal. Just work with what is given. If you want to check your work quickly, the answer key for Activity C generally places the organisms in this order from most basal to most derived: lamprey, shark, lizard, dove, crocodile, leopard. The node traits from bottom to top are vertebrae, jaws, four limbs, amniotic egg, and hair. Some versions include scales or feathers as additional nodes depending on the exact trait list provided. Make sure you are matching the version you have, because ExploreLearning updates these periodically and the exact trait names shift between releases.
Common pitfalls: Putting the outgroup anywhere other than the root branch. The gizmo will still let you, but it will be wrong. Placing a shared trait on the wrong node and then trying to correct it by shuffling organisms instead of moving the trait. These two errors compound each other and make debugging harder than it needs to be. Fix the node first, then move the organisms. Limitations of this activity:
The Gizmo uses a simplified character matrix. Real cladistic analysis involves dozens or hundreds of characters, molecular data, and statistical methods like maximum parsimony or likelihood modeling. This activity teaches the logic of nested hierarchies, which is valuable, but it does not prepare you for the messiness of actual phylogenetics. If you want something closer to real work, look into PhyloCode exercises or the Tree of Life Web Project. The Gizmo is fine for an introductory course. It is not a substitute for learning how actual systematists build trees. If you are stuck and need the reference answers, searching for Cladograms Gizmo Answer Key Activity C will bring up a number of teacher resources and student posts. Use them to check your logic, not to copy blindly. The activity changes between school districts and years, so the exact organism set and trait list may not match what you see. The process I outlined above works regardless of the specific variant you are handed.
