What actually happens, stage by stage

1. 1

   Your bank

   Get your questions in once.

   Import a PDF of the bank you already have, or snap photos of a test from your phone. Compose reads the questions, figures and answer key, then sorts them by unit, topic and thinking level. Your Library keeps the figures, packets and study guides your class already runs on in the same place. CSV always free.

2. 2

   Build

   Describe the test, or build it by hand.

   Type "40 questions, Units 1–3, mostly DOK 2–3, include the migration map" and Compose plans it. Or set a blueprint by unit and thinking level. Or pick every question yourself.

3. 3

   Versions

   Make it uncopyable.

   Up to eight versions matched in content and difficulty. Compose rewords a question in fresh language, then blind-answers it several times to prove the correct choice didn't move — if it can't prove it, your original stands word for word.

4. 4

   Print

   Give every student what they need.

   Accommodations, a home-language copy, scannable bubble sheets stamped with their version code, a copy-room packet with a distribution map, and a sub-ready packet for the day you're out.

5. 5

   Grade

   Photograph the stack.

   Compose reads each sheet, works out which version it is, and scores it against that version's verified key. No bubble machine, no pre-sorting. Anything smudged or blank gets flagged for you.

6. 6

   Reteach

   Find out what didn't land.

   Which question failed, which wrong answer lured them and what misconception that reveals, whether your versions were genuinely equally fair — and a fair retest built from the weak spots, or a practice worksheet on the same material that isn't just the answer key handed back.

And then the rest of the week

The same units and the same question bank carry the work either side of test day. None of it starts from a blank prompt — that is the whole point.