Most resume bullets describe a job. What you need is a bullet that proves a result.

There's a difference. And it's the difference between getting filtered out and getting a call.

I'm going to show you exactly how to write bullets that clear the ATS, hold up in human review, and actually reflect the work you did — using examples from my own background in security and law enforcement, because that's where I can be most honest with you.

Why most bullets fail

Here's the most common bullet I see from people in security and operations roles:

*Responsible for managing security officers and ensuring site safety.*

That bullet tells me nothing. It tells a recruiter nothing. It tells an ATS nothing useful either, because "responsible for" is noise — it's not a skill, not a tool, not an outcome. It's a job description of a job description.

The problem is that most of us were never taught to write our experience as *evidence*. We were taught to list it. Those are two different things.

The framework: Action → Scope → Outcome

Every strong bullet follows a simple structure:

What you did (specific action verb) + **what you did it to or with** (scope, tools, people) + **what happened because of it** (outcome, impact, metric)

You don't always have all three — and that's fine. But you should always be reaching for at least two.

Let me show you what this looks like in practice.

Before and after: security and operations

Before: > *Responsible for managing security officers and ensuring site safety.*

After: > *Supervised 40 contract security officers across 10 sites, directing scheduling, licensing compliance, and performance expectations to maintain operational quality for a major client.*

The second bullet uses the language a recruiter actually searches for: contract officers, multi-site, scheduling, compliance, operational quality. It also gives them scale — 40 officers, 10 sites. Now they know what level of responsibility you actually held.

Before: > *Handled emergency situations and reported incidents.*

After: > *Led incident response, investigations, and compliance reporting under the Clery Act across a 24/7 campus safety operation serving multiple locations.*

"Led" is stronger than "handled." "Clery Act" is a specific, searchable credential. "24/7" and "multiple locations" communicate scope. And "campus safety operation" uses the language of the industry.

Before: > *Managed access control systems.*

After: > *Administered full access control infrastructure — HID, Lenel, Avigilon, and Verkada — managing credentials, alarms, permissions, and system integrations in coordination with IT and facilities.*

The first version gives me one vague verb and one vague noun. The second version names the actual systems, explains what administration meant in practice, and shows cross-functional collaboration. Every named system is a potential keyword match.

On metrics: be honest, be specific

You don't need to make up numbers. But you should go find the real ones.

Look at annual reports from your previous employer. Look at your own performance reviews. Think about the scale of what you touched — how many people, how many sites, how many incidents per year, what changed after you implemented something.

If you developed a new policy that reduced documentation errors, estimate the impact. If you ran emergency drills, say how many per year and how many people they covered. If you managed a budget, say the dollar range.

Recruiters and ATS systems both respond to specificity. Vague bullets are forgettable. Specific bullets are searchable.

On action verbs: vary them and mean them

Don't open every bullet with "Managed." Use the verb that's actually true.

For leadership: *Directed, Supervised, Led, Oversaw, Mentored, Built* For operations: *Administered, Coordinated, Implemented, Executed, Maintained* For improvement: *Developed, Streamlined, Redesigned, Upgraded, Reduced* For collaboration: *Partnered, Collaborated, Liaised, Supported, Briefed*

The verb you choose signals the level you operated at. "Assisted with scheduling" and "Directed scheduling across 10 sites" are not the same seniority. Make sure your verbs match your actual level of ownership.

The one-sentence test

After you write a bullet, read it out loud and ask: *would someone who has never met me know exactly what I did, at what scale, and what came of it?*

If the answer is no — if it could describe anyone who ever held that job title — rewrite it. A bullet that could belong to anyone belongs to no one.

What to do right now

Pick the weakest bullet on your resume — the one that starts with "Responsible for" or "Assisted with." Rewrite it using the framework: Action → Scope → Outcome. Add one specific tool, system, or credential you actually used. Add one number if you can find an honest one.

That's one bullet. Now do the rest.