How to Describe Your Work in a Job Email When You Have No Metrics

When you have no performance metrics, describe what you personally did, the setting that made it useful, and something concrete that supports the claim. In a job email, that might be a process you documented, a difficult constraint you handled, or a deliverable someone used. Leave out a claimed improvement if you cannot verify it.

You do not need to apologize for missing revenue figures or add a percentage to every sentence. The task is to give a hiring contact enough detail to understand your experience and ask a useful follow-up question.

Harvard's resume guidance recommends specific, fact-based language and quantifying where possible. The worksheet below is our suggested way to apply that principle to a short outreach email. It is an editing tool, not a hiring standard or a promise of interviews.

Find evidence you actually have

Start with a responsibility in the target job description. If the employer needs someone to document customer onboarding, choose a relevant documentation example before searching your memory for an impressive business result.

Look for details in your own permitted records, such as a project summary or feedback you received. Do not copy private employer material into an email or a drafting tool. You can use a record to check your recollection without sharing the record itself.

Useful details include:

• Scope: Which workflow, audience, or part of a project did your work cover?
• Constraints: What requirement or limitation did you have to accommodate?
• Ownership: What did you decide, create, or maintain yourself?
• Artifacts: What concrete output could you describe or, with permission, show?
• Observable outcomes: What happened afterward that you can support?

A deliverable and a business outcome are different claims. You may know that your team adopted a checklist while having no evidence that it reduced errors. Say the team adopted it only if that happened; omit the error-reduction claim.

Five before-and-after examples without invented metrics

These scenarios and names are fictional. The revised sentences assume the described work happened and could be explained in a conversation. Replace them with your own facts. None requires a numerical performance result.

1. Use scope to explain routine support work

Vague: "I have strong customer service experience."

More specific:

I handled account-access questions for customers using our web portal, including checking account status and documenting unresolved cases for the technical support team.

This identifies the work and the handoff. It fits a support role more clearly than a general claim about communication. Do not add "high-volume" or "enterprise" unless those descriptions accurately fit your experience.

2. Name the constraint in an operations project

Vague: "I improved our onboarding process."

More specific:

I rewrote the onboarding instructions so new customers could complete setup without administrator access, using the permissions available in our standard account tier.

The constraint explains what you had to solve. This sentence does not claim that onboarding became faster. If you only drafted the instructions and they were never tested or used, say you drafted them and explain the intended purpose.

3. Separate your ownership from the team's delivery

Vague: "I led the launch of our new reporting dashboard."

More specific:

For our reporting dashboard launch, I wrote the release notes and customer setup guide. The engineering lead owned the release plan and rollout.

Use "led" when you actually directed the relevant work. If you contributed to one part, name that part. A precise contribution gives a hiring contact something you can discuss without taking credit for colleagues' decisions.

4. Describe an artifact when results were not measured

Vague: "I made our reporting more effective."

More specific:

I built a spreadsheet that paired each open purchasing request with its approval status and next owner, replacing my own separate notes for the weekly operations review.

The reader can understand the output even without a savings estimate. This example limits the replacement claim to the applicant's own notes. Do not imply the whole department adopted the spreadsheet if it remained a personal tool.

If you can share a cleared example, follow the guide to sending work samples by email. If you cannot share it, describe its structure without including confidential records.

5. Use a qualitative outcome you can verify

Vague: "My training had a major impact."

More specific:

I wrote a troubleshooting guide for the scheduling tool, and the team supervisor added it to the new-starter training pack.

Adoption is a concrete outcome if you know it happened. It does not establish that the guide reduced training time or improved performance. If a supervisor praised the draft but never used it, describe the feedback accurately rather than turning it into adoption.

Fill out a contribution worksheet before writing

Use one project per worksheet. Keep uncertain details visible while working; resolve or remove them before sending.

Target role responsibility:
Project and setting:
What the team was responsible for:
What I personally did:
What another person owned:
Constraint I handled:
Output I produced:
What I know happened afterward:
How I can verify that detail:
What I do not know:
What I am allowed to describe or share:
One relevant sentence for this employer:

Here is a completed fictional example:

Target role responsibility: Maintain customer onboarding documentation.
Project and setting: Setup instructions for a customer portal.
Team responsibility: Release a revised onboarding flow.
My contribution: Drafted setup steps and troubleshooting instructions.
Other ownership: Product manager approved the flow; engineering built it.
Constraint: Customers used accounts without administrator access.
Output: A setup guide for standard-tier accounts.
Known outcome: Support lead linked the guide in the team's onboarding reply.
Verification: My approved project summary records that handoff.
Unknown: Whether setup became faster or support requests decreased.
Sharing: Describe the work; do not send internal customer records.
Sentence: I wrote portal setup instructions for customers without
administrator access; our support lead used the guide in onboarding replies.

You can omit a field from the final sentence. Including every detail would turn a short email into a project report. Choose the detail that best matches the employer's stated task, then save the rest for a conversation.

Put one evidence sentence into the email

Use personalization to connect the role to your experience. The evidence sentence then shows what you did. Add a specific ask and check any application instructions before sending.

This fictional email assumes the applicant has already applied:

Subject: Customer Operations Associate application - onboarding documentation

Hi Morgan,

I applied for the Customer Operations Associate opening. The posting's
focus on maintaining setup documentation matches my recent support work.

I wrote portal setup instructions for customers without administrator
access; our support lead used the guide in onboarding replies.

Would that documentation experience be relevant to the team's current
needs? I would be glad to discuss the role.

Best,
Alex

The message leaves out a performance claim because the applicant does not have one. If the role requires evidence of a particular result you cannot demonstrate, do not treat better wording as a substitute for that qualification.

What if you have useful numbers, but no performance data?

You can include a verified count that clarifies scale, such as the number of locations supported or the length of a project. Label what it measures. "Maintained the guide for four locations" describes scope; it does not mean the guide improved performance across those locations.

Avoid reconstructing a percentage from memory or borrowing the team's revenue figure as your own achievement. If you later recover a reliable result, check the time period and your contribution before adding it. A supported qualitative sentence is usable now; an uncertain number should stay out of the email.

Before sending, ask whether you could explain every claim with a concrete example. Check that your resume and email describe your responsibility consistently. Remove confidential details and any outcome you inferred from a compliment or a completed task.

Personal Reach helps you find relevant jobs and contacts and prepare role-specific outreach drafts you can review and edit. When reviewing a draft, replace any unsupported achievement with a sentence grounded in your own work. Create a Personal Reach account to prepare outreach around relevant opportunities.