{"id":"cs-success-plan-actual-vs-target-status","audience":"managers","category":"support-work","technique":"verification","track":"support","level":"intermediate","title":"Grade five success-plan goals against target with percent rules","free":false,"task":"Grade the five goals with a table whose header row is exactly \"Goal | Target | Actual | Status\" and five rows in the given order. Status is Met at 100% of target or more, On track from 80% to 99%, Behind below 80% (edges inclusive at the lower end). Work out the percent yourself. Plain text, table only, under 60 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"SUCCESS PLAN REVIEW, Calder Group (target vs actual, all measures where higher is better)\nWeekly active users: target 100, actual 112.\nStaff trained: target 80, actual 68.\nReports built per month: target 400, actual 300.\nTeams onboarded: target 10, actual 8.\nIntegrations live: target 4, actual 4.\n\nStatus rules: percent of target = actual / target x 100. Met = 100% or more. On track = 80% to 99%. Behind = below 80%.\nHelp: 112/100 = 112%. 68/80 = 85%. 300/400 = 75%. 8/10 = 80%. 4/4 = 100%.\nCSM comment: 'Teams onboarded at 80% feels Behind.' (80% is On track.)","rules":[{"type":"plainText"},{"type":"maxWords","max":60}],"mistakes":[{"title":"Calling 80% Behind","why":"The CSM comment says it feels Behind.","fix":"Say: \"80% is On track: the lower edge is inclusive.\"","checks":["r1"]},{"title":"Wrong percents","why":"The AI eyeballs the ratios.","fix":"Say: \"Percent = actual / target x 100.\"","checks":["r1"]},{"title":"Wrong table","why":"The AI adds a percent column or notes.","fix":"Give the exact header; table only.","checks":["r0","r2"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"States the rules","patterns":["80%","100%","lower end|inclusive"]},{"label":"Gives the header","patterns":["goal \\|","header"]}],"hint":"Status grading depends on thresholds and edges. State them with the formula and the exact header.","rubricLabels":["The header row is exactly \"Goal | Target | Actual | Status\" with five rows in the given order and nothing outside the table","Statuses are Weekly active users Met, Staff trained On track, Reports built Behind, Teams onboarded On track, Integrations live Met","Targets and actuals match the notes (100/112, 80/68, 400/300, 10/8, 4/4)"]}