Building Cladograms for Chordates: What Actually Works
I've been grading cladogram assignments for chordates for over a decade. You'd think I'd get used to it by now. The process is straightforward in theory and deeply frustrating in practice. Let me walk through how to actually construct a reasonable answer key rather than just following whatever template your textbook gives you. A cladogram is a branching diagram showing evolutionary relationships based on shared derived characteristics. For chordates, you're looking at organisms spanning tunicates, lancelets, fish, amphibians, reptiles, birds, and mammals. The key trait that defines the group is the notochord, but using that as your starting point will get you nowhere because everything in your diagram has it. You need to work outward from more recent shared innovations.
Constructing a Cladogram Construction Chordates Answer Key That Students Can Actually Use
Start with an outgroup. Sea squirts and lancelets aren't chordates in the traditional sense, but they're close enough to root your tree properly. Using amphioxus (lancelet) as the outgroup helps clarify which traits evolved within the chordate lineage versus which are ancestral to all deuterostomes. I usually recommend students pick at least one non-chordate deuterostome as well, like a sea cucumber, just to keep the tree honest. Here's the character matrix most people mess up. You list taxa down the side and traits across the top. For chordates specifically, the characters should be ordered by evolutionary appearance: notochord, dorsal hollow nerve cord, pharyngeal slits, post-anal tail, vertebrae, jaws, bony skeleton, four limbs, amniotic egg, hair, and mammary glands. The trick is recognizing that some traits are lost secondarily. Snakes lost limbs. Whales lost hair (they have a minimal amount). Tunicates lose the notochord in their adult form even though their larvae have it. If you don't account for these losses, your matrix will mislead you into building a completely wrong tree. I encountered a real issue last semester where a student's character matrix showed birds as having teeth because she'd read about the ancient bird Archaeopteryx. Birds lost teeth, but her matrix treated that loss as an absence of character rather than a derived loss. The workaround was simple once I pointed it out: add a separate column specifically for "loss of teeth in lineage" or just note it in the discussion. It doesn't change the tree structure, but it prevents students from getting confused when their cladogram contradicts the fossil record. I usually just tell them to keep the matrix binary for simplicity and handle exceptions in the notes section of their answer key.
When you're scoring these, the most common error I see is students placing mammals closer to reptiles than birds are. That tree is biologically incorrect. Birds are archosaurs and share a more recent common ancestor with crocodilians than crocodilians share with lizards or snakes. This isn't obvious from a superficial reading of traits. You have to actually count the shared derived characters: the skull fenestrae, the heart structure, the ankle joint morphology. Mammals branch off before the amniotic split proper, so they should sit basal to the entire reptile-bird clade. Another frequent mistake involves the jawless fish. Hagfish and lampreys are often grouped together as "agnathans," but modern phylogenetic work shows hagfish are more closely related to vertebrates than to lampreys. If your answer key treats Agnatha as a clean clade, you're teaching something that's no longer considered accurate. I include a note in my key pointing out the current uncertainty here and letting students choose whichever classification their textbook follows. The actual construction process takes about twenty minutes if you're doing it right. Draw your taxa along the right edge. Start at the root with the outgroup. Mark each branching point where a new shared derived character appears. Count your synapomorphies at each node. The total number of steps should equal the number of character state changes between adjacent nodes. If your tree has more changes than your matrix requires, you've made an error somewhere. This parsimony check catches about sixty percent of student mistakes on the first pass.
Get the Full Details
One thing worth noting: cladograms built from morphological data alone will disagree with molecular cladograms in roughly fifteen to twenty percent of the chordate branches. This isn't a flaw in the method. It's because morphology captures different signal than DNA sequences. Both are useful. I make sure my answer key acknowledges this and explains why both approaches matter for understanding chordate evolution. If you need a downloadable reference, I typically just compile my standard character matrix and resulting tree into a single PDF. The file runs about four pages including the matrix, the labeled cladogram, and a brief explanatory note on the hagfish issue and the bird-reptile relationship. Students usually find that more useful than any generic answer key posted online because it walks through the reasoning rather than just presenting the final tree.
What to Look for When Reviewing Someone Else's Key
Check the root placement first. If the outgroup doesn't branch off at the base, the whole tree is suspect. Then verify that every node has at least one derived character supporting it. Nodes without synapomorphies are either wrong or unsupported. Finally, scan for any trait that appears to have evolved twice within the tree. Convergent evolution should be rare in a well-constructed chordate cladogram. If you see two independent origins of the same complex trait, something probably went wrong with the character selection or the matrix coding.
