Apply to my task
arXiv:2507.15157 ★ 83 Jul 20, 2025

A rubric in the prompt: the LLM evaluates texts at an expert level

Key result

Asking an LLM to "rate this text" is like asking a random passerby to rate your work. You'll get an opinion. Not much use. The study showed: add a codebook with criteria and examples to the prompt, and the LLM evaluates at the level of an experienced expert. The method lets you use an LLM as a consistent reviewer for any text: résumés, business emails, pitches, posts. The trick: the model doesn't guess your standards, it follows them if you've written them down. Add a rubric before the task, and the model stops guessing and starts following patterns. The result: ratings become predictable and comparable to expert ones.

CanLLMsGenerate User Stories and Assess Their Quality?

Key Aspects of the Study:

The researchers set out to learn whether LLMs can generate and, more importantly, assess the quality of a specific type of text ("user stories"). They found that LLMs evaluate almost at a human level, but only on one condition: the prompt must contain very clear, detailed instructions with criteria and examples, a so-called "codebook." They also found that LLMs generate less diverse and less creative texts than people, and are especially bad at explaining reasons and rationale ("why this is needed").

Key Result: Giving an LLM a detailed "codebook" with evaluation criteria and examples is the decisive factor in getting high-quality, reliable assessments comparable to human ones.


The Core Idea of the Method:

The method the study proves effective is about moving from simple, vague requests to structured prompts with explicit evaluation criteria. Instead of asking the LLM to "Evaluate this text," the user should act like a client handing over a clear spec for the evaluation.

This approach, called a "codebook-augmented prompt" in the paper, means in practice that an everyday user includes three key components in their request:

  1. Define the criteria: Spell out exactly which parameters the text should be judged on. For example: "Evaluate on these criteria: 1. Clarity, 2. Persuasiveness of the arguments, 3. Originality of the idea."
  2. Rating scale: Set a clear scale. For example: "Rate each criterion on a scale from 1 (poor) to 3 (excellent)."
  3. Calibration examples (the most important part): Give the model short examples of what you consider a good or bad result for each criterion. For example: "For 'Clarity,' a 3 means 'The text reads in one breath,' and a 1 means 'You have to reread a sentence twice to get it.'"

This method turns the LLM from a subjective "opinion" into an objective evaluation tool that works by your rules. The study also highlights an important trait: LLMs are great at evaluating structure and form (LC, IC) but struggle to evaluate depth of meaning and rationale (RC). That means when writing the prompt, you need to put special emphasis on explaining the "why," or not expect the model to deeply understand hidden motives.


Practical Applicability Analysis:

  • Direct applicability: Users can immediately apply this approach to any task that involves critique, evaluation or generating text to a template. For example, you can give the LLM your own "codebook" for evaluating business emails, blog posts, résumés or even startup ideas. The method is implemented by simply adding structured text to a regular prompt.

  • Conceptual value: The study gives the user two key concepts:

    1. The LLM as an "evaluator by instruction": To get a quality assessment from the model, you first have to teach it your standards by providing a clear set of rules and examples. The LLM doesn't guess your expectations; it follows instructions.
    2. Knowing the "blind spots": Models see the "what" (structure, grammar) very well but poorly understand the "why" (rationale, purpose). Knowing this, the user can either avoid demanding the impossible from the LLM or deliberately reinforce the prompt with an emphasis on explaining purpose and logic.
  • Adaptation potential: The adaptation mechanism couldn't be simpler. For any task, mentally break the idea of a "good result" into its components (criteria). Then for each criterion, describe what "good" and "bad" look like, and package it in the prompt as a list of rules and examples before the main task. This framework works for any domain.


Practical Example:

# ROLE
You are an experienced editor at the popular food blog "Taste of Life." Your audience is cooking beginners looking for simple, easy-to-follow recipes.

# TASK
Rate the draft recipe submitted by an author on a 3-point scale according to my "Editor's Codebook." Your goal is to give the author constructive feedback to improve the text.

# EDITOR'S CODEBOOK

**1. Beginner-Friendliness (BF):**
*   **3 (Excellent):** All steps are described simply, with no complicated jargon. Anyone cooking for the first time will understand what to do. Example: "Finely chop the onion" instead of "Sweat the shallots."
*   **2 (Acceptable):** Mostly clear, but there are 1-2 terms that could confuse a beginner (for example, "blanch").
*   **1 (Poor):** The recipe is written for professionals, with lots of complex terms and techniques and no explanation.

**2. Practical Value (PV):**
*   **3 (Excellent):** Exact measurements and cooking times are given, plus useful tips (for example, "if you don't have parchment paper, grease the baking sheet with butter").
*   **2 (Acceptable):** The basic data is there, but useful details and alternatives are missing.
*   **1 (Poor):** Measurements are "eyeball it," no times given, no tips.

**3. Engaging Style (ES):**
*   **3 (Excellent):** The text is lively, makes you hungry, and includes a short backstory or an interesting fact about the dish. Example: "This recipe was handed down to me by my grandmother, and its aroma instantly takes me back to childhood."
*   **2 (Acceptable):** The style is dry but functional. Just a list of steps.
*   **1 (Poor):** The text is boring and written in bureaucratic language.

# TEXT TO EVALUATE
"Take flour, eggs, sugar. Mix the ingredients until smooth. Bake in the oven. Serve."

# RESPONSE FORMAT
Give a rating for each criterion (BF, PV, ES) and a short but clear justification for each one explaining why it received that score.

Why It Works:

This prompt is effective because it leaves the LLM no room for guesswork or subjectivity. It works thanks to the following mechanics described in the study:

  1. Clear criteria (BF, PV, ES): The model doesn't have to invent what a "good recipe" means on its own. It's given three specific axes of analysis: clarity, practicality and style.
  2. A defined scale (1 to 3): This standardizes the evaluation and makes it measurable.
  3. Concrete examples (Example: ...): This is the most important part. Examples "calibrate" the model by showing it in practice what the user means by "excellent" or "poor." The model learns from these examples and applies the pattern to a new text.
  4. A set role and context: Specifying the role ("food blog editor") and audience ("beginners") helps the model better understand the overall goal and tone of the evaluation.

Instead of an abstract "make this recipe better," we hand the model a precise tool (a rubric) it can use to carry out a detailed, useful analysis.


Another Practical Example

# ROLE
You are an HR specialist who helps job seekers improve their cover letters. Your job is to give honest but motivating feedback.

# TASK
Rate a cover letter for a "Marketing Specialist" position on a 3-point scale, using my "Cover Letter Codebook."

# COVER LETTER CODEBOOK

**1. Personalization and Targeting (PT):**
*   **3 (Excellent):** The letter is addressed to a specific company, mentions the position, and shows the candidate has researched the employer. Example: "I was especially inspired by your recent 'X' campaign, and I'm confident my experience in 'Y' can help build on it."
*   **2 (Acceptable):** The company and position are mentioned, but without deep personalization.
*   **1 (Poor):** A template letter that could be sent to any company.

**2. Relevant Experience Shown (RE):**
*   **3 (Excellent):** The candidate doesn't just list duties but gives 1-2 specific achievements with numbers that tie directly to the job requirements. Example: "At my last job, I grew social media reach by 40% in 6 months."
*   **2 (Acceptable):** Experience is described, but without specific numbers or achievements.
*   **1 (Poor):** Experience is irrelevant or described too vaguely ("did marketing").

**3. Call to Action (CA):**
*   **3 (Excellent):** The letter ends with a polite, confident call to the next step. Example: "I'd be glad to discuss in an interview how my skills could benefit your team."
*   **2 (Acceptable):** There's a hint of wanting to continue the conversation, but it's vague.
*   **1 (Poor):** The letter just stops without a logical ending.

# TEXT TO EVALUATE
"Hello. Saw your marketing job posting. I have a lot of marketing experience, I'm responsible and a good communicator. Ready to work. Thanks."

# RESPONSE FORMAT
Output a table with three columns: "Criterion," "Score (1-3)," "Comment for improvement."

Why This Example Works.

This example runs on the same fundamental principle as the previous one, the one proven in the study: turning a subjective task into a structured analysis.

  1. Making an abstraction concrete: "A good cover letter" is an abstract idea. The prompt breaks it into three measurable components: personalization (PT), relevance of experience (RE) and closing (CA). This gives the model a clear structure for its analysis.
  2. Calibration through examples: The examples for each score on each criterion act as a "training set" for the LLM. The model sees the pattern "template letter = 1 point" and "letter with numbers and facts = 3 points." Given a new text, it looks for these patterns and bases its verdict on them.
  3. Reducing the LLM's cognitive load: Without a "codebook," the model would have to "guess" what matters in a cover letter based on its general knowledge. That could lead to generic, useless advice. The "codebook" focuses the model's attention on the aspects that matter to the user and makes it give specific, useful feedback on each one.

Usefulness Score: 88

02

Main Evaluation Criteria

  • A. Relevance to prompting techniques: Yes, the study directly demonstrates the effectiveness of a "codebook-augmented prompt," a prompt reinforced with detailed instructions, criteria and examples. It's a fundamental technique for structuring requests.
  • B. Better conversational answers: Significantly. The method lets you get not just an answer from the LLM but a structured, well-argued assessment that meets the standards the user set.
  • C. Direct practical applicability: Absolutely. The "codebook" method needs no code or special tools. Any user can apply it right away in an LLM chat for evaluation, critique or template-based generation tasks.
  • D. Conceptual value: Very high. The study clearly proves that an LLM isn't a "conversation partner" but an "instruction follower." The more detailed and structured the instruction (prompt), the more accurate and reliable the result. It also exposes a key LLM weakness, the inability to formulate rationale on its own (Rationale Clarity), which is critical for users to know.
  • E. New useful practice (clustering): The paper falls into several clusters at once:
    • #1 (Phrasing techniques): A direct description of a technique for structuring instructions.
    • #2 (Behavioral patterns): Identifies a weakness in generating "Rationale Clarity" and low "diversity" compared to humans.
    • #3 (Structure optimization): Shows how adding a structured "codebook" to the prompt improves results.
    • #7 (Reliability and stability): The method directly improves the reliability and consistency of the LLM's assessments.
  • Practicality checklist (+15 points): Yes, the study provides ready-made constructions (the "codebook" idea), shows how to structure complex evaluation requests and reveals non-obvious LLM behavior (weakness on the "why" and low creativity).
03

Numeric Usefulness Score

The score of 88 is given because the study presents and proves the effectiveness of a universal, powerful prompting method that any user can apply immediately to a wide range of tasks involving evaluation, critique and content generation to set standards.

Arguments for the score: * Universality of the method: The "codebook" idea applies not only to User Stories but also to evaluating essays, marketing copy, business plans, résumés, customer support replies and more. * Direct action: Users can start writing prompts the new way right away and see improvement. It's not theoretical knowledge but a practical guide. * An important conceptual idea: The study clearly demonstrates a fundamental principle: to get quality output from an LLM, you have to clearly define what "quality" means for your task. * Exposing LLM weaknesses: The finding that models struggle with "Rationale Clarity" is a critical insight for any user. It helps you see where the prompt needs extra tuning, or where not to expect too much from the model.

Counterarguments (why the score could be lower/higher): * Why not 90+? The study doesn't offer a single "magic phrase" (like "Think step by step"); it describes a methodology that takes some effort from the user to write criteria and examples. It's more of a powerful framework than an instant trick. * Why not below 70? Despite the narrow academic topic (User Stories in software development), the main finding about the power of structured instructions and examples in a prompt is completely universal and fundamental to prompt engineering. Its practical value for everyday users is huge.


Research digest

Key result

Asking an LLM to "rate this text" is like asking a random passerby to rate your work. You'll get an opinion. Not much use. The study showed: add a codebook with criteria and examples to the prompt, and the LLM evaluates at the level of an experienced expert. The method lets you use an LLM as a consistent reviewer for any text: résumés, business emails, pitches, posts. The trick: the model doesn't guess your standards, it follows them if you've written them down. Add a rubric before the task, and the model stops guessing and starts following patterns. The result: ratings become predictable and comparable to expert ones.

Principle

A typical request: "rate this email." The LLM gives a general opinion, sometimes useful, more often about nothing. A rubric changes that. Break the idea of a "good text" into 2-4 specific parameters. For each one, set a scale (three points is enough) and, most importantly, examples: what exactly counts as "3 points" and what counts as "1 point." Examples are calibration. Without them, the model leans on averaged notions from training. With them, it sees your pattern and applies it to the new text. This turns the LLM from a "random opinion" into a tool that works by your rules.

Why it works

An LLM doesn't have your quality standards; it doesn't know what matters to you. Without examples, the model generates an averaged rating based on everything it saw in training. Examples give it a specific pattern: "this is worth three points, this is worth one." Given a new text, the model looks for those patterns. A fundamental blind spot: the model rates form and structure well but poorly understands the "why": motivation, rationale, hidden logic. If you need to evaluate the depth of arguments, emphasize the purpose explanation in the prompt. Or simply don't expect the model to do what it can't.

When to apply

Tasks that need consistent, repeatable text evaluation: reviewing résumés and cover letters, breaking down pitches and business proposals, feedback on blog posts, grading student work. Especially useful when you need to rate many similar texts the same way: the rubric makes the LLM consistent where, without it, it puts the emphasis somewhere different every time. NOT a fit for evaluating hidden motivation, non-obvious causes and deep rationale, which is the model's blind spot.

Mini recipe

1. Split "a good result" into parts: not "a good email" but specific parameters: clarity, specificity, call to action. 2-4 criteria are enough. 2. Set a scale: three points is optimal. 1 = poor, 2 = acceptable, 3 = excellent. More gradations and the model starts to drift. 3. Add examples (the main thing): for each criterion, write one line for 3 points and one for 1 point. That's the calibration; without it the rubric loses half its power. 4. Give a role and context: say who the LLM is ("you are an editor at a business publication") and who it's for ("the audience is small business owners"). This focuses the evaluation. 5. Set the output format: ask for a table with "criterion / score / what to improve" columns and you'll get a clean, readable result instead of a wall of text.

Examples

[BAD]: `Rate this cover letter and tell me what needs improving` [GOOD]: `You are an HR specialist who helps job seekers. Rate the cover letter on three criteria, scale 1-3. Criterion 1, Personalization: 3 points = the candidate mentioned a specific company project and explained why it matters; 1 point = a template letter without the company's name. Criterion 2, Specific achievements: 3 points = there are numbers ("grew reach by 40% in six months"); 1 point = "did marketing." Criterion 3, Closing: 3 points = a clear proposal to meet; 1 point = the letter just stops with no logical ending. Format: a table "criterion / score / what specifically to improve." Letter: [letter text]`

In plain words

Here's the deal: LLMs no longer just generate text, they act as strict quality inspectors. The study shows that if you give a model a clear scale and a role, it rates content as well as a human expert. The whole secret is in breaking down the criteria: we don't ask the model to "make it nice," we make it check the text against specific "checkboxes," like beginner-friendliness or exact measurements. That turns a subjective opinion into a structured audit, where every point is backed by logic, not hallucinations.

It's like hiring a head chef to grade homework at a culinary school, but instead of "tasty/not tasty" you give them a strict rulebook. Technically, everything might be edible, but if the recipe says "fry until done" instead of "7 minutes over medium heat," the chef slaps on a 1 for lack of specifics. The model works like that picky chef: it spots gaps in the data that a regular person might miss out of carelessness.

In the example above, three methods worked perfectly: role-play (you are an experienced editor), scaling (a 3-point system instead of "good/bad") and few-shot examples built into the rules. When we write in the prompt "Finely chop the onion" instead of "Sweat the shallots", we give the model a reference point. So a score of 1 out of 3 for practical value isn't nitpicking; it's because the text really has no numbers. The model simply matches the instructions against reality and delivers an objective verdict.

The study was done on user stories and recipes, but this principle is universal. You can build it into any business process: from reviewing legal contracts to grading support replies. If you have a codebook, the model turns into a tireless inspector that finds the flaws in a thousand documents in seconds. The human factor drops out, and all that's left is a clean check against the standards.

Bottom line: stop asking the model to "evaluate the text". That road leads nowhere. Give it a role, a scale and examples, and turn it into a professional auditor. A structured prompt is a filter that strains out the junk and leaves only quality content. Whoever learns to "train" models like this will save hundreds of hours on editing and report reviews, while everyone else keeps grinding through edits by hand.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on A rubric in the prompt: the LLM evaluates texts at an expert level arXiv:2507.15157

Sign in to apply this study New accounts get 50 free credits.

Get the week’s best papers by email

One email on Sundays with the highest-rated new techniques. Unsubscribe with one click.