The straightforward way people miss until they mess up a recipe or split an invoice
Multiplying a fraction by a whole number is one of those things everyone learns in fifth grade and then promptly forgets because nobody uses it daily. The procedure is mechanically simple but the edge cases where people lose confidence are real. I ran into this last year when I was reconciling a batch of supplier invoices that had pricing listed in fractional weights—thirds and sevenths of a pound—and someone had multiplied them incorrectly across forty line items. It took me twenty minutes to spot the pattern of errors and another ten to walk the junior accountant through the fix. Write the whole number as a fraction over 1. Multiply the numerators together. Multiply the denominators together. Simplify if needed. That is literally the entire algorithm. When I say write the whole number over 1, I mean treat 5 as 5/1, not as some separate entity that needs a different rule. The rule is the same. The reason this works is that any whole number is already a rational number, just one with denominator 1. Once you see that, the multiplication of two fractions applies uniformly. You are not learning a new operation. You are applying the same fraction multiplication rule with one of the fractions disguised as a whole number.
Let me walk through a concrete case. Take 3/4 times 5. Rewrite 5 as 5/1. Multiply numerators: 3 times 5 is 15. Multiply denominators: 4 times 1 is 4. The result is 15/4. As a mixed number that is 3 and 3/4. If the problem is 2/7 times 6, you get 12/7, which simplifies to 1 and 5/7. You can convert to a decimal at the end if the context requires it, but keeping it as a fraction longer usually prevents rounding errors from stacking up. Here is where people routinely trip. They forget to multiply the denominator. They only multiply the numerator by the whole number and leave the original denominator untouched. That is wrong every time. Another common slip is multiplying the whole number by the denominator instead of the numerator. The direction matters, and mixing it up gives you 4/15 instead of 15/4 in the first example, which is not a small mistake in most real work. Cross-canceling before you multiply is the trick most beginners skip and most professionals use. Take 6/9 times 3. If you multiply straight through you get 18/27, then simplify to 2/3. If you reduce 6/9 to 2/3 first, then multiply by 3, you get 6/3, which is 2. Same answer, fewer arithmetic steps. The cross-cancel approach means you divide any numerator and any denominator by a common factor before doing the multiplication. In 6/9 times 3/1, 6 and 3 share a factor of 3, and 6 and 9 share a factor of 3. Reduce first, then multiply. This usually cuts calculation time in half for anything beyond trivial numbers, and it prevents the intermediate fractions from ballooning into unwieldy values.
I encountered a genuinely messy case recently involving 7/13 multiplied by a large integer in a materials budget. The integer was 312. Multiplying straight through gives 2184/13, which is exact but ugly to work with. Recognizing that 312 is divisible by 13, I divided 312 by 13 first to get 24, then multiplied 7 times 24 for 168. That took about twelve seconds instead of the fifteen minutes it would have taken to perform long division on 2184 over 13 by hand. This kind of pre-simplification is what separates people who do this quickly from people who brute force it. Improper fractions are not a problem. They are the normal state after you multiply. 15/4 is an improper fraction and it is correct. Convert to a mixed number only when the application demands it, like when you are reading a measurement on a tape or presenting to someone who thinks in mixed numbers. In technical work, improper fractions are often preferable because they avoid the extra step of division and keep everything in a form that composes cleanly with further operations. One thing worth noting that nobody emphasizes enough: when the whole number is zero, the result is zero regardless of the fraction. When the whole number is negative, apply the sign to the numerator, not the denominator, to keep things tidy. Multiplying -3 by 2/5 gives -6/5, not 6/-5. The value is the same, but the convention matters for grading and for keeping subsequent algebra clean.
Get the Full Details
There are real limitations to just following the mechanical procedure. If you are working with repeating decimals and the problem originally came from a decimal approximation of a fraction, converting back to fractions and then multiplying can actually reduce accuracy compared to staying in decimals, depending on your tolerance. I once saw a structural engineering check fail because someone converted 0.333 back to 1/3 and then multiplied through, introducing a small systematic error that compounded across dozens of beams. Sometimes you just have to stay in decimals and round at the end. If you want a quick reference, the rule fits on one line: a/b times c equals ac/b. Anything more elaborate than that is just padding. The rest is practice and pattern recognition so you stop second-guessing yourself on simple problems and can focus on the cases where precision actually matters.
