Quality Rubrics for Business Output

"Is this good?" is an unanswerable question until you have decided what good means. A rubric is a short, explicit list of the qualities an output must have. Business professionals already use rubrics informally (a good status report is short, honest and ends with asks), and writing them down does two things: it makes your own evaluation consistent, and it gives Claude a target to aim at and to check itself against.

The six dimensions that cover most business output

Most rubrics for workplace documents draw on the same handful of dimensions. You will rarely need all six; pick the three or four that matter for the task.

Dimension	Question	Typical failure
Accuracy	Are the facts, figures and names correct?	Hallucinated detail, stale information
Completeness	Is everything the reader needs present?	Missing section, unanswered question
Relevance	Is anything present that the reader does not need?	Padding, tangents, generic advice
Clarity	Can the reader understand it on first reading?	Jargon, long sentences, buried lead
Fitness for audience	Does tone and depth suit the reader?	Too casual for a board, too technical for customers
Actionability	Does the reader know what to do next?	No decision requested, no owner, no date

Accuracy is always in the rubric; it is non-negotiable. The others vary. A brainstorm list can be low on clarity and still be useful; a customer apology cannot.

Writing a rubric in under a minute

A usable rubric is three to five lines, each testable. Compare these two.

Weak: "The report should be high quality and professional."

Usable:

• Every figure matches the attached spreadsheet.
• Opens with a two-sentence summary a director could read alone.
• Each risk has an owner and a mitigation.
• No more than two pages.
• No internal project codenames.

Each line can be answered yes or no. That is the test of a good rubric criterion.

Putting the rubric in the prompt

Once written, the rubric belongs in the prompt itself. It is the most efficient form of constraint because it tells Claude the standard rather than listing individual dos and don'ts.

Draft the monthly steering report from the notes below. It must meet
these criteria:
1. Every figure matches the attached sheet; do not round.
2. Starts with a two-sentence summary.
3. Each risk has an owner and a mitigation.
4. Under 600 words.
5. No project codenames; use product names.
After the draft, add a short section headed "Self-check" stating
whether each criterion is met, and if not, why.

The self-check instruction is the key move. Claude is good at evaluating text against explicit criteria, including its own output. It will often catch its own omissions ("Criterion 3: the supply-chain risk has no owner because the notes did not name one"), which is far more useful than a silent gap.

Using the rubric to evaluate

When the output arrives, score it against the rubric before you read it for style. Discipline here prevents the common trap of being charmed by fluent prose and missing a factual hole. A practical routine:

1. Read the self-check. Treat each "not met" as a to-do.
2. Check accuracy items yourself against the source (never trust the self-check for accuracy; Claude cannot verify facts it was never given).
3. Confirm completeness against your original list of required content.
4. Only then read for tone and clarity.

If an output fails two or more criteria, the brief probably lacked something; revisit it rather than patching the output.

Rubrics as team assets

A rubric written once can be reused. Store the rubric for recurring documents (board papers, customer updates, incident reports) in a Project's instructions or a Skill so every draft starts against the same standard. This is how individual good judgement becomes a team-wide quality floor, and it is a theme the exam returns to in Domains 4 and 5.

Scenario: the vendor comparison

A procurement lead asks Claude to compare three vendor proposals. Without a rubric, Claude produces a balanced but general essay. With a rubric (covers all five mandatory requirements, states each vendor's price on a like-for-like basis, flags any requirement a vendor did not address, ends with a recommendation and the two main risks of that recommendation), the output is a table plus a short recommendation, and the self-check reveals that one vendor's proposal never mentioned data residency. That gap becomes the first clarification question to the vendor. The rubric did not just improve the document; it surfaced a real procurement issue.

Exam focus

• A rubric is a short list of testable criteria defining what good means for a specific output; accuracy is always included.
• Including the rubric in the prompt and asking for a self-check lets Claude flag its own omissions.
• The self-check is reliable for structure and completeness but cannot verify facts Claude was never given; accuracy checks remain yours.
• Evaluate against the rubric before reading for style, to avoid being swayed by fluent prose.
• Rubrics for recurring documents belong in Project instructions or Skills so the standard is applied consistently across a team.