How to Evaluate an Argument Step by Step

How do you evaluate an argument?

Identify the conclusion, list the reasons offered for it, and check both those reasons and the connection between them. Make any added assumption explicit. Record what remains unresolved instead of forcing a yes-or-no verdict. For medical, legal, financial or accusatory decisions, use the relevant professional or institutional process; this general reading exercise cannot establish those conclusions.

A persuasive paragraph can feel finished before its reasoning has been inspected. Slowing it down is useful: put the statements on separate lines and ask what each one contributes. The aim is a fair account of the argument, followed by a precise assessment of its support.

This guide uses an original fictional catalogue project. The people, records, rules and quantities below are invented teaching material. No research experiment or improvement in readers' reasoning is claimed.

What exactly are you being asked to accept?

An argument offers reasons, called premises, in support of a conclusion. The conclusion is the claim the writer wants accepted. OpenStax's explanation of arguments separates checking whether premises are true from checking whether they support the conclusion. A true conclusion can still be reached through poor reasoning.

Begin with this fictional proposal:

We should print the catalogue on Friday. All twelve item descriptions are complete, and every image has permission for this print run. We promised the group a finished catalogue this month.

Write the conclusion without enlarging it: “We should print the catalogue on Friday.” Do not replace it with “The whole project is ready” or “Friday is the best possible publication date.” Those are different claims.

Now list the offered reasons: completed descriptions, image permission and the month's commitment. Keep the original paragraph beside your reconstruction. If someone supplied it, ask whether your version captures their intended claim before criticizing it.

Which part is a record, and which part is a decision?

Use this original project sheet. Each entry is a detail supplied by the exercise, not a verified fact about a real project.

The sheet does not accuse anyone of an error. It identifies what the proposal actually gives you and what it leaves open. In particular, a monthly commitment does not itself choose a day within that month.

Our observation, inference and assumption guide provides a separate vocabulary for labeling notes. Here the task is narrower: determine how the supplied statements are meant to support this particular action.

What assumption would connect the reasons to the decision?

The HKU tutorial on hidden assumptions explains how making an implicit premise visible allows its meaning and justification to be examined. An added premise needs assessment too; writing it down does not establish it.

For our example, propose this possible decision rule:

If descriptions are complete and image permission is confirmed, we should print on Friday.

Label that sentence proposed assumption, because the original paragraph did not state it. Ask the fictional project lead whether it is the actual rule. Do not attribute your reconstruction to the speaker as though you had discovered a quotation.

Now imagine the lead supplies the project's agreed checklist: descriptions complete, permission confirmed, page proof approved, and printer availability confirmed. That changes the task. The original paragraph addresses only two of the four listed requirements. It does not tell us whether the other two are satisfied.

The useful response is a specific request: “Please confirm the page proof and printer availability.” It is not “You have failed to prepare,” which the supplied records do not establish.

Is the support meant to guarantee the conclusion?

Some arguments aim at a conclusion that must follow if their premises hold. Others offer support that remains uncertain. OpenStax's inference overview distinguishes deductive reasoning from inductive reasoning, which does not guarantee its conclusion. Do not demand certainty from a claim that offers only a provisional expectation.

Compare two invented statements about the same project:

• Rule application: Our agreed rule says to approve printing when all checklist requirements are satisfied. All those requirements are satisfied. Therefore, printing should be approved under that rule.
• Expectation: The last few catalogue jobs finished on their planned dates. This job may also finish on its planned date.

The first makes its decision rule part of the premises. Evaluating the rule's wisdom remains a separate question. The second looks to earlier jobs; we would want to know how comparable they were before relying on that expectation.

For this exercise, keep the decision-rule version. We have supplied a finite checklist, so we can inspect its entries without turning the article into a forecasting lesson.

Have you checked the premises separately from the reasoning?

In deductive logic, validity means the premises cannot all be true while the conclusion is false. Soundness additionally requires true premises. HKU's soundness tutorial explains why validity alone does not establish that the premises are true.

Suppose our fictional project rule requires every item on the checklist, and the printer booking is still unconfirmed. Someone writes, “All requirements are satisfied; therefore approve printing.” The inference follows the stipulated rule, but the stated record does not establish its key premise. Mark that premise unresolved rather than treating the tidy format as approval.

For real factual claims, follow our source-credibility guide. A reasoning worksheet cannot substitute for examining the actual record. Equally, collecting more records will not repair a connection you have never explained.

Does the proposed repair add any independent support?

Consider a replacement sentence: “Friday is the right date because it is the date we ought to choose.” It repeats the decision in different words and supplies no additional project information.

HKU's good-arguments tutorial discusses why circular support does not give independent reasons for accepting a conclusion. A formal-looking arrangement is not enough to make an argument useful to someone who needs reasons.

For our project, a useful repair would supply the missing checklist records or change the proposed action while those checks remain open. Adding “clearly,” “obviously” or a second copy of the conclusion would leave exactly the same gap.

Can you revise the project argument yourself?

Use these newly supplied fictional facts:

1. The checklist has four requirements: descriptions, permission, proof approval and printer availability.
2. The first three are confirmed.
3. Printer availability has not been confirmed.
4. The group's stated rule requires confirmation of all four before approving printing.

Draft a conclusion that fits these facts. Keep the project rule visible and do not invent a reason for the missing confirmation.

A suitable answer is: “Under the group's stated rule, printing cannot yet be approved because printer availability remains unconfirmed. Ask for that confirmation before applying the approval rule again.”

Notice the precision. Three confirmed requirements out of four leave one unconfirmed. That is a checklist count, not a 75% probability of success. Nor does “unconfirmed” mean the printer is unavailable. The answer identifies the unresolved requirement and the next information needed.

An unsuitable answer is: “The catalogue will be late because the printer cannot do the job.” The exercise says neither of those things. Replacing “will” with “probably will” would still introduce a forecast unsupported by these supplied facts.

What should your final evaluation say?

Our suggested final note is short enough to reread beside the original paragraph:

Keep a link or locator for each real supporting record in your source log. If your assessment changes, retain the earlier wording and identify which new information changed it. This is an editorial recordkeeping suggestion, not a validated scoring system.

Do not assign motives, publish private material or use this worksheet to establish misconduct, diagnosis, legal liability or financial suitability. Follow the qualified process that governs a consequential decision.

A useful evaluation ends with an identifiable reason: a premise needs verification, a connection needs explanation, or the supplied support establishes only a narrower conclusion. That gives the next reader something concrete to inspect and the original writer something concrete to answer.

Sources

• OpenStax: Arguments.
• HKU: Hidden assumptions.
• OpenStax: Types of inferences.
• HKU: Soundness.
• HKU: Good arguments.