AP Biology · Teacher guide

For teachers

What the Lab Bench is, how your students will use it, how they hand work in, and what stays on their computer. It takes about five minutes to read.

5-minute teacher quick start · Illustrative report · Feedback

Projector mode Show today’s lab on the classroom screen, with a timer.

Using projector mode

  1. Open Projector mode.
  2. Pick the lab and tick today’s parts. The timer fills in from the parts’ time estimates, and you can add a due date or a note.
  3. Click Start, then press F for full screen. Space starts or pauses the timer; Esc goes back to setup.

projector.html#lab05 opens a lab directly (use the lab’s number), which makes a handy bookmark. The page remembers your last setup on that computer. Each lab page also has a small “Project this lab” link in its header.

What this site is

The Lab Bench is 13 interactive versions of the AP Biology investigations, one page per lab. Each page is adapted from the College Board AP Biology Investigative Labs: An Inquiry-Based Approach teacher manual (updated 2019). It is not affiliated with or endorsed by the College Board. The simulations are modeled on typical classroom results. They are meant to sit beside wet-lab work, or to stand in for it when you cannot run the real thing.

Every lab page has the same parts, so students learn the layout once:

OverviewThe driving question, objectives and science practices, and a safety note where the real lab has hazards.
BackgroundKey ideas, key terms and the science in short sections students can open as they need them.
Pre-labAuto-checked questions, each with an explanation, including the calculations students will need.
SimulationsOne part for each procedure in the manual. Students choose settings, run trials and record data in a table and graph.
DesignStudents write a question and hypothesis, choose a variable, levels and replicates, run it and analyze it with the right statistic.
Analyze and EvaluateWritten prompts, including a claim-evidence-reasoning block, for students to answer in their own words. The Reflect or Evaluate part ends with a one-tap Rate my confidence (“I could teach this”, “I mostly get it”, “I’m lost”); it goes in the report and on your dashboard and never counts as required work.
SubmitReport buttons, a progress file for backup, and a printable worksheet.

Pre-lab questions are graded for the student right away. Written answers are not graded by the site; they go into the report for you to read.

How students use it

  • Sign in once. The first time, a student types their name as you know it and chooses a class period. That one sign-in works on every lab on that computer.
  • One part at a time. A lab shows a single part on screen. Students move with the part tabs along the top or the Back and Next buttons at the bottom of each part. A check mark appears on a part when all of its questions, boxes, tables and required steps are done. All parts shows the whole lab on one page.
  • A checklist in every simulation. The Steps list ticks itself off as the student works, and a short Next: line says what to do now. Buttons that need an earlier step explain what is missing instead of failing silently.
  • Results beside the scene. On a laptop the Data and Graph tabs sit next to the simulation, so students watch the graph build while a run plays. On a phone or narrow window they switch between Scene, Data and Graph.
  • Saved in that browser only. Answers, tables and quiz results save automatically on the computer being used. They are not sent anywhere, so a different computer or a cleared browser starts blank unless the student moves their work (see below).
  • A short tour. The first time a student opens a lab after signing in, a five-step tour points out the part tabs, the Steps list, the results tabs, the sign-in line and the Submit tools. It appears once per browser. Students can skip it, and the Help link in the sign-in line shows it again.
  • Shared computers: sign out at the end of class. Because work is kept in the browser, the next student on that computer would otherwise see it. After saving, a student chooses Sign out in the sign-in line, which erases their name and all of their work from that computer. Manage my data on the home page also offers Start over with all labs, which keeps the name and class but erases the work and gives fresh data.

Handing in work

The last part of every lab, Submit, builds a lab report from everything the student has done: name, class period, date, Dataset ID, every answer, every data table and every graph. Students hand it in one of two ways:

  • Download .docx. A Word file the student can open, check and upload.
  • Save as PDF. A clean report view opens and the student chooses “Save as PDF” as the printer. This works on any computer, with no extra software.

Either file can be uploaded to any LMS, or handed in the way you already ask for lab work. There is also Copy all my responses, which puts the answers on the clipboard as plain text for pasting into a form or a document.

Nothing is submitted through this site. Students always hand in a file, so you keep the same grading workflow you use today.

Moving between computers

Because work lives in one browser, students who switch computers (a classroom laptop on Monday, a home computer on Tuesday) need a way to carry it along. The Submit part has a panel called Move your work to another computer:

  • Progress file. Save progress file downloads a small .json file. On the other computer, the student opens the same lab and chooses Load progress file. A progress file is for one lab; it will not load into a different lab.
  • Resume code. Get a resume code makes a short block of text starting with LB1. The student can email it to themselves and paste it into Load resume code on the other computer. This is handy on a locked-down laptop where files are awkward.

Loading asks before it replaces anything. The site also reminds students to save a progress file once they have done real work and have not backed it up, and warns them before they close the page with unsaved work.

If a student has real work that is not backed up and has had the lab open for 40 minutes, a small banner says “Period ending soon? Download your report or get a transfer code,” with buttons for each. It appears once per browser session, never in the middle of a simulation animation, and can be dismissed.

Per-student data and Dataset IDs

The simulations do not give every student the same numbers. Each student’s data is generated from their name, class period, the lab and a dataset number, so a student gets the same numbers every time they reopen the lab, and a different student gets different ones. Two students who sit side by side and run the same settings will still see different results, which is what real replicates look like.

Each report prints a Dataset ID such as K7M-4QX, shown in the sign-in line and on the report. How it helps:

  • It is tied to the student’s name, period and lab. A report handed in under another student’s name will carry the wrong ID for that student.
  • If two reports have identical data tables, the two students did not each run their own simulation. A progress file copied from a classmate loads that classmate’s name and Dataset ID along with the data, so it does not pass as the student’s own.
  • You can ask a student to read out their Dataset ID in class and compare it with the report.

New dataset. Next to the Dataset ID, New dataset gives that student fresh numbers for that lab from then on, after a confirmation. It is useful when a student wants to repeat a simulation, or after a mistake. Data already recorded in their tables stays; only new runs change. The ID on the report changes to match.

Printing worksheets

If you want paper, every lab has a Print worksheet button (in the Submit part, and at the top of each lab page). It builds a clean, black-and-white sheet from the lab: the background text, the pre-lab questions with answer bubbles, blank ruled data tables, and ruled lines under each written prompt. The worksheet has no answers and no student data. Students can also use the browser’s own Print command on a lab page; printing always includes every part.

Every printed page of the worksheet has a header with Name ____ Class ____, the lab number and title, a Dataset ID ____ line and the page number, so loose pages can be put back together. The same running header (with the student’s own name, class and Dataset ID filled in) appears on every page of the Word and PDF reports.

Class dashboard

Students also have a Get my transfer code button (Submit part) that shows their resume code and a QR code they can photograph to carry on from a phone, and a Pause & bookmark button that saves, remembers the part and next step, and shows it on the home page.

Every .docx report and progress file also carries the student’s progress data (name, class, Dataset ID, key results, pre-lab answers, parts done). Drop a whole class’s files on the class dashboard to get a sortable grid per lab (with each student’s Rate my confidence answer and a count of “I could teach this”, “I mostly get it” and “I’m lost” for the lab), a CSV export, flags for shared Dataset IDs or identical key results, and the pre-lab questions most often missed, worst first, so you know what to re-teach.

Everything happens in your browser: nothing is uploaded, and the page works offline once loaded. Reports printed to PDF carry no data, so ask for the .docx or the progress file.

Privacy

  • Nothing students type leaves their browser. Names, class periods, answers and data tables are kept in the browser on that computer. There are no accounts and no student records on a server.
  • Anonymous page views only. The site counts how many times each page is opened using GoatCounter, which sets no cookies and records no names or answers.
  • Reports are made on the student’s computer. The .docx and PDF are built in the browser. (The .docx tool is fetched from a public code library the first time it is needed, so that download needs an internet connection; Save as PDF does not.)

Teacher notes and answer keys

Teacher notes for every lab cover timing, materials, how each simulation maps to the bench procedure, common misconceptions, suggested answers and expected results. Because they include answer keys, they are password protected and encrypted, so they can’t be read from the page source or the repository. These notes are encrypted in the page, not behind a school login. Anyone with the password can open them.

Once unlocked, a notes page has a Lock notes button. The password is remembered only if you tick “Keep unlocked in this tab”, and only until you lock the notes or close the tab.

Open the teacher notes. To request the password, email [email protected]. Please don’t share the password with students.

Students see only the explanation that appears after they answer each pre-lab question.

Tips

  • Test on a student laptop first. Open a lab on the same kind of computer and browser your students use. Check that sign-in, a simulation run, Download .docx and Save as PDF all work on your school network and with your browser settings.
  • Clearing browser data erases work. Remind students that clearing history, cookies or “site data”, or working in a private window, removes their saved work. If they might do that, or if laptops are wiped between classes, they should save a progress file before they leave. The site shows a warning if it sees that the browser is not saving.
  • Shared computers. The site keeps one saved copy of each lab per browser, not one per student. Students who share a computer and a browser profile also share that saved work, so a second student would see the first student’s answers. Give each student their own computer or browser profile, or have them save a progress file and use Start over at the end of the period.
  • Ask for the file you want. Tell students whether you want the .docx or the PDF, and whether to include their Dataset ID (it is already on the report).

All 13 labs, their parts and where students get stuck

Each part name links straight to that part. The last column counts the parts in the lab and, in brackets, how many of them hold student work (written prompts, quiz questions, saved data tables or simulation steps). Overview, Background and Submit are reading or report tools, so they are not counted. The same number is used in each lab’s own progress count (“3 of 6 parts done”) and on the home page cards.

Two levels of progress. The completion rule is unchanged: a part counts as done only when all of its work is done. Beside that count, the lab’s step bar and the home page card also name the part a student is in the middle of and how many of its items are finished, for example “3 of 6 parts · Float assay 6/11 items”. A student who has begun but has not finished any part sees “Started · Float assay 6/11 items”, never “0 of 6”; a lab with no work yet reads “Not started”. An item is one prompt box, one quiz question, one saved data table or one required simulation step. Each step in the lab’s step bar also shows its own item count on hover.

The Where students get stuck column lists one or two places where students typically stall, taken from what each part’s Steps list and disabled buttons ask for. They are prompts for what to look for when you walk around, not answers.

InvestigationParts (links open that part)Where students get stuckParts (with work)
1. Artificial SelectionOverview Background Pre-lab Grow & score Select & pollinate Generation 2 Design Analyze Reflect Submit
  • Select & pollinate stays locked until all 150 generation 1 plants are scored; Score generation 2 needs generation 2 planted first.
  • Hand counts use the hairs on the right margin only, then Record my count; students tap hairs on the wrong side.
10 parts (7 with work)
2. Mathematical Modeling: Hardy-WeinbergOverview Background Pre-lab Card model Build the model Many generations Design Analyze Reflect Submit
  • The Steps list wants recorded runs at N = 100 and N = 1000, not just the first 16-zygote runs, and several Recalculate clicks.
  • In Design, Run experiment stays disabled until at least two levels are typed.
10 parts (7 with work)
3. Comparing DNA Sequences with BLASTOverview Background Pre-lab Morphology BLAST the genes Place the fossil Design Analyze Evaluate Submit
  • Record top 5 hits and the tree buttons do nothing until BLAST has been pressed.
  • Clades are grouped starting with the most widely shared trait, after the trait table has been checked; students start with a rare trait.
10 parts (7 with work)
4. Diffusion and OsmosisOverview Background Pre-lab SA:V Model cells Plasmolysis Water potential Design Analyze Evaluate Submit
  • The calculated columns (SA, V, SA:V, % reached or % change) are typed in the Data tab and then checked; students stay on the Graph tab.
  • Run the bag set at least twice for error bars. In Design, a level outside the allowed range (sucrose above 1.5 M, for example) is rejected.
11 parts (8 with work)
5. PhotosynthesisOverview Background Pre-lab Sink disks Float assay Design Analyze Evaluate Submit
  • Disks must all sink before the timer can start; if some do not after three vacuums they are left out, and a cup with no sunk disks blocks Start timer.
  • ET50 needs half the disks floating: if the run ends first, set a longer run (More options, Speed) and start again.
9 parts (6 with work)
6. Cellular RespirationOverview Background Pre-lab Microrespirometer Gas sensors Design Analyze Evaluate Submit
  • The check and rate boxes say “Run the experiment first” until a 25-minute run exists, and the white columns in the Data tab are typed by the student.
  • Equilibration and the water bath start ticked; a mean ± SE needs three runs in the replicate table.
9 parts (6 with work)
7. Cell Division: Mitosis and MeiosisOverview Background Pre-lab Mitosis model Root tips Cancer karyotypes Meiosis model Sordaria Design Analyze Reflect Submit
  • Record counts says “Mark some cells first”, and the χ² test stays locked until both jars are recorded or class data is added.
  • Meiosis needs Next stage until four gametes appear; pale asci in the Sordaria slide are immature and are not scored; 50 asci are needed.
12 parts (9 with work)
8. Bacterial TransformationOverview Background Pre-lab Transform Design Analyze Evaluate Submit
  • Counting, calculating and adding a run all say “Incubate your plates first”; students skip the nine procedure steps or the six predictions.
  • In Design at least one level must be ticked before Run experiment; the UV check is a separate tick box.
8 parts (5 with work)
9. Restriction Enzyme Analysis of DNAOverview Background Pre-lab Restriction enzymes Run a gel Standard curve Design: crime scene Analyze Evaluate Submit
  • Run the gel until the dye is about 1 cm from the end (about 60 mm on the Dye front readout), then turn the power off.
  • Measuring bands needs the gel stained and the power off. Samples must be loaded first, black lead to black and red to red; marker sizes are typed largest first.
10 parts (7 with work)
10. Energy DynamicsOverview Background Pre-lab Part 1: NPP Part 2: Larvae Design Analyze Reflect Submit
  • Harvest says “Let the seedlings grow first” until day 3, and the next harvest waits until the last one is dried.
  • Seal 5 plants (dark respiration) has to be done on the same day as a harvest; the barn data needs at least three barns for a standard error.
9 parts (6 with work)
11. TranspirationOverview Background Pre-lab Leaf area Stomata Water loss Design Analyze Evaluate Submit
  • Calculate and record stays disabled until both the full and partial square counts are typed.
  • Stomata are counted at 400X once the fine focus makes the guard cells sharp, for at least three fields; the t-test needs two groups run.
10 parts (7 with work)
12. Fruit Fly BehaviorOverview Background Pre-lab Geotaxis vial Choice chamber Design Analyze Evaluate Submit
  • Sex identification needs four of five correct; the reference card and the focus both matter.
  • Run the water-versus-water control first; the cross-trial button waits for a finished trial. Chamber position, light and fly type are in More options.
9 parts (7 with work)
13. Enzyme ActivityOverview Background Pre-lab Procedure 1 Procedure 2: pH Design Analyze Reflect Submit
  • Run needs valid conditions first: at least one pH buffer ticked and valid levels (the message sits under the box).
  • The color match is typed by the student in the Data tab (not needed with the spectrophotometer); the pH part needs at least three trials.
9 parts (6 with work)

Buy me a coffee ☕

The Lab Bench is free for every teacher and student. If it saved you some prep time and you'd like to say thanks, you can buy me a coffee. It's completely optional.

Buy me a coffee on Venmo (opens in a new tab)