Advisor
:::tip Use this page when You are documenting the role that guides students, reviews proposals and milestones, and keeps assigned projects moving. :::
The advisor role focuses on guiding assigned students and keeping projects moving through review and milestone checkpoints.
Why this role is pivotal
The advisor is where department process becomes direct academic supervision.
This role sits closer to the actual student work than the department head or coordinator. In practice, the advisor is the role that most directly shapes whether a project improves through feedback, reaches each milestone on time, and becomes genuinely ready for evaluation and defense.
Fastest route through this guide
- Read Landing area to see where advisors start.
- Read First actions after invitation acceptance for the first useful workflow.
- Read Core responsibilities to understand the advisor's real ownership zone.
- Read Operational checkpoints if you want the repeating review cycle.
- Continue to Milestone delivery and advisor review for the deeper review workflow.
Landing area
- Dashboard:
/dashboard/advisor - Key sections: my-projects, students, evaluations, schedule, announcements, messages
First actions after invitation acceptance
- Review assigned projects and active students.
- Check pending reviews and evaluation duties.
- Open upcoming schedule items.
- Review student submissions and attach feedback.
- Keep communication channels active with students and the department.
Core responsibilities
The advisor is not just a reviewer. This role owns the quality and continuity of supervised project progress.
Direct supervision
- guide assigned students from active project work through milestone completion
- review proposals or early project context when that supervision signal is visible
- keep each project moving through academically valid deliverables rather than only file uploads
- make sure students understand what to revise next and why
Review and feedback control
- inspect milestone submissions in the advisor review queue
- add actionable feedback, including optional review attachments
- decide when a submission should be revised and when it is ready for approval
- approve milestone work only when it is strong enough to unlock the next stage
Readiness support
- watch for students or groups that are falling behind repeatedly
- keep late-stage projects strong enough for evaluator review and defense preparation
- maintain schedule awareness for evaluation and defense related duties
- coordinate with department staff when project progress indicates broader intervention is needed
What the dashboard is designed for
The advisor workspace includes:
- assigned project and student visibility
- pending proposal and milestone reviews
- evaluation-related responsibilities
- schedule awareness
- feedback entry with optional attachments
Operational checkpoints
The advisor role usually works in a repeating supervision loop instead of a high-level management loop.
Checkpoint 1: Assigned-project clarity
The first question is whether the advisor clearly understands which students and projects need attention now.
Questions to answer:
- which projects are active and require immediate review
- which students are waiting on feedback or approval
- which milestones are approaching due dates without enough progress
Checkpoint 2: Review quality
Advisor work is strongest when feedback is specific enough to improve the next submission, not just reject the current one.
Questions to answer:
- is the feedback concrete enough for the student to act on
- is this submission ready for approval or still missing essential quality
- would approving this milestone create problems in the next stage
Checkpoint 3: Revision loop health
Some projects do not fail because students never submit. They fail because the feedback loop becomes slow, vague, or repetitive.
Questions to answer:
- are the same issues recurring across multiple revisions
- is the student getting enough direction to improve efficiently
- should the advisor escalate concern because the project is no longer only a local review issue
Checkpoint 4: Late-stage readiness
As the project approaches evaluation and defense, the advisor's role shifts from milestone review into readiness support.
Questions to answer:
- is the project mature enough for evaluator review
- are required deliverables and supporting materials in good shape
- does the student group appear ready for the defense stage, not just the next upload
Practical handoff model
The advisor sits between staff assignment and final evaluation.
| Phase | Primary advisor job | Typical handoff |
|---|---|---|
| Project activation | understand assigned project context and student needs | coordinators remain responsible for staffing and department movement |
| Milestone delivery | review submissions, give feedback, approve quality work | students revise and resubmit based on advisor direction |
| Late-stage preparation | prepare the project for evaluation readiness | evaluators take over formal scoring and review |
| Defense context | support readiness and academic continuity | coordinators and evaluators own the formal defense workflow |
What success looks like
The advisor is doing the role well when the supervised projects reach this state:
- students understand what to do next after each review cycle
- milestone approvals reflect real academic readiness, not rushed throughput
- repeated revision loops are identified early rather than normalized
- projects approach evaluation with fewer preventable quality gaps
- students arrive at late-stage review better prepared because advisor guidance has been consistent
Product snapshot
Onboarding note
An advisor should be able to enter the platform and immediately understand which students and projects require action. That is the main purpose of this role's landing experience.
Common mistakes to avoid in the docs
- Do not describe the advisor as only a milestone approver. The advisor is the main supervision layer across sustained project progress.
- Do not reduce review to approve versus reject language. Feedback quality and revision clarity are central to the role.
- Do not present the advisor as the owner of evaluator assignment or staff monitoring. Those remain coordinator and department-head concerns.
- Do not imply the advisor disappears before defense. The role still matters for readiness and academic continuity late in the process.
Best page after this one
| If you want to do next... | Go here | Why |
|---|---|---|
| Follow advisor review work in detail | Milestone delivery and advisor review | It covers submissions, feedback, approval, and resubmission. |
| Understand the full academic process | Project lifecycle | It shows how advisor work fits across the full journey. |
| Understand evaluation-stage crossover work | Evaluation and defense workflow | It covers the later stage where advisors often remain involved. |