A construction manager resume should make the project context and your responsibility clear. Building type, delivery arrangement, scale and project stage help a reader understand the work. Project value is useful when authorized for disclosure, but it is not automatically budget authority or revenue you personally delivered.

This guide uses a fictional career progression to show how to organize titles, selected projects and supporting evidence. There is no single career path or layout that fits every general contractor, owner’s representative or construction-management role.

Fictional example: Douglas Pedersen and the employer, education, projects, training and recognition below are invented. Contact details are placeholders. The entries show superintendent work from 2009, project management from 2013 and construction management from 2018. They do not establish earlier carpenter experience, an 18-year career, real project outcomes or active professional credentials.

The sample uses separate dated roles at the same employer and two project entries. Grouping promotions or adding a project table are alternatives explained below. Replace every entry and skill rating with your own evidence.

Adapt the structure to your actual work. Preserve official titles and dates, label your project role, and check whether figures or client details can be disclosed. A resume example is a writing aid, not evidence that an applicant was hired.

Grouping promotions under one company can clarify tenure; separate entries can also work if the employer and dates remain clear. Neither arrangement guarantees that a parser will associate every field correctly.

Fictional grouped structure: Cedar Commercial Builders, followed by Construction Manager (2018–present), Project Manager (2013–2018) and Superintendent (2009–2013). Put each title beside its own actual dates and describe the responsibilities held during that period.

Check any parsed application fields rather than assuming the grouped format is always safer. The guide to how an ATS works explains the broader workflow. Do not claim that several entries at one company inherently look like job hopping.

Give more space to work that supports the target mandate. A field role may deserve detail when trade coordination, site logistics or safety work is directly relevant. Recent management work may need more space for budget, staffing or owner coordination.

Use these relevance checks instead of a fixed bullet allocation:

Two pages may suit a substantial career, but follow instructions and retain relevant evidence. A third page is not automatically unacceptable, and a project table is not mandatory. Reduce repetition before shrinking the font. See bullet-count guidance.

Explain project scale using the measures that matter for the target work and are permitted to disclose. A number does not prove responsibility by itself. In particular, coordinating a trade package differs from controlling the full project budget or employing all site personnel.

Fictional wording example: “Coordinated trade sequencing and owner reporting for a commercial fit-out, maintaining the look-ahead schedule and tracking unresolved RFIs.” Add actual project value, size or outcomes only when supported and permitted.

If reporting savings, distinguish a proposed value-engineering option, approved scope change, avoided cost and realized saving. Unused contingency is not automatically personal value creation. Use action verbs that reflect whether you led, coordinated, reviewed or supported the work.

A selected-project list can show breadth without repeating the same details in every employment entry. A table is one option; compact text entries may be easier to read or submit in some systems.

Illustrative rows only: the following names, values and sizes are fictional and are not completed client projects. Delivery method and pricing are kept separate because they answer different questions.

For each project, state your actual role and the stage in which you participated. Order selected work by relevance, keeping dates clear. Do not imply that every project listed was completed during your involvement.

Use text rather than a screenshot for the important details. If a table becomes cramped or parses poorly, convert it to short entries. No table or PDF guarantees reliable parsing; inspect the submitted result. See resume length guidance.

Safety measures require a defined scope, period and reliable source. A total recordable incidence rate uses recordable cases and hours worked; the BLS calculation guide gives the standard rate formula as cases multiplied by 200,000, divided by employee hours worked. A count of incidents is not the same as a rate.

An experience modification factor is an insurance measure, not an individual manager’s safety grade or a project TRIR. For example, Washington L&I’s explanation compares a business’s actual and expected losses. Use the applicable insurer or rating authority’s definition and identify the employer and rating period if disclosure is permitted.

“Zero lost-time incidents” and “zero recordables” are different numerical claims, and both need evidence. If records are unavailable, describe actual practices: coordinating toolbox talks, tracking corrective actions or escalating hazards. Do not substitute an invented zero or imply that training alone proves compliance.

Use the actual contract and delivery terminology, explaining abbreviations once when useful. Search behavior varies, so do not assume a recruiter always misses an abbreviation.

DBIA describes design-build as design and construction under a single owner contract. The delivery method is distinct from pricing or procurement. A guaranteed maximum price is not a separate delivery system, and participating in the project does not mean you personally held the contract.

State only arrangements you actually worked under and explain your contribution. Experience across several methods can be relevant, but it does not prove readiness for every contract structure. Project type, pricing, procurement and delivery method should not be collapsed into one ambiguous label.

Check the vacancy and applicable requirements. List actual training, certifications and licenses with their exact names, dates and status. A course-completion card is different from professional certification or a contractor license. See credential placement.

Describe software through the work you performed. Procore might support RFIs or submittals; Primavera P6 or Microsoft Project might support scheduling; Bluebeam Revu might support drawing review. No one product is a universal qualifier or proof of schedule ownership.

Building a baseline, updating activities, producing reports and reviewing someone else’s schedule are distinct responsibilities. Pull planning is a collaborative planning practice, not simply another name for using P6. Name only tools and methods you actually used.

Read the actual vacancy and map its requirements to evidence. This is an editorial example of that process, not a measured list of the most common contractor requirements:

Use the job description to select accurate terminology, then verify that each claim reflects your role. Do not add a credential, project value or contract method solely to improve a match score.

In Roleframe, review imported dates, financial figures and project labels. Check AI-assisted rewrites for exaggerated authority or invented safety outcomes. A match assessment is an editing aid, not the employer’s screening score.