← Teacher guide

Algorithms for congruence

Students follow, order, fix and design algorithms that decide whether two triangles are congruent, similar or neither, testing them on one pair of every kind (AC9M8SP04, nodes 1 and 2).

Angles and shapes · Algorithms · about 45 minutes · Open the student lesson

Classroom resources

Load these into Waypoints Prepare: choose Load URL and paste the copied address, or download the file and import it. In Prepare, the worksheet's Teacher edition shows the answers; the student copy hides them.

Students will be able to

Timing

Predict and Run 10 min · Investigate 10 min · Modify 10 min · Practise and Make 15 min

Before class

Do the Run board yourself first. Students need the congruence tests, similar triangles and the shape-classifying algorithms from Year 7.

The one idea: order matters (congruent before similar, because congruent triangles are similar too), every case needs a path, and the algorithm is only trusted once it has been tested on one pair of each kind. The common mistake is an algorithm that accepts any angle with two sides (Raj's SSA mistake).

The board is the same key used for classifying shapes; each specimen is a pair of triangles. Answer "yes" only when the description says the parts are equal. The improved key adds step G for SAS similarity, a gap students find in Modify.

Wider: compare two correct algorithms for the fewest questions; write the algorithm in Python with if and elif.

Running the lesson

  1. Predict: ask what equal angles alone tell you.
  2. Run: ask which question separates congruent from similar.
  3. Investigate: ask Raj which angle the SSA pair has.
  4. Modify: ask what test case would have found the gap.
  5. Make: ask a partner to trace your algorithm on an SSA pair.

The hard part (on purpose)

Answering from what is known, not what could be worked out. Ask 'does the description say that?' before every yes.

When students get stuck

What you will seeA question to askThe fix
A student answers yes to SSS for the RHS pair (by working out the third side).Does the description give all three sides?Answer from what is given; RHS has its own question.
A student answers yes at step B for the RHS pair.Is the right angle between the hypotenuse and the 5 cm side?The right angle is between the two shorter sides; RHS has its own question at E.
A student puts the similarity question first.What would a congruent pair be called then?Ask the most specific question (congruent) first.
A student's algorithm has no answer for some pairs.Where does a 'no' at your last question go?End with a catch-all: 'not enough to tell'.

Answers to the checks

  1. angles only: An algorithm asks only: 'Are all three pairs of angles equal? Yes: congruent.' Two triangles both have angles 40°, 60° and 80°, but one is twice as big. What does it say?
    Congruent, which is wrong. Equal angles make the triangles similar; congruence needs a matching side too.
  2. six pairs: Follow the algorithm for all six pairs of triangles. Answer each question from what the description says is equal. How does it handle the twice-as-big pair, compared with your prediction?

    Every pair reaches its own answer. Equal angles with unequal matching sides give 'similar', and SSA gives 'not enough to tell'.
  3. Order the steps: Put the steps of a short algorithm in order. It leaves out RHS and the other similarity tests; the Run algorithm has them.
    see the program below
    List the parts, test SSS, then SAS, then two angles (with or without a matching side), and finish with 'not enough to tell'.
    List the equal parts of the two triangles.
    If all three pairs of sides are equal, say "congruent (SSS)" and stop.
    If not, and two pairs of sides and the angle between them are equal, say "congruent (SAS)" and stop.
    If not, and two pairs of angles are equal, check the sides next.
    If a matching pair of sides is equal too, say "congruent (ASA or AAS)"; if not, say "similar".
    Otherwise, say "not enough to tell".
    
  4. Find the mistake: Raj tests his algorithm on triangles with sides 6 cm and 8 cm and a 30° angle opposite the 6 cm side, and it says congruent. Click the line that is wrong.
    line 3
    Line 3: 'any pair of angles' lets SSA through. The angle must be between the two sides (SAS).
  5. Trace a pair: Two triangles both have angles 50° and 60°. The sides between those angles are 5 cm and 10 cm. Trace the Run algorithm. Where does it end?
    Similar (AA): two angles equal, but the matching sides are not
    A no, B no, C yes (two angles), D no (5 ≠ 10): similar with scale factor 2.
  6. A gap: One triangle has sides 4 cm and 6 cm with 50° between them; the other has 8 cm and 12 cm with 50° between them. Where does the first algorithm (the Run board) send this pair?
    Neither, or not enough to tell: it has no step for this
    It answers no at every step. But the pair is similar: two sides in the ratio 2 with the angle between them equal (SAS similarity).
  7. The fix: This algorithm has a new step G. Run it on all seven pairs. Does every pair, including the new one, reach the right answer?

    Step G catches SAS similarity, and the six old pairs still get the same answers.
  8. The longest path: In the improved algorithm, how many questions does it ask before it says 'Neither, or not enough to tell'?
    6
    A, B, C, E, F, G: six questions. Pairs that are congruent by SSS need only one.
  9. Test again: Why must a fixed algorithm be tested on the old pairs again, not only the new one?
    A change can break a path that used to work
    Re-running every test case checks the fix didn't break anything else.
  10. RHS: Both triangles have a right angle, a 10 cm hypotenuse and a 6 cm side. Which answers does the algorithm give, in order?
    No, No, No, then Yes at E: congruent (RHS)
    A no, B no (the right angle is not between them), C no, E yes: RHS.
  11. SSA: Both triangles have sides 7 cm and 5 cm, and a 40° angle opposite the 5 cm side (not between them). What should a correct algorithm say?
    Not enough to tell
    SSA can give two different triangles, so the algorithm must not say congruent.
  12. Describe it: Which describes the algorithm best?
    It checks the congruence tests first, then the similarity conditions, and says 'not enough to tell' if none fit
    Most specific first (congruent), then the wider class (similar), then a catch-all.
  13. Review: parallelograms: Review: in parallelogram ABCD, angle A = 75°. What is angle B, in degrees?
    105
    A and B are neighbours (co-interior): 180 − 75 = 105°.

Solutions

One possible solution for each task. Other correct programs are fine.

find a gap and fix it › A gap

Open task: any program that does what the step asks.

find a gap and fix it › The fix

Open task: any program that does what the step asks.

find a gap and fix it › The longest path

Open task: any program that does what the step asks.

find a gap and fix it › Test again

Open task: any program that does what the step asks.

your own algorithm

Open task: any program that does what the step asks.

Stretch and support

Stretch: Write the algorithm in Python with if, elif and else, and test it on your six pairs. What is the fewest number of questions that separates all the answers?

Support: Give the questions on cards and the six test pairs on cards; students order the questions, then run each pair through.

Coach prompt (optional)

For a student who has done the lesson and is still stuck. They paste it into an AI tool your school allows; it asks questions about this lesson's one idea and doesn't give answers. Students see it on the course recap page only through a link ending in ?coach=1: recap with coach prompts.

You are a patient maths coach for a Year 8 student in Australia. Help me understand the ideas in ONE lesson only, from the lesson "Algorithms for congruence".

The ideas:
- Designing a congruence/similarity classification algorithm: I can Students design a step-by-step algorithm that correctly classifies two triangles as congruent, similar, or neither, using the appropriate conditions.
- Evaluating and describing algorithms: I can Students trace through a given algorithm with test cases, identify errors or limitations, and describe in plain language how it works.

What understanding looks like:
- Designs an algorithm that correctly classifies triangles using at least two conditions.
- Includes clear decision points with yes/no branches.
- Tests the algorithm with at least two examples and corrects any errors.
- Correctly traces an algorithm with given inputs.
- Identifies at least one error or limitation in a given algorithm.
- Describes the algorithm's logic in plain language.

Mistakes students often make here:
- A student answers yes to SSS for the RHS pair (by working out the third side).
- A student answers yes at step B for the RHS pair.
- A student puts the similarity question first.

How to coach me (rules from the Waypoints Kit coach):
- Ask me one short question at a time (2 to 4 sentences) and wait for my answer. Never give me the answer before you have heard my thinking, and don't hide the answer inside your question.
- Start in Discover: ask me to explain the idea in my own words, or to predict what happens in a simple example. I can switch any time: "teach it back" (you play a beginner and I explain), "spot the flaw" (you show me an answer with one common mistake and I find it), or "check" (I explain, and you tell me what is solid and what to revisit).
- If I am stuck or say "just tell me", ask what I think first, then give a small hint or a simpler example. Explain only after I have had a real go.
- Stay in this idea: don't teach later ideas or add extra content. If I ask about something else, say it is for another lesson and bring me back.
- After you help, ask me one reflective question, such as how I know my answer is right or what I would check.
- Praise my effort and method, not my ability.
- You can be wrong: if I rely on something you said, remind me to check it against my notes or the lesson. If you don't know, say so.
- Use simple words.
- Stop when I can explain the idea in my own words and get one new example right. Then tell me to go back to the lesson "Algorithms for congruence".

Exit ticket

Why must an algorithm for congruence not answer 'congruent' when two sides and any angle are equal?

If the angle is not between the sides (SSA), two different triangles can fit, so they might not be congruent.

What each step is for

Where it leads

This covers AC9M8SP04.

Where it leads: algorithms in code (the Code pathways), and similar triangles in trigonometry (Year 10).