Systems Log Guide
The Systems Log is the child's running record of noticing, drawing, predicting, and revising. It should feel useful, not heavy.
A simple notebook, stapled packet, or folder of pages is enough.
The Main Template
Use this simple template all year:
What I noticed:
What moved:
Where it came from:
Where it went:
My drawing:
One question I still have:
This is the base format that appears across the weekly pages.
Add The Environmental Checkpoint When Needed
When a lesson includes a claim, chart, sign, map, video, product label, or project idea, add one or two questions from the Environmental Checkpoint:
- What system is involved?
- What parts are connected?
- What evidence, observations, or data are shown?
- Who or what is affected?
- What should we ask or check next?
The Systems Log does not need every prompt every week. It works best when facilitators choose the smallest useful next question.
Why This Works
The log helps children:
- slow down and notice details
- draw flows instead of only talking about them
- connect predictions with results
- keep a record of how their thinking changes
- return to earlier pages and see growth over time
Keep It Child-Friendly
A good Systems Log page does not need long writing.
Good entries can include:
- arrows
- boxes or circles
- a labeled sketch
- one or two short sentences
- a count, estimate, or quick table when it helps
- a question that still feels alive
Accept drawing-first entries, dictated answers, or shared writing when needed.
Younger Learner Tips
For ages 8-9, drawings often carry the thinking.
Helpful sentence starters:
- I noticed...
- It moved from... to...
- I think next...
- The system changed when...
Strong younger-learner entries often include:
- arrows showing direction
- labels like in, out, wet, dry, up, or down
- one comparison, such as before and after
- a question at the end
Older Learner Tips
Older learners can gradually add more evidence without losing the simple structure.
Useful upgrades:
- times or dates
- counts or approximate weights
- quick comparison tables
- simple before-and-after estimates
- short notes about tradeoffs, limits, or patterns
- source notes, attribution reminders, or questions about whether a chart or image might need checking
The goal is still clarity, not fancy formatting.
Reflection And Self-Assessment
The Systems Log can also support reflection. Every few weeks, ask the learner to circle or answer one short self-check prompt from Self-Assessment, such as:
- I can name parts of a system.
- I can show a cycle, flow, or cause-and-effect relationship.
- I can ask what should be checked before I trust or share a claim.
Keep the tone low-pressure. The log is for noticing growth, not grading effort.
Example: Week 3 Terrarium Entry
What I noticed:
Water drops formed on the lid.
What moved:
Water moved from the soil and plants to the glass.
Where it came from:
The water started inside the jar.
Where it went:
Some of it slid back down.
My drawing:
Jar with drops on top and arrows back to the soil.
One question I still have:
Will there be more drops tomorrow or fewer?
Example: Week 10 Fish Pond Entry
What I noticed:
The pond got smaller fast when we took too many fish early.
What moved:
Fish moved from the pond to the players.
Where it came from:
The fish started in the shared pond.
Where it went:
The pond had too few left to grow back well.
My drawing:
Start pond and end pond with round numbers.
One question I still have:
Which rule would help the pond most next time?
What Growth Looks Like Across the Course
| Early weeks | Middle weeks | Capstone weeks |
|---|---|---|
| noticing and drawing | tracing paths and loops | planning, testing, and revising |
| simple labels | clearer arrows and categories | tradeoffs and version 2.0 thinking |
| short predictions | simple cause-and-effect explanations | stronger redesign reasoning |
Facilitator Habits That Help
- Ask to see the log during the lesson, not only afterward.
- Model one quick entry yourself from time to time.
- Accept unfinished drawings if the system idea is clear.
- Revisit older pages and compare them with newer ones.
- Keep the log useful. Do not turn it into copying practice.
Common Problems and Quick Fixes
| Problem | Quick fix |
|---|---|
| The child freezes when asked to write | Start with the drawing box first |
| The child copies vocabulary only | Ask for one real example from the room or house |
| The page gets too wordy | Limit it to one sketch and three short sentences |
| The numbers have no meaning | Ask, "What does that number tell you?" |
| The child resists every week | Let them pick marker color, format, or which prompt to answer first |