Administrative Assistant to Project Coordinator Resume

An assistant usually supports one person or a team by responding to requests. A coordinator helps keep a piece of work on track, often for several people at once. The resume has to show that shift: you tracked things, followed up without being asked, and kept work from slipping. Read five or six coordinator postings you would actually apply for. You will see the same themes: scheduling, tracking tasks and deadlines, communicating with stakeholders, preparing status updates, managing documents, and working in tools like Excel, Smartsheet, Asana, Trello, or Microsoft Project. Those themes are your guide for what to move to the top of your resume. You do not need the word "project" in your old job title. You do need to show that you handled work with a start, an end, and several moving parts.

Start with a plain list of everything you did in your last two or three jobs. Then go through it with these questions: - Did you plan or run an event, office move, software rollout, audit, onboarding, or system change? - Did you keep a tracker, spreadsheet, or calendar that other people relied on? - Did you follow up with people who owed information or approvals? - Did you send updates, meeting notes, or reports to a manager or team? - Did you manage a budget, vendor, or purchase order, even a small one? - Did you train a new hire or write down a process? Each yes is a possible bullet. A task like "booked travel" is admin work. "Coordinated travel for a 40-person sales meeting, including flights, hotel block, and ground transportation" is coordination. Same work, described by scope and outcome. If you cannot remember details, check old emails, calendar entries, shared drives, and performance reviews. They often hold dates, headcounts, and dollar amounts you have forgotten.

Lead each bullet with an action verb, say what you owned, and add a number or result where you honestly can. The numbers below are examples only. Use your own, and estimate conservatively if you do not have exact figures. Before: Answered phone calls and scheduled meetings for the operations team. After: Scheduled and confirmed weekly meetings across 3 departments, resolving calendar conflicts so project reviews started on time. Before: Helped with office move. After: Coordinated an office move for 25 employees, managing a checklist of 60+ tasks, vendor scheduling, and daily status updates to the office manager. Before: Maintained spreadsheets. After: Built and maintained a shared tracker for open purchase requests, cutting follow-up emails and giving managers a single place to check status. Before: Took meeting notes. After: Documented decisions and action items for weekly team meetings and followed up with owners until each item was closed. If you are unsure how to come up with numbers, the guide on quantifying achievements walks through ways to estimate them. The guide on action verbs can help you avoid starting every line with "Assisted."

Put a short summary at the top that names the target role. For example: "Administrative professional with 7 years of experience coordinating schedules, vendors, and deadlines for operations and HR teams. Skilled at tracking tasks in Excel and Smartsheet and keeping stakeholders informed. Seeking a project coordinator role." Three sentences is plenty. Skip vague phrases like "hard-working team player." In the skills section, list the tools and abilities that match the postings: scheduling, task tracking, status reporting, budget tracking, vendor coordination, document control, meeting facilitation, plus the software you have really used. Only list a tool if you could talk about it in an interview. If you have used Asana only once, say so in the interview, not with a skills bar on your resume. On titles, never change your real title. But you can add clarity with a descriptor, such as "Administrative Assistant (Project and Event Coordination)." Many employers are fine with this as long as dates, company, and the actual title remain accurate. If you have a certification such as CAPM or a project management certificate course, list it in a separate section. It helps, but it is not required for most entry-level coordinator jobs.

Do not bury your best project work at the bottom of a long duties list. Put the two or three strongest bullets first under each job, and cut routine items like "answered phones" unless the posting asks for them. Do not exaggerate. Saying you "managed" a project when you supported the person who did can fall apart in an interview. Words like "coordinated," "tracked," "scheduled," and "supported" are accurate and still show value. If you did lead something, say "led" and be ready to explain how. Do not send one resume to every posting. Coordinator jobs vary: construction, IT, marketing, healthcare, and nonprofits all use different terms. Match your wording to each posting, as covered in the guide on tailoring a resume to a job description. Finally, keep it to one page if you have under about ten years of experience, and use a plain layout with standard headings so applicant tracking systems can read it. If you want help getting started, aNewJob can build the resume from documents you already have, such as an old resume or performance reviews, through a short interview.