Team Member Status Report
The team member status report is filled out by team members and submitted to the project manager on a regular basis. It tracks schedule, quality, and cost status for the current reporting period and provides planned information for the next reporting period. Status reports also identify new risks and issues that have arisen in the current reporting period. Typical information includes:
- Activities planned for the current reporting period
- Activities accomplished in the current reporting period
- Activities planned but not accomplished in the current reporting period
- Root causes of activities variances
- Funds spent in the current reporting period
- Funds planned to be spent for the current reporting period
- Root causes of funds variances
- Quality variances identified in the current reporting period
- Planned corrective or preventive action
- Activities planned for the next reporting period
- Costs planned for the next reporting period
- New risks identified
- New issues identified
- Comments
This information is generally compiled by the project manager into a project status report. The team member status report and the project status report are examples of work performance reports, as men- tioned in 4.5 Monitor and Control Project Work in the PMBOK® Guide – Sixth Edition. This report is sub- mitted at predefined intervals throughout the project.
Tailoring Tips
Consider the following tips to help tailor the team member status report to meet your needs:
- You can add a field for escalations to identify those areas that need to be escalated to the sponsor, program manager, or other appropriate individual.
- Some reports include a field to record decisions These would be transferred to the project decision log.
- If your organization has a robust knowledge management process you might consider adding fields for knowledge transfer or lessons These can then be transferred to the organization’s knowledge repository or lessons learned register.
Alignment
The team member status report should be aligned and consistent with the following documents:
- Project schedule
- Cost estimates
- Project budget
- Issue log
- Risk register
- Project status report
- Variance analysis
- Earned value status report
Document element | Description |
Activities planned this reporting period | List all activities scheduled for this period, including work tobe started, continued, or completed. |
Activities accomplished this reporting period | List all activities accomplished this period, including work that was started, continued, or completed. |
Activities planned but not accomplished this reporting period | List all activities that were scheduled for this period, but not started, continued, or completed. |
Root cause of variances | For any work that was not accomplished as scheduled, identify the cause of the variance. |
Funds spent this reporting period | Record funds spent this period. |
Funds planned to be spent this reporting period | Record funds that were planned to be spent this period. |
Root cause of variances | For any expenditures that were over or under plan, identify the cause of the variance. Include information on labor vs. material variances. Identify if the basis of estimates or the assumptions were inaccurate. |
Quality variances identified this period | Identify any product performance or quality variance. |
Planned corrective of preventive action | Identify any actions needed to recover cost, schedule, orquality variances or prevent future variances. |
Activities planned for next reporting period | List all activities scheduled for next period, including work to be started, continued, or completed. |
Costs planned for next reporting period | Identify funds planned to be expended next period. |
New risks identified | Identify any new risks that have arisen. New risks should be recorded in the risk register as well. |
Issues | Identify any new issues that have arisen. New issues should be recorded in the issue log as well. |
Comments | Document any comments that add relevance to this report. |