The Need-to-Know List: Inquiry That Drives Itself

What if your class wrote the to-do list for the whole project instead of you?

UNI-FIED Education TeamLast reviewed September 7, 2026
Students adding sticky notes with questions to a class chart at the start of a project

You launch a project with a great driving question. Students nod. Then ten minutes later, hands go up: "What are we actually supposed to do?" and "How is this graded?"

That gap between launching a project and students owning it is where a lot of PBL stalls. The Need-to-Know List is the small routine that closes it. It asks students, right at the start, to name what they already know and what they still need to find out, so the project becomes their list of questions, not just yours.

In this guide:

  • What a Need-to-Know List actually is
  • Why it works, according to PBLWorks
  • How to run it in seven concrete steps
  • A real example from a Grade 7 science class
  • Variations and the best moments to use it
  • Mistakes that quietly kill the routine
  • Quick answers to common questions

What is a Need-to-Know List?

A Need-to-Know List is a running, visible list of the questions students must answer to complete a project. You generate it together right after the project launch, and you revisit and grow it as the inquiry goes on.

It comes from PBLWorks (the Buck Institute for Education) and lives inside their Gold Standard PBL design element called Sustained Inquiry. The idea is simple: an authentic project naturally raises questions, so you make those questions explicit and let them steer the work.

In practice it's often two columns or two charts. One side captures "What do we already know?" The other captures "What do we need to know?" The second list is the engine. Each item is something students will research, test, interview about, or figure out, and the list keeps changing as they learn.

Why does it work?

It works because it hands the inquiry to students without giving up rigor. PBLWorks describes Sustained Inquiry as an extended process of asking questions, finding resources, and applying information, and the Need-to-Know List is how that process gets named and tracked.

There are a few reasons it earns its place. First, it surfaces what students already know, so you're not teaching over the top of existing understanding. Second, it turns a vague project into a concrete set of questions, which lowers the anxiety of "what are we doing?"

Third, and most important, the questions belong to the class. PBLWorks ties strong projects to student voice and ownership, and a list students wrote themselves carries more pull than a checklist you handed out. When a student researches something they personally asked, the work feels like answering their own question, not completing your assignment.

It also doubles as quiet formative assessment. The questions students raise (and the ones they don't) tell you exactly where their understanding starts.

How to run it, step by step

You can run the first round in about twenty minutes. Here's a sequence that keeps it student-led.

  1. Launch with a strong entry event first. A film clip, a guest, a field trip, a surprising data set, or a provocation. PBLWorks calls this the entry event, and the Need-to-Know List works best when students have just hit something they care about and don't fully understand yet.

  2. Post the driving question where everyone can see it. Something open and real, like "How can we make our cafeteria more sustainable?" The list will hang off this question.

  3. Ask what they already know. Give two minutes of quiet thinking, then collect answers on a "Know" chart. This builds confidence and shows you their starting point. Accept partial or shaky knowledge; you'll test it later.

  4. Ask what they need to know. This is the heart of it. Have students brainstorm every question they'd have to answer to do the project well. Sticky notes or a shared doc work well so everyone contributes, not just the fastest talkers.

  5. Sort and cluster the questions. Group them into themes: content questions ("How much waste do we produce?"), process questions ("Who do we present this to?"), and logistics ("When is it due?"). Answer the logistics on the spot so they don't crowd the thinking.

  6. Keep the list visible and use it to plan. The Need-to-Know List becomes your shared agenda. When you teach a mini-lesson or schedule research time, point back to which questions it answers. Cross off questions as they get answered.

  7. Revisit and add new questions in cycles. PBLWorks describes inquiry as cycles of research, refinement, and a fresh Need-to-Know List. Every week or so, ask "What do we know now that we didn't? What new questions came up?" The list should grow and shift as the project deepens.

A real example: Grade 7 science

Picture a Grade 7 science class on a local water-quality project. The driving question is "Is our creek healthy, and what can we do about it?" The entry event is a short walk to the creek, where students notice foam near the storm drain and almost no insects in the water.

Back in class, the "Know" chart fills fast: water comes from rain and runoff, pollution is bad, fish need clean water. Then comes the "Need to Know" chart, and it gets specific: What makes water "healthy"? How do scientists actually test it? What's that foam? Where does the storm drain go? Who decides if a creek is clean? How do we present what we find, and to whom?

Those questions become the project map. The teacher runs a mini-lesson on dissolved oxygen and pH because three sticky notes asked about it. A small group researches the storm drain because that question clearly hooked them. Two weeks in, after sampling, new questions appear: "Why is oxygen lower downstream?" and "Could the school be part of the problem?" The list grows, and the project keeps its momentum because students are still chasing their own questions.

Variations and when to use it

The routine flexes to fit your grade and timeline.

For younger students, keep it oral and visual. Use pictures, draw the questions, or do a shared "I wonder" wall. The thinking is the same; the recording is lighter.

For a single rich lesson rather than a multi-week project, you can run a mini version. Show a phenomenon or text, then build a quick "what we know / what we wonder" chart to drive that day's work. It pairs naturally with See-Think-Wonder.

For individual accountability, have each student keep a personal Need-to-Know section in their project journal alongside the class list, so everyone tracks their own open questions.

The best time to use it is right after any project launch or entry event, when curiosity is high and direction is low. It's also useful any time a project loses steam: pull the list back out and ask what's still unanswered.

Common mistakes to avoid

The most common mistake is making it your list. If you arrive with the questions pre-written, you've skipped the entire point. Let the questions be a little messy and student-shaped, even if you have to nudge a missing one into view.

A second mistake is treating it as a one-time launch activity. The power is in revisiting it. A list made once and never touched is just a poster. Build a weekly moment to update it.

Third, watch for skipping the entry event. Without something concrete to react to, students struggle to generate real questions and you end up back in lecture mode. Give them an experience worth wondering about first.

Finally, don't let logistics swallow the content. "When is it due?" matters, but answer those quickly so the meaty questions get the air time.

How UNI-FIED helps

Building this from scratch for every topic takes time most teachers don't have. UNI-FIED builds routines like the Need-to-Know List into ready-to-teach activity cards matched to your topic and grade, with entry-event ideas, question prompts, and a starter chart you can put on screen in the first minute of class. You stay in charge of the inquiry; the prep is just lighter.

Frequently asked questions

How is a Need-to-Know List different from a KWL chart? They're cousins. A KWL chart is usually a one-time, lesson-level snapshot. A Need-to-Know List is a living document for a whole project that you grow and revisit across weeks, and its questions actively drive the work rather than just record it.

Do I grade the list? Not directly. It's a thinking and planning tool, not a product. You can use it formatively to see where students are and to plan instruction, and you can ask students to reflect on how their questions changed.

What if students don't ask the right questions? That's normal, especially early. Add a question yourself as "one I'm wondering too," or run a short entry experience that points them toward the gap. You're allowed to seed the list as long as the bulk of it is theirs.

How long does it take to set up? The first round runs in about twenty minutes once you have an entry event. Updates later take five to ten minutes.

Does it work outside of full PBL? Yes. Even a single inquiry lesson benefits from a quick "what we know / what we need to know" chart. The full version shines in PBLWorks-style projects, but the move scales down nicely.

Give your students the first word on what the project needs, and you might be surprised how much they're willing to carry from there.

Sources & further reading

Run this in your classroom tomorrow

UNI-FIED turns your topic, grade, and lesson length into ready-to-teach activity cards built on routines like this one — no prep, no curriculum change.

See how UNI-FIED works

Related routines

Published September 7, 2026.