How to Assess a Student Business Project Fairly

A student business unit is one of the best things you can run in a classroom, and one of the hardest to mark. The work happens in groups. Half of it is talking. Some of the businesses will not work, and a few of the ones that do will work for reasons that have nothing to do with the student. By report card time you can be looking at a pile of flyers and tally sheets and wondering what, exactly, you are grading.

This post is about that problem. If you want the timeline for a unit that ends at a December market, the fall term plan covers it week by week. This one covers what to assess, how to mark individuals inside groups, and how to keep marks and feedback private when money is involved.

Mark the thinking, not the profit

The single most useful decision is to stop treating the result as the grade.

A student who sold out because their aunt bought half the stock has not shown you more than one who sold four items, worked out why, and changed the price for next time. Profit depends on who walked past the table. Reasoning does not.

So assess the things a student controls:

• The problem. Is it specific, and is there evidence that someone other than the student has it?
• The customer. Can they describe who would buy this, and why?
• The numbers. Are costs identified, is the price reasoned, and does the student use the numbers to make a decision?
• The change. When something did not work, did they notice and adjust?
• The reflection. Can they say what they learned, with reference to what actually happened?

A business that failed can score well on every one of those. That is not a loophole. It is the point. The unit is teaching a way of working, and a business that did not sell is often where that way of working shows most clearly.

Decide what you will assess before the unit starts

Entrepreneurship feels enormous if you try to mark everything. Pick a small set of pieces before the first lesson and write them down. A blueprint like this is enough:

• Planning work: an idea sheet or problem statement, a one-page plan, and a budget with a price.
• Execution work: the market day or pitch, plus evidence of iteration, such as a revised plan or an adjusted price.
• Reflection: a written or recorded reflection, and a short self-assessment on teamwork.

Then, if you report against provincial expectations, map each piece to them. Budgeting sits naturally under financial literacy, a pitch under oral communication, and market data under numeracy. That reading is yours to do. We have not published a mapping between Hatchable and any provincial curriculum document, and we would rather say so than imply one.

Four rubrics cover most of it

You do not need a new rubric for every task. Four reusable ones handle almost everything, and students get better at reading them each time they see one.

Keep the levels few and the descriptors plain. Then hand each rubric out when you launch the task, not when you mark it. Students can use it as a checklist while they draft, and it removes most "but I did the work" conversations before they start.

For younger students, cut each rubric down to fewer criteria and walk through it together. For older students, add a self-assessment column and have them rate themselves before you do. The gap between the two is often the most useful conversation of the unit.

Mark individuals inside groups

Groups are where marking gets unfair, in both directions. Two habits fix most of it.

Roles and a weekly log. At the start, each group assigns roles, for example a lead, a numbers person, someone on marketing and someone on production. They write the roles on a short group contract and everyone signs it. Then, at a few checkpoints, each student writes one or two sentences about what they personally did that week. When an individual mark has to differ from the group's, the log is your evidence.

A split you announce in advance. Decide before the unit how much of the grade comes from group outcomes, such as the booth or the pitch, and how much from individual pieces, such as reflections, short quizzes and solo tasks. Tell students on the first day. A student in a weak group should know their own work still counts, and a student in a strong one should know they cannot coast.

Track progress with a grid, not an app

You need to see, at a glance, where every student is. A simple grid does it, in your gradebook, your board's learning platform, or on paper:

• One row per student.
• A column for each checkpoint: idea sheet in, plan reviewed, budget checked, market day or pitch done, reflection in.
• A column for the rubric level on each major piece.
• A short notes column, for things like "needed help with the budget".

Update it at the end of any class where a checkpoint happened. A tick is enough. The grid's real job is to catch the quiet student who is present every day and not moving.

Give students the same list from their side: a one-page checklist of every task with a target date and a space to record when they handed it in. Between your grid and their checklist, keeping up becomes a shared job rather than yours.

Keep marks and feedback private

Money makes it tempting to rank. Resist it.

• No profit leaderboards. Do not announce which group made the most, with or without numbers. Talk about patterns instead: which pricing choices worked, which displays drew people in.
• Spread recognition around. If you give awards, give them for different things, so it is not the same students every time.
• Feedback goes to the student, not the stream. Use private comments in a board-approved tool, or paper. Never a shared chat or a class-wide post.
• Rubric plus one note. For each major task, return the rubric with one clear strength and one clear next step. Short and specific gets read.
• Ask a question back. After a reflection, reply with a prompt they have to answer: "You said pricing was hard. What would you try next time, and why?"
• Aim panel comments at the idea. If guests judge pitches, brief them to comment on the plan, not the person, and not to compare students.

The same care applies to the work itself. Keep portfolios visible to the student and you, or to the class if your policy allows it. Use first names or business names on signage, not last names. Photograph products and posters, not faces, and follow your board's media consent rules if any photo might leave the room. Keep recordings off public platforms. If you want to keep good work as a model for next year, save a copy with the identifying details removed.

Where Hatchable fits

Hatchable is built around the same structure. Modules 1 to 8 are published at /learn, and the assignments in them follow the order this post assumes: finding and checking a problem, a Lean Canvas plan, costs and pricing, and a final presentation.

With a teacher account, your class roster shows which lesson each student finished and when, which does the job of the progress grid. Students hand in written answers, files or links. Hand-ins are not posted anywhere public, and when you leave feedback the student gets an email telling them to look. Every module has a teacher guide, most of them include notes on what a strong submission looks like, and the Module 8 guide includes a rubric for the final project. If you run a pitch night through the platform, nothing a student enters appears until you approve it.

For Teachers covers the classroom side in more detail, and the Hatchable Loop post explains how a class moves from an idea to a sale.