See the input.
Inspect the feedback.

1. Diagnosis

Your strongest fit for this target is the work already happening in your operations role: maintaining a request queue, checking whether requested records have arrived, following up with owners and producing a status summary. The draft hides those outputs behind claims of cybersecurity leadership and supplier compliance that your intake does not support.

The target is supervised coordination, so an accurate account of that work is more useful than presenting yourself as the person who performed security assessments. Your Cedar exercise can demonstrate how you organize a small evidence question, but it should be labeled as educational practice. It cannot establish professional audit experience.

The resume does not currently provide direct experience assessing access controls. That is a gap to retain, not cover with a skill-list keyword. The project can support a conversation about what you have practiced and where your limits are.

2. Edit these items first

1. Remove unsupported seniority and results. Replace “cybersecurity leader,” “full compliance” and the 40% claim. You confirmed that the percentage has no measurement behind it.
2. Put your actual outputs into the current role. Make the 30-file tracker, completeness check, follow-up and weekly summary visible. Retain the Operations Coordinator title.
3. Relabel the project. It used fictional inputs and did not certify a real company. State the comparison performed and its narrow conclusion.
4. Replace broad skill labels with explainable tools and learning. Identify the spreadsheet features you can actually use. Keep framework reading separate from a credential or professional assessment skill.

3. Section-by-section feedback

Header

The city and email are enough for this sample's contact header. Use your own current contact details in a real document. If adding a portfolio link, check that it opens the intended public project and that its educational label is visible.

Summary

Use a short transition statement based on your current occupation and relevant work. A supported example is: “Operations coordinator experienced in supplier-document tracking, stakeholder follow-up and weekly status reporting. Targeting supervised GRC coordination roles, with educational practice analyzing a fictional approval record.” This does not claim you already hold a security position.

Current experience

Use two or three focused bullets rather than separating tools from the work they support. Your evidence-request tracker is the strongest connection to the target. The weekly summary deserves its own line because it is a concrete communication output. Remove the percentage claim entirely unless a real measurement with a defensible baseline becomes available.

Earlier experience

Keep the Elm title, dates and two concise bullets. The action log supports a consistent coordination story. There is no need to rename routine administrative work as risk management. If space is tight, shorten meeting-material detail before deleting the chronological entry.

Educational project

Change the heading to “Fictional approval-sequence review — educational exercise.” Explain that you compared supplied timestamps against an invented procedure. The packet did not support a general conclusion about access-control effectiveness. If your worksheet includes a hypothetical follow-up, preserve the distinction between the original case and changed facts.

Education, tools and learning

Keep the education entry concise and accurate. For the tool section, “document trackers, status summaries and spreadsheet reconciliation” is more specific than a row of broad field names, provided you can explain the work. Identify any particular Excel features only after confirming you actually use them. “Selected NIST CSF reading” describes learning; “NIST certified” would not describe the facts supplied here.

Organization and export

Use the order Header, Summary, Experience, Educational Project, Education, Tools and Learning. Keep date formatting consistent and give headings enough space to scan. After editing, inspect the actual PDF on a small screen and copy its text into a plain-text editor to check reading order. These checks improve readability; they do not produce a universal ATS score.

4. Selected bullet revisions

5. Questions to resolve before applying

1. Does “30 files” describe the current queue, a particular period or lifetime work? Use the interpretation you can support; do not imply 30 completed assessments.
2. Which spreadsheet features have you used directly? Replace a broad proficiency claim with a description you could demonstrate.
3. Did you produce the project worksheet independently, adapt a supplied answer or do both? The portfolio README should explain that contribution.
4. Did you revise request instructions? Use the conditional example only after confirming the facts.

6. Your final editing checklist

1. Replace the summary with the supported transition statement, adapted to your own voice.
2. Use the tracker and weekly-summary bullets; remove the unsupported 40% result.
3. Keep real job titles and dates intact.
4. Move Cedar under Educational Projects and retain its fictional label.
5. Confirm scale and tool details; omit unconfirmed additions.
6. Export and inspect the revised file, then rehearse one short explanation for each highlighted claim.

The next useful improvement is a document that consistently tells this narrower, well-supported story. A second round of stronger adjectives would not address the underlying mismatch.