From "what it cost" to "what it should cost"
Everything you have done in accounting so far has looked *backward*. A journal entry records what already happened; the income statement reports what a period actually earned and spent. Even the budgets in the earlier guides of this rung — the master budget and the flexible budget — are forward-looking, but they answer a *quantity* question: how many units, how much cash, how much total spending. A standard cost asks a sharper, more personal question about a single unit: not 'what did this one cost?' but 'what *should* this one have cost, if everything went the way it ought to?'
Think of it the way a recipe works. A recipe does not tell you what *last night's* loaf of bread cost; it tells you that one loaf *takes* 500 grams of flour and 12 minutes of kneading. That is a standard — a pre-set, per-unit expectation for both *how much* of an input a unit should consume and *what each bit of that input should cost*. Standard costs are simply recipes written in the language of money, and like any recipe they are most useful precisely when reality refuses to follow them. The gap between the recipe and last night's actual bake is where every lesson lives.
Notice already that a standard is built from *two* separate decisions, never one. There is a price standard (what a kilo of flour, or an hour of labor, *should* cost) and a quantity standard (how many kilos, or how many hours, a finished unit *should* use). Keeping these two apart is not pedantry — it is the seed of everything to come. When the actual cost later disappoints, you will want to know *which* half went wrong: did we overpay for inputs, or use too many of them? Two clean standards make that question answerable; one blurred number hides it.
The standard cost card: three rows, one number
When you set a price standard and a quantity standard for every input a product needs and lay them out on one page, you have built a standard cost card. It is the unit's full cost recipe on a single sheet, and it has exactly the three rows you already know from manufacturing costs: direct materials, direct labor, and manufacturing overhead. Each row multiplies a quantity standard by a price standard, and the three results add up to the standard cost of one finished unit — the single number that the rest of this guide leans on.
Let the café from the contribution-margin guide grow up into a small bakery that sells one product: an artisan loaf. Materials: a loaf *should* take 0.5 kg of flour, and flour *should* cost 2.00 per kg, so the materials row is 0.5 × 2.00 = 1.00. Labor: a loaf *should* take 0.2 hours of a baker's time, and that time *should* cost 15.00 per hour, so the labor row is 0.2 × 15.00 = 3.00. Overhead — the ovens, the rent, the electricity — does not attach to a loaf naturally, so it is applied using a predetermined overhead rate, here 10.00 per labor hour; at 0.2 hours per loaf that is 0.2 × 10.00 = 2.00. Add the rows: 1.00 + 3.00 + 2.00 = a standard cost of 6.00 per loaf.
STANDARD COST CARD -- one artisan loaf
quantity x price = standard cost
Direct materials 0.5 kg x 2.00 /kg = 1.00
Direct labor 0.2 hr x 15.00 /hr = 3.00
Mfg. overhead 0.2 hr x 10.00 /hr* = 2.00
--------
Standard cost per loaf 6.00
* overhead is APPLIED via a predetermined rate,
not traced -- it does not stick to a loaf on its ownIdeal or attainable? The honest tension in setting standards
Where do the numbers 0.5 kg and 0.2 hr actually come from? This is the part beginners skip and practitioners lose sleep over, because a standard is only as honest as the assumption beneath it. There are two philosophies. An ideal standard (sometimes called *perfection* or *theoretical*) assumes flawless conditions: no flour spilled, no dough wasted, no machine ever breaks, no baker ever pauses. A practical standard (also *attainable* or *currently attainable*) assumes a skilled person working efficiently *but human* — it bakes in the normal spillage, the unavoidable rest breaks, the routine oven maintenance that any real bakery lives with.
The choice has teeth, because the standard you pick quietly decides how people feel and behave. Ideal standards are almost never met, so the gap they produce is *always* unfavorable — and a number you can never hit stops being a goal and becomes background noise that workers learn to ignore. Practical standards are demanding but reachable, so missing one actually *means* something and prompts a real look. Most companies choose practical standards for exactly this reason: a yardstick is only useful if landing on the line is genuinely possible. The deeper truth is that a standard is as much a motivational instrument as a measurement one.
The card feeds the budgeted income statement
Here is where the single 6.00 number earns its keep. Recall from the master budget that the whole plan begins with a sales forecast — say the bakery expects to make and sell 1,000 loaves next month. Multiply that planned volume by the standard cost per loaf and you have an instant, defensible budgeted cost of goods sold: 1,000 × 6.00 = 6,000. There is no need to guess at total flour spending and total wages separately and hope they reconcile; the standard cost card has already done the per-unit work, and the budget simply scales it up.
Carry that up into the budgeted income statement. If each loaf sells for 10.00, budgeted revenue is 1,000 × 10.00 = 10,000, budgeted cost of goods sold is 6,000, and the budgeted gross profit falls out as 4,000 — all of it traceable back to two cards, the price the bakery charges and the cost the bakery should incur. This is the quiet power of standard costing: the same per-unit recipe that lets a manager reason about one loaf also lets the company assemble a whole forward-looking income statement before a single loaf is baked.
The yardstick that makes variances possible
All of this has been quietly building toward the next guide. Once a period ends, you can place the actual costs next to the standard ones and the difference is a variance — a measured gap between what should have happened and what did. The bakery planned 6,000 of cost for 1,000 loaves; suppose it actually spent 6,400. That 400 of extra cost is unfavorable, but the bare number tells you nothing about *why* — and 'why' is the only thing worth knowing.
This is why we split each row into a price standard and a quantity standard back at the start. That split lets you ask the 400 two questions instead of one. Did flour cost more per kilo than the 2.00 we assumed — a *price* problem? Or did we burn through more kilos per loaf than the 0.5 we planned, wasting dough — a *quantity* problem? Standard costing hands you the machinery to slice every variance into a price piece and a quantity piece, for materials, for labor, and for overhead, so a single disappointing total becomes a precise list of causes you can actually act on.
There is one honest caveat to carry forward. A meaningful comparison must hold *volume* constant — you cannot fairly judge the cost of 1,100 loaves against a budget built for 1,000. That is exactly the job of the flexible budget from the previous guide: it re-states the standard cost at the volume *actually* achieved, so that the variance you finally read reflects how well each loaf was made, not merely how many loaves were sold. Standard costs supply the per-unit yardstick; the flexible budget makes sure you are holding it against the right length of cloth.