A message needs a shared code
Choose a fictional distance-message problem and define a simple code before testing it. The sender and receiver need the same meaning for each signal. Provide visual, sound, or tactile alternatives and do not assume one mode is accessible to everyone. A successful signal must be detected and interpreted, not merely produced. Model this example: A tabletop code uses one gentle drum tap for start and two for stop; both partners receive the key before testing.
A worked example
A tabletop code uses one gentle drum tap for start and two for stop; both partners receive the key before testing.
- Start a dated investigation page for a message needs a shared code. Read and draw the complete included model: A tabletop code uses one gentle drum tap for start and two for stop; both partners receive the key before testing. Label at least three relevant features, separate two observations from one question, and choose a safe real observation or the included record as your evidence source.
- Construct an annotated diagram, sequence, comparison table, or tabletop paper model that explains this target: Design a light or sound signal with agreed meaning. Keep the included record beside the model, add arrows and labels for its relationships, and identify which detail is observed and which idea is a prediction or explanation.
- Use the two Practice questions as a discussion, then return to the investigation notebook for sustained work. Add three precise labels or records about the week’s phenomenon, compare the evidence with an initial prediction, and correct one unsupported statement without inventing an observation.
- Develop the weekly investigation or design: Create a two-message code, draw the key, test several messages, and record whether the receiver interprets each correctly. Compare a second safe observation with the first when available, or reconstruct a comparison from the included record. Label the evidence source, preserve any differences, and revise the model or plan using one specific result.
- Complete the evidence product: Create a two-message code, draw the key, test several messages, and record whether the receiver interprets each correctly. Check every label and claim against an actual observation or included record, invite a partner’s question, and add a limitation or next test. Present through drawings, objects, pointing, dictation, typing, or AAC, then complete the separate Check questions.
Open the printable learning material