Committee member
The committee-member role appears late in the project lifecycle. It is designed for formal review participation around evaluation readiness, defense sessions, and committee-facing academic decisions.
Why this role is distinct
Committee work is not the same as day-to-day advising and it is not identical to evaluator scoring. A committee member usually joins when a project is already visible, already staffed, and close to its final academic checks.
That makes this role narrower but still important. Committee members need fast access to the project context, defense schedule, and the materials needed to participate confidently in the review process.
Fastest route through this guide
- Read Landing area to see the committee workspace.
- Read First actions after invitation acceptance for the initial work sequence.
- Read Core responsibilities to understand what committee members actually own.
- Read Operational checkpoints if you want the repeating late-stage review cycle.
- Continue to Evaluation and defense workflow for the broader defense process.
Landing area
- Dashboard:
/dashboard/committee-member - Key sections: dashboard, projects, schedule, reports, messages
First actions after invitation acceptance
- Confirm department access and review assigned committee work.
- Open the projects or reports that require committee attention.
- Check the upcoming defense schedule.
- Review supporting documents before the session.
- Follow coordinator messages or decision requests tied to the defense stage.
Core responsibilities
The committee-member role supports formal academic review once the project is already deep in the lifecycle.
Committee-stage review
- review the project context before the defense or final committee discussion
- understand team composition, proposal history, milestone progress, and submitted reports
- prepare for the academic questions or review concerns that may arise during the session
- help ensure that late-stage review decisions are based on visible project evidence
Defense participation
- follow the published defense schedule
- join the session with enough project context already understood
- participate in the review process in coordination with evaluators and staff
- support a clear, timely outcome rather than a delayed post-session cleanup
Decision support and traceability
- use the workspace to stay aligned with coordinator communication
- review reports or supporting records that explain the current project state
- help keep the final academic decision understandable and well supported
- avoid informal off-platform review where the department loses visibility
What the dashboard is designed for
The committee-member workspace is built for fast late-stage orientation:
- project context for committee review
- defense schedule visibility
- access to reports and supporting records
- messages connected to defense-stage coordination
- a focused dashboard instead of the wider operational surfaces used by staff
Operational checkpoints
Committee work is usually concentrated near evaluation and defense milestones.
Checkpoint 1: Assignment clarity
The first question is whether the committee member understands which projects and sessions require attention now.
Questions to answer:
- which project or defense items are currently assigned or visible
- whether the committee member has enough context to prepare before the session
- whether the schedule timing is clear enough to avoid last-minute coordination problems
Checkpoint 2: Review readiness
Committee participation is strongest when the project context is reviewed before the live session.
Questions to answer:
- have the key reports, project details, and supporting records been reviewed
- is the academic progress understandable from the visible record
- are there open questions that should be clarified before the defense begins
Checkpoint 3: Session participation
The committee-member role matters most when the defense stage is active.
Questions to answer:
- is the committee member prepared for the scheduled review session
- is the evaluation context aligned with what the staff and evaluators are tracking
- can the session move toward a clear outcome without missing evidence or context
Checkpoint 4: Outcome visibility
The platform should retain a visible academic record after the committee work is done.
Questions to answer:
- are the relevant reports and outcomes visible to the department
- did the final review complete inside the tracked workflow rather than outside it
- can staff follow up without reconstructing the session manually later
Practical handoff model
The committee member enters after earlier workflow owners have already moved the project close to final review.
| Phase | Primary committee-member job | Typical handoff |
|---|---|---|
| Late-stage preparation | review the project context and upcoming session needs | coordinator and advisor have already moved the project toward readiness |
| Defense-stage review | participate in committee-facing review and discussion | evaluators and staff remain active in the formal late-stage workflow |
| Outcome stage | leave the department with a clear, visible review outcome | reporting and oversight stay with staff-owned operational surfaces |
What success looks like
The committee-member role is working well when the defense-stage workflow reaches this state:
- committee participants can prepare without chasing context from multiple places
- defense sessions are supported by clear schedules and visible project records
- final review decisions stay connected to the tracked workflow
- coordinators do not have to manually reconstruct committee activity afterward
- students experience a credible and organized final review stage
Common mistakes to avoid in the docs
- Do not describe committee members as identical to evaluators. The roles overlap in late-stage review but they are not the same responsibility surface.
- Do not describe committee work as a day-to-day operational role. It is concentrated around review and defense activity.
- Do not imply committee members own advisor assignment, milestone feedback, or department setup. Those remain outside this role.
- Do not treat committee participation as informal. The product exposes dedicated late-stage surfaces so the process remains visible.
Best page after this one
| If you want to do next... | Go here | Why |
|---|---|---|
| Follow the broader late-stage process | Evaluation and defense workflow | It shows how committee review fits the formal defense flow. |
| Understand where committee work appears in the full journey | Project lifecycle | It places the role in the end-to-end academic sequence. |
| See how staff manage late-stage readiness | Staff oversight and assignment | It explains the operational layer behind committee-facing work. |