Construct a logical argument about an invented procedure

Counting complaints is not the same as judging a procedure

• A fictional makerspace receives complaints about equipment reservations. An essay must decide whether the proposed procedure is justified. It needs a conclusion, relevant evidence and an explanation connecting them—not a claim that rules are automatically good or bad.
• This GAC015-aligned lesson uses a made-up institutional procedure to practise logical argument. It states no actual law or legal right. The source log and criteria are classroom evidence, not a legal authority.

Define the decision and the evidence boundary

• The proposal is to require users to confirm bookings the day before use. A fictional four-week log lists forty bookings: six unused slots and four cases where someone arrived but another user had the equipment. Reasons for unused slots are incomplete.
• A staff note proposes confirmations; a student note warns that not everyone checks email daily. The log describes problems but does not test the proposal. The notes add perspectives, not measured predictions about how many problems will disappear.

State the warrant linking evidence to a proposal

• A warrant explains why evidence supports a conclusion. Unused slots support checking whether users still need their bookings; they do not establish that email-only confirmation is accessible. A sound argument makes the missing link visible.
• Choose criteria such as reducing conflicts, preserving access and keeping effort manageable. These are proposed decision criteria, not measured achievements. Explain which evidence relates to each and which information still needs collecting.

Address a strong objection rather than a weak substitute

• A fair objection is that mandatory email confirmation may exclude people who miss the message. Do not answer by saying “students hate all rules,” which changes the objection. Consider an alternative channel or a small trial, while keeping its effectiveness unmeasured.
• Acknowledge that keeping the existing system also has costs: unused slots and conflicts. An argument can compare imperfect options. It should state what a limited trial would test and how users could report access problems.

Write a conclusion proportionate to the support

• Draft 160–190 words recommending either a limited trial or more investigation before one. Include the bounded log evidence, a warrant, the access objection and a response. State a review criterion; do not invent a successful trial to close the argument.
• Use “supports testing” rather than “proves the policy will work.” If your recommendation depends on an accessible confirmation route, write that condition explicitly. Conditional reasoning is clearer than burying an important assumption.

Check logical consistency and source use

• Label conclusion, evidence, warrant and counterargument in your draft. Every borrowed fact needs acknowledgment to its fictional source; real essays need real retrievable sources. Check that your ending does not claim a stronger result than your body established.
• Ask a partner to identify the most important uncertainty. If they cannot, revise it into the argument. Acknowledging a genuine weakness can improve a recommendation by showing what must be checked before a wider decision.

{callout:example} The log supports testing a way to release unneeded slots, but it does not establish that email-only confirmation is suitable. A limited trial with another response route could examine both slot use and access before a wider decision. {/callout}

{callout:warn} A source describing a problem is not automatically evidence that your preferred solution will solve it. {/callout}

{callout:key} A logical argument connects relevant evidence to a bounded conclusion through an explicit warrant and a fair response to objections. {/callout}