Project Management Fundamentals at Work: Evidence from 100 Current U.S. Vacancies
Evidence date: 12 September 2026
Sample: 100 unique current U.S. vacancies from 92 employers
Source quality: 90 employer or public-sector first-party pages
Research design: balanced structured purposive sample, not nationally representative
Permanent identifier: https://doi.org/10.5281/zenodo.22728016
Archived report: Download the research report PDF
Executive summary
What do employers mean when they ask someone to support or manage a project? Across 100 current U.S. vacancies, the answer is practical and document-heavy. Sixty-nine roles required coordination of project execution. Sixty-eight required schedule maintenance. Forty-seven involved controlled documentation, 44 status reporting, 43 budget or financial support, 41 scope or requirements work, and 36 risk or issue tracking. These responsibilities appeared across all four U.S. Census regions and a deliberately diverse set of sectors.
The strongest pattern is not allegiance to one methodology or software product. It is the ability to keep a bounded project visible and decision-ready: clarify what is authorized, define scope, organize work, maintain a schedule, surface risks, coordinate stakeholders, report status, record decisions and changes, and close the loop with acceptance and handoff.
The evidence supports an artifact-first route into project work. A beginner benefits from building a connected control pack rather than memorizing isolated terminology. The pack should include a project charter, requirements and scope records, a work breakdown, a milestone and dependency schedule, a risk register, an issue log, a stakeholder map, a communication plan, a status report, action and decision logs, a change record, and acceptance and closeout evidence. Each document should have a blank template and a completed example based on one coherent fictional case.
This research also clarifies how two MTF programmes can serve different learner needs without competing on the same promise. The Professional Certificate in Project Management is the broader AI-augmented pathway across the profession, Agile and hybrid delivery, leadership, quality, procurement, crisis, strategy, portfolio and career themes. The new Professional Certificate in Project Management Fundamentals is designed as the narrower, more practical pathway for learners who want repeated practice with the core artifacts used to authorize, plan, control and report one everyday project. Neither replaces the other.
The research question
The study asked three connected questions:
- Which project duties, decisions and work products recur in current U.S. vacancies suitable for an early-career or individual-contributor learner?
- Can those requirements support at least 20 distinct practical capabilities without padding the course with broad leadership, Agile, procurement, portfolio or industry-specialist content?
- Does the evidence favor a cross-industry fundamentals course, or does it indicate that an IT, construction or other industry specialization would have a stronger and more coherent commercial case?
The study did not attempt to estimate national vacancy prevalence, predict a learner's salary, promise employment, measure MTF conversion, or reproduce a certification standard. It was designed to discover a defensible applied learning scope and identify the limits of the evidence.
How the 100 vacancies were selected
The final corpus is a dated cross-section captured as current on 12 September 2026. Eligible roles had a U.S. location or explicit U.S.-wide eligibility and recurring responsibility for initiating, coordinating, monitoring, reporting or closing a bounded project. The sample emphasizes project coordinators, project specialists, project analysts, assistant project managers and closely related individual-contributor roles. A generic coordinator or manager was accepted only when the posting clearly described bounded-project work.
Executive, director, programme, portfolio and PMO-leadership roles were excluded. So were records that were expired, inaccessible, non-U.S., duplicated, too vague to code, or inseparably dependent on clinical, engineering-signoff, construction-code, safety-critical, licensed-financial or other regulated judgment. Construction, healthcare, finance and public-sector roles could remain when their transferable project-control work was separable from specialist practice.
The quality controls matter because a simple search result can create a misleading sample. The final set contains 100 unique URLs and 100 unique deduplication keys from 92 normalized employers. Ninety records came directly from employer or public-sector career pages. Only seven came from public job boards carrying employer-supplied text and three from public recruiter pages.
Geography was deliberately balanced. The sample contains 20 Northeast, 20 Midwest, 33 South and 20 West roles. Seven U.S.-wide or remote vacancies were retained but were not assigned to a Census region. No single sector represents more than 18% of the sample. The largest groups are cross-industry business services and built-environment/professional services, followed by healthcare and life sciences, education, technology and digital services, energy and manufacturing, public sector, marketing and consumer settings, and smaller nonprofit, professional and financial-services groups.
These controls improve breadth and reproducibility. They do not turn the sample into a probability survey. All percentages below mean “observed in this 100-vacancy sample.”
What was coded
Each vacancy was reviewed for duties, outputs, methods, observable behaviors, tools, level, cadence, interfaces, authority and escalation. Positive codes were tied to a source record. “Not stated” remained unknown rather than being converted into a negative conclusion.
The coding distinguished an activity from an exact artifact label. For example, 36 vacancies described risk or issue work, but only three used wording that clearly supported an exact risk-register label and five supported an exact issue-log label. Employers often care about the function without naming the template. A course should therefore teach why the artifact makes the work executable, not claim that every employer demands the same document name.
Finding 1: the schedule is the most visible control surface
Schedule maintenance appeared in 68 vacancies. Project schedules were also the most common explicit work product. This is unsurprising but easy to teach badly. A schedule is not merely a list of dates. It is a reasoned model connecting work, sequence, dependencies, ownership, duration assumptions, constraints, milestones and evidence of completion.
The beginner's most useful progression starts before software. Define the deliverable, break it into manageable work, identify the activities required, show which activities depend on others, assign owners, estimate duration using stated assumptions, and select milestones that represent meaningful progress or decisions. Only then should the learner place the plan into a spreadsheet or project system.
The study also supports a distinction between baseline and forecast. The baseline is the approved plan against which change is controlled. The forecast is the current best estimate of what will happen. When the two diverge, a competent project professional does not quietly overwrite history. They identify the cause, explain the impact, recommend an action and, where necessary, request a controlled change.
Finding 2: coordination requires evidence, not just reminders
Execution coordination appeared in 69 vacancies, the largest duty family in the sample. The word “coordinate” can sound administrative, but the underlying work is consequential. It includes clarifying ownership, aligning contributors, collecting progress evidence, resolving routine blockers, following up on actions, preparing decision requests and escalating exceptions.
A practical learning experience should therefore turn coordination into a visible system. An action log needs a specific action, one owner, a due date, a status and an escalation rule. A decision log needs the question, options considered, the decision-maker, the decision, the rationale and any downstream change. A meeting agenda should be built around outcomes and decisions; minutes should record commitments and unresolved matters, not transcribe conversation.
The strongest test is whether another person can read the record and understand what must happen next. That is more useful than memorizing a definition of coordination.
Finding 3: scope and requirements protect the project from invisible growth
Scope or requirements work appeared in 41 vacancies. The evidence supports four different beginner capabilities that are often compressed into one chapter: eliciting requirements, defining boundaries, decomposing deliverables and maintaining traceability.
Requirements should identify the source, priority, rationale and acceptance evidence. Scope should state what is included, what is excluded, the deliverables, assumptions, constraints and acceptance criteria. A work breakdown turns deliverables into manageable components; it should not be a disguised task list copied from a previous project. Traceability then connects each material requirement to a scope element, acceptance test and approved change.
This chain prevents two common failures. The first is accidental omission: a stakeholder assumes something is included because nobody made the boundary explicit. The second is uncontrolled addition: useful ideas enter the plan without an owner, resource, schedule impact or approval. A practical course should show both failures in a worked example, then ask the learner to repair the records.
Finding 4: status reporting is a decision product
Forty-four vacancies described status-reporting work, and 25 named a status report as an output. Status reporting also connects to the broader stakeholder-communication signal, which appeared across the sample.
The effective status report is not a diary of completed activity. It answers the questions a sponsor or project lead needs to act on:
- What outcome and milestone are we trying to reach?
- What is complete, in progress or blocked, and what evidence supports that view?
- Where does the current forecast differ from the baseline?
- Which risks or issues matter now?
- What changed since the previous report?
- Which decision, approval or support is needed, from whom and by when?
- What are the next-period priorities?
A simple red-amber-green indicator can help readers scan, but the color must follow a defined threshold and be supported by facts. “Green” should never mean that the author hopes the project will recover. “Amber” should identify the consequence and recovery action. “Red” should be paired with a decision or escalation, not used as decoration.
Finding 5: risk and issue work is common even when template names are not
Risk and issue tracking appeared in 36 vacancies. Exact risk-register language was much rarer. This gap is educationally useful. The artifact should be introduced as a way to perform recurring work, not as a ritual required by every methodology.
A high-quality risk statement separates cause, uncertain event and effect. “Vendor risk” is too vague to act on. A better entry records the uncertain event, the consequence for scope, schedule, cost, quality or outcome, the trigger, the probability and impact criteria, the response, one owner, a due date and the residual exposure after response.
The learner must also distinguish a risk from an issue. A risk may occur; an issue is happening now. An assumption is a planning belief that must be tested. A dependency is an external condition or deliverable on which work relies. Mixing all four in one informal list makes escalation harder and status reporting less trustworthy.
Finding 6: stakeholder work should change the plan
Stakeholder communication appeared as a recurring output and interface across the corpus, while an exact “stakeholder map” label was uncommon. Again, the evidence supports the function more strongly than the name.
A stakeholder register should identify who is affected, what legitimate interest they have, how the project may affect them, what decision or information they need, and who owns the relationship. A map can prioritize engagement by influence and impact, but it should not profile protected or sensitive personal traits. The communication plan should then define purpose, audience, owner, channel, cadence, input evidence and escalation rule.
The map matters only if it changes action. A high-impact stakeholder who must approve a deliverable should appear in the schedule and acceptance plan. A stakeholder who supplies a dependency should have an owner and follow-up cadence. A group affected by a change should appear in the change impact and communication plan. These links turn stakeholder management from a kickoff exercise into a live control.
Finding 7: budget, resource and document control are part of fundamentals
Budget or financial support appeared in 43 vacancies, and resource coordination in 25. The course does not need to become a finance programme to respond. A beginner should be able to state resource assumptions, distinguish planned from actual or committed amounts, identify capacity constraints, and explain how a change affects the plan.
Document control appeared in 47 vacancies. As project facts move through spreadsheets, chat, documents, ticketing tools and dashboards, the learner needs a source-of-truth rule: which record is authoritative, who updates it, how often it is reviewed, how versions are identified, and how conflicting data are reconciled before status is published.
These controls become more important when AI assists with summaries or updates. An AI-generated status draft can be useful only when the underlying records are current, the source of each fact can be checked, and a named human reviews the output and owns the message.
A practical project-control pack
The evidence supports a connected set of original, tool-neutral artifacts:
| Artifact | Decision it enables | Minimum quality test |
|---|---|---|
| Project charter | Is this project authorized and worth doing? | Purpose, success evidence, sponsor, authority, constraints and assumptions are explicit |
| Requirements record | What must the outcome satisfy? | Each material requirement has a source, priority and acceptance evidence |
| Scope and work breakdown | What is included, excluded and manageable? | Deliverables and boundaries are clear; work packages are neither vague nor microscopic |
| Schedule baseline and forecast | When can the work credibly finish? | Dependencies, owners, estimates, milestones and variance are visible |
| Risk register and issue log | What uncertainty or current problem needs action? | Statement, impact, response, owner, due date and escalation are usable |
| Stakeholder map and communication plan | Who needs involvement, information or a decision? | Engagement follows legitimate project impact and authority |
| Status report | What does leadership need to know or decide now? | Evidence, variance, forecast, risks, decisions and next actions fit one page |
| Action and decision logs | Who committed to what, and why? | One owner, due date, status and decision rationale are recorded |
| Change record | Should the baseline change? | Impact across scope, schedule, resources and risk precedes approval |
| Acceptance and closeout record | Is the work accepted, handed over and closed? | Criteria, exceptions, owner handoff and remaining actions are explicit |
The blank template is only the starting point. The completed example should demonstrate internal consistency. If the scope changes, the schedule, risk register, stakeholder plan and status report must reflect that change. If a risk becomes an issue, ownership and escalation should move to the issue log and status report. If a stakeholder must approve a deliverable, their decision date should appear in the schedule.
Why the evidence favors a general practical course
The corpus supports at least 24 distinct capabilities across authorization, scope, schedule, risk, stakeholders, status, change and closeout. More than 70% of the recurring capability signals appear in at least three sampled sectors. No essential capability depends on a single industry or vendor. That is enough depth for a coherent 20-lesson core without adding broad topics merely to fill space.
Construction is a plausible future specialization because project controls are tangible and commercially important. It also brings contract interpretation, claims, estimating, building codes, safety, technical drawings and licensing boundaries. IT project management offers strong implementation demand but faces intense competition from vendor and Agile-framework courses and overlaps more with the existing MTF programme. On the current evidence, neither narrower audience provides a better risk-adjusted starting point than the cross-industry artifact-first offer.
This is a comparative model, not a measured-sales result. The existing MTF project-management page recorded only 115 impressions and two clicks in the latest three-month Search Console view. That sample is too small to estimate demand, conversion or cannibalization. It does reveal weak current non-brand discovery, which supports building an organic cluster around specific templates and worked examples rather than relying on one broad programme page.
Which MTF course should a learner choose?
Choose the Professional Certificate in Project Management if you want a broad AI-augmented view of project work, including Agile and hybrid delivery, leadership, quality, procurement, crisis, strategy, portfolio thinking and career development.
Choose Professional Certificate in Project Management Fundamentals if you want a concentrated, beginner-accessible route through the practical control pack: charter, scope, schedule, risk register, stakeholder map, status reporting, changes, acceptance and closeout, supported by blank templates and completed examples. The new programme's canonical link will be added here after its landing page is published and verified.
Limitations
Vacancies are employer-authored demand signals. They may describe an ideal candidate, omit informal work, change after capture or disappear. Publicly indexable applicant-tracking systems are easier to observe than less accessible employers. The study balances source type, geography, employer identity and sector, but it is not weighted by workforce size, establishment count or population.
The coding is conservative but still interpretive. Similar words can mean different levels of responsibility in different sectors. Exact artifact names are undercounted when a posting describes a function without naming the document. Conversely, a named artifact does not show how well it is used. Counts should be read as signals for learning design, not universal employer requirements.
The research does not measure course purchases, price sensitivity, completion, job outcomes or employer recognition. Marketplace enrolment figures and template catalogues used in the private commercial review are point-in-time context, not comparable sales. Future release decisions should be updated with MTF landing queries, template entrances, checkout starts, purchases, refunds and completion evidence.
Sources and research assets
The occupational context comes from the U.S. Bureau of Labor Statistics Project Management Specialists profile and the O*NET Project Management Specialists profile. Global directional context comes from the PMI Global Project Management Talent Gap report and is not used as a U.S. vacancy denominator.
The archived research package preserves the 100-record source inventory, inclusion and exclusion rules, record-level coding, aggregate calculations, limitations and cryptographic hashes. Its open PDF provides a stable research record for citation and later comparison.
Conclusion
Current U.S. vacancy evidence makes the practical core of project management unusually clear. Employers repeatedly need people who can coordinate work, maintain schedules, control documents, clarify scope and requirements, support budget and resource visibility, track risks and issues, communicate with stakeholders, report status and keep decisions moving.
The most useful beginner programme is therefore not another encyclopedic overview. It is a disciplined practice environment in which every artifact connects to the next decision. Learners should leave with one coherent project-control pack they can explain, update and defend. That scope is broad enough to serve multiple industries, narrow enough to remain distinct from MTF's existing wider project-management certificate, and specific enough to support organic discovery through genuinely useful templates and completed examples.