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.