Create an editorial rubric scoring tool in Claude

An editorial rubric scoring tool is useful when you need to review a draft against an explicit editorial scoring rubric. The result should make the underlying records easier to inspect and the next decision easier to explain. This guide develops a specific editorial rubric scoring tool with a source schema, operating rules, a fictional example, and observable review checks. It is intended for someone who already has the underlying material and needs a dependable way to organize it.

Product references checked: 7 October 2026. The examples and implementation specifications below are original editorial guidance. They illustrate expected behavior and have not been presented as a benchmark or as a completed tool tested inside another product.

Define the deliverable and its scope

Use reviewer-approved ratings to support editorial revision. The score does not establish factual accuracy or publication approval.

Write the acceptance standard before asking Claude for a draft. A reviewer should be able to identify the criterion id, inspect the score anchors, and understand the revision note without guessing what a blank field means. Decide which records belong in the deliverable, which are out of scope, and who can confirm the final interpretation. Keep those choices visible in the working specification rather than leaving the assistant to supply convenient defaults.

Prepare the source package

Gather an approved rubric, its weighting rules and a versioned draft. Assign source IDs and preserve original wording wherever a small difference could change the outcome. Record the collection date and the version of each source. If two files disagree, keep both references and mark the conflict. Do not replace a disputed value with whichever one produces the cleanest display.

Use a small representative subset for the first draft. Include one ordinary record, one incomplete record, and one record that challenges an important rule. For this task, use the following as the incomplete-record check: A missing rating leaves the total incomplete. Preserve the original package separately from the assistant's transformed output. A polished result is easier to audit when its IDs still lead back to the original supplied material.

Define the record schema

Treat criterion id as a deliberate part of the data model. Stable editorial criterion and rubric version. Keep its representation consistent when you sort, filter, or revise the output. The score anchors field has a different job: Written definitions for every allowable rating. Combining these fields into one sentence can hide the distinction the reviewer needs to inspect.

Pay particular attention to assigned rating and weight. The former means: Reviewer-entered rating tied to draft evidence. The latter means: Approved contribution to any combined score. Store them separately and label both in the detail view or report. This makes disagreements visible at the exact point where they affect the result instead of burying them in a general note at the bottom.

Apply the task rules

Rule 1. Do not invent weights or score anchors.

Rule 2. Missing ratings block a complete combined score.

Rule 3. A high total cannot override a separately required factual check.

Rule 4. Keep reviewer evidence separate from the assistant’s suggested rating.

Make these rules inspectable alongside the editorial rubric scoring tool. Ask Claude to describe how each rule affects a record and what should happen when the supplied data does not establish an answer. A rule written in prose still needs a defined output state. Use an explicit missing, disputed, or not-applicable label where appropriate, and reserve a valid zero or an empty result for cases where it has a defined meaning.

Work through a fictional example

A fictional rubric grades clarity and evidence on 0-to-4 scales, with weights 40 and 60 percent. A reviewer assigns clarity 3 and evidence 2, producing 3 times 0.4 plus 2 times 0.6, or 2.4 out of 4. The artifact shows both contributions. If the evidence rating is blank, it reports incomplete scoring instead of treating the blank as zero. A factual claim flagged for verification remains flagged even if other ratings improve. A later draft is scored as a new review version so its total is not compared with the old version without context.

Use the example as a review fixture rather than as real operational data. Before generating the output, write down which fields should be populated and which should remain unresolved. Then compare the generated result with that expectation. If Claude supplies an unsupported value, correct the underlying instruction or calculation rule instead of merely editing the one visible record. Otherwise, the same error may return when the next record is processed.

Build the first version

Ask for the simplest interactive artifact that displays the schema and supports the specific review task. Start with the fictional example and an obvious detail panel. Keep the source data separate from display labels and interaction state. A selected row, a filter, or an open panel should change what the reviewer sees, not silently rewrite the underlying evidence. Add editing only to fields that the specification explicitly identifies as user inputs.

For the first interaction pass, prioritize score breakdown: Per-criterion calculation and visible total or unavailable state. Then add the revision note behavior: Draft location and specific change suggested by the reviewer. Use visible text labels for both. Test the core logic before spending time on animation or visual polish. Provide a keyboard path through the controls and preserve a readable empty state when the selected view has no records.

A reusable prompt

Create a editorial rubric scoring tool from the supplied source package. Goal: review a draft against an explicit editorial scoring rubric. Use these fields: Criterion ID: Stable editorial criterion and rubric version.; Score anchors: Written definitions for every allowable rating.; Assigned rating: Reviewer-entered rating tied to draft evidence.; Weight: Approved contribution to any combined score.; Score breakdown: Per-criterion calculation and visible total or unavailable state.; Revision note: Draft location and specific change suggested by the reviewer.. Preserve source IDs. Rules: Do not invent weights or score anchors. Missing ratings block a complete combined score. A high total cannot override a separately required factual check. Keep reviewer evidence separate from the assistant’s suggested rating.. First explain the proposed data model and unresolved inputs. Then build the smallest usable version. Use only supplied facts; label the demonstration fictional. Do not invent approvals, thresholds, owners, or external integrations. Include an empty state and explain the expected result for these checks: A missing rating leaves the total incomplete. Weights must satisfy the approved total before scoring. A required factual flag remains visible regardless of the score.

Review behavior and edge cases

Check 1. A missing rating leaves the total incomplete. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 2. Weights must satisfy the approved total before scoring. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 3. A required factual flag remains visible regardless of the score. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Repeat the checks after adding another source record or changing the presentation. A working first example does not prove every record is handled correctly. Pay attention to retained selections, stale derived values, and unexplained changes in the number of displayed records. For editorial rubric scoring tool work, the reviewer must be able to tell whether a difference comes from new evidence, an edited rule, or merely a changed view.

Maintain the reviewed version

Keep a version label, source cutoff, and short change record with the finished editorial rubric scoring tool. Record who approved the rules and which demonstration cases were reviewed. When the source package changes, preserve record IDs and revisit the checks affected by the change. Do not treat yesterday's verified result as evidence that today's replacement input is complete.

Before handing the output to another person, review its audience and the material it contains. Use a sanitized demonstration for general feedback when the real source package is confidential. Explain whether changes are saved, whether the output is a preview, and which source remains authoritative. If persistence or sharing is required, verify that behavior in the actual account and intended environment instead of assuming it from a successful preview.

Frequently asked questions

Sources and related reading

Consult the current primary references for account-specific availability and controls: Current Claude artifact documentation, Claude sharing documentation. The schema, examples, prompts, and review checks here are editorial recommendations rather than documented built-in features.

For broader context, read the related Claude workflow guide.