KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesDecoding the Group Report RubricProject Delivery · Principles of Project ManagementLesson 56/58← PrevNext →
GuidePublished 13 Aug 20269 min readBy Kevin Joginproject managementproject deliveryprinciples of project managementmarks
On this page

Ask about this page

KEVOS AIDecoding the Group Report Rubric

KEVOS knowledge first · trusted web sources when needed

Home/ Project Delivery/ Principles of Project Management

KEVOS® Project Delivery Handbook

Decoding the Group Report Rubric

A Format B cheatsheet translating the Uni Group Report marking rubric into concrete, actionable tactics.

8 min read1,703 words Guide 55 of 57Reviewed 2026-08-13
In this handbook article
  1. Rubric Breakdown
  2. Component 1 — Content (40 marks)
  3. The Seven Required Content Elements
  4. HD vs C vs P Treatment
  5. Content Self-Check
  6. Component 2 — Logic and Support (10 marks)
  7. Argument Structure Template
  8. Logic Self-Check
  9. Component 3 — Clarity of Written Expression (10 marks)
  10. Business Writing Rules
  11. The Paragraph Test
  12. Component 4 — Planning, Language & Grammar (10 marks)
  13. Required Structural Elements
  14. Word Count Bands
  15. Grammar & Spelling
  16. Component 5 — Collaboration & Teamwork (20 marks)
  17. What "Equitable Contribution" Means
  18. How Markers Detect Uneven Contribution
  19. Teamwork Self-Check
  20. Component 6 — Acknowledgement of Research (10 marks)
  21. Harvard Referencing Essentials
  22. Common Referencing Errors
  23. Reference Management Tools
  24. The 10-Point HD Self-Assessment
  25. Common Failure Modes at a Glance
  26. Key Takeaways
  27. References

Source and edition context

Source basis: This handbook article is adapted from the supplied file(s): 56. Decoding the Group Report Rubric.md.

Interpretation rule: Named scenarios, schedules, percentages, monetary values and thresholds are source examples or illustrative proposals unless an identified authority, contract or approved baseline makes them mandatory.

PMI edition context: The supplied notes primarily teach fifth- and sixth-edition process groups and knowledge areas. PMI currently publishes the PMBOK® Guide—Eighth Edition, which retains the principles and performance-domain foundation while presenting evolved, non-prescriptive process guidance. Historical counts in this article remain for source/course context, not as a claim about the current edition.

PRINCE2 edition context: The current PRINCE2 Project Management Version 7 uses seven principles, seven practices and seven processes, with explicit attention to people, sustainability, digital/data and tailoring. Earlier counts are retained only where the supplied source discusses an earlier edition.

A Format B cheatsheet translating the Uni Group Report marking rubric into concrete, actionable tactics. What does HD look like for each of the six rubric components, and where do groups typically lose marks?

Format note. Second of three rubric decoder guides for MPM411. This one addresses the Group Report — the 30% group-based business report on the Zoo Relocation case study. A dedicated full-length masterclass on the seven Content elements exists as a separate article; this guide is the compact operational cheatsheet.

Rubric Breakdown

The Group Report is marked across six components totalling 100 marks:

# Component Marks Relative Weight
1 Content 40 40% — dominant
2 Logic and support 10 10%
3 Clarity of written expression 10 10%
4 Planning, language & grammar 10 10%
5 Collaboration & teamwork 20 20% — second largest
6 Acknowledgement of research 10 10%

Two components account for 60% of the grade: Content and Collaboration. Groups that prioritise these first — and only then polish the other four — consistently outperform groups that invest evenly across all six.

Component 1 — Content (40 marks)

The Seven Required Content Elements

The rubric explicitly enumerates seven topics that must be analysed and explained:

# Required Element What it Means
1 Alignment with corporate strategy Link the project to a named strategic objective
2 Accountability & Responsibility RACI-style governance mapping
3 Organisation structure PMBOK taxonomy classification + project org chart
4 5x Processes + methodologies Five PMBOK process groups + methodology justification
5 9x Knowledge Areas All ten PMBOK knowledge areas applied to the case
6 Success measurement Multi-level success framework with criteria
7 Implementation Staging Plan Phased delivery with gates and rollback

Critical rule. Missing any single one of these elements caps Content at roughly C-band. All seven must be present and treated at HD depth for HD Content marks.

HD vs C vs P Treatment

Element Pass Treatment Credit Treatment HD Treatment
Strategic Alignment Mentions strategy Explains project-strategy link Uses theoretical framework, names strategic objective, maps benefits to strategic criteria
Accountability Says PM is in charge Provides responsibility list RACI matrix with singular accountability per decision
Org Structure Shows an org chart Classifies structure type PMBOK taxonomy + matrix analysis + friction-point prediction
Process Groups Lists the five Describes each briefly Shows overlapping/iterative nature + applies each to case
Knowledge Areas Lists all ten Defines each Applies each specifically to the case study
Success States on-time/budget Adds quality dimension Three-level framework (PM/product/benefits) + stakeholder dimension
Staging Draws a Gantt chart Adds phases Gates + rollback options + dual-ops protocols + stage criteria

Content Self-Check

Component 2 — Logic and Support (10 marks)

This component evaluates whether your argument is actually argued, not just asserted. Markers look for chains of reasoning where each claim is supported by evidence (from the case) or theory (from the literature) and connects to a clear conclusion.

Argument Structure Template

Every major claim in the report should follow this structure:

Claim → Evidence (case study or theoretical source) → Analysis (why the evidence supports the claim) → Implication (what this means for the project)

Weak (P-level): "The project needs a risk management plan."

Strong (HD-level): "The project's zero-casualty welfare mandate [claim] — which the CEO's letter treats as a binary constraint rather than a target [evidence from case] — structurally removes 'accept' as a legitimate risk response strategy for any welfare-impact risk [analysis], meaning the risk management plan must pre-commit to mitigation for every identified welfare risk regardless of calculated probability [implication]."

Logic Self-Check

Component 3 — Clarity of Written Expression (10 marks)

This is where groups routinely underperform because they treat business writing like essay writing. It is not.

Business Writing Rules

Rule Why
Topic sentence at the start of every paragraph Markers skim; the first sentence must carry the paragraph's main point
One idea per paragraph Multi-idea paragraphs lose points for organisation
Active voice preferred "The PM will implement the plan" not "The plan will be implemented"
No contractions "Do not" not "don't"
No rhetorical questions They read as filler
Consistent terminology Pick "Project Manager" or "PM" and stick with one
Minimal hedging "will" not "would likely hopefully"
No first person in most of the report Use "the project team" or "the report" rather than "we" or "I"

The Paragraph Test

Read each paragraph and ask: can I state the paragraph's main point in one sentence? If not, the paragraph has too many ideas and needs splitting.

Component 4 — Planning, Language & Grammar (10 marks)

Required Structural Elements

The rubric lists eight minimum structural elements:

  1. Cover Sheet
  2. Title Page
  3. Table of Contents
  4. Introduction
  5. Discussion
  6. Staging Plan
  7. Conclusion
  8. References

Trap. The Staging Plan is listed as a separate structural element from the Discussion. If you bury your staging plan inside the Discussion, you lose structural marks even if the content is excellent. Give it its own top-level section.

Word Count Bands

Word Count Variance Grade Band
0–10% HD / D
11–15% D
16–25% C
26–50% P
> 50% F

For a group of 3 students at 1300 words per student, the target is 3900 words (±10% = 3510–4290 words). This is tight. Groups routinely blow through the word count by producing excessive background material at the front.

Grammar & Spelling

HD requires "accurate spelling and correct grammar throughout." Use spell-check. Use grammar-check. Have at least one group member do a dedicated proofread after the final edit. Errors visible on a first read cap this component at C level regardless of content quality.

Component 5 — Collaboration & Teamwork (20 marks)

This is the second-largest component and the one most often sabotaged by poor group process.

What "Equitable Contribution" Means

The rubric uses the word equitable, not equal. Equitable means each group member contributes proportionally to their share of the work commitment, with the contribution visible in the final deliverable.

Behaviour Grade Impact
All members contributing substantively, voice harmonised HD
All members contributing, minor voice variations D
Most members contributing, one member notably light C
Two members doing most of the work P
One member carrying the entire report F

How Markers Detect Uneven Contribution

  • Sudden shifts in writing style or vocabulary between sections
  • Inconsistent terminology (one section says "PM," another says "project manager")
  • Section-level quality variance (Section 3 is brilliant, Section 4 is incoherent)
  • Formatting inconsistencies (different bullet styles, heading hierarchies)
  • Contribution logs or self-assessment forms (if required)

Teamwork Self-Check

Component 6 — Acknowledgement of Research (10 marks)

Harvard Referencing Essentials

The rubric requires Harvard referencing with:

  • In-text citations — (Author, Year, page if direct quote)
  • Reference list — alphabetical order, consistent formatting
  • Matching — every in-text citation has a matching reference list entry and vice versa

Common Referencing Errors

Error Fix
URL-only references ("Available at: www...") Include author, year, title, source with full metadata
Missing page numbers on direct quotes Always include page number for direct quotation
Different referencing styles mixed in one document Pick Harvard and enforce consistency
Citations in the text that don't appear in the reference list Cross-check before submission
Reference list entries not cited in the text Either cite them or remove them
PMBOK cited without edition number Always specify "6th edn" (or whichever you are using)

Reference Management Tools

Manual reference management at postgraduate level is a recipe for error. Use one of:

  • Zotero (free, open source, works with Word and Google Docs)
  • Mendeley (free, Elsevier-owned)
  • EndNote (paid, often provided free by universities)

The 10-Point HD Self-Assessment

Before submission, answer each question honestly:

  1. Are all seven Content elements present with HD-level depth?
  2. Does every major claim have evidence or theoretical support?
  3. Is the writing business-register throughout (no contractions, no rhetorical questions, active voice)?
  4. Are all eight required structural elements present?
  5. Is the word count within 10% of target?
  6. Is the voice harmonised across all sections?
  7. Is contribution equitable and visible?
  8. Are all references in consistent Harvard format?
  9. Is every in-text citation matched to a reference list entry?
  10. Has a dedicated proofread been completed in the final 48 hours?

Ten "yes" answers = HD territory. Eight "yes" answers = D territory. Six "yes" answers = C territory.

Common Failure Modes at a Glance

Failure Mode Cost
Omitting one of seven Content elements ~5–10 marks from Content
Defining Knowledge Areas without applying them Content capped at C
Staging Plan presented as a Gantt chart only Content loses ~3 marks
Uneven group contribution visible in prose Collaboration capped at C
URL-only references Referencing capped at P
Word count outside 10% Planning capped at D
Last-minute submission, no proofread Clarity and Grammar both drop
Copy-paste from PMBOK without paraphrase Referencing failure + plagiarism risk

Key Takeaways

  • Content (40%) and Collaboration (20%) together make up 60% of the grade — prioritise accordingly.
  • All seven required Content elements must be present; missing one caps the entire Content component.
  • Every claim needs evidence + analysis + implication structure.
  • Business writing rules are non-negotiable at postgraduate level.
  • The Staging Plan is a separate structural element — give it its own section.
  • Harvard referencing must be consistent, complete, and machine-assisted.
  • Equitable contribution requires a named final editor and harmonised voice.
  • Word count within 10% is strict — write lean from the start, not at the edit.
  • The 10-point self-assessment should be completed before submission, not after.

References

  • Project Management Institute 2017, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 6th edn, PMI, Newtown Square, PA.
  • University of South Australia 2015, MPM411 Principles of Project Management — Group Report Marking Guide, UniSA, Adelaide.

Continue learning

Postgraduate Project Management StudyHow to Score a High Distinction on a Postgraduate Project Management Group Report28 min readPostgraduate Project Management StudyDecoding the Examination Rubric10 min readPostgraduate Project Management StudyDecoding the Active Participation Rubric10 min readZoo Relocation Case AnalysisAnatomy of the Zoo Relocation Case Study18 min read

Prepared for the KEVOS® Knowledge Library. Apply the governing contract, approved project method and current standards to live work.

Continue learning

Decoding the Active Participation RubricGuide · Principles of Project ManagementNEXT LESSON →Decoding the Examination RubricGuide · Principles of Project ManagementHow to Score a High Distinction on a Postgraduate Project Management Group ReportGuide · Principles of Project ManagementAnatomy of the Zoo Relocation Case StudyGuide · Principles of Project Management
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®