Timeline Architect

Not what order. How far apart.

Skill this builds

Locate a founding or constitutional event on a scaled timeline, calculate the interval between two of them, and predict how long a change to the Constitution actually takes.

About

About 10 minutes · Standards: C3, NCSS · Plays offline

One event at a time. Slide the marker to the year you think it happened and drop it. The timeline is drawn to scale, so the distance on your screen is the distance in years. You are not being asked to put things in order — you are being asked how far apart they are.

Every date here is a matter of public record and each event links to a primary source. Dates are the ratification or enactment date, not the date something was proposed — a distinction that turns out to be the whole point of the last round. Nothing in this game is an interpretation; the interpretation is what you do with the gaps once you can see them.

The point

Almost everybody gets the ORDER right. Almost nobody gets the DISTANCE right, and the distance is where the history actually is. The Constitution was signed in 1787 and slavery was abolished in 1865 — seventy-eight years, four generations, inside the same document. Seneca Falls to the Nineteenth Amendment was seventy-two years, long enough that most of the women in that room in 1848 were dead before it passed. The Fifteenth Amendment said race could not bar you from voting in 1870, and the Voting Rights Act was ninety-five years later, which tells you exactly how much a sentence in a document accomplishes on its own. This is the least comfortable thing a timeline can teach and the most useful: the country does change, and it changes on a scale longer than a human attention span and often longer than a human life. That is an argument for starting, not for waiting.