See which student teams need a check-in.

Mid-project health checks collect students' own reports and surface teams for staff to review while there is still time to follow up.

Example Check-in view: each label comes with its reason and response count, and a team with no responses shows No data rather than Healthy.

How it works

  1. Prepare a check-in

    Staff

    Create a mid-project check for your published teams.

    Options
    Include teammate contribution ratings and requests for staff help, and choose whether comments appear without names.
  2. Answer through an individual link

    Students

    Students rate overall team health, fairness of workload, communication and meetings, and comfort raising issues, and can leave an optional comment.

    Before answering
    A notice explains what course staff can see.
  3. Review the signals

    Staff

    Read the reasons and response counts before deciding on follow-up.

    Evidence
    Healthy, Watch or At risk: signals from students' own reports, not grades.
    No responses
    Teams without responses show No data.
  4. Decide the follow-up

    Staff

    Read the team's responses in context, then decide what support is needed.

    Record
    Keep staff notes, record actions and mark them done.
    Messages
    Message a student or the team. It is saved as a follow-up action.

What students see

  • An individual survey link, with no account to create
  • Short ratings about their team's experience and an optional comment
  • Teammate contribution ratings and a request for staff to check in, when enabled
  • A notice explaining that course staff can see responses and that the check is for support, not grading

Frequently asked

What does a mid-project team health check ask?

Students rate overall team health, fairness of workload, communication and meetings, and comfort raising issues on a one-to-five scale. They can leave an optional comment. Staff can also enable teammate contribution ratings and a question asking whether they would like a tutor or coordinator to check in.

How are Healthy, Watch, and At risk decided?

Teamer uses rules, not AI, to highlight responses for staff review. Healthy means the available responses have raised no concerns under those rules. Watch flags mixed health reports, poor communication, low participation, or uneven contribution ratings. At risk flags a request for help, a comment mentioning a serious issue, low health reports, or low or very uneven contribution ratings. Teams with no responses show No data. These are signals to review, not findings about a student or a grade.

What can tutors see?

Staff with access can see team health summaries and open a team to review ratings, comments, and follow-up history. When tutorial-scoped visibility is enabled, tutors are limited to teams in their assigned tutorials. Coordinators choose that setting for the check.

Are students' health-check answers anonymous?

The check uses individual student links. Staff can choose to show comments without the respondent's name, but that is not a promise that the whole survey is anonymous. The student form explains what course staff can see before the student submits. It describes the check as support for the team, not grading.

How do staff follow up with a struggling team?

Open the team detail and review the reasons and responses before deciding what is needed. Staff can save notes, record actions, mark actions done, and mark the team reviewed. Staff with permission can also send a message to an individual student or the whole team from the health view, with that outreach recorded in the follow-up history.

Plan a check-in for your next project

Tell us when your teams start working together and how staff follow up today. We can walk through a health check for your course as part of a pilot.

Start a pilot

Just have a question? Email hello@teamer.university