Assign roles and responsibilities

Practice PM-05 in the Project Management group. The basis is public-record, and the row asks for 3 pieces of evidence.

At a glance

Ref: PM-05
Process: Project Management
Basis: public-record
Source: Public abstract, 1.1 Fields of application
Evidence: 3 items
Gaps: 2 common

Evidence to keep

Project ManagementThe responsibility table with names and authority
Project ManagementThe role descriptions the firm uses
Project ManagementThe record of any delegation

Questions before you sign

Who holds each role on this project?
What does each role decide, and what does it produce?
Where has a role been delegated, and to whom?

The practice, in our words

Name the person who does each role the project needs, not the job title. The profile assigns tasks and work products to roles, so the file must show who holds each role on this project and what authority comes with it.

What it means in a VSE

Use a simple responsibility table: role, name, what they decide, what they produce. A role held by nobody is the most common cause of a missing work product. A role held by the same person in three projects is the most common cause of a late one.

In a firm of 25 people or fewer, assign roles and responsibilities has to earn its time. The test for PM-05 is not whether the team understands it but whether the artefact exists at the end of the project. Shrink the meeting. Shrink the document. Keep the record.

How to evidence it

Attach the artefacts above to the Assign roles and responsibilities row with the project name, the owner and the date. The anchor for PM-05 is The responsibility table with names and authority. A named person must produce it on request.

For PM-05, the reviewer will sample one live decision and ask for The role descriptions the firm uses. No artefact, no evidence. A file that depends on one person's mailbox is not a file for assign roles and responsibilities.

What an assessor samples

An assessor reads the assign roles and responsibilities practice, asks for its evidence and tests one project against it. For PM-05, the useful sample is the most recent project that used the practice, not the best one. A reconstruction written for the visit is a finding for PM-05 if the practice cannot be shown to have happened when it mattered.

Common gaps

Roles written as departments rather than people
One person holding every role with no recorded delegation

What changes from the 2019 report. For PM-05, project management is the spine the other practices hang from. The transition work is to make the plan, the progress reading and the closure exist as records rather than as habits.

Where the draft fits

The public abstract places assign roles and responsibilities inside one of the four processes the Intermediate profile covers. For PM-05, the draft clause numbering and wording are not public, so this page cites Public abstract, 1.1 Fields of application and does not quote the draft. The basis label for PM-05 says whether the practice is stated in the public record, named as a process in the series, or our reading.

Related practices

Source for this page: Public abstract, 1.1 Fields of application. Open the record and compare it with the PM-05 statement above. Retrieved 2026-10-22.