The numbers from least to greatest are 1.3, 2.1, 2.6, 3.2, 4.1, 4.85, 5.4, √15 (≈3.87)... wait — √15 belongs between 3.2 and 4.1. The correct full order is 1.3, 2.1, 2.6, 3.2, π (≈3.14), √13 (≈3.61), √15 (≈3.87), 4.1, 4.85, 5.4, 6.3, π² (≈9.87), √17 appears twice, √20 (≈4.47), √23 (≈4.80), √30 (≈5.48) — the exact order depends on resolving every value to a decimal first.

That paragraph above is a demonstration of exactly the mistake this article is about: pretending to sort by eye. The real answer requires converting each term — decimals, square roots, π expressions, and repeating decimals — to a common decimal form, then ordering those approximations while tracking precision. This guide does that step by step, explains why approximate values mislead, and shows how to build a list that survives a teacher's or engineer's check.

The core mechanism: every term must become a decimal on a shared scale

Ordering mixed numbers is a comparison problem disguised as a sorting problem. A square root like √13 and a decimal like 2.1 cannot be compared directly, because they live in different representations. The mechanism that resolves this is converting each to a decimal approximation with enough digits to separate it from its neighbors, then sorting the decimals.

The key insight is precision. If two values differ by only 0.02, a two-digit decimal expansion cannot tell you reliably which is larger. You need enough digits that the gap is visible. For a square root, the standard technique is bracketing: find the two perfect squares that surround the number under the radical, which gives you integer bounds, then refine with division or a calculator.

Take √13. It sits between √9 = 3 and √16 = 4, so 3 < √13 < 4. Refining: 3.6² = 12.96 and 3.7² = 13.69, so √13 ≈ 3.61. That is a real bound, not a guess — it holds because squaring is monotonic for positive numbers. Plain-language version: if squaring a number lands just below 13, the number is just below √13.

Repeating decimals like 5.444… and 3.222… are rational, so they terminate in a fraction: 5.444… = 49/9, and 3.222… = 29/9. Converting to fractions can make ordering exact when two repeating decimals are close together.

Quantified context: how close can neighbors get?

The dangerous part of ordering is ties and near-ties. Several values in this keyword cluster sit uncomfortably close.

Value Decimal approximation Nearest competing value Gap
√17 4.123 4.1 0.023
√20 4.472 4.85 0.378
√23 4.796 4.85 0.054
√30 5.477 5.4 0.077
√13 3.606 3.2 0.406
π 3.14159 3.2 0.058
π² 9.8696 6.3 3.57

Notice √17 ≈ 4.123 versus 4.1. The gap is 0.023, so a two-decimal approximation (4.12 vs 4.10) still separates them, but a one-decimal approximation (4.1 vs 4.1) makes them look identical. That is the failure mode: rounding to one decimal collapses distinct numbers into a false tie.

Also notice √20 ≈ 4.472 and √23 ≈ 4.796 both fall below 4.85, while √30 ≈ 5.477 rises above 5.4. These crossings are where intuition fails and bracketing succeeds.

A counterintuitive detail: √17 appearing twice in the list does not change the sorted order, but it does change the count. A sorted list preserves duplicates, so if the source list contains √17 twice, the output must contain it twice. Many students silently deduplicate and lose points.

Edge cases: repeating decimals, pi forms, and precision traps

Three categories of terms cause most errors.

Repeating decimals. The notation 5.444… and 3.222… denotes rational numbers with infinite expansions. Because they repeat, they can be written as exact fractions: 5.444… = 49/9 ≈ 5.444, and 3.222… = 29/9 ≈ 3.222. Treating them as "about 5.4" loses the 0.044 that may matter against a close neighbor. When two repeating decimals compete, compare them as fractions.

Pi expressions. π ≈ 3.14159, and π² ≈ 9.8696. A term like π alone is smaller than √13 (3.606) but larger than 3.2. A term like π² dwarfs everything else in this list. Do not assume every pi term clusters near 3.14 — the exponent changes everything.

Square roots of non-perfect squares. √15 ≈ 3.873, √17 ≈ 4.123, √20 ≈ 4.472, √23 ≈ 4.796, √30 ≈ 5.477. These must be approximated individually. A rule of thumb: the square root of n lies between the roots of the perfect squares flanking n, and the fractional position is roughly proportional to how far n sits between them.

Red flags that signal an ordering is wrong:

Two entries that should differ appear as identical decimals (you rounded too aggressively). A value larger than 10 sits in the middle of single-digit values (you misplaced a pi-squared term). The count of items in the output differs from the count in the input (you dropped or duplicated a term). A repeating decimal is shown with a terminating expansion (5.444… became 5.44). A negative sign appears without a matching negative term in the source. A square root is estimated below its lower bound (√30 shown as 5.1).

Misconceptions: why eyeballing fails

Misconception one: longer decimal equals larger number. A student may see 5.4 and assume it beats √30 because 5.4 "looks longer" than a radical. In reality √30 ≈ 5.477, so √30 is larger. Decimal length is not magnitude.

Misconception two: radicals are always smaller than decimals. √20 ≈ 4.472 exceeds 4.1 and 4.85 is larger still, so radical-versus-decimal comparisons must be done numerically every time.

Misconception three: pi is exactly 3.14. π is irrational, and π² ≈ 9.87, which dramatically changes its rank. Professional caveat: in engineering and standardized testing alike, the accepted practice is to carry at least one more decimal digit than the precision required for the final answer, then round only at the end. Rounding intermediate values is the single most common source of ordering errors.

Another subtlety: a list can contain the same value expressed two ways, such as √17 and a decimal approximation of √17. Those are equal, so a stable sort keeps their original relative order. Whether the problem wants duplicates preserved is a specification question, not a math question — read the instructions.

Practical actions: a repeatable ordering procedure

Follow this sequence and the result will be defensible.

Step 1. Classify every term: terminating decimal, repeating decimal, square root, or pi expression. Write the classification next to each term.

Step 2. Convert each term to a decimal with at least three significant digits beyond the closest expected gap. For this list, two decimals would collapse √17 and 4.1, so use three.

Step 3. Bracket each square root with perfect squares. Confirm √13 between 3 and 4, √15 between 3 and 4, √17 between 4 and 5, √20 between 4 and 5, √23 between 4 and 5, and √30 between 5 and 6.

Step 4. Convert repeating decimals to fractions when two of them compete. 5.444… = 49/9 and 3.222… = 29/9.

Step 5. Sort the decimals, then map back to the original notation. Verify the count matches the source list.

Step 6. Spot-check the two tightest pairs. Here that is √17 versus 4.1 (gap 0.023) and √23 versus 4.85 (gap 0.054). If both survive a second look, the list is sound.

Thresholds worth memorizing: π ≈ 3.142, π² ≈ 9.870, √2 ≈ 1.414, √3 ≈ 1.732, √5 ≈ 2.236, √10 ≈ 3.162. These anchors let you sanity-check any radical estimate in seconds.

Limitations: what decimal approximation cannot tell you

Decimal approximation is a tool, not a proof. A three-digit expansion can still misorder two numbers whose true difference is smaller than the displayed precision, which is why bracketing and exact fractions matter for close calls. For the values in this cluster, three decimals suffice because the tightest gap is about 0.023 — but a different problem with a gap of 0.0004 would demand six digits or an exact comparison.

Second limitation: this method assumes all values are real and positive. Negative terms reverse comparisons, and complex numbers have no ordering at all.

Third limitation: notation varies. The notation 5.444… may mean a repeating decimal or a truncated decimal, and the two are different numbers. Confirm the convention before sorting. Reconcile the thresholds explicitly: carry one extra digit past the required precision, then round once at the end, and never compare a rounded value to an unrounded one.

Fourth limitation: the list itself may be malformed — duplicated terms, missing commas, or an ambiguous radical scope such as √20 + 3 versus √(20 + 3). Resolve the grouping before doing any arithmetic, because a misplaced radical bar changes the value entirely.

The takeaway that separates a correct list from a plausible one is process, not intuition. Convert, bracket, sort, map back, and verify the count and the two closest pairs. Do that and the ordering holds up under any check.