Vocabulary | What Is a Decision Table? Turning Everyday Rules into Clear Choices

Imagine a small reading club preparing two kinds of activity pack. Its organiser gives a complete rule: “Use the outdoor pack when the courtyard is open and the activity has been assigned outdoors. In every other case, use the indoor pack.” The instruction is short. Even so, there are two separate conditions. An open courtyard does not tell us where the activity has been assigned. An outdoor assignment does not tell us whether the courtyard is open.

A reader who notices only the first condition may take the outdoor pack simply because the gate is open. Another may notice only the activity list and take the same pack when the courtyard is closed. Both know the individual words. Their difficulty lies in combining the words without losing a requirement.

The table does not add a new policy. It expresses the stated policy in a different form. Every row answers the same question: which pack should be used? The first two columns describe conditions. The final column gives the result. Read one row across, checking every condition in that row before taking its result.

A row is a rule for a kind of case

One row can cover many actual occasions. Monday’s activity and Thursday’s activity could both have an open courtyard and an outdoor assignment. They are different events, but they belong to the same row for this decision. The table deliberately ignores details that do not change the pack: the name of the student carrying it, the colour of the timetable and the title of the story.

That selective attention is useful only if the ignored details really are irrelevant to the stated decision. Suppose a new activity requires a special accessible format. The original pack rule may still decide indoor versus outdoor, but it cannot decide whether the selected pack meets that participant’s needs. We would need another decision or a revised specification. A neat table does not make an incomplete problem complete.

Notice the phrase “in every other case” in the original instruction. It matters. Without that phrase, the sentence about using the outdoor pack would tell us what happens when both conditions are satisfied, but it would not necessarily settle all remaining combinations. The table is complete here because the supplied rule explicitly covers them. We must not silently write an opposite result merely to fill an empty cell.

Several layouts can express the same logic

This guide puts rules in rows and conditions in columns because that is easy to read on a page. Other decision tables put conditions in rows and rules in columns. Neither orientation changes the underlying job. What matters is that readers can distinguish the conditions, the combinations and the outputs, and that the legend explains any symbols.

Formal systems also use decision tables. The Object Management Group publishes Decision Model and Notation, including the version 1.5 specification, for representing decision logic. Our everyday examples are teaching tables, not a claim to implement that specification. You can learn the central reasoning without learning a software language.

What the representation lets you inspect

Return to the four rows. You can now ask questions that are less obvious in the flowing sentence. Have we accounted for all combinations? Do two rows describe the same case? Does the result really follow from the source instruction? What happens if we do not know whether the courtyard is open? Is “open” a description of the gate, an official availability status or something else?

Those questions show why the table belongs in a vocabulary series. The table’s structure creates places where meanings must be made explicit. The word open needs a stable interpretation. The word and requires both conditions. The phrase every other case closes the remaining possibilities. Language is doing practical work inside the representation.

Try explaining the second row without using the table’s exact wording. A good explanation is: “The courtyard can be used, but this activity has not been assigned there, so the stated rule selects the indoor pack.” You have shown the relevant distinction. Saying “indoor because the answer is indoor” merely repeats the result. A useful table should support an explanation that connects the known facts to the rule.

Contents · Next chapter

A vocabulary item becomes more useful when it helps someone perform a task. In a decision table, a word can identify a condition, separate one state from another, mark the relationship between requirements or specify the next action. These are different jobs. Treating them as one undifferentiated list of “important words” makes the table harder to build.

Consider a group preparing a display. Its working vocabulary includes draft, reviewed, approved and displayed. These labels describe different states. A draft exists. A reviewed draft has been examined. An approved version has received the required decision. A displayed version has actually been put up. A group can use different local definitions, but it needs to agree what its own labels mean.

If the group treats all four words as synonyms for “done”, it loses information. Someone may display a reviewed version that has never been approved. Someone else may assume an approved file is already on the board. The problem is not a shortage of impressive vocabulary. It is a failure to preserve distinctions that affect action.

Words help divide the work

Imagine the complete local rule is: “If both the content review is complete and the display approval is recorded, display the current version. Otherwise, keep it in the preparation folder.” We can ask separately about review and approval. A reviewer can confirm one field; an organiser can confirm the other. The decision table then combines those answers.

This division can make teamwork easier to inspect. Instead of asking, “Is everything okay?”, the group asks, “Which version was reviewed?” and “Where is the display approval recorded?” Those questions are narrower. They give a person a fair chance to answer exactly what they know. The table connects the answers without pretending that one person has checked everything.

The same principle applies to personal study. A student might distinguish attempted, checked and corrected. Those words can identify the next useful action: attempt a question, compare the reasoning, or repair a particular mistake. The result depends on the task and the chosen study routine; the labels do not guarantee learning merely because they appear in coloured boxes.

The table changes what you have to remember

Without a written representation, you may need to keep several conditions and exceptions in mind while checking a case. With a table, you can inspect them. That is a practical change in the task: some of the structure is now on the page. You still have to read it correctly, gather the right facts and notice when the situation falls outside its limits.

Research by Jiajie Zhang and Donald Norman examined how internal and external representations work together in problem solving, using versions of the Tower of Hanoi task. Their 1994 paper on distributed cognitive tasks provides a useful research background for taking representations seriously. It does not establish that any particular vocabulary table improves every learner’s performance. The applications in this guide are original teaching examples to inspect and test.

You can observe a modest benefit directly in the display example: the table gives review and approval separate places. That makes their difference visible. Whether this reduces actual mistakes depends on whether the labels are understood, the records are current and the group uses the table at the relevant moment. Those are conditions to examine, not details to wish away.

Learn the relationship as well as the word

Writing “approved means accepted” on a flashcard may help with an initial definition. It does not answer who can approve the display, which version they approved, what the approval permits or whether another requirement remains. A richer learning record includes the word, an example, a non-example and the action it changes in a specified situation.

For instance: “Reviewed: someone completed the agreed content check. Non-example: someone opened the file but did not inspect it. Consequence: one requirement for display has been met; the separate approval requirement may still be outstanding.” That record has a small operational role. It helps the learner use the word without stretching it beyond the evidence.

Vocabulary as technology does not mean that every sentence is computer code or that people should behave like machines. It means language can be deliberately arranged into a reusable aid. The aid can amplify attention and coordination by keeping a meaningful distinction available. Its value comes from the quality of that distinction and the care with which people apply it.

A useful first exercise is to find three words your group currently uses as if they meant the same thing. Ask whether they actually describe different facts. If they do, choose one small decision that depends on the difference. You now have the beginning of a decision table grounded in a real communication need.

Contents · Previous chapter · Next chapter

Before drawing a large table, sort the information into three parts. A fact describes the particular case you are considering. A condition is a test used by the rule. A result is what the rule assigns when the relevant tests are satisfied. Confusion between these parts can make a table look complete while its reasoning runs in a circle.

Suppose a fictional art club must choose a label for a supply envelope. The rule says, “Label an envelope complete when it contains six paper sheets and one instruction card; otherwise label it awaiting contents.” An observed envelope contains six sheets and no card.

The observed facts are the counts in that envelope. The conditions ask whether the required sheets and card are present. The result is awaiting contents. The result is not itself evidence about the envelope; it is a conclusion reached by applying the rule to the observed facts. If someone labels an envelope complete without checking it, the label alone does not establish that its contents satisfy the rule.

Do not let the result appear as its own requirement

A circular table might say, “If the envelope is complete, mark it complete.” That sentence can be useful in a system where another defined process has already established completeness. But it does not teach a new volunteer how to decide whether the contents are complete. It moves the unanswered question into the first column.

To repair it, ask what evidence would make the condition answerable. “Contains six sheets” and “contains one card” are narrower than “ready”. They still need context: are damaged sheets acceptable, does the card have to be the current edition, and is the count exact or a minimum? You do not have to answer every imaginable question. You do have to answer the ones that could alter this decision.

The companion article on operational definitions examines how to connect a term with checkable criteria. A decision table begins after, or alongside, that work. It combines criteria to produce outcomes. A carefully defined condition is valuable; several carefully defined conditions still need a rule explaining how they interact.

Keep evidence separate from the value it supports

For the condition “instruction card present?”, the value might be Yes. The evidence might be a direct count made by Maya at the packing table. These are not interchangeable. The value lets the table operate. The evidence explains why someone entered that value and whether another person can check it.

In a low-stakes classroom activity, a short spoken confirmation may be sufficient. In a shared project with many handovers, a dated note may be more helpful. Choose a record proportionate to the task. A table should not turn a simple activity into a paperwork competition, but it should not hide a guess behind a confident Yes.

A result can be an action, a classification or a next question

Some tables choose an action: place the envelope in the waiting tray. Others assign a category: awaiting contents. Others identify the next information needed: check the card pocket. Be clear which job your output column performs. A category does not necessarily tell someone what to do, and a proposed action does not establish that it has happened.

“Send reminder” and “reminder sent” differ in time and meaning. The first is an instruction. The second is a record of an event. If a table returns “reminder sent” before anyone has sent it, the table creates false information. Prefer “send reminder” for the next action and record completion separately after it occurs.

Try a small diagnostic. Someone writes the columns “Good work?”, “Teacher happy?” and “Finished?” for a homework table. What makes these columns difficult? They mix vague evaluation, an inferred emotional state and a completion label. A more workable decision might ask, “Which preparation step remains?” with conditions such as “all assigned questions attempted?” and “identified corrections completed?”. Even those criteria describe preparation, not a guarantee of understanding or a prediction of the teacher’s response.

The discipline is simple: let evidence support condition values, and let a stated rule connect those values to a result. When any link is missing, show the missing link instead of borrowing certainty from the appearance of the table.

Contents · Previous chapter · Next chapter

A decision table becomes easier to use when its title names the decision. “Club table” is vague. “Choose the tray for an activity envelope” tells the reader what the output means. A title should identify an actual question, not merely a subject area. The difference is similar to the difference between a folder labelled “School” and one labelled “Forms to return this week”.

Write the decision as a question before you write any columns. For example: “Which tray should receive this envelope after the contents check?” That question limits the table. It does not decide who should attend the activity, whether the instructions are educationally suitable or which student should carry the tray. Those may be reasonable questions, but they require different information.

State what a case is

Does one row evaluation concern an individual envelope, a whole batch or a person’s work over a week? If you do not specify the unit, readers may answer the same condition at different levels. One volunteer may enter Yes because most envelopes contain cards. Another may enter No because the particular envelope being checked lacks one.

For our table, write: “Apply to one envelope at a time.” If a batch contains twenty envelopes, evaluate twenty cases or use a separate batch-level rule. “At least one complete envelope” and “every envelope complete” are different conditions. A shared noun such as batch can make the difference visible, but only if everyone agrees which items belong to that batch.

This is where seemingly ordinary vocabulary performs substantial work. Each points to individual cases. All requires the whole relevant set. Any needs careful reading because its role changes with the sentence. Current selects a version or time. Removing these words to make a heading shorter may remove the distinction that makes the rule valid.

State when the table applies

A rule used during preparation may differ from a rule used after the activity begins. Before the session, an incomplete envelope can go back for packing. During the session, the organiser might supply the missing card directly. Neither action follows automatically from the word incomplete. The phase of work changes the available next step.

A useful scope line might read: “For ordinary paper activity envelopes, during the preparation session, before they leave the packing table.” This is a local boundary for an invented example. If a case falls outside it, the table has not answered the question. Outside scope does not mean failed, forbidden or unimportant. It means this rule was not written to settle that case.

The same issue appears when a person copies a table from one project to another. The second project may have different materials, different deadlines or a different person responsible for decisions. Copying the layout can be useful. Copying its outcomes without checking the scope can carry an obsolete rule into a new situation.

Separate the model from the authority to use it

A student can model a rule to understand it without becoming the person who controls it. If a teacher’s instruction is unclear, the student can show a table with an unresolved cell and ask what belongs there. Filling that cell with a sensible guess does not make the guess an authorised school rule.

For an original family or project agreement, the people involved may be able to decide the missing case together. For a published requirement, the appropriate move is to consult the relevant source or responsible person. The table helps make the question precise: “What happens when the draft is reviewed but the requested change is still unresolved?” That is more answerable than “Can you explain everything again?”.

Recognise when the question is too large

“What should I do with my future?” is not a good first decision-table question. It includes values, uncertain outcomes, changing opportunities and many decisions over time. A smaller question might be, “Which information should I gather before comparing these two courses?” A table can organise that limited next step without pretending to choose a life path.

Likewise, a table about whether a paragraph contains evidence does not decide whether an entire essay is excellent. It can support one check within a wider judgement. Give that modest function its proper name. Readers are less likely to overuse the output when the title, scope and explanation all describe the same limited job.

Before continuing, write a four-line contract for your own table: decision question; unit of one case; situations in which it applies; person or source that supplies the rule. If one line remains unclear, keep the table small while you resolve it. A defined scope is a foundation for useful detail.

Contents · Previous chapter · Next chapter

Transforming prose into a table is an interpretation task. The goal is to preserve the rule while changing its representation. You should be able to point from each output back to the wording that supports it. If the source does not settle a case, an honest table makes that gap visible.

Here is an invented instruction for a class display: “Use a blue label for a contribution when its title is present and its contributor has checked the spelling of their name. Use a yellow label when either check is unfinished. A blank title counts as unfinished. A name that has not yet been checked also counts as unfinished.” This is a complete local rule for choosing label colour. It is not a judgement of the contribution’s quality.

First, find the output

The decision is label colour: blue or yellow. It is tempting to make the output “accepted” or “rejected”, because those words sound like familiar decisions. They would change the instruction. The source says nothing about accepting or rejecting the contribution. A yellow label identifies a preparation status within this invented activity.

Keep the output vocabulary as close as necessary to the source. You can improve readability, but you must not strengthen the consequence. “Needs a check” is not “failed”. “Awaiting a decision” is not “refused”. A table is especially dangerous when its tidy categories make an unsupported interpretation look official.

Next, extract the separate tests

The first condition is whether a title is present. The second is whether the contributor has checked the spelling of their name. “Name present” would be the wrong second condition: a name can be present and still unchecked. “No spelling mistakes” is also different. The rule requires a person’s check; it does not claim that all errors are impossible after checking.

Read the third row aloud: the name check is complete, but the title is missing, so the contribution receives a yellow label. This explanation uses the actual condition that remains unfinished. It does not accuse the contributor of making an error elsewhere.

Then check the reverse translation

Hide the paragraph and ask someone to explain the table. Can they recover the same rule? A sound explanation is: “Blue requires both checks; otherwise the label is yellow.” An unsound explanation is: “Blue means the work is perfect.” The table contains no condition about perfection, and the source did not make that claim.

Reverse translation is useful because it exposes meaning that the author may have smuggled into a label. If three readers interpret “ready” in three different ways, changing its background colour will not solve the problem. You may need to replace it with a narrower phrase such as “both preparation checks recorded”.

Mark missing rules instead of inventing them

Now shorten the source to: “Use a blue label when the title is present and the name check is complete.” The first row remains supported. The other three rows are not settled by that sentence alone. Perhaps yellow is intended. Perhaps a label should not be attached yet. Perhaps different incomplete cases need different colours. We do not know.

Write “not specified in the supplied instruction” in those output cells. This is a useful result of the modelling process. The table has identified exactly what clarification is needed. It has not failed because it contains a question. It would fail if it replaced that question with an invented instruction and concealed the change.

When clarification arrives, record it accurately. Suppose the organiser says, “For any unfinished check, use yellow.” You can now fill the remaining rows and note that the second sentence supplied the missing rule. If the organiser instead says, “Do not attach a label yet,” the output changes accordingly. The table must follow the clarified rule.

A good conversion routine therefore has four passes: identify the decision, extract the tests, fill only supported outcomes, and translate the table back into ordinary language. This is more than formatting. It is a way to check whether the words and the structure still mean the same thing.

Contents · Previous chapter · Next chapter

A table depends on repeated words having stable local meanings. If complete means “all parts are present” in one row and “all parts are excellent” in another, the table cannot be used consistently. Readers may follow it carefully and still reach different conclusions because they are applying different tests.

Start with the few labels that actually control the decision. For a shared folder, these might be current version, review complete and ready for display. You do not need a dictionary for every ordinary word. You need a working explanation for words whose interpretation could change the selected row or outcome.

Use a short local glossary

An invented project glossary might say: “Current version means the file linked in today’s project index. Review complete means every item on the agreed review list has been checked. Ready for display means the current version has completed review and has the organiser’s recorded approval.” Each entry has a different role. The third combines facts established through the first two and the approval record.

These are local definitions for a particular project. Another group can organise its work differently. The point is not to declare the only true meaning of ready. It is to make the intended meaning visible where people are coordinating around it. If the definition is unsuitable, the group can discuss the criteria rather than arguing indefinitely about the label.

Keep examples beside difficult entries. For “current version”, an example might be the file linked in the project index; a non-example might be an older attachment in yesterday’s message. The older file may have a later download date on someone’s device, so “the latest file I can see” would be an unreliable substitute.

Avoid changing the question through a synonym

Suppose one column says “available?” and a later note says “approved?”. The writer may have varied the vocabulary to avoid repetition. In ordinary descriptive prose, variation can be elegant. In a rule, it can quietly change the condition. An available room is not necessarily an approved booking. An approved booking may concern a room that later becomes unavailable.

Repeat the exact controlling term when repetition protects meaning. Explain it once, then use it consistently. You can vary the surrounding prose. There is no need to replace submitted with accepted merely because the same word appeared two sentences earlier. Precision sometimes requires deliberate repetition.

This is a practical lesson for vocabulary learning. A rich vocabulary includes knowing when two words should remain different. It also includes knowing when a stable label is more helpful than an impressive alternative. The goal is control over expression, not maximum variety in every paragraph.

Make abbreviations earn their place

A small table may use Yes and No without abbreviations. A larger table might use Y and N. Either can work if the legend is clear. Do not introduce a string of unexplained initials to make the table look technical. A reader who must repeatedly decode the column heading is doing extra work unrelated to the decision.

Be particularly careful with a dash. It might mean “either value”, “not applicable”, “unknown”, “not checked” or “no action”. Those meanings are different. If a dash means “this condition does not affect the output in this row”, state that explicitly. Use a different word for missing information. A compact symbol should reduce clutter without erasing a distinction.

Support different language backgrounds

A learner may understand the underlying condition before they know its English label. Ask them to show the case, paraphrase it or discuss it in a familiar language. Then connect that understanding to the English term. Difficulty recalling eligible does not, by itself, prove difficulty understanding the requirements in the example.

When a group uses more than one language, a bilingual note can help if the meanings are checked carefully. A translation should preserve the local condition, not merely replace each English word with its first dictionary equivalent. If the translation adds permission, certainty or completion that the original lacked, the table’s logic changes.

Try auditing one table with a partner. Each person independently explains its three most important labels and supplies a borderline case. Compare the explanations. If they diverge, revise the labels or definitions before debating the outputs. This catches a disagreement at the level where it begins.

A stable vocabulary is not a rigid vocabulary. You can revise a definition when experience reveals a problem. Record the revised meaning and check the affected rows together. Keeping a term stable during use and changing it openly when necessary are compatible habits.

Contents · Previous chapter · Next chapter

Yes and No make a useful starting point because they expose combinations clearly. They are not suitable answers to every question. “Which format was requested?” might require printed, digital or both. “How many pages are in the file?” requires a number. “Has the request been checked?” may require Yes, No or Not yet known, depending on what has actually been established.

The choice of values shapes the distinctions the table can make. If you combine printed and digital requests into a single category called “materials”, the table cannot select a delivery format. If you divide an irrelevant feature into ten categories, you create complexity without improving the decision. Choose values because they alter the rule, not because they are easy to collect.

Ask a question that has an answer

“Quality?” is a label rather than a condition. A user must guess what to enter beneath it. “Does the file contain a title and a source list?” is answerable for a defined file, although the two requirements may deserve separate columns if they lead to different next actions. “Is the work good enough?” requires agreed criteria and may still need human judgement.

A condition can be a judgement without being meaningless. A group can explicitly appoint a reviewer to decide whether a poster’s text is readable from a stated distance under specified viewing conditions. The input then records the reviewer’s assessment. It should not be presented as an objective measurement of every viewer’s experience. The table records how the decision is made; it does not erase the nature of the evidence.

For early practice, prefer conditions with straightforward observations. They let the learner concentrate on the language of combination. Later, introduce judgements and discuss how disagreement is handled. Mixing every source of uncertainty into the first example makes it difficult to tell which idea the learner has misunderstood.

Keep categories mutually clear

Suppose a request can be printed, digital or both. If the table has only printed and digital rows, a request for both might match two rows. That may be acceptable if the explicit rule is to provide every requested format. It is a problem if the table is supposed to return exactly one format label. The category system and the output rule must work together.

You have two reasonable designs. One uses a single input called requested format, with three stated values. Another uses two inputs: printed copy requested, and digital copy requested. The second design also allows a fourth case in which neither is requested. You must decide whether that case is valid, a request for clarification or outside the task.

Neither design is automatically better. The first may be simpler for an agreed form. The second may reveal a missing case in informal messages. A vocabulary choice has become a modelling choice: what counts as one value, which combinations exist, and which distinction the user must preserve.

Do not force unknown into No

A blank request field does not necessarily mean the person wants neither format. They may have missed the question, the form may not have saved, or the request may not yet have arrived. You need not invent an explanation. Simply record that the preference is unknown and identify how to obtain it if it matters.

Likewise, “not yet reviewed” is different from “reviewed and did not meet the criterion”. You can sometimes route both cases to the same temporary action, such as keep in preparation, while retaining their different reasons. Sharing an action does not make the underlying states identical.

Practise designing the input

Take the vague heading “late”. For a fictional classroom collection, a better condition could be “received after 3:00 p.m. on the stated collection date?”. That requires an agreed time reference and a record of receipt. Another task might ask “arrived after the activity began?”. The same everyday word can correspond to different precise conditions.

Now ask what would change the result. If the exact number of minutes late does not matter, a Yes/No condition may be sufficient. If different intervals lead to different actions, use defined ranges. If the arrival time is missing, preserve that fact. Selecting inputs is a way of selecting which aspects of the situation the rule can actually see.

Contents · Previous chapter · Next chapter

The smallest words often carry the largest part of a rule. And combines requirements. An inclusive or allows one condition, the other, or both. An exclusive choice allows one or the other but not both. Everyday language can leave the intended kind of or unclear, so a careful table makes that choice explicit.

Begin with two invented conditions for a craft pack: a drawing sheet is included, and a writing sheet is included. We are choosing a description of the pack under three different rules. The rules are alternatives for teaching; they are not three instructions to apply simultaneously.

The input facts have not changed. The connective has. That is why a vocabulary exercise about and and or can be more useful than replacing a familiar noun with an elaborate synonym. The connective determines which cases satisfy the requirement.

Use the both-true case to test your reading

When a sentence says “bring a pen or a pencil”, context may allow both. When a form says “choose tea or juice”, it may intend a single choice. Do not assume that one interpretation fits every use of the word. Ask what happens if both conditions are true. The answer often exposes the intended rule.

For a fictional activity, write “bring at least one of these: a pen, a pencil; bringing both is allowed” if that is the intended instruction. Write “choose exactly one drink” if only one selection is permitted. These phrases reduce the reader’s need to infer the choice structure from context.

A table gives the same clarification a visible location. The Yes/Yes row must have an outcome. If the source is unclear, mark that row for clarification. You can then ask a targeted question: “If a learner brings both, does that satisfy the requirement?” This is a practical use of logical vocabulary.

Group conditions before combining them

Consider “Use the display card when the title is present and the picture is labelled or the organiser has provided a replacement card.” Does the replacement card independently allow use, or does the title remain required in every case? The sentence’s grouping is not sufficiently clear for a reliable table.

One interpretation is: either both the title and picture label are present, or a replacement card is provided. Another is: the title must be present, together with either the picture label or the replacement card. A case with no title but a replacement card distinguishes them. The first interpretation permits use; the second does not.

Rewrite the intended rule in two sentences or use explicitly grouped phrases. For example: “A replacement card may be used whenever one is provided. If there is no replacement card, the original card may be used when both its title and picture label are present.” This preserves the sufficient conditions in the first interpretation; it still does not specify what to do when neither qualifying option is available. Ask for that missing instruction if the task requires a complete action table. If the organiser intended the other grouping, choose wording that preserves it.

Explain the result using the failed or satisfied part

When a both-required rule fails, identify which requirement is absent. “The pack contains a drawing sheet, but it lacks the required writing sheet” is more informative than “wrong pack”. Under an at-least-one rule, explain which available item is sufficient. Under an exactly-one rule, explain that two selected items violate the one-choice limit even though each item is individually permitted.

These explanations help a learner repair the right part of the task. They also prevent a common misunderstanding: assuming that because an item is allowed on its own, adding more allowed items must always remain acceptable. Some rules concern combinations, totals or mutual exclusivity. The table makes that structure visible.

For practice, invent two conditions using objects on a desk. Write three complete rules: both required, at least one required, exactly one required. Test all four combinations. Then change only one connective and predict which rows will change before checking. This asks you to use the meaning of the word as an operation.

Contents · Previous chapter · Next chapter

A negative condition can be perfectly clear, but several negatives in the same table can make reading unnecessarily demanding. Compare “Is the title absent?” with “Is the title present?”. Either question can work. Trouble starts when a Yes under the first heading is later interpreted as a Yes under the second.

Suppose a draft table has a column called “Not incomplete?” and an output called “Do not hold”. A learner must reverse two expressions before understanding the action. Unless the distinction requires this wording, use a positive condition such as “All required contents present?” and a direct result such as “Move to the prepared tray”. The logic should remain the same while the reading becomes easier.

Changing a heading requires changing its values

If you replace “title absent?” with “title present?”, every established Yes becomes No and every established No becomes Yes. You cannot keep the old values under the new heading. The appearance of the table may barely change, while its meaning reverses.

Work through one case whenever you edit a negative heading. A card with a title should answer Yes to present and No to absent. A card without a title should answer the other way round. A card whose contents you have not inspected remains unknown. Negating the condition does not transform missing evidence into a known value.

This is a useful editing habit beyond tables. If you rewrite “no fewer than six” as “at least six”, the meaning is preserved. If you rewrite it as “more than six”, the boundary changes. Surface simplification is successful only when the cases remain aligned.

Distinguish not both from neither

Imagine two optional badges: a circle and a star. “Do not choose both” permits a circle alone, a star alone or neither, unless another rule requires a choice. “Choose neither” permits only the case with no circle and no star. The expressions differ even though both include a negative idea.

Now add the separate requirement “choose at least one badge”. Combined with “do not choose both”, it leaves exactly one badge. The exactly-one result comes from the two requirements together. It does not come from “not both” alone. This distinction is easy to miss when readers recognise a familiar phrase and supply a rule from memory.

Keep the scope of not visible

“Not every contribution has a title” means at least one relevant contribution lacks a title, assuming the statement is being used in its ordinary logical sense. It does not mean that no contributions have titles. “No contribution has a title” is a much stronger statement about the whole set.

For a table applied to one contribution at a time, neither sentence is a sufficient input description for every case. You still need to know which contribution you are checking. A statement about a collection cannot always be copied into the value for an individual item. The words every, no and some change the level of the claim.

Consider an invented batch of four cards. Three have titles; one does not. “Not every card has a title” is true. “Every card lacks a title” is false. If a student applies the second interpretation, they may send all four cards for title completion even though only one needs that action. The error comes from the relationship between negation and the set.

Use countercases to check a negative rule

A countercase is a case selected to distinguish two possible readings. To test “not both” against “neither”, choose one badge. To test “not every” against “none”, choose a mixed batch. You do not need to memorise the names of logical transformations before you can use these practical tests.

When a learner gives the wrong result, ask them to explain what their negative phrase excludes. If they say “not both means no badges”, place a single circle on the desk and ask whether both badges have been chosen. That concrete case can expose the mistaken reading without a long abstract lecture.

The next step is to return to language. Ask for a sentence that accurately describes the single-circle case: “One badge is selected; the two have not both been selected.” The physical arrangement and the words now support each other. Vocabulary practice becomes a way of controlling a distinction across representations.

Contents · Previous chapter · Next chapter

The words if and only if point in different directions. A decision table can help you see that difference, but only if you resist filling unspecified outcomes by habit. Many everyday instructions give one part of a rule and rely on context for the rest. A careful reader separates what the sentence states from what they are assuming.

Consider: “If a contribution has a green sticker, put it on the left display board.” This establishes a sufficient condition for that action in the stated setting. A green sticker is enough to trigger the instruction. The sentence alone does not tell us where every contribution without a green sticker belongs. Perhaps some other kinds also go on the left board.

Now consider: “Put a contribution on the left display board only if it has a green sticker.” This makes a green sticker necessary for that placement. A contribution without the sticker must not be placed there under the rule. The sentence alone does not say that every green-sticker contribution must be placed there. Another condition might also be required.

Use the two questions that reveal direction

Ask, “Is the condition enough?” and “Is the condition required?”. In the first sentence, the sticker is enough for the stated action. In the second, it is required. When a rule says both, the sticker is necessary and sufficient within the rule’s scope.

A complete two-way instruction could say: “Put a contribution on the left board exactly when it has a green sticker. Put contributions without a green sticker on the right board.” This supplies an outcome for both sticker states. We can now build a two-row action table without inventing an unstated default.

The middle row is deliberately careful. “Not ruled out” is weaker than “required” and weaker than “fully authorised”. A necessary condition can be satisfied while other requirements remain. If you shorten that cell to “Yes”, the reader may infer much more than the sentence supports.

Do not confuse a rule with a prediction

“If the group rehearses, its presentation will be perfect” is a prediction about an outcome. It is not a reliable instruction merely because it has an if–then shape. The statement would require evidence, and the word perfect itself needs explanation. A table can represent what a claim says without proving that the claim is true.

By contrast, “If rehearsal is complete, record the rehearsal status as complete” is an administrative rule about a record. Its usefulness depends on what counts as completing rehearsal and whether the record is accurate. It does not promise a flawless presentation. Keep rule-defined outcomes separate from claims about how the world will behave.

Apply the distinction to an everyday request

A friend says, “You can borrow my spare notebook only if you return it tomorrow.” Returning it tomorrow is a condition of the proposed arrangement. The sentence does not imply that everyone who returns a notebook tomorrow automatically gains permission to borrow this one. Identity, agreement and availability still matter in the ordinary context.

For teaching, simplify the arrangement into a fully stated invented rule. For example: “For this exercise, a request is accepted exactly when the spare notebook is available and the borrower agrees to return it tomorrow; otherwise it is declined.” Now the action table has a defined scope and two requirements. We are studying the stated rule, not extracting a universal rule of friendship.

Practise without relying on a familiar example

Write one sentence using if and another using only if, with a paper shape and a coloured tray. Ask a partner to produce a case that the sentence does not fully settle. Then add a sentence that completes the rule. This exercise tests the direction of the relationship and the boundary of your knowledge.

If the learner can repeat “necessary and sufficient” but cannot explain an unspecified case, return to the objects. Ask which placement the words require and which placements they merely fail to exclude. The vocabulary earns its place when it helps the learner distinguish those possibilities accurately.

Contents · Previous chapter · Next chapter

A default tells us what to do when no specified exception applies. It is a rule chosen for a purpose. It is not the same as “whatever seems normal”, and it should not be invented merely because a table contains a blank cell. A default becomes reliable when its scope and exceptions are explicit.

Here is a complete invented instruction: “Place ordinary finished cards in the display tray. If a card is marked for an individual feedback meeting, place it in the meeting folder instead.” The default is display tray. The stated exception is meeting folder. The word instead tells us that the exception replaces the default action for that case.

Now change the wording: “Place ordinary finished cards in the display tray. If a card is marked for feedback, make a note for the meeting.” This second instruction does not necessarily replace the display action. Making a note could be an additional action. The difference lies in the relationship between the instructions, not simply in the presence of the word if.

Distinguish replacement from addition

A table with one output column called destination can represent one final destination. A separate output called meeting note required can represent an additional task. If you force both into a single undifferentiated cell, readers may not know whether to choose one action or perform both.

Write “meeting folder instead of display tray” when that is the rule. Write “display tray, and also create a meeting note” when both actions are required. These are longer phrases, but they preserve a difference that changes what someone does. Concision is useful after the relationship is secure.

Do not assume the newest sentence overrides every earlier sentence

A later note can clarify, supplement or replace an earlier rule. Which one it does depends on its content and authority. Suppose the original rule requires both a title and a name check. A later message says, “Remember to check titles.” That reminder does not remove the name-check requirement.

Likewise, a message about one special contribution does not automatically create a new policy for every contribution. Keep the difference between an individual exception and a general rule change visible. A note might say, “For card 17 only, the organiser will supply the missing title.” Applying it to all untitled cards would broaden the instruction without support.

Understand unless through explicit cases

In a simple instruction, “use the display tray unless a meeting is required” commonly points to the default when no meeting is required. It may leave the alternative action unstated. Do not assume that “meeting required” automatically means “meeting folder” unless the rule supplies that action.

A complete version is easier to table: “If no meeting is required, use the display tray. If a meeting is required, use the meeting folder.” Once these two cases are established, the shorter unless form can serve as a reminder. The fuller version protects the meaning when a new reader joins the task.

This is especially useful when translating instructions or explaining them to a learner. A direct word-for-word substitution may preserve the vocabulary while making the relationship harder to see. First identify the two cases and their outcomes, then choose natural wording that preserves those cases.

Handle an exception to an exception openly

Imagine the meeting-folder rule has a further exception: some cards are needed for a display rehearsal, so a copy goes to the meeting while the original stays available. A single column headed “meeting?” no longer captures the decision. The table needs to distinguish whether a meeting is required and whether the original is needed for rehearsal.

Do not keep attaching footnotes until the table can no longer be read on its own. Rebuild the relevant conditions. You might now have outputs for original destination and copy required. The vocabulary original and copy makes a previously hidden distinction available for action.

At the same time, check whether the added complexity is justified. If the special case happened once and is already resolved, a dated case note may be better than permanently expanding the general table. A reusable rule should represent a recurring decision, not become a museum of every unusual event.

Test the default with a genuine ordinary case

Select a case where no stated exception applies and explain why the default follows. Then select one case for each exception. Finally, ask whether two exceptions can apply together. If they can, the table needs a rule for their interaction. “We will probably know what to do” leaves the hardest case outside the written logic.

The aim is a visible agreement about priority and action. A default should simplify ordinary work while keeping exceptional cases answerable. When it cannot do that, the next useful step is clarification or redesign, not a more confident label.

Contents · Previous chapter · Next chapter

Unknown is a statement about what you know. No is a value for a condition. Confusing them can send a case down the wrong path. If nobody has checked whether the title is present, you cannot honestly enter No merely because the field is blank.

There are several reasons information might be unavailable: it has not been collected, it has not arrived, the record is unreadable, or two records disagree. You do not need to solve all these problems with one symbol. A short note such as “not checked” or “conflicting records” can identify the next useful action more clearly than an empty cell.

Ask whether the missing fact could change the outcome

For a complete rule that requires both conditions A and B, suppose A is established as No while B is unknown. The combined requirement cannot be satisfied, regardless of B. If the only decision is whether the combined requirement is met, the answer is already No. You may not need to investigate B for that particular decision.

For a complete at-least-one rule, suppose A is Yes and B is unknown. The combined requirement is met because A is sufficient under that rule. Again, the outcome can be determined without pretending to know B. This distinction lets you preserve uncertainty while avoiding unnecessary checks.

This table assumes the rules are fully stated and the known input is reliable. It does not define the behaviour of every computer system or every legal instruction. It shows ordinary logical reasoning over the possible remaining values. The practical action may still require more information than the simple requirement result.

A known output does not settle every next action

Return to the envelope that needs six sheets and one card. If the sheets are missing, the envelope is incomplete even if the card has not been checked. But if your task is to prepare a list of everything that must be added, you still need to check the card. The first decision was completeness; the second is the full repair list.

This is why defining the output matters. “Can we mark complete?” and “What exactly should we add?” are related questions, but they need different information. Do not claim that a missing value is irrelevant to every task just because it is irrelevant to one result.

Use a temporary action with a precise reason

If the unknown input could change the result, a reasonable local procedure might route the case to clarification. Write the action explicitly: “Ask the contributor to confirm the requested format.” Avoid an output such as “failed” when the issue is incomplete information.

There can be a shared holding action for several reasons. One request lacks a format choice; another has contradictory dates; a third refers to a file that cannot be found. They may all remain in preparation, but the reason field should identify the repair. Otherwise a person can see that work is waiting without knowing how to move it forward.

The choice of a temporary action is itself a rule. In a real setting, use the agreed procedure. The invented examples in this guide do not authorise ignoring a required check, withholding a service or replacing an established process. The transferable lesson is to distinguish an unknown fact from an established negative and to make the next question concrete.

Do not replace uncertainty with a confident estimate by accident

A person may say, “The room is probably available.” That is not the same input as a confirmed availability status. If the rule requires confirmation, probability language does not satisfy it. If the task is early planning and tentative information is acceptable, the table should say so and preserve its tentative status.

Similarly, an AI-generated summary can suggest where to look for a fact, but a plausible sentence does not become a verified input merely because it is fluent. Keep the source and confidence appropriate to the decision. A table can make an unsupported value look more settled than it is.

Practise with three partly known cases. For each, state what is known, what is unknown, whether the unknown could change the current output, and what information would be needed for the next task. This exercise builds a more useful habit than simply refusing to proceed whenever any cell is blank.

Contents · Previous chapter · Next chapter

A table can look substantial and still omit a case. Three well-written rows are not enough for four relevant combinations if the fourth combination has no applicable rule. Coverage asks whether every case within the chosen scope has an outcome or an explicitly defined route for further judgement.

For two independent Yes/No conditions, there are four combinations. For three, there are eight. Each additional independent binary condition doubles the count. This is a counting fact about the possible assignments of values; it does not mean every assignment is physically possible or relevant to your actual task.

Enumerate before compressing

Imagine an invented activity pack with three checks: title present, name check complete and source card included. The full rule says the pack is ready for display preparation exactly when all three checks are Yes. Otherwise it returns to preparation. Listing all eight combinations makes it clear how many different kinds of unfinished pack can exist.

A compact version could say “all three Yes” and “at least one No”. That is fine if the reader understands the grouping and the input values are known. For teaching, the expanded version can reveal cases the learner overlooked. For routine use, the compressed version may be more convenient. Preserve the meaning when moving between them.

Distinguish a missing rule from an impossible combination

Suppose you choose the conditions “contains at least three sheets” and “contains at least five sheets”, referring to the same counted sheets at the same moment. The combination No/Yes is impossible under those definitions. A pack cannot contain at least five while containing fewer than three. The two conditions are not independent.

If the table receives No/Yes, it should prompt a check of the data or definitions. Perhaps one count concerns blank sheets and the other includes instruction pages. Perhaps the values were entered at different times. The impossible combination can reveal a mismatch, but only after you confirm that the conditions refer to the same thing.

Do not delete an inconvenient row by declaring it impossible without a reason. “We have never seen it” is different from “the definitions rule it out”. A rare combination may be exactly the one that needs clarification. State the constraint that makes a combination impossible and check whether it still holds in the current scope.

Define what completeness means for this table

A complete table for known Yes/No inputs may still need a separate procedure for unknown inputs. A complete table for ordinary contributions may intentionally exclude unusual formats. Completeness is always relative to the domain you have defined. A claim that a table covers “everything” is too broad unless everything has a precise meaning.

Write a small coverage statement: “These rows cover all combinations of the three checks when each check has an established Yes or No value. If a value is unknown, follow the clarification procedure.” That statement does not hide a limitation; it tells readers how the table and the surrounding process fit together.

Look for gaps by constructing cases

Give each row a concrete example. Then ask someone to create a valid case that does not fit any row. If they succeed, inspect whether the case is within scope, whether the inputs have permitted values, and whether the table lacks a rule. This is more informative than asking only whether the table “looks clear”.

For the three-check example, a learner might invent a pack with a title, no name check and no source card. It belongs to the fourth row. Another might invent a pack with two conflicting source cards. If the condition is merely “source card included”, the table may classify it as Yes while missing a quality issue. The lesson is not necessarily to add another column immediately; it is to reconsider whether the current decision was defined adequately.

Coverage can expose both missing combinations and missing distinctions. Use it to improve the model, while keeping its purpose manageable. A table that tries to settle every possible concern can become too large to inspect, which defeats the reason for making it.

Contents · Previous chapter · Next chapter

Coverage asks whether a case has somewhere to go. Overlap asks whether it fits more than one rule. An overlap can be intentional, but it needs an explicit interpretation. If the table is supposed to choose one result and matching rows produce incompatible results, the table has a conflict.

Consider two invented rules for sorting story submissions: “If a story has at least 500 words, use the long-story folder.” “If a story has no more than 600 words, use the short-story folder.” A 550-word story satisfies both conditions. If the two folders are exclusive destinations, the instructions conflict for that case.

The problem is easy to miss if you test only a 200-word story and an 800-word story. Both receive an apparently sensible result. You need a case inside the overlap. The relevant vocabulary is at least, no more than and the implied relationship between the destinations.

Do not repair an overlap by guessing which rule matters more

You might feel that the long-story rule should win because it appears first. That is a new priority rule unless the table explicitly says to use the first matching row. Another reader may choose the last row or the more specific wording. All can believe they are following the same table.

Ask the person defining the categories to clarify the boundary. Perhaps short means fewer than 500 words and long means at least 500. Perhaps the folders were intended to overlap because a story can enter both workshops. The correct repair depends on the task. Mathematical tidiness alone cannot determine the intended policy.

Separate harmless agreement from conflicting outputs

Two rows might overlap and return the same result. For example, “title missing” and “name check unfinished” may both return “keep in preparation”. A contribution with both problems matches both rows. That can be acceptable if the table is designed to collect all outstanding reasons or to return the shared preparation status.

However, the overlap is still worth understanding. If a later editor changes one row to a different action, the same case may become a conflict. If the task requires a complete repair list, selecting only the first reason can conceal another issue. Agreement in the current result does not remove the need for an explicit rule about multiple matches.

Formal research makes similar inspection problems precise. Calvanese and colleagues’ 2016 paper on the semantics and analysis of DMN decision tables develops methods for identifying overlapping and missing rules. That work concerns formal decision models. Our small examples use the same two questions as practical reading checks, without claiming to reproduce the researchers’ algorithms.

Use an overlap witness

An overlap witness is simply a concrete case that satisfies both rows. You do not need the technical phrase to use the method. For the story folders, 550 words is a witness. For “available on Tuesday” and “available in the afternoon”, a Tuesday afternoon slot is a witness. State the case and show how it satisfies each condition.

This makes a disagreement easier to resolve. Instead of saying, “Your table is confusing”, say, “A Tuesday afternoon slot matches both row 2 and row 5, but the rows assign different rooms.” The discussion can now focus on an observable inconsistency.

Check labels that appear opposite but are not

Popular and expensive are not opposites. An option can be both. Reviewed and needs changes are not opposites either; review may reveal that changes are needed. If a table uses such labels as though they were mutually exclusive, it may omit or mishandle common combinations.

Similarly, new and unfamiliar differ. A new edition may be familiar to someone who helped prepare it. An old file may be unfamiliar to a new group member. Ask whether your labels describe one dimension or several. Independent dimensions often deserve separate conditions.

For practice, write two plausible rules that accidentally overlap. Construct a case in the overlap, identify whether the outputs conflict, and propose two possible repairs. One repair might make the conditions exclusive; another might explicitly allow both outputs. Explain which repair fits the intended task and why. The exercise develops judgement about rules, not merely an ability to draw a grid.

Contents · Previous chapter · Next chapter

A table’s row order may be decorative or meaningful. You must know which before using it. If every valid case matches exactly one row, rearranging the rows should not change the result. If the instruction is “use the first matching row”, rearranging them can change the decision.

Formal decision-table systems use the term hit policy for the rule governing matching rows and returned results. For example, Camunda’s official explanation distinguishes Unique, which allows at most one matching rule, from First, which returns the first matching rule’s output, and Collect, which can return multiple matching outputs. The important everyday lesson is to state the intended behaviour explicitly.

Start with one matching row when that fits the task

For a simple destination table, mutually exclusive rows are often easy to explain. A pack goes into exactly one of two trays according to a complete rule. If two rows match, you investigate the overlap. This makes unintended conflicts easier to notice because multiple matches are not part of normal use.

Do not confuse “at most one match” with “at least one match”. The former prevents overlap; the latter provides coverage. A table can have no overlaps and still leave a gap. It can cover every case while assigning two conflicting outputs to some. These are separate checks, even when a good design aims to satisfy both.

Use first-match priority deliberately

Consider a fictional reading-club planning rule: “If the facilitator is absent, postpone the activity. Otherwise, if the assigned room is unavailable, use the agreed backup room. Otherwise, use the assigned room.” The word otherwise creates an ordered structure. You do not reach the second check when the first condition has already selected postponement.

The backup room is assumed to be agreed and usable within this invented rule. If that assumption is not true in a real task, more clarification is required. The table does not create a room, make it suitable or establish permission to enter it.

A case with both an absent facilitator and an unavailable room matches the first two conditions. The declared first-match policy selects postponement. Moving the room row to the top would change the action, which is why row order must be protected during editing. Sorting this table alphabetically would be a substantive rule change.

Collect multiple outputs when the task asks for a list

Now change the decision to “Which preparation items are missing?”. A missing title produces “add title”; an unchecked name produces “confirm name spelling”; a missing source card produces “add source card”. A contribution can require all three actions. Stopping at the first match would give an incomplete repair list.

This is a different kind of output from selecting one destination. Make the distinction visible in the title: “List every outstanding preparation action.” The word every matters. It tells the reader to continue checking after finding the first issue.

Multiple actions can also conflict or depend on one another. “Discard the original” and “review the original” cannot be performed casually as an unordered pair. If the output list includes sequential work, describe the sequence or separate decisions. A collect-all rule does not mean that every combination of actions is sensible.

Keep priority separate from importance

A row’s position in a first-match table controls selection; it is not a moral ranking of people or a measure of how important a condition is in every context. In the reading-club example, facilitator absence comes first because it makes the room choice unnecessary for that activity. The room may still matter for another event.

Ask a partner to use your table without verbal coaching. Then ask what they would do if two rows matched. If they answer “choose the one that seems best”, your written rule may be incomplete. Add a clear policy or redesign the rows so that the ambiguity disappears.

The practical vocabulary here is small: first, all, one, priority, otherwise. Each word changes the procedure. Learning them in a table gives the learner a way to see and explain that change.

Contents · Previous chapter · Next chapter

Numerical conditions often appear precise because they contain numbers. Precision depends on the accompanying words. Less than ten, at most ten, more than ten and at least ten divide the possible values differently. The number alone does not tell us whether the boundary is included.

Use an invented paper-box rule: “The small box is for bundles containing at most ten sheets. The large box is for bundles containing more than ten sheets.” For a bundle of exactly ten sheets, the small-box rule applies. If someone rewrites “at most ten” as “less than ten”, the ten-sheet case becomes a gap.

Check below, at and above the threshold

For a whole-number sheet count, nine, ten and eleven are useful test values around the boundary of ten. For a measured length, values might be 9.9 cm, 10.0 cm and 10.1 cm, if that precision is appropriate to the measurement. Choose values that make sense in the domain. There is no such thing as 9.9 whole sheets in a rule that counts intact sheets as discrete units.

Ask the learner to explain the boundary case before testing the others. If they can say why ten belongs under at most but not under less than, they are controlling the inclusion rule. If they merely repeat the symbol, ask for an everyday paraphrase: “Ten is allowed; anything larger is not.”

Do not leave between undefined when the endpoints matter

“Between five and ten pages” can be interpreted differently depending on context. If the rule requires inclusive endpoints, write “from five to ten pages, inclusive”. If the endpoints are excluded, say “more than five and fewer than ten pages”. If the source is ambiguous, the table should expose the need for clarification.

When adjacent ranges meet, check the shared endpoint. “Five to ten” and “ten to fifteen” can overlap at ten if both are inclusive. They can leave a gap if both exclude ten. A clean-looking list of ranges does not establish that every number belongs to exactly one group.

Carry the unit into the heading

A column headed “length” with an entry of 12 is incomplete. Is the value in centimetres, millimetres, words or minutes? Write the unit in the heading or beside each value. A rule about a twelve-centimetre card cannot be applied to a value recorded in millimetres without conversion.

Also specify what is being measured. The length of the printed text area is different from the width of the entire card. The duration of a presentation including questions is different from speaking time alone. Vocabulary identifies the object and the boundary of the measurement before arithmetic begins.

A number can also be a count of different kinds of thing. Ten pages may mean ten printed sides or ten sheets, depending on the task. If the distinction affects the rule, define it. A table cannot compensate for two people counting different units under the same heading.

Distinguish recorded values from exact reality

Suppose a toy example uses a measured width rounded to the nearest centimetre. A recorded value of ten does not necessarily mean the unrounded width is exactly ten. If the boundary matters, the procedure needs to say whether to use the recorded rounded value or a more precise measurement. Do not silently switch between them.

For a simple classroom activity, the group can choose a practical convention. For a technical task, the relevant measurement method and requirements govern the decision. This guide does not supply those domain-specific rules. It teaches the question to ask: which value, measured how, compared with which boundary?

Use an error to locate the vocabulary gap

If a learner puts ten sheets in the wrong box, ask them to read the expression aloud and explain whether ten is included. If they understand the phrase but counted eleven sheets as ten, the issue is counting. If they counted ten correctly but applied a different unit, the issue is representation. The same wrong destination can arise from different errors.

That is why useful feedback names the failed step. “At most includes the stated maximum” addresses a boundary misunderstanding. “Count the sheets, not the printed sides” addresses a unit misunderstanding. A decision table helps vocabulary teaching become specific enough to guide the next attempt.

Contents · Previous chapter · Next chapter

A condition can change while the words stay the same. A room was available in the morning and occupied in the afternoon. A file was current yesterday and replaced today. A contribution was unreviewed when the first table was completed and reviewed later. The table needs inputs that belong to the relevant moment.

Imagine a fictional class reading corner with a single reference book. Its local rule says, “Offer the reference book for use at the table when it is on the shelf and has no current reservation. Otherwise, ask the organiser about another copy.” This is an invented availability rule, not a public library policy.

At 10:00, the book is on the shelf and unreserved. At 10:05, another student begins using it. A record made at 10:00 does not establish its availability at 10:10. The phrase on the shelf describes a state at a time. Carrying the earlier Yes into a later decision without checking creates an error even if the original entry was accurate.

Separate a state from the event that changed it

Reserved describes a status. Reservation recorded describes an event or record. Reservation cancelled describes another event that may alter the current status. A table about present availability should use the current status, with enough information to establish it, rather than simply asking whether a reservation has ever existed.

The same distinction applies to a school project. “Feedback received” does not mean “feedback addressed”. “Revision submitted” does not mean “revision checked”. “Meeting scheduled” does not mean “meeting held”. These word pairs help preserve the sequence of work.

A table can decide the next step based on the current state. A separate sequence diagram or checklist may be better for showing the whole process over time. Do not force every event into one table if doing so makes the states impossible to distinguish.

Choose the time reference explicitly

When a rule refers to “today”, “tomorrow” or “the latest version”, its interpretation depends on context. A message copied into a document may outlive the context that made it clear. For a reusable table, a date, named session or version identifier can be more stable than a relative expression.

In an invented weekly club routine, write “apply to requests for the Friday session named at the top of this sheet”. That prevents a reader from accidentally using last week’s decisions for this week’s session. If participants work in different time zones, the relevant deadline also needs a stated time zone. The right detail depends on the task, not on a desire to make every table longer.

Do not use future intention as present completion

“I will check the file this evening” is a plan. It does not make “review complete?” a Yes now. “The organiser expects to approve it” is an expectation, not an approval record. A table that turns plans into completed inputs may report readiness before the work exists.

You can include planned and completed as separate states if they are useful. For example, a preparation table might assign “wait for scheduled review” to a planned review and “request a review slot” when none is planned. The distinction should change an actual next action; otherwise it may be unnecessary detail.

Update the affected decision after a meaningful change

Suppose a display version receives approval, then someone adds a new paragraph. Does the previous approval still cover the changed version? The answer depends on the actual agreement. The table cannot infer it from the word approved alone. Version and scope belong with the status.

A simple project rule might say that any content change requires a fresh review, while correcting a filename does not. Another project may use a different distinction. Make the chosen rule explicit and avoid claiming that your local convention applies everywhere. The words content change, format change and current version need working meanings.

Practise with a short timeline

Create three moments: a draft is written, a reviewer checks it, and a new diagram is added. Ask what is known at each moment and which earlier facts remain usable. The learner should not erase the fact that the earlier review happened. They should recognise that the review concerned an earlier version.

This exercise teaches a powerful distinction: a true historical statement may be insufficient for a current decision. Vocabulary helps us preserve both truths at once. The earlier version was reviewed; the current version’s review status still needs to be established.

Contents · Previous chapter · Next chapter

Some decisions require more than one output. A planning table might return a destination, a reason and a follow-up action. That can be helpful if each column answers a clear question. It becomes confusing when one cell mixes a status, an instruction, a prediction and a judgement about a person.

Consider a fictional vocabulary practice session. A learner can explain a word when seeing it but cannot yet retrieve it from a meaning prompt. A useful next step might be practice recalling the word from a cue. Calling the learner “weak” is neither a precise result nor a useful action. It turns a task observation into an overbroad personal label.

Keep the observed performance narrow

We can write a simple teaching decision: “Which practice should we try next for this word in this task?” Inputs might include whether the learner can explain the intended sense and whether they can retrieve the word from an appropriate cue. The result is a suggested practice step, subject to the teacher’s judgement and the learner’s needs.

This is an informal support tool, not a standardised assessment. One attempt may be affected by unfamiliar instructions, fatigue, language background or an unsuitable cue. The table should not convert a single response into a diagnosis or a permanent ability category.

The fourth row matters. A learner can produce a word without demonstrating its intended meaning. The table preserves this possibility instead of assuming that recall proves full understanding. It also avoids the reverse mistake of treating difficulty with an English explanation as proof that the learner lacks the underlying concept.

Distinguish a recommendation from a requirement

The output column says “possible next practice”. That phrase signals professional or learner judgement. A table titled “mandatory next action” would make a stronger claim. Do not switch between these modes casually. The reader needs to know whether the table records a binding rule, offers a heuristic or organises a discussion.

A heuristic is a practical aid that may work in many suitable cases but still needs judgement. If your table is a heuristic, say so. You can then explain when to reconsider it. For the vocabulary example, a learner who is frustrated by repeated cueing may benefit from returning to a meaningful activity and observing their use there.

Keep reasons separate from actions

A reason explains why a result was selected. An action says what to do next. “Meaning unclear” is a reason to investigate, not a complete instruction. “Compare two examples and explain the difference” is an action that may help investigate it. Separating these fields makes the table easier to revise.

It also helps communication. A parent can see why a particular practice is proposed without treating the observation as a label for the child. A learner can say, “I understood the idea in my first language but could not explain it in English,” which may change the next step. The table should make such corrections possible.

Do not infer a successful outcome from a selected action

Selecting recall practice does not establish that recall has improved. The action needs to be tried, and the later performance needs to be observed. A result field called “learning complete” would overclaim unless the task’s criteria and evidence supported it.

The same distinction appears in ordinary projects. “Send the revised file” is an action; “file received” is a later event; “revision accepted” is another decision. Multiple output columns can preserve these distinctions, but they cannot skip the actual work between them.

Before adding an output column, ask what question it answers and who will use it. If two columns repeat the same information under different names, combine them. If one column hides several different jobs, separate them. The goal is a representation that supports a meaningful next move.

Contents · Previous chapter · Next chapter

A decision table can help a reader separate what a passage states from what they expect. It is especially useful when the text gives a rule and then describes several cases. The table should preserve the passage’s wording and uncertainty. It should not replace close reading with a mechanical search for familiar keywords.

Read this original teaching passage: “For the club’s exhibition, a printed caption is placed beside an object when the contributor has supplied the caption text and the organiser has checked that it matches the object. Otherwise, the object receives a temporary number card. Arun supplied his text on Monday. Bea’s caption had been checked against her object. Chen supplied a caption, and the organiser confirmed that it matched his object. No further information about the checks was included in the note.”

The question is: which contributors’ objects can we confidently say receive a printed caption under the stated rule? The word confidently here means supported by the information supplied, not a numerical confidence estimate. We must inspect the two required facts for each object.

Map the evidence before selecting the outcome

For Arun, supplied text is established. The matching check is not stated. For Chen, both requirements are established. For Bea, the wording says her caption had been checked against her object; depending on the ordinary reading, this establishes a caption exists and was checked, but it does not explicitly say the check succeeded. A check can discover a mismatch.

The important distinction is between checked and confirmed to match. If the rule requires a successful match, a record that a check occurred is not enough. The passage deliberately leaves Bea’s result unstated. We should not award a positive result merely because the same verb appears near the relevant object.

The table does not conclude that Arun and Bea receive number cards in reality. It concludes that the note does not establish their actual condition values. The source rule says what happens for unmet requirements, but missing evidence in our reading is not the same as a requirement being unmet.

Keep the rule and the reader’s knowledge separate

This is a subtle but valuable point. The organiser may know exactly what happened. The reader has only the note. A rule can be complete while the evidence available to the reader is incomplete. Writing “not enough information” can therefore be the correct reading result even when the real process assigns a definite outcome.

Ask what additional sentence would settle each case. For Arun: “The organiser confirmed that Arun’s caption matched his object.” For Bea: “Bea had supplied her caption, and the check confirmed a match.” These additions provide missing information rather than changing the rule.

Use the table to check a paraphrase

A weak summary might say, “Everyone who submitted a caption received a printed label.” That removes the matching requirement. Another might say, “Only Chen submitted a caption.” That invents a negative fact about Arun, who clearly supplied his text. The table shows which relationship or fact was lost.

A more faithful summary is: “A printed caption required supplied text and a confirmed match; Chen is the only case for which the note clearly establishes both.” This is a statement about the available evidence. It does not assert that the other contributors failed the actual process.

Return to the passage when interpretation is contested

Tables can help organise a reading, but they do not settle every linguistic ambiguity. If a phrase could reasonably imply more than its literal words state, discuss the context and the question being asked. Do not treat a teaching table as a universal rule that ordinary readers must ignore all reasonable inference.

The useful habit is to label the difference: explicitly stated, reasonably inferred, or unresolved. Then explain why the distinction matters to the particular question. A reader gains control when they can identify which part of an answer comes from the passage and which part comes from an assumption.

Contents · Previous chapter · Next chapter

Mathematical examples can make a decision table’s logic easy to inspect because the conditions can be defined precisely. They also reveal why the domain matters. A rule written for whole numbers should not be applied to every possible quantity without checking what its conditions mean.

Use this invented sorting task: “For an integer, place its card in the green tray when the number is divisible by both two and three. Put every other integer card in the white tray.” Divisible means that division gives an integer quotient with no remainder. We are sorting written number cards; this is not an official school assessment task.

Six belongs in the first row. Four belongs in the second. Nine belongs in the third. Five belongs in the fourth. These examples establish that all four combinations are possible for the chosen conditions. We are not merely drawing four rows and assuming they correspond to actual integer cases.

Separate the arithmetic from the connective

A learner who puts nine in the green tray may know that nine is divisible by three but overlook the requirement involving two. Another learner may miscalculate nine divided by two. The same wrong tray can reflect a logical reading error or an arithmetic error. Ask them to give both condition values before selecting the result.

If they correctly say No and Yes but still choose green, the problem lies in applying both. If they say Yes and Yes, inspect the divisibility judgement. This makes feedback more specific. It also prevents a student from relearning a word they understand when the actual difficulty is elsewhere.

Test zero and negative values if they are within scope

Zero is an integer and is divisible by two and by three, since zero equals each divisor multiplied by the integer zero. It therefore goes in the green tray under the stated rule. Negative six also meets both divisibility conditions. If the intended exercise excludes zero or negative integers, that restriction must appear in the scope.

This is a useful check against relying on the appearance of familiar examples. A learner may associate “number card” with positive counting numbers and silently narrow the task. The word integer includes zero and negative whole numbers. Knowing that word’s scope changes which cases belong in the exercise.

A card showing 7.5 is outside this integer-card task. That does not make the number wrong. It means the sorting rule, as stated, does not cover that input. The distinction between outside scope and a negative condition appears again in a concrete form.

Compress the rule only after checking equivalence

For integers, being divisible by both two and three is equivalent to being divisible by six. You can therefore use “multiple of six” as a shorter condition in this particular task. The table helps show what has been compressed, but the mathematical relationship needs its own justification.

Do not generalise that shortcut to every pair of divisors by multiplying them. Divisibility by both two and four is equivalent to divisibility by four, not eight. Four itself is a counterexample to the mistaken multiply-every-time rule. A compact label is useful only when it preserves the actual condition.

Use changed examples to test transfer

Now change the connective from both to at least one. Four and nine move to the selected tray; six remains selected; five remains unselected. The arithmetic facts did not change. The rule did. Ask the learner to predict the changed rows before trying more numbers.

Next change the domain to positive integers less than ten. Zero and negative six no longer belong to the input set, even though their divisibility facts remain true. The learner must now track both the scope and the selection rule. This is a richer task than memorising a tray for each familiar number.

Finally, ask for a verbal explanation without the table: “The green tray contains the integer cards that satisfy both divisibility tests.” Then ask for one example and one near miss. A near miss such as nine shows why the second requirement matters. Vocabulary, arithmetic and representation now support one another in an inspectable way.

Contents · Previous chapter · Next chapter

Lina’s fictional project group is preparing a short presentation. They have a limited rehearsal slot and want to avoid spending it arguing about equipment. Their immediate question is narrow: which rehearsal format should they use today? They are not deciding the final quality of the presentation or the mark it deserves.

The group agrees this complete local rule: “Use the slide rehearsal when the current slides are available and the projector booking is confirmed. If that combination is not available, use a paper rehearsal when the current speaking outline is available. If neither format is available, use the slot to prepare the outline.” All three input statuses must be established before applying this version of the table.

Define the terms before choosing the rows

Current slides means the version linked in the group index. Available means the group can open that version for the rehearsal. Booking confirmed means the organiser has confirmed the projector for this particular slot. Current speaking outline means a readable outline that matches the intended presentation order.

These definitions prevent several shortcuts. A file with the right title may be an old version. A projector visible in the room may belong to another booking. An outline on one person’s phone may not be accessible to the group. The conditions concern usable resources for this session, not the existence of something vaguely similar.

The phrase “Either Yes or No” means that this established input does not change the outcome in that row. It does not mean unknown. The rows are arranged so that each fully known combination matches one row. The longer wording is deliberate: it avoids asking beginners to guess what a dash means.

Apply the table to a case

Today’s facts are: the current slides can be opened; the projector booking has not been confirmed and the organiser has explicitly said it is unavailable for this slot; the current outline is available. The inputs are Yes, No and Yes. The third row selects paper rehearsal.

Lina explains the decision: “We have the slides, but the slide format requires a confirmed projector as well. Our current outline is available, so the agreed backup is paper rehearsal.” This explanation preserves the conjunction and the fallback. It does not say the slides are poor or the presentation is unready in every respect.

Distinguish No from waiting for an answer

Now change one fact. The group has asked about the projector but has not received a response. The booking status is unknown, not an established No. Under this table’s scope, the group must use its agreed clarification procedure before treating the inputs as complete. They might set a decision time and ask the organiser; any fallback at that time should be explicitly agreed.

If the group chooses a practical rule such as “use paper rehearsal when confirmation has not arrived by the start of the slot”, that is a legitimate new local convention once agreed. Its condition is confirmation received by the start, not the broader claim that no booking exists. The distinction protects the accuracy of the record.

Check the table’s limits

The rule does not ask whether every speaker has practised, whether the slides are accurate or whether the group can finish on time. Those concerns belong to other checks. Choosing slide rehearsal does not certify the whole presentation. A useful table answers its defined question and leaves other questions visible.

The group can also reconsider its preference for slides. Perhaps the main aim today is to practise speaking without reading from a screen. Then a paper rehearsal may be educationally preferable even when equipment is available. That would be a change in purpose and rule, not a failure to follow the old table correctly.

Use the case to learn transferable vocabulary

The strongest words to learn here are not necessarily long: current, available, confirmed, both, otherwise, fallback and scope. For each, explain what would go wrong if it were removed or replaced.

For transfer, change the task to rehearsing a puppet performance. Identify which structure can remain: preferred format, necessary resources, agreed fallback. Identify which details must change: slides, projector and speaking outline. A learner who can preserve the relationship while replacing the surface details is using the table as a thinking tool.

Contents · Previous chapter · Next chapter

A decision table can identify options that meet agreed requirements. That does not mean it can decide which option people will enjoy most. Separating feasibility from preference helps prevent the table from making a stronger claim than its inputs support.

Imagine four family members choosing a game for an invented evening at home. They agree to consider games that can include all four players and have a usual playing time of no more than thirty minutes. They have three available games and a short information card for each. These fictional durations are teaching values, not product recommendations.

The decision for each game is “does it meet our stated requirements for consideration?”. A complete rule says Yes exactly when the player range includes four, the listed usual duration is at most thirty minutes, and the required pieces are present. Otherwise the game does not meet this particular set of requirements.

Apply the same conditions to every option

Garden Paths meets all three conditions. Island Letters also meets them: thirty minutes is included by at most thirty. Bridge Builders does not include four players within its stated range, so it does not meet the agreed requirement even though its listed duration is short enough.

The output is a shortlist of two games. The table has not selected a winner. The family still needs a fair way to choose between the remaining options, perhaps taking turns, discussing preferences or agreeing another criterion. That decision involves information and values the first table did not contain.

Do not turn a usual duration into a guarantee

The information says usual duration. It does not promise that a game will finish in exactly that time. New players, explanations and interruptions may change the actual duration. The family can use the listed duration as a rough planning input while keeping its meaning intact.

If they have a strict thirty-minute window, they may choose a larger time margin or an agreed stopping point. That is a change to the planning rule. It should not be hidden by relabelling a usual duration as “maximum possible duration”. Vocabulary about estimates, limits and guarantees matters because those words support different decisions.

Keep a preference from becoming an invisible requirement

One family member prefers word games. That is a preference to discuss, not an automatic exclusion of every other game. If the table quietly adds “word game?” as a mandatory condition, it changes the group’s agreement. A neat representation can conceal whose preference became the rule.

This is one reason decision tables need human judgement. They can make criteria visible, but they cannot decide whose interests should count or how competing preferences should be balanced. Those are substantive choices. The table should help people inspect the choices instead of making them disappear behind a result.

Revise the input when the situation changes

Suppose one person decides not to play. The relevant player count becomes three, and Bridge Builders may now meet that condition. That does not prove the earlier result was wrong. The facts changed. Reapply the rule to the new case rather than treating the old shortlist as permanent.

Suppose instead that Island Letters is missing a required piece. Its availability changes even though the player range and duration do not. The table helps identify the exact reason for the changed result. “We are not choosing it tonight because a required piece is missing” is more precise than “it is a bad game”.

Use the exercise with children respectfully

Invite learners to explain a condition and suggest a fair additional question. Avoid turning the table into a device for dismissing their preferences. They can understand that an option does not fit today’s constraints while still valuing it for another occasion.

For a transfer task, replace games with three possible craft activities. Keep the distinction between requirements, estimates and preferences. Ask what the table can conclude and what remains for discussion. The vocabulary becomes useful because it helps the family disagree about the right thing: the facts, the criteria or the final choice.

Contents · Previous chapter · Next chapter

A table that works for its author may fail during a handover. The author remembers why a row exists, which version is current and what an abbreviation means. A new reader sees only the page. To make the table reusable, preserve the context that affects interpretation.

Imagine a student group handing its activity materials to next week’s organisers. The table has a column marked “checked” and two destinations labelled A and B. The original group knows that checked means “contents checked against the list” and that A is the preparation tray. The new group assumes checked means “teacher reviewed” and that A means approved. Everyone may read the same words while following different rules.

Include the minimum context needed to use it

A useful handover includes the decision question, the scope, definitions of controlling terms, the rule for multiple matches and the date or version of the instructions. It also identifies where current facts come from and what to do with an unresolved case. These details can be brief. Their purpose is to prevent a new reader from reconstructing the agreement by guesswork.

Replace A and B with meaningful destination names unless the letters are stable labels on the actual containers. If letters are necessary, include their meanings beside the table and on the containers. A table should connect its language to the world in which someone will act.

Separate the reusable rule from today’s case record

The rule table describes what to do for classes of cases. A case record describes one application: the observed inputs, the selected row, the outcome and any follow-up. Mixing these into a single changing document can make it difficult to tell whether someone altered the rule or merely recorded a new case.

A simple record might say: “Envelope 8: title present, name check incomplete; row 2; keep in preparation; ask contributor to confirm spelling.” That record does not need to copy the entire rule table. It should refer to the correct version if more than one version exists.

Do not collect personal details merely because a form has space. For a classroom exercise, invented case numbers are usually sufficient. In a real project, record the information needed for the task and follow the relevant local arrangements. The aim is traceable reasoning, not an unnecessarily detailed profile of the people involved.

Check the handover with a fresh example

Give the new reader a case that was not used during the explanation. Ask them to identify the input values, select the row and explain the result. If they cannot, inspect the point of difficulty. Perhaps the condition is unclear; perhaps the row policy is missing; perhaps a local word has not been defined.

Do not rescue the table immediately with spoken instructions. First note what the reader needed to ask. That question identifies information the written handover may need. Then revise the table or its short supporting note and try another case.

A successful demonstration by one person is useful evidence about that interaction, not proof that every reader will understand the table. If the table will serve a varied group, include readers with relevant differences in familiarity or language background. Keep the check proportionate to the task.

Record a change as a change

Suppose the group adds a new condition requiring the current instruction card. Do not silently overwrite the old definition of complete while leaving yesterday’s records unexplained. Note when the new rule applies and which cases need rechecking. An old case can be correctly classified under the old rule and require a different classification under the new one.

Vocabulary helps distinguish correction from revision. A correction repairs an error in expressing or applying the intended rule. A revision changes the intended rule itself. Both can be legitimate, but they have different implications for past records and future use.

Keep a route for disagreement

A new organiser may discover a case that the table handles poorly. The useful response is to identify the case and the relevant row, then discuss whether the facts, definitions or policy need revision. “The table says so” is not a sufficient answer to evidence that the table is wrong or incomplete.

This is how the representation remains a tool for people. It stores an agreement, makes its consequences inspectable and allows a specific challenge. It should not become a shield against reasonable questions. A good handover gives the next person enough understanding to use the table and enough context to know when to ask for help.

Contents · Previous chapter · Next chapter

A paper table is often enough. A spreadsheet can be useful when many cases share the same rule, and an AI assistant can help propose a first layout or generate test examples. The essential task remains the same: preserve the meaning of the rule and check the result. The medium does not supply missing authority or missing facts.

Begin with a small human-readable version. If you cannot explain the conditions and outcomes in ordinary language, automating them is likely to carry the ambiguity into another format. A table with clearly named inputs is a better starting point than a complicated formula whose intended behaviour nobody can describe.

Keep manual inputs distinct from calculated outputs

In a spreadsheet, you may enter the observed facts in one set of cells and calculate a result in another. Label both clearly. If someone types an assumed result into an output cell, the sheet may look consistent while bypassing the rule. The design should make the source of each value understandable to its users.

This guide does not prescribe a particular spreadsheet function or current product interface. Different tools handle blank cells, text, errors and logical values differently. Before relying on an implementation, check the tool’s relevant documentation and test the specific behaviours your rule needs. A blank input is especially worth testing because it must not silently acquire a meaning you did not intend.

Test the implementation against known cases

For a two-condition rule, manually establish the four known Yes/No outcomes. Enter one case from each row into the implementation and compare the output. Then try the boundary values, unknown values and invalid entries relevant to your task. The purpose is to test meaningful risks, not to generate a large number of redundant examples.

A correct result for the easiest case is not enough. If the rule requires both checks, a case with one Yes and one No is essential. If the rule uses at most ten, test exactly ten. If the table uses first-match priority, include a case that matches more than one condition so the order is exercised.

Also check the explanation a human will see. An output such as “0” may be technically convenient but unclear. A meaningful result such as “keep in preparation: name check outstanding” can support action, provided the reason is generated from the correct condition rather than attached as a generic message.

Ask an AI for a bounded transformation

A useful request is: “Turn the following invented instruction into a decision table. Preserve the stated conditions. Do not invent outcomes for unspecified cases. Show the rule for multiple matches. Provide one concrete test case for each row and identify any ambiguity in the source.” Then supply the actual instruction.

This request defines the work. It does not guarantee a correct response. Inspect the output using the original wording and the test cases. Ask for concise, checkable explanations of which source sentence supports each output. You need an accountable mapping from rule to row, not a claim about the system’s hidden internal process.

Review the words most likely to change the rule

Check and, or, only if, unless, at least, at most, each, current and otherwise. Also inspect whether the proposed table has converted missing evidence into a negative, a recommendation into a requirement or a planned action into a completed one.

If the assistant supplies a polished default for a blank case, ask where that default came from. If it came from an assumption, label it as a proposed addition and decide whether the appropriate person accepts it. Do not let fluency hide the difference between interpreting a rule and designing a new one.

Keep the learner involved in verification

For educational use, ask the learner to predict an output before revealing the automated result. Then compare their explanation with the source. This preserves an opportunity to practise reasoning. If the tool does every classification and the learner only copies the answer, the table may support task completion without demonstrating independent understanding.

You can also ask the learner to find one case that would expose a suspected error. For example, a table may accidentally treat an inclusive or as exclusive. The both-true case reveals the difference. Designing that test is a substantive use of vocabulary and logic.

Use automation when it reduces repetitive work without hiding the decision. Keep a readable rule, a few decisive examples and a route for correcting the implementation. The useful technology is the combination of language, representation and human verification.

Contents · Previous chapter · Next chapter

This workshop brings the distinctions together. It concerns an invented classroom survey about which fictional story to discuss. The records are deliberately small and contain no real personal information. The aim is to practise preserving rules, not to learn a general research or school policy.

The class uses numbered response slips. For this exercise, the organiser gives a complete processing rule: “First, if the response number has already been entered, set the slip aside for a duplicate check. Otherwise, if the slip arrived after noon, place it in the late-response folder. Otherwise, if the slip does not contain exactly one permitted story choice, ask for clarification. If none of those conditions applies, include the response in the current count.”

The rule applies only when the response number, receipt time and marked choice can be read and checked. An unreadable or missing input goes to clarification before this table is used. Noon is included in the on-time period. Permitted choices are A, B and C. Setting a slip aside does not mean accusing its contributor of wrongdoing.

Build the table before reading the answers

Name the decision: which processing action applies to this slip? Name the three conditions: response number already entered, received after noon, and exactly one permitted choice present. State the row policy: use the first matching row. The priority comes directly from first and otherwise in the source.

Notice that the second row does not repeat “response number not already entered”. The first-match policy supplies that ordering. You could instead write mutually exclusive rows that include every earlier negative condition. Both designs can express the same process if written correctly. Do not combine the compact rows with an unstated assumption that all matching actions should be performed.

Case A: an ordinary eligible response

Slip 041 has a number not previously entered, arrived at 11:58 a.m., and contains choice B only. No earlier condition matches, so row 4 includes it in the current count. The explanation should name the three checks: no duplicate number, on-time receipt and exactly one permitted choice.

A response such as “include because B is allowed” is incomplete. It identifies one necessary part of the route but ignores time and duplicate status. Ask the learner to show the full path through the ordered rules.

Case B: the exact time boundary

Slip 042 has a new number, arrives at exactly noon, and contains A only. It is included. The condition says after noon, and the scope note explicitly includes noon in the on-time period. Changing the condition to “at or after noon” would change this result.

This is a boundary test. A learner who treats noon as late should explain which wording they used. They may be importing an assumption from another deadline rule. The task is to follow the supplied convention, not whichever convention feels most familiar.

Case C: two permitted choices

Slip 043 has a new number, arrives at 11:50 a.m., and contains both A and C. It reaches row 3 and requires clarification. Each choice is permitted individually, but the rule requires exactly one. The set of allowed values and the number of selected values are separate conditions.

Do not choose A because it comes first alphabetically, and do not split the response into two counts. Neither action is supplied by the rule. A table should expose the unresolved choice, not settle it by an invisible preference.

Case D: a duplicate number and a late time

Slip 044 has a number already entered, arrives at 12:05 p.m., and contains B only. It matches rows 1 and 2, but the declared first-match rule selects the duplicate check. This is the case that tests priority. If a learner sends it directly to the late folder, they have followed one condition while overlooking the order.

The duplicate check may later reveal a copied number, a corrected slip or another explanation. The current table does not decide that later investigation. “Duplicate number found” is a record condition; “person deliberately submitted twice” is an unsupported claim about behaviour.

Case E: an unreadable time

Slip 045 has a new number and choice C only, but its receipt time cannot be read. It goes to the preliminary clarification route because this table requires checked inputs. It does not automatically enter the current count, and the unreadable time is not treated as proof of lateness.

After the time is established, apply the table again. If it was 11:55 a.m., the slip can reach row 4. If it was 12:03 p.m., row 2 applies. The missing fact matters because its possible values lead to different outcomes.

Case F: a changed rule

The organiser now extends the deadline to 12:15 p.m. for all slips in this exercise. This is a rule revision. Recheck the time condition and identify which previously late slips are affected. Do not assume that duplicate checks or unclear choices are automatically resolved by the extension.

A learner who can explain that only the time boundary changed is preserving the structure. A learner who moves every set-aside slip into the count has treated one revised requirement as if it cancelled every other requirement.

Reflect on what the table made visible

The workshop distinguishes a permitted value from a permitted combination, a boundary from a vague deadline, a duplicate record from an accusation, and missing evidence from a negative fact. It also separates a processing action from the final survey result. The vocabulary is useful because each distinction changes a concrete step.

To extend the exercise, invent one additional slip that exposes a mistake you think another reader might make. Explain the expected action and the exact word or relationship the case tests. Creating a revealing case shows a deeper understanding than repeating a definition of decision table.

Contents · Previous chapter · Next chapter

If a learner struggles with a table, do not assume the table itself is too advanced or the learner lacks vocabulary in general. Locate the step that failed. They may misunderstand a word, misread the relationship, use the wrong fact, overlook a boundary or explain the result too broadly.

Use a small case and ask for four things: the decision question, the input values, the selected row, and the reason the outcome follows. These four observations give more information than a single right-or-wrong mark. They also keep the discussion focused on the task rather than on the learner’s identity.

Match the repair to the error

This is an inspection aid for teaching, not a validated diagnostic instrument. More than one difficulty can occur in the same response. A learner may need clearer instructions, a familiar context or a different way to demonstrate understanding before a vocabulary gap can be identified.

Session one: explain a tiny rule

Use two visible conditions and four combinations. Coloured paper shapes are enough. Ask the learner to say the rule in their own words, classify each arrangement and explain one near miss. Keep the activity short enough that attention remains on the distinction.

End by hiding the table and asking which words controlled the result. The learner might identify both, at least one or exactly one. Ask for a fresh example using the same relationship. This checks whether the word is connected to an operation.

Session two: reconstruct after a gap

At a later suitable opportunity, ask the learner to rebuild the small table from a sentence. Do not provide the old grid immediately. If they need support, reveal one condition or one worked row, then let them continue. Record what support was needed rather than presenting assisted performance as independent recall.

The interval can fit the learner and the teaching schedule. This guide does not prescribe a universal optimum. The purpose is to see what the learner can reconstruct when the first demonstration is no longer immediately in view.

Session three: change one feature

Change and to or, move a numerical boundary, or replace a known input with an unknown. Ask the learner to predict which result changes and why. Keep other features stable so the effect of the change can be examined clearly.

Then reverse the task. Give the desired change in outcomes and ask which part of the rule would need revision. For example, “We now want the both-selected case to be excluded.” The learner should identify an exactly-one requirement rather than changing an unrelated label.

Session four: use a new setting

Move from paper shapes to an everyday planning task. Ask what carries over and what must be redefined. A learner might preserve the both-required relationship while replacing colours with available resources. Insist on a new explanation, not a memorised sentence with different nouns.

For bilingual learners, allow explanation in a familiar language or through objects when that helps reveal the concept. Then practise the relevant English wording. This separates conceptual understanding from the ability to produce one particular English phrase under pressure.

Session five: inspect someone else’s table

Provide a short table with one deliberate error: a missing case, overlapping destinations, an ambiguous dash or an unsupported default. Ask the learner to construct a case that reveals the problem. Identifying the exact failing case is more useful than saying the table is confusing.

Finish with a repair and a limit statement: what the corrected table can decide, and what it still cannot decide. If the learner can explain both, the vocabulary is beginning to support independent judgement. Continue with a real task only when the added structure helps that task.

Contents · Previous chapter · Next chapter

Is a decision table just a checklist?

A checklist helps you remember items or actions to inspect. A decision table shows how combinations of conditions connect to results. A checklist might remind you to inspect the title and name. The table explains what to do when one is complete and the other is not. The tools can work together: a checklist gathers facts, and a table applies a rule to those facts.

How is it different from a comparison matrix?

A comparison matrix places options beside criteria such as time, effort or preference. It helps people examine trade-offs. A decision table specifies outcomes for combinations of conditions. A family-game shortlist can use a rule table to exclude options that do not meet agreed requirements, then a comparison matrix or conversation to choose among the remaining options. Do not call a preference ranking a logically necessary result.

Would a flowchart be easier?

Sometimes. A flowchart can make a sequence of questions clear. A table can make combinations, overlaps and gaps easier to compare side by side. Choose the representation that suits the question and reader. You can translate a small ordered rule into both forms and compare them. If the forms produce different outcomes for the same case, investigate the translation before deciding which layout you prefer.

Do I need programming knowledge?

No. You can build and use a simple decision table with paper, familiar objects and ordinary language. Formal software standards add precise notation and implementation requirements for specialised work. They are a possible extension, not a prerequisite for understanding how two conditions combine. The essential skill is explaining what each condition means and why the result follows.

Why include an unfamiliar term such as hit policy?

Use a technical term when it names a distinction you need. Hit policy names the rule for dealing with matching rows. You can first learn the distinction using “choose the first match” and “collect all matching actions”. The technical label then provides a compact way to discuss it. Memorising the label without understanding the difference adds little to the task.

Can a table include uncertain judgements?

Yes, if the uncertainty and judgement are represented honestly. A condition may record a reviewer’s assessment, an estimate or an unresolved input. The table should explain what those values mean and what action they support. Do not turn “probably suitable” into “confirmed suitable” merely because the output needs a clean answer. Sometimes the appropriate result is a request for further information or discussion.

Does unknown always mean we must stop?

No. Ask whether the missing value could change the particular result. If a fully stated rule requires both conditions and one is definitely No, the combined requirement is not met regardless of the other value. You may still need the missing information for a repair list or another decision. Preserve the unknown while separating what can already be concluded from what remains unresolved.

What if two people disagree about a condition?

Ask whether they are using the same definition and examining the same evidence. They may disagree about what current means, which file is being checked or whether the review criterion was satisfied. Resolve that issue before arguing about the final output. If the disagreement is a legitimate judgement difference, the process needs an agreed way to handle it; the table alone cannot supply one.

Should every rule be made into a table?

No. A single straightforward instruction may be clearer as a sentence. Tables become useful when combinations, exceptions or repeated decisions make the structure worth inspecting. Creating a table can also be a temporary thinking exercise, even if the final communication returns to prose. Keep the tool when it makes the task easier to understand or check, not because every activity must look technical.

Can decision tables improve writing?

They can support a particular writing task by exposing missing conditions, inconsistent labels or an overbroad conclusion. Whether a learner’s writing improves needs to be observed in actual work. A table about one instruction does not demonstrate general writing mastery. Ask the learner to rewrite the paragraph, preserve its meaning and explain the changes, then try a different task later.

What if a child understands the table but cannot explain it fluently?

Offer another way to demonstrate the relationship: point to the relevant row, arrange objects, choose a counterexample or explain in a familiar language. Then support the English expression separately. Fluent explanation is useful, but its absence in one moment does not establish a lack of conceptual understanding. Look for the specific support that helps the learner connect meaning and wording.

How do I avoid making the table too complicated?

Keep one decision question, remove inputs that do not affect that decision, and separate genuinely different outputs. Define a small scope before adding exceptions. If the number of combinations becomes difficult to inspect, consider several linked decisions or a different representation. Complexity should come from the task’s necessary distinctions, not from an attempt to anticipate every imaginable event.

Does a complete table guarantee a good decision?

No. Completeness concerns coverage of the defined input space. A complete table can still use poor criteria, inaccurate facts or an unsuitable scope. It can also express an unfair agreement very consistently. Inspect the rule’s justification and consequences as well as its structure. A representation helps make choices visible; it does not make them automatically wise.

What is the smallest useful starting exercise?

Choose two clearly observable conditions and a fully stated rule. List the four Yes/No combinations, explain one result from each, and test the case where both conditions are true. Then change one word in the rule and predict which outcomes change. This small exercise contains the central idea: vocabulary can be used to control relationships and actions.

Contents · Previous chapter · Next chapter

A decision table is valuable when its language stays connected to a task. The following terms are worth keeping because each answers a different question. You do not need to memorise every definition before starting. Use the term when it helps you locate a difficulty or explain a choice.

A compact working glossary

• Decision: the particular question the table is intended to answer. A precise decision question limits what its output claims.
• Input: information supplied about a case. An input value should have a clear meaning and a suitable basis.
• Condition: a test used by a rule. A condition can concern a category, a number, a state or a defined judgement.
• Rule: the relationship that connects a specified combination of conditions with an outcome.
• Output: the result returned by applying the rule. It may be a category, proposed action or list of next steps.
• Scope: the situations and inputs for which the table is intended. A case outside scope is not automatically a negative case.
• Coverage: whether the relevant cases have a defined result or route. Coverage must be assessed against a stated domain.
• Overlap: a case satisfying more than one rule. Its acceptability depends on the intended treatment of multiple matches.
• Conflict: incompatible results for a case under the table’s intended behaviour. A concrete example can make the conflict visible.
• Default: an explicitly chosen result when specified alternatives do not apply. A missing instruction is not a default.
• Unknown: information that has not been established. It must not be silently treated as an established No.
• Boundary: the point at which a condition changes value. Inclusion words and units determine how the boundary works.

Primary sources and what they support

The teaching cases, fictional records and practice routines in this article are original illustrations. They are not reported experiments or official school policies. The following sources provide the limited scholarly and technical background identified in the relevant chapters.

• Object Management Group: Decision Model and Notation 1.5. A formal specification route for decision modelling. The everyday tables here are introductory representations, not certified DMN implementations.
• Camunda: decision-table hit policies. Official documentation showing how a formal implementation distinguishes ways of handling matching rules. Consult documentation for the actual tool and version when implementing a table.
• Calvanese and colleagues: Semantics and Analysis of DMN Decision Tables. Original research addressing formal analysis of missing and overlapping rules. It supports the importance of those analysis questions, not a claim that the classroom exercises have been experimentally validated.
• Zhang and Norman: Representations in Distributed Cognitive Tasks. Original research on the relationship between internal and external representations in specified problem-solving tasks. Its findings should not be stretched into a promise that every table improves every kind of learning.

Choose one real question to improve

Find a small instruction that people repeatedly interpret differently. It might concern which file to use, which preparation step remains or which materials fit an activity. Write the decision question in one sentence. Identify the words whose meanings change the result. Then build the smallest table that reveals the relevant combinations.

Ask someone else to use it with a fresh case. Notice whether they need an unstated definition, invent a default or confuse an unknown with a negative. Make one concrete repair. If the table becomes more cumbersome than the original task, reduce its scope or return to a clearer sentence.

To develop the wider idea, read how words and representations work as cognitive artefacts, how verbal interfaces connect language to action, and how to test vocabulary in a real task. These routes examine different parts of the same practical ambition: making language usable.

The next useful step is a clear case, a precise distinction and a reasoned result. When those stay connected, vocabulary becomes something you can work with: a way to inspect a rule, coordinate with another person and improve the next decision.

Contents · Previous chapter · Continue at the vocabulary hub