Skip to content

Running a Meeting

When you start a Meeting, Admire gives you a focused workspace for observing and scoring — with the context you need right alongside it.

Scoring is the heart of a Meeting — but it’s flexible. It’s up to you, the coach, to decide which skills to rate and how deeply, based on what you actually observed.

  • Record an observation. For each skill you choose to assess, record a score using its assessment type — a yes/no, a rating, or a set of trials. Scores build the person’s progress and count toward mastery.
  • Take notes as you score. Capture notes directly against a skill while it’s fresh, so the score carries the context behind it.
  • Get AI coaching help. If your organization has set up AI Assistants, you can get in-the-moment coaching guidance while you assess — what to look for and how to frame feedback.

You’re never required to assess everything: rate only what you had time to observe, and skills you skip are simply left untouched (see the overview).

When a skill has child skills — for example behaviours beneath it — you can work at whichever level fits:

  • Use the children as a checklist to guide your judgment of the parent skill, or
  • assess the skill directly without scoring each child.

Scoring every behaviour is optional — the children are there to help, not to add work.

Meetings support several kinds of notes, each with its own visibility, so you can be candid where you need to be and transparent where it helps.

Note typeWrittenVisible to
Agenda notesBefore the sessionEveryone — shared so all come prepared
Observation notesDuring or afterShared when you choose to
Supervisor notesAny timeSupervisors and observers only
Personal notesAny timeOnly you

The session view shows previous context — past observations and recent notes — so you can see how the person has trended without leaving the page. People being observed can contribute to the session’s notes even without full edit access.

A Meeting moves through a simple flow — planned, run, then signed off — and can be cancelled along the way or reopened after it’s done:

stateDiagram-v2
  direction LR
  [*] --> Pending: plan
  Pending --> Started: begin session
  Started --> Done: complete and sign off
  Done --> Started: reopen
  Pending --> Cancelled
  Started --> Cancelled
  Done --> [*]
  • Pending — planned but not yet started.
  • Started — in progress; you’re capturing observations and notes.
  • Done — completed and signed off.

Completing a Meeting marks it as done and locks in the observations you recorded. When you finish, you (and optionally the person) can add a digital signature to confirm the session took place and the record is agreed. Signing moves the Meeting to done.

If you need to change a completed Meeting — fix a score, add a note, or capture something you missed — you can reopen it. Sign off again once you’re done.

Completed observations feed the person’s progress and your reports.