Start with one actual role description and a private record of work you can explain. Do not begin by copying impressive numbers from a resume example. This guide produces a requirement-to-evidence table and a checked application file, not a guaranteed interview.
Separate the requirement from your evidence
Pick the responsibilities that matter for the role. Beside each, write what you personally did, your contribution within a team, the result you can support and where you could verify it. School, volunteer and personal projects can be relevant when described accurately.
| Role requirement | Your action and scope | Evidence you can support | Resume decision |
|---|---|---|---|
| Copy from the actual role | What you did, not the whole team's achievement | A deliverable, record or truthful observation | Include, clarify or omit |
The table is a private drafting aid. Do not upload confidential employer records, client details, identification numbers or credentials. A resume can describe an outcome without disclosing a protected document.
Draft an accurate bullet
Use “action + task or scope + supported result” as a drafting structure. A placeholder example is: “Updated [the process you actually changed] for [the scope you can verify], producing [the documented result].” Replace every bracket with a fact or remove it. Do not insert an assumed 30 percent improvement or double a follower count because an example sounds stronger.
If a result was not measured, describe the completed deliverable and its purpose. Distinguish leading a task from assisting it. Check dates, job titles and qualifications against your records. Harvard's resume guidance recommends factual, specific language and tailoring to the role; its conventions are not universal requirements for every country or profession.
Turn one evidence row into one finished bullet
This is a synthetic example, not anyone's resume or a real vacancy. Assume a role asks for document checking. In the example project, a volunteer checked six draft headings against a supplied list and recorded two missing sections. The team wrote the missing sections; no delivery-time measurement exists.
| Requirement | Supported individual contribution | What the bullet must not claim |
|---|---|---|
| Check documents against requirements | Compared six headings with the list; recorded two omissions | Wrote the team's revisions, led the project or saved 30% of the time |
A finished example is: “Checked six draft headings against the requirements list and documented two missing sections for the team to revise.” The numbers are inputs to this invented exercise, not achievements to copy. If your real record has no count, omit the number rather than borrowing six or two. “Reduced turnaround by 30%” is rejected here because the assumed record contains no timing evidence.
Choose a format the recipient can use
Follow the application's file type, length and required-field instructions. Make headings, dates and text easy to scan, and check how the document converts to the requested format. There is no single template that guarantees applicant-tracking-system success. Do not add hidden keywords, qualifications you lack or a photo merely because an unrelated template includes one.
Verify the file before submitting
Open the exported file on a second screen size if available. Check selectable text, broken lines, links, dates, contact details and whether placeholders remain. Confirm the intended recipient and filename. Keep the role description and submitted version together so interview preparation uses the same facts. This site does not need your resume or personal details to use the worksheet.