Use units to understand problems and guide solutions, choose and interpret units and scales in graphs, define appropriate quantities for modeling, and choose a level of accuracy appropriate to the measurement (TN A1.N.Q.A.1-3).

What this topic is asking

The Number and Quantity standards A1.N.Q.A.1 to A.3 are about quantities and units as the foundation of modeling. You use units to understand a problem and guide its solution (dimensional analysis), you choose and interpret units and scales on graphs and data displays, you define appropriate quantities for a model, and you report answers to a level of accuracy the measurement supports. These ideas run through every applied item on the test.

Units guide the solution

The most testable idea is dimensional analysis: write each conversion as a fraction, then arrange the fractions so units cancel until only the target unit remains. This both performs the conversion and checks it, because if the leftover units are wrong, the setup is wrong.

Scales, quantities, and accuracy

Two more sub-skills round out the standard.

• Interpret scale and origin. When reading a graph, note what each axis measures and the size of each gridline. A scale that starts above zero (a "broken axis") can exaggerate differences, a point the statistics items revisit.
• Define appropriate quantities. To compare two cities' traffic fairly, a rate (accidents per 1000 drivers) is more meaningful than a raw count, because it accounts for population. Choosing the right quantity is part of descriptive modeling.
• Appropriate accuracy. Report digits the measurement supports. A scale reading to the nearest gram should not be quoted to the nearest milligram.

How TNReady examines this topic

• Numeric response. Convert a rate between units (for example miles per hour to feet per second), scored by exact value.
• Multiple choice. Choose the most appropriate unit, quantity, or level of accuracy for a context.
• Drag and drop. Match conversion factors or arrange a unit-cancellation chain.

A clarifying idea is that units travel through every operation: when you multiply a rate (dollars per hour) by a quantity (hours), the shared unit cancels and leaves dollars. Tracking units is therefore a free check on whether a formula is set up correctly.

Why a number without units can mislead

A bare number rarely answers an applied question. "The answer is $88$" is incomplete; "$88$ feet per second" is the answer, and the units justify it. The same value can be right or wrong depending on the unit: $60$ is correct for miles per hour but wrong for feet per second. On the EOC, a numeric-response item often specifies the unit in the prompt precisely so the grader can check an exact value, which is why converting to the requested unit before entering the answer is essential. Carrying units also catches a slipped conversion factor, because the leftover units come out wrong before the number does.

Try this

Q1. A runner covers $400$ meters in $50$ seconds. What is the speed in meters per second? [1 point]

• Cue. $\frac{400 \text{ m}}{50 \text{ s}} = 8$ m/s.

Q2. Using $1$ inch $= 2.54$ cm, convert $10$ inches to centimeters. [1 point]

• Cue. $10 \times 2.54 = 25.4$ cm.