Field Investigation Toolkit
BEYOND THE REFERENCE RANGE • FIELD INVESTIGATION SYSTEM
The website is the system. The files are working instruments. The archive is where an investigation remembers what happened.
Start with a question, choose only the tools that fit, work wherever the investigation actually happens, then return with findings, related files, repeat history, and the next rabbit hole.
FIRST: WHAT IS THIS THING? Four pieces. Four different jobs.
The Toolkit
The control center. Start here to choose an investigation path, build a field kit, find blank masters, and move into the archive.
The Working Files
Editable Word and fillable PDF instruments used during the investigation. They are not the archive and they do not silently upload anything.
My Investigation Archive
A real destination that stores the investigation’s home record, status, findings, tags, related links, repeat/branch relationships, and archive notes on that device.
BRR Public Libraries
Published Wonder Jar activities, completed Full SOPs, completed QUICK SOPs, and other finished BRR examples. These are examples and released resources—not a visitor’s private archive.
THE OPERATING LOOP Start → build → work → return → archive → branch.
Create a home record and name the question before paperwork starts breeding.
Choose only the files the investigation needs. A field kit can be one page or the entire cabinet.
Use the editable instruments in the field, kitchen, garage, classroom, backyard, or wherever curiosity caused the problem.
Add findings, next questions, file locations, evidence links, and what changed.
Close the record without flattening its history into “done.”
Create a linked new record for a repeat, variation, new site, new season, or suspiciously better idea.
CHOOSE THE DOOR, NOT THE FORM NAME
What is this becoming?
BUILD MY FIELD KIT
Check the instruments this investigation needs.
Selections stay on this device until cleared. The panel below becomes a compact download station for the chosen files. Start from scratch or use a sensible preset and edit it.
WONDER JAR ACTIVITY PUBLISHING MASTERS
Two blank masters. One activity. Different jobs.
These are the actual blank activity masters for creating Wonder Jar-style releases. They are intentionally separate from the general Investigation SOP Builder.
Full Activity SOP Master
The complete BRR activity record: Wonder and setup logic, materials, full procedure, mechanism/learning layer, field notes/QC, adaptation, extensions, closeout, and revision control.
When to use the Full master
Use it to create the complete authored activity record—the version that explains what to do, why it works, what can go wrong, what to notice, how to adapt it, and what should be retained for the next run.
What is built into it?
Wonder/question, activity identity, Builds, timing/setting/age, learning goals, materials, substitutions, preparation, safety, full numbered procedure, mechanism notes, field-note prompts, Bench Notes, QC/troubleshooting, tiny-scientist/access adaptations, extensions, cleanup, storage/reference metadata, and revision history.
How do I build one?
Write the Wonder first. Then design the activity around the observation or mechanism that can genuinely answer it. Build the Full SOP before condensing anything into a QUICK card. Keep procedural steps separate from the science explanation so the activity can be followed without burying the reason it works.
Advanced publishing workflow
Give every activity a stable activity ID and revision. Publish the activity story/page, Full SOP, and QUICK SOP as a linked set. Keep completed releases in the public SOP libraries; use My Investigation Archive for the working record, source/storage links, repeat history, and future revisions.
QUICK SOP Master
The at-a-glance working card used while the activity is actually happening: six run steps, Builds, safety, Field Note, Bench Note, QC, and access/tiny-scientist cues.
When to use the QUICK master
Use it as the working companion to the Full SOP—the page that can sit beside the activity without requiring anyone to reread the complete protocol while holding a toddler, a dropper, and an increasingly questionable tray of water.
How the pair works
The Full SOP is the complete record and teaching document. The QUICK SOP is the compact run card. A released Wonder Jar activity can have both without duplicating their jobs.
How do I make the QUICK version?
Do not write it independently. Condense the approved Full SOP into the six working steps, Builds, safety cue, Field Note, Bench Note, QC cue, and access/tiny-scientist adaptation. If an essential safety or decision point cannot survive condensation, the QUICK card is too short.
What belongs somewhere else?
Long explanations, references, source provenance, full troubleshooting logic, detailed substitutions, and revision rationale belong in the Full SOP or investigation record—not on the one-page run card.
GENERAL INVESTIGATION INSTRUMENTS
Use one. Stack several. Promote a small question when it refuses to stay small.
Activity & Investigation SOP Builder
A reproducible plan for a general investigation—not the Wonder Jar publishing master.
What is this?
A structured builder for turning a general activity, experiment, field outing, household test, comparison, or project into something another person—or future-you—could actually repeat.
When would I use it?
Use it when the process matters enough to repeat, compare, share, or revise: experiments, field outings, kitchen tests, household projects, comparisons, and multi-step curiosity.
How do I use it?
Start with the question and objective. Define what would count as a useful observation. Add only enough procedure to make the work reproducible. Record decision gates rather than pretending the original plan survived intact. Finish with findings, repeatability, changes for next time, and the next question.
What’s inside?
Question, objective, criteria, materials, preparation, safety, setup, procedure, decision gates, observations, evidence, deviations, interpretation, repeatability, next question, versioning, and storage/record-management metadata.
Advanced ways to use it
Pair it with Field Notes for repeated observations, assign evidence IDs that cross-reference a Case File, create branching decision paths, compare revisions, and promote an excellent repeatable process into a reusable Reference Sheet.
Rapid Investigation Guide
For questions that need structure, not a committee meeting.
What is this?
The compact front door to the system: question, context, quick check, observation, answer-for-now, and a deliberate decision about whether the question deserves promotion into something larger.
When would I use it?
The question is same-day, spontaneous, or small enough that a full protocol would be ridiculous—but interesting enough that memory cannot be trusted.
How do I use it?
State the question in one sentence. Capture only the context needed to interpret the result. Choose the next check before collecting more information. Stop when the question is answered—or deliberately promote it into a full investigation, case, or observation series.
What’s inside?
Question, context, prediction, conditions, mini-path, observations, evidence, decision gate, confidence check, unexpected finding, answer-for-now, next rabbit hole, and repeat/record status.
Advanced ways to use it
Run several as independent trials, compare observers, attach them to a Reference Sheet as field-verification records, or use recurring rapid investigations to justify a larger longitudinal project.
Field Notes + Observation Record
The raw evidence layer: conditions, measurements, sketches, patterns, repeats, and details that disappear first.
What is this?
The raw evidence layer for qualitative observations, quantitative measurements, sketches, timestamps, photo references, conditions, repeated observations, and comparison points.
When would I use it?
Use it whenever the observation itself matters: nature walks, growth tracking, weather, repeated tests, before/after comparisons, materials behavior, or as the evidence layer beneath another toolkit document.
How do I use it?
Record conditions before interpretation. Separate what was seen or measured from what it might mean. Preserve strange details even when they do not fit the current explanation. Use the same fields during repeats so comparison becomes possible.
What’s inside?
Date/time, location/context, conditions, prediction, sensory observations, measurements, sketch space, photo/attachment references, patterns, comparisons, unexpected changes, confidence, interpretation, and next observation.
Advanced ways to use it
Create longitudinal records, run parallel observers, use one sheet per specimen/site/day, assign evidence IDs for a Case File, and compare seasons, locations, or treatment conditions.
Reference Sheet + Field Guide Builder
Turn repeated lookup, explanation, or rediscovery into a useful one-glance reference.
What is this?
A builder for turning scattered knowledge into a one-glance field guide: identifiers, thresholds, quick steps, warnings, visual cues, exceptions, comparison points, and source notes.
When would I use it?
The same information keeps being searched for, taught, packed, identified, measured, or forgotten in exactly the same irritating way.
How do I use it?
Begin with the decisions the guide needs to support. Keep information that changes recognition, action, or interpretation. Put exceptions beside the rule they modify. Field-test the guide and revise whatever was difficult to find.
What’s inside?
Purpose, audience, identifiers, essential facts, process summary, thresholds, cautions, decision points, exceptions, source notes, visual/sketch area, field test, revision history, and publication/storage references.
Advanced ways to use it
Create beginner and advanced editions, laminated field sheets, seasonal versions, QR-linked deeper references, or a family reference binder with version control.
Case File + Investigation Record
Known facts, unknowns, evidence, competing explanations, testing, disposition, and reopen criteria.
What is this?
A case dossier for questions with multiple clues, competing explanations, tests, eliminated possibilities, unresolved pieces, and a conclusion that may still contain an asterisk.
When would I use it?
Mysteries, troubleshooting, “what caused this?” investigations, identification problems, multi-source evidence, or any situation where one observation is not enough.
How do I use it?
Separate known facts from assumptions. Inventory evidence before choosing an explanation. Write competing explanations down early, then record what each check supports, weakens, or leaves unchanged.
What’s inside?
Case identity, question, knowns, unknowns, evidence inventory, timeline, competing explanations, tests/checks, findings, eliminated possibilities, evidence-strength review, unresolved questions, working conclusion, disposition, reopen criteria, and storage references.
Advanced ways to use it
Number evidence and connect it to clue cards, create timelines, run blinded interpretations, compare related cases, or reopen a closed case when new evidence appears without overwriting the original record.
Evidence, Clue + Signal Set Builder
Cards, clues, specimen/evidence IDs, matching, sorting, sequencing, progressive reveals, and trail systems.
What is this?
A builder for evidence cards, clue cards, specimen cards, signal sets, matching/sorting systems, sequence cards, trail markers, progressive reveals, and mini investigation prompts.
When would I use it?
Use it when information is easier to investigate as movable pieces: scavenger hunts, identification, classification, sequencing, case evidence, field stations, pattern detection, or branching activity paths.
How do I use it?
Decide what each card is allowed to do before designing it. Keep one primary piece of information per card, assign stable IDs, use signal types consistently, and test whether the set accidentally gives away the answer.
What’s inside?
Set identity, card purpose, legend/key, ID scheme, front/back prompts, evidence strength, source/reference, reveal timing, sorting logic, sequence rules, distractors, field-use notes, and revision tracking.
Advanced ways to use it
Cross-reference card IDs to a Case File, build progressive clue releases, create blind sorting tasks, design location-based field trails, or maintain multiple versions for different ages/experience levels.
Unexpected Findings + Deviation Record
Because “that was not supposed to happen” is often the beginning of the useful part.
What is this?
A formal place for the moment when the plan and reality stop being on speaking terms: what was expected, what actually happened, why it matters, what changed, and what should happen next.
When would I use it?
Use it when a procedure changes, a material behaves differently, a safety/quality checkpoint fails, an unplanned condition appears, or a deviation produces a surprisingly useful result.
How do I use it?
Capture the deviation before rewriting the story. Record the immediate response, effect on the result, supporting evidence, suspected causes, whether the run remains interpretable, and what will be changed or verified next time.
What’s inside?
Expected vs. actual, timing, impact, evidence, suspected cause, immediate action, recovery, validity, recurrence risk, corrective/preventive change, verification, related record/storage link, and closeout.
Includes “Unexpected, but better.”
Not every deviation is a failure. Capture whether the unexpected route improved access, clarity, efficiency, engagement, or the investigation itself—and whether it should become the next approved version.
Complete Field Investigation Workbook
The whole 20-stage investigation spine in one continuous editable record.
What is this?
The full 20-stage investigation system in one continuous record for work that is complex, long-running, multi-part, or simply too interesting to keep scattering across separate pages.
When would I use it?
Use it when an investigation will likely span multiple sessions, require several evidence types, involve repeats/branches, or eventually need a coherent final record rather than a stack of disconnected tools.
How do I use it?
Do not fill every field because it exists. Use the stages that genuinely support the investigation, mark unknowns honestly, preserve changes and deviations, and keep the record map/storage locations current so the website archive can point back to the working material.
What’s inside?
The complete shared spine from identity/question through procedure, evidence, interpretation, next questions, repeatability, revision, record map, and storage references.
Advanced ways to use it
Use it as a parent record for multiple related investigations, maintain linked repeats by season/location/treatment, or pair it with the website archive as the durable narrative document while the archive handles project navigation.
SHARED LOGICSee the 20-stage investigation spine+
Every instrument speaks the same underlying language, so a ten-minute note can become a full case without losing its original record.
- 01Identity + version
- 02Question / curiosity
- 03Why this matters
- 04Background / context
- 05Objective
- 06Prediction / hypothesis
- 07Success / observation criteria
- 08Materials + equipment
- 09Safety + preparation
- 10People + roles
- 11Conditions + environment
- 12Setup
- 13Procedure / path
- 14Checkpoints + decisions
- 15Observations
- 16Measurements + evidence
- 17Unexpected findings / deviations
- 18Interpretation + findings
- 19Follow-up questions
- 20Record management: archive / repeat / adapt
MY INVESTIGATION ARCHIVE
The archive is now an actual destination.
Create investigation records, filter by status/type, add findings and related links, archive records, create linked repeats/branches, and export/import a backup. Records are stored locally on that browser/device unless exported.
PUBLISHED BRR LIBRARIES
Blank masters live here. Finished BRR work lives there.
FIELD RULES
A SMALL MARK OF APPRECIATION
No account needed. Tap again to undo.
