Turn Your Work Records into a Resume for One Job

To tailor a resume for one job, choose and organize the experience you can support. Use the job description to decide what is relevant, then use your own records to decide what you can say. Those are different sources: a requirement for workplace SQL does not establish that you have used SQL at work.

This walkthrough produces a complete resume for a fictional reporting role. It starts with a whole baseline resume, a whole job brief, work records and a corrected rough capture. The finished document makes recent reporting work specific, keeps earlier coordination experience under its original employer and labels personal SQL practice as learning. A missing requirement stays outside the resume as an editing gap; it does not become a new skill.

All people, employers, institutions, records and 2028–2034 dates in the case are original fiction. None is a real candidate, vacancy, employment history or product result. The wrong resume and repaired document were written for the example; no separate model trial, software execution or application submission produced them. Case dates are not this article's publication date.

Start with the whole application task

Riley Vale wants to prepare a resume for the fictional Reporting Operations Coordinator role at Fernline Operations. The job asks for reports shaped around colleagues' needs, Excel work, CSV checks, handoff instructions and workplace SQL. Power BI and an external analytics certification are helpful extras.

The supplied history supports reporting, CSV checks, instructions and coordination. It does not support workplace SQL, Power BI or the certification. Riley has chosen to prepare the application with that gap. This exercise does not decide whether an employer should select Riley or predict what the employer will do.

The writing task is larger than polishing a bullet. The baseline has two jobs, broad skills and education. The final resume needs to select the relevant evidence, make the current wording more useful and preserve which employer owns each contribution. It should read as a resume without requiring the reader to consult an audit table.

Two historical public discussions — one about tailoring a resume with unsupported keywords and another about checking an AI-generated resume before submitting it — describe invented experience and accomplishments drifting between jobs. The discussions also contain objections to spending more time prompting and correcting than making the edits manually. These are two individual self-reports with selected comments, not a representative sample or a test of a current model. Tool promotions, screening claims and reported job outcomes from the comments are not evidence for this tutorial.

For a small adjustment, edit your existing resume yourself. If a suitable base version already exists, reuse it and change only what the job calls for. An assistant can help organize a larger packet, but this example does not establish that it saves time or improves an application result.

Read the records before improving the prose

The fictional packet distinguishes a source from a proposed claim. W1–W4 describe the reporting role. W6–W7 describe the earlier service role. W8 records personal learning after the recent job ended. The rough capture O1 is something to clarify, not permission to rearrange that history.

O1 contains an explicit correction from “dashboard” to “workbook,” but it also says “I led” and floats a 30% saving. The work records do not support those statements. Q1 asks about ownership, the figure, the SQL work and the employer that owns the six sessions. C1 answers those questions: Riley supported another person's project, no time saving was measured, SQL was a personal exercise, and the sessions belong to Bracken.

A correction should not erase other supported work. There is still a monthly reporting workbook, a specific CSV check and a written guide. The resume can describe those concrete contributions without promising faster reports, fewer errors or complete suitability for the job.

Copy a complete repair request with all its inputs

The following is the complete request, including the whole job brief and baseline resume, every work record, the rough capture and clarification, and the entire deliberately wrong resume. Nothing depends on another chat, a real account or an absent attachment. The correct resume is not in this input.

You can also read the complete source packet, complete wrong resume and complete repair request as standalone files. The wrong draft is an authored counterexample, not captured output from a model.

Write a complete replacement resume for Riley Vale for the one fictional job in the source packet below. Use the complete packet, not the wrong draft, as the factual basis. All names, employers, institutions, roles, records and dates are invented teaching material.

Return:
1. A whole readable resume in Markdown, from its fiction label and name through profile, experience, skills, additional learning and education. Keep the evidence audit and requirements gaps outside it.
2. A separate internal claim-to-record table for every factual statement, including identity, roles, dates, contribution, tools, numbers and learning scope.
3. A separate internal requirement-to-evidence check and a disposition of the baseline/source records: retained, made more specific, excluded, corrected or needing clarification, with reasons. Do not score or rank a person for an employer.

Organize the entire resume for this reporting role. Use the reporting and CSV evidence to make the relevant recent work specific, and retain the earlier coordination work under its own employer. Treat JD requirements as the employer's request, never as proof that Riley has a skill. A missing requirement remains an internal gap; do not fill it with invented credentials, tools, years, results or a claim of full qualification.

Preserve Riley's exact employers, role titles, employment periods and diploma. Keep the six orientation sessions at Bracken in February 2030. Distinguish Riley's work supporting the four-person intake change from the other colleague's project leadership. Remove the unsupported 30% saving and all other invented results. Do not replace a guessed percentage with an unmeasured qualitative speed or accuracy claim. Supported scope counts describe their objects, not business improvement.

Apply the explicit corrections in C1 to the rough capture O1 and unverified W5 question. Use workbook, not dashboard. SQL is a May 2034 self-directed training exercise, not workplace database experience or a certification. Power BI and an external analytics certification have no support. Keep supported Excel/CSV/documentation work even though professional SQL remains a gap. Do not transplant work across roles or turn a reviewed guide into a training program.

Return the entire repaired document, not suggested edits or a keyword template. Do not add contact details, an application route, a date of submission, a photo, a certificate or a missing education item. The wrong draft is authored counterexample text, not another source. Do not include the answer inside a rewrite of the input packet.

This is a local writing exercise only. Do not browse, contact anyone, upload a real resume, submit an application, access an account, run software or models, evaluate other candidates, infer sensitive attributes, or promise ATS scores, interviews, hiring outcomes or AI effectiveness. The complete packet and entire wrong resume follow; no previous chat or attachment is required.

=== BEGIN COMPLETE SOURCE PACKET ===
RESUME-01 — Complete original fictional source packet

All people, employers, institutions, roles, requirements, messages, work records and dates in this packet are invented for this teaching case. Riley Vale, Alderloop Services, Bracken Desk Cooperative, Eastmere Learning Centre and the hiring organization, Fernline Operations, are fictional. The 2028–2034 dates are case dates, not this tutorial's publication date. No real candidate, employer, resume, recording, job posting or software result was used. No contact details, application destination or submission permission are supplied. Treat this packet as the case's entire factual universe.

CASE0 | Writing task and boundary | 14 June 2034, 12:00 UTC
Riley wants a complete resume for the one job below, using Riley's own supplied experience. Riley has chosen to prepare this application despite the professional SQL requirement remaining unsupported. The writer is not deciding whether an employer should hire or rank Riley. Return a complete resume, not a cover letter or a single rewritten bullet. Do not add an address, phone, email, portfolio URL, certification or an application date. Keep any evidence gaps and questions outside the resume. Label the standalone document as fictional teaching material.

JD0 | Complete fictional job brief | Fernline Operations
Role: Reporting Operations Coordinator.
Work: Maintain a shared team's request reports, understand what colleagues need from a report, check incoming records and document the repeatable steps. Coordinate with the person responsible for a process change and explain problems clearly. This is an individual-contributor role; it has no people-management duties.
Required experience:
J1. Turn a colleague's reporting question into a useful recurring report.
J2. Use Excel filters, lookups and pivot tables to organize operational records.
J3. Check incoming CSV records for duplicate identifiers and missing required values, then communicate exceptions.
J4. Write clear handoff instructions and coordinate tasks with other people during a process change.
J5. Write routine SQL queries against a workplace database.
Helpful, not required:
J6. Build reports in Power BI; a completed external analytics certification is also helpful.
Application material for this exercise: one complete resume. No cover letter, contact route, salary, location requirement or screening procedure is supplied. The job brief describes the role's needs; it supplies no facts about Riley's experience.

B0 | Complete baseline resume supplied by the fictional writer
Riley Vale
Operations support

Summary
Operations support worker with experience in spreadsheets, service coordination and team documentation.

Experience
Reporting Assistant — Alderloop Services
May 2031–April 2034
- Helped with monthly reports and spreadsheet updates.
- Checked incoming task records.
- Helped the team move to a new request process and wrote notes.

Service Coordinator — Bracken Desk Cooperative
September 2028–April 2031
- Arranged orientation sessions and kept track of confirmations.
- Wrote a checklist for session hosts.

Education
Diploma in Business Administration — Eastmere Learning Centre, 2028

Skills
Excel, CSV files, coordination, written instructions

The baseline is complete for the case, not a fragment of a hidden CV. Its broad wording can be made more specific from W1–W8 and C1 below. No employer, role, date or education entry may be moved or extended without a supplied correction.

W1 | Alderloop work record | Monthly request workbook
During the Reporting Assistant role, Riley asked the service coordinator which request statuses the monthly review needed, then maintained the monthly request workbook around those statuses. Riley used Excel filters, lookups and pivot tables to summarize requests by status. This was a workbook, not a Power BI dashboard. No database queries or measured improvement in reporting speed are part of this record.

W2 | Alderloop work record | Incoming CSV checks
Riley checked incoming CSV records for duplicate request_id values and empty assigned_owner cells. Riley sent an exception list to the service coordinator for correction. Riley did not delete duplicate rows automatically or claim that the checks prevented every data error. No error-reduction percentage was measured.

W3 | Alderloop work record | Reporting handoff guide
Riley wrote the guide for rerunning the monthly workbook and checking duplicate identifiers and missing owner values. The team supervisor reviewed the guide, and the team kept it in its reporting folder. Riley wrote the instructions; this record does not say Riley designed a training program, trained a stated number of people or measured their later performance.

W4 | Alderloop work record | Request-intake change
A four-person team moved request intake from an email inbox to a shared form. Another colleague was the project lead and owned the rollout decision. Riley checked the old-to-new field mapping, drafted the handoff checklist and recorded colleagues' questions. Riley supported this team change; Riley did not independently lead it or manage the other three people. The supplied records contain no measured time saving, adoption rate or reduction in support requests.

W5 | Alderloop work note | Missing outcome measurement
A rough planning line says, "Maybe the new process saved 30% of reporting time?" It is an unverified question, not a measurement. No before/after times, sample, calculation or attribution record is supplied. C1 explicitly withdraws the percentage. The existence of a new form or a guide does not establish a speed improvement.

W6 | Bracken work record | Orientation coordination
Riley coordinated room bookings and attendee confirmations for six orientation sessions in February 2030 and kept a tracker of unresolved arrangements. Six is the count of sessions in that period, not a satisfaction score, an annual total or a percentage improvement. This belongs to the Service Coordinator role at Bracken, not the later Alderloop role.

W7 | Bracken work record | Session-host checklist
Riley wrote a checklist covering room preparation, attendee confirmation and handing unresolved arrangements to the session host. It was used for the orientation sessions. This was a session-host checklist, separate from the reporting guide written later at Alderloop. No measured attendance improvement or management responsibility is supplied.

W8 | Personal learning record | May 2034
After the Alderloop role ended, Riley practised SELECT, WHERE and GROUP BY queries on a supplied training table in a self-directed SQL exercise. This was personal practice, not work for an employer or access to a workplace database. Riley has not written SQL against a workplace database in any supplied role. Riley has no Power BI experience and no external analytics certification in this case. No course provider, certificate, credential level or claim of SQL proficiency is supplied.

O1 | Complete authored rough spoken capture | 12 June 2034, 09:00 UTC
"I built the dashboard at Alderloop — no, the workbook, not a dashboard. I led that move from email to the new form. Maybe it saved thirty percent of reporting time? I also did the SQL work. Put the six sessions under my recent job because it sounds more relevant there."
This is an invented rough capture, not audio or an actual transcription. Its assertions and placement request need checking against the work records; they are not automatic approvals to overwrite them.

Q1 | Clarification questions prepared for Riley | 12 June 2034, 09:10 UTC
Did you lead the intake change or support another lead? What supports the 30% time figure? What exactly did the SQL work involve, and when? Which employer owns the six sessions? Is "dashboard" your final term, or did you correct it to "workbook"? Have you used Power BI or completed the certification mentioned in the job brief?

C1 | Complete authored clarification and correction | 12 June 2034, 09:30 UTC
"Use workbook, not dashboard; that correction in my rough capture stands. I supported the four-person intake change. Another colleague led it. My work was the field mapping check, handoff checklist and recording questions. We never measured a time saving; I do not know a percentage and should not claim 30%. My SQL work was only the personal training exercise in May 2034, after Alderloop ended, not workplace database work. The six orientation sessions belong to Bracken in February 2030; do not move them to Alderloop. I have not used Power BI and have no external analytics certification. Keep my employers, roles, dates and diploma as supplied. I want a factual resume; I am not asking you to claim that I meet every job requirement."
C1 resolves these particular conflicts; it is not permission to invent other missing experience. The supported reporting, CSV and documentation work remains supported even though the workplace SQL requirement is a gap.
=== END COMPLETE SOURCE PACKET ===

=== BEGIN COMPLETE WRONG RESUME ===
AUTHOR-WRITTEN COUNTEREXAMPLE — Intentionally incorrect fictional resume. All people, employers, credentials and dates are invented. Not a real candidate's material or captured model output.

# Riley Vale
Senior Reporting Leader | Certified Analytics Professional

## Profile
Reporting leader with ten years of SQL, Power BI and people-management experience. Independently delivered a reporting transformation that cut processing time by 30% and eliminated data errors. Meets every requirement for the Reporting Operations Coordinator role.

## Experience
Reporting Manager — Alderloop Services
May 2031–Present
- Independently led the four-person move from email intake to a shared form and managed the rollout.
- Built Power BI dashboards and production SQL queries to accelerate monthly reports by 30%.
- Automatically removed all duplicate and incomplete records, eliminating reporting errors.
- Coordinated six orientation sessions at Alderloop and improved attendance by 25%.
- Designed a training program and certified the team on the new reporting process.

Service Coordinator — Bracken Desk Cooperative
September 2028–April 2031
- Supported general administration.

## Education and certifications
Diploma in Business Administration — Eastmere Learning Centre, 2028
External Analytics Professional Certificate, 2034

## Skills
Production SQL, Power BI dashboards, people management, automated data cleansing, Excel
=== END COMPLETE WRONG RESUME ===

Read the complete repaired resume

The result below is the entire repaired document. The standalone resume contains the same text. Its first line marks it as fiction; the rest gives the reader a coherent account of the supplied experience, without source IDs, a requirement score or an internal gap checklist.

Fictional teaching example — all people, organizations and dates below are invented. Not a real application.

# Riley Vale
Operations reporting and coordination

## Profile
Operations support worker with experience maintaining request reports, checking CSV records and writing handoff instructions. Uses Excel filters, lookups and pivot tables to organize operational records.

## Experience
### Reporting Assistant — Alderloop Services
May 2031–April 2034
- Asked the service coordinator which request statuses the monthly review needed and maintained the monthly request workbook around those statuses.
- Checked incoming CSV records for duplicate request_id values and empty assigned_owner cells; sent an exception list to the service coordinator for correction.
- Wrote the guide for rerunning the monthly workbook and checking duplicate identifiers and missing owner values; the team supervisor reviewed it.
- Supported a four-person move from email intake to a shared form by checking the field mapping, drafting the handoff checklist and recording colleagues' questions.

### Service Coordinator — Bracken Desk Cooperative
September 2028–April 2031
- Coordinated room bookings and attendee confirmations for six orientation sessions in February 2030; kept a tracker of unresolved arrangements.
- Wrote the session-host checklist covering room preparation, attendee confirmation and handoff of unresolved arrangements.

## Skills
Excel filters, lookups and pivot tables; CSV record checks; handoff documentation; session coordination.

## Additional learning
SQL practice, May 2034: practised SELECT, WHERE and GROUP BY queries on a supplied training table as a self-directed exercise.

## Education
Diploma in Business Administration — Eastmere Learning Centre, 2028

See what changed across the whole resume

The final version does not copy the job description into a skills list. Its profile brings together reporting, CSV checks and instructions because those are relevant to the role and supported by the work records. The experience sections then explain those contributions under the correct employer.

This is selection and organization across a complete document. The generic baseline skills are replaced with the specific supported methods. Both jobs remain because both supply relevant experience. The training record has its own section so that it does not silently become part of the recent job. No objective about meeting every requirement is needed.

Keep the missing requirement in the working notes

A private editing table can pair each job requirement with the writer's own records and any gap. In this case, the first four requirements have relevant evidence. The workplace SQL requirement does not: a self-directed exercise is a different kind of experience. The Power BI and external-certification preferences are also unsupported, and C1 explicitly says Riley does not have them.

Do not add those terms as professional skills to make the document look complete. Conversely, do not remove the supported Excel and reporting work merely because SQL remains a gap. The application decision belongs to Riley; the resume should describe the experience supplied, without announcing that every requirement is met or judging Riley against other applicants.

Keep the factual mapping beside the draft, outside the resume. A small table with the proposed statement, source passage, employer or project, and any condition is enough. Also record why you kept, condensed or removed an existing item. The reader of the resume needs the experience; the editor needs the supporting detail.

For your own material, a missing fact should become a specific question: which work did you personally do, which project and employer does it belong to, and what record supports a number? If there is no measurement, describe the supported work itself. An estimate or an employer's desired result does not become your achievement simply because it fits a sentence.

Repair the wrong claims without keeping their softer versions

The deliberately wrong resume changes more than tone. It turns an assistant role into management, extends an ended job to Present, moves the sessions to another employer, upgrades practice to production SQL, invents Power BI and a credential, and converts uncertain benefits into percentages.

The repaired document removes those claims and returns to the source packet. It also removes “eliminated data errors” and the invented attendance result, rather than weakening them to “greatly improved accuracy” or “boosted attendance.” Neither replacement would have a source. The correct statements say what was checked, written or coordinated.

The two checklists stay separate. One belongs to the reporting handoff at Alderloop; the other supports orientation hosts at Bracken. Similar words do not make them the same project. The six-session count is retained only with the earlier role and its stated month, not as a later annual total or evidence of increased attendance.

Read the complete repaired resume one last time without the teaching packet beside it. Does each section describe the kind of experience it claims? Are personal work, team participation and learning distinguishable? Are titles and dates consistent? Could the writer explain each factual statement from their own records? This is a check of the supplied document, not a reader study or an interview result.

The finished example is a whole piece of writing with inspectable support. It does not demonstrate ATS performance, model accuracy, time savings, interview invitations or hiring outcomes. No application has been sent. Manual editing and reuse of an appropriate base version remain valid alternatives throughout.