Turn Work Logs into Self-Evaluation Metrics

Convert your raw work notes into quantifiable achievement statements.

Prompt · 3 variables

You are an experienced evaluator reviewing and scoring self-assessments for a {{job position role}}. You strictly differentiate between statements of what was done versus statements of measurable impact.

I am preparing my self-evaluation for {{evaluation time period}}. Below is an unfiltered list of tasks I completed during this period—currently just a raw task list rather than structured achievement statements. The reader will be a higher-level manager who does not observe my day-to-day work directly.

For each item in my log, please fill in three elements: ① What I did, ② The resulting impact or change (for the team, company, or customer), and ③ Concrete metrics or evidence proving that change. If specific data is missing from my notes, do not fabricate numbers; instead, mark it as [Check Metric] and provide a one-line tip on where I can find that data.

Output the result as a markdown table. The columns must be: Task Completed | Impact / Change | Evidence (Metrics/Data) | Self-Evaluation Draft (2 sentences max). Below the table, provide a 3-bullet executive summary grouping these accomplishments, plus a 2-sentence draft suggestion on how to professionally address underperformed goals.

After drafting the table, perform a self-audit: verify whether the "Impact / Change" directly resulted from my specific actions and ensure no placeholder numbers were invented. Correct any discrepancies before displaying the final output.

Work Record: """ {{work record}} """

Copy, then paste here · ChatGPT and Claude open with the prompt filled in Open in ChatGPT ↗Open in Claude ↗Open in Gemini ↗ Edit in builder Download classroom card

Some variables here may contain personal data. Replace real names, numbers and company names with placeholders.

Why it is written this way

Role
You are an experienced evaluator reviewing and scoring self-assessments for a {{job position role}}. You strictly differentiate between statements of what was done versus statements of measurable impact.
Context
I am preparing my self-evaluation for {{evaluation time period}}. Below is an unfiltered list of tasks I completed during this period—currently just a raw task list rather than structured achievement statements. The reader will be a higher-level manager who does not observe my day-to-day work directly.
Task
For each item in my log, please fill in three elements: ① What I did, ② The resulting impact or change (for the team, company, or customer), and ③ Concrete metrics or evidence proving that change. If specific data is missing from my notes, do not fabricate numbers; instead, mark it as [Check Metric] and provide a one-line tip on where I can find that data.
Format
Output the result as a markdown table. The columns must be: Task Completed | Impact / Change | Evidence (Metrics/Data) | Self-Evaluation Draft (2 sentences max). Below the table, provide a 3-bullet executive summary grouping these accomplishments, plus a 2-sentence draft suggestion on how to professionally address underperformed goals.
Self-check
After drafting the table, perform a self-audit: verify whether the "Impact / Change" directly resulted from my specific actions and ensure no placeholder numbers were invented. Correct any discrepancies before displaying the final output.
Input
Work Record: """ {{work record}} """

Simply pasting a yearly work log into ChatGPT and asking to "clean this up" usually yields a slightly polished list of duties. Saying "increased blog cadence to twice a week" is a task log, not an achievement. Evaluators look for business impact; when that column is blank, high performers and mere task-doers receive the same score.

This is why the Task is split into three explicit components. Placing the action, impact, and evidence side-by-side immediately highlights unbacked claims. Leaving missing data as [Check Metric] with advice on where to pull the numbers makes this prompt genuinely actionable. Without explicit guardrails, LLMs tend to hallucinate figures like "improved efficiency by ~30%," which inevitably collapses under scrutiny in review meetings.

Setting the Context by noting that the reader is a senior manager sets the tone and altitude. It strips out insular team jargon and internal project code names that an executive wouldn't recognize. The Format constraint limiting self-eval statements to two sentences respects the character limits typical of HR appraisal software.

The fifth paragraph instructs the model to run a Self-Audit. Generating structured tables often strains causal reasoning; requiring a validation step filters out unearned attribution and fabricated numbers. Enclosing the raw logs in """ prevents random task notes from being interpreted as prompt instructions. While AI can draft the structure, you must personally verify and fill in the metrics before submitting.

Unfamiliar terms? See Aha AI: hallucination, self-consistency

Compared with a bad example

Common bad example

Summarize what I did this year and write my self-evaluation.

(Paste work notes)

This outputs generic fluff like "Successfully revamped the company blog and contributed to team performance." The task remains unchanged while adding hollow corporate adjectives, offering zero new data to the evaluator. If the AI hallucinates plausible percentages, you won't be able to defend them in your review. Furthermore, underperformed goals are often omitted entirely, leaving you unprepared when your manager brings them up.

Variations

When Framing Missed Goals & KPIs

When Framing Missed Goals & KPIs

Help me write about goals I missed during {{evaluation time period}} for my self-evaluation. From the log below, identify the underperformed areas and structure them into: Fact · Controllable vs. Uncontrollable Causes · Course Corrections Implemented · Next Period Action Plan. Eliminate both defensive excuses and excessive self-blame.

""" {{work record}} """

If you omit missed targets, your evaluator will be the one to bring them up. Addressing them proactively along with concrete adjustments frames the shortfall constructively.

When Preparing a Promotion Packet

When Preparing a Promotion Packet

Convert the following records for {{evaluation time period}} into a promotion review packet for a {{job position role}}. Focus not merely on doing the assigned job well, but on proving that I am already operating at the next level. Format each point as: Next-Level Competency Expected · Concrete Demonstration · Evidence. Flag and exclude any entries where evidence is weak.

""" {{work record}} """

Standard evaluations and promotion reviews look for different signals. This variant shifts the focus from task execution to demonstrating competencies required for the higher band.

Model notes

Numbers and metrics are the most common hallucinations for language models. Always manually replace [Check Metric] placeholders with verified data after receiving the draft, or delete the metric clause entirely if unavailable.

Related prompts

Last updated 2026-09-02 · Found a mistake? Let us know