CAL Individual Contribution Board

Each Friday creates a new weekly score for every student. The project-final contribution score is the average of those weekly scores, not a running total. Historical XP is shown separately as context.

0students tracked
0valid weekly logs
0logs needing update
0project average so far
Fri 8 Maynext log check 18:00 AEST

Individual Accountability Table

Current week score is generated every Friday. Final project score is the average across all scored weeks.

Member Group Current Week Project Average Task Delivery Friday Log Evidence Current Focus Next Deadline Historical XP

Scoring Rules

Use this rubric every Friday. A new weekly score is appended each week; the project-end score is the average.

Weekly Formula: 100 Points

  • 60 points task delivery: completed required task with usable evidence by deadline.
  • 30 points Friday personal log: valid individual log checked every Friday at 18:00 Australia/Melbourne.
  • 10 points evidence quality: paths, ownership, usefulness, and review readiness are clear.
  • Each Friday produces one new weekly score from 0 to 100. Historical XP stays separate.

Final Project Score

  • Final score = average of weekly scores.
  • Do not sum weekly scores; long projects should not inflate raw totals.
  • Unexcused missing weeks count as 0 in the average.
  • Zaimao can mark an excused week; excused weeks are excluded from the average.

Task Delivery Score

  • 60: on-time, usable, linked evidence or accepted deliverable.
  • 40: on-time but partial or needs reviewer clarification.
  • 36: useful evidence submitted late and still reviewable.
  • 25: blocker documented before the deadline with owner, what was tried, help needed, and next date.
  • 0: no evidence, no blocker, or task past due without update.

Friday Log Score

  • 30: valid log before Friday 18:00.
  • 20: valid log submitted late before the next Monday 09:00.
  • 5: template exists but minimum content is missing.
  • 0: no log file.
  • A valid log needs 2-5 work bullets, at least one evidence path or blocker note, next actions, and help needed if blocked.

Evidence Quality Score

  • 4 points: evidence paths are specific and openable by the team.
  • 3 points: another group can understand or reuse the output.
  • 2 points: owner and shared-credit split are clear.
  • 1 point: reviewer can tell what changed this week.

Friday Check Workflow

  • Friday 18:00: scan individual log folders and current task board.
  • Friday after check: append one weekly score row per student.
  • Next 48 hours: students can submit corrections with evidence paths.
  • Next Monday: unresolved missing logs remain in that week's score unless Zaimao accepts a correction.

Fairness Rules

  • No evidence means no verified credit, but a well-documented blocker still counts.
  • Logs are not scored by length; short, factual, linked logs are best.
  • Attendance alone is not enough for task credit.
  • Group artifacts need a credit split before assigning full individual credit.