Why Round Numbers in an Estimate Are Suspicious

Ten per cent is a straight-lay number wearing a general label

A 10% tile waste baseline is round because it was set as a defensible starting point for the single most common case — a straight lay in a roughly rectangular room — not because cut loss on a real floor naturally clusters at exactly 10.0%. The step up to roughly 15% for a diagonal layout and roughly 20% for herringbone is also round, for the same reason: these are conventions chosen to be memorable and safely on the high side of typical, not figures measured off a specific floor.

The tile calculator still uses those round conventions, because most visitors know their layout pattern but not their room's exact perimeter-to-area ratio or whether the tile has a repeat to match. Where those extra details are known, the waste factor calculator computes a room-specific figure from five separate inputs instead of asserting one flat number — the output is deliberately not round, because it's built rather than chosen.

Four inches of gravel is a compromise depth, not a measured one

A 4 in gravel base sits between what a lightly loaded footpath could get away with and what a vehicle-bearing driveway actually needs, which commonly runs 6 to 8 in or more in a compacted, layered sub-base. Four inches is round because it was picked as a workable default for the calculator's most common visitor — someone building a walkway or patio base — not because 4 in is where gravel compaction physics settles for every project.

It stops being the right number the moment the project is actually a driveway rather than a path, or the site sits somewhere with a frost depth that exceeds it, both of which call for a deeper, engineered base rather than the walkway default. The gravel & stone calculator and gravel cubic yards by project type both let that depth be changed rather than fixing it, which is the entire point of publishing it as an editable default instead of a constant.

Two coats is a rule about hiding, not a rule about paint

Two coats became the default answer to 'how many coats' because it's the smallest number that reliably hides a moderate color change given how opaque typical wall paint actually is — not because paint chemistry has a two-coat constant built into it. A same-color repaint on a sound existing coat can genuinely need only one; a dark-to-light change routinely needs a primer plus two finish coats, sometimes three, because pigment opacity and the size of the color shift are the actual variables and neither one is fixed at 'moderate' by default.

How many coats of paint do you really need goes through those decision factors directly; this page's point is narrower — that 'two' is a convention chosen to be safe for an unknown, average case, and the paint calculator multiplies whatever coat count you actually enter rather than assuming everyone's case is average. Paint sheen: what it changes besides the look covers a second variable, sheen, that shifts real coverage the same way coat count does.

Why a calculator picks a round number in the first place

A calculator has to return an answer for every visitor, and most visitors won't or can't supply the extra variable — subgrade soil type, the exact size of a color change, a room's precise perimeter-to-area ratio — that would let a tool return a genuinely case-specific figure instead of a convention. A round default is what keeps a page usable without demanding five extra fields before it will show anything at all. That's a legitimate design tradeoff, not a defect being hidden — but it means the roundness is evidence of 'a reasonable convention chosen under real uncertainty,' not evidence of 'correct for your project specifically.'

Not every round number on this site is a convention

• 27 cubic feet per cubic yard and 12 inches per foot are exact unit definitions, not chosen figures — there's no edge where they stop being right, because they're true by definition rather than by convention.
• A tile pattern's waste baseline, a gravel base depth and a paint coat count are all chosen conventions, and each one is stated on its calculator page as a starting figure you can change once you know more about your specific project.
• A worked example's result, by contrast, is neither a convention nor a definition — it's a computed figure from real inputs, which is why this site's worked examples are run through the live calculator rather than typed in by hand.