Labeling & Feedback
Labels are how operators tell Gaard whether a classification was right. This guide shows how to attach feedback labels from the web app and the API, and how those labels feed back into model quality.
Why feedback matters
Section titled “Why feedback matters”Every classification carries a model-derived risk level, but only a human knows the ground truth. A feedback label records that ground truth against a specific result: was this alarm real, or was it a branch moving in the wind?
Labeled results give you three things:
- Measured accuracy. Confirmed true and false positives let you quantify how the model performs on your cameras and scenes, not a generic benchmark.
- Tuning signal. Systematic false positives on a camera are the input to threshold changes and exclusion zones: you cannot fix what you have not measured.
- Training data. Labeled clips are the highest-value examples for improving the model over time. Feedback closes the loop between operators and the classifier.
Labeling is quick and additive: label the results you are confident about, and skip the rest. Even a small, consistent labeling habit sharpens the accuracy picture for your tenant.
Feedback labels
Section titled “Feedback labels”The four standard feedback labels describe the relationship between what Gaard flagged and what actually happened:
| Label | Meaning | Use when |
|---|---|---|
TP | True positive | Gaard correctly identified a real threat. |
FP | False positive | Gaard flagged the video but there was no real threat. |
FN | False negative | Gaard missed a real threat. |
TN | True negative | Gaard correctly classified the video as safe. |
If you do not need the full confusion-matrix vocabulary, the simpler true and false labels are also accepted.
Alongside feedback labels, Gaard ships a set of descriptive standard labels (categories such as person, vehicle, animal, and plant, plus environmental factors like rain and wind) that let you record what was in the clip rather than only whether the alarm was correct. See the Labels reference for the complete list returned by the API.
Custom labels
Section titled “Custom labels”Standard labels rarely cover every operational distinction a team cares about: a specific gate, a known vehicle, a recurring nuisance. Custom labels are free-text labels you define for your own tracking.
- Create a custom label inline the first time you need it: type a new value into the label selector and add it.
- Custom labels are scoped to your tenant. Once created, a custom label is remembered and offered as a suggestion the next time you label a result.
- Any string value is accepted and stored. Custom labels also appear in the list returned by the API, so they are available to integrations as well as the web app.
Label from the web app
Section titled “Label from the web app”You label results while reviewing them, so feedback is a natural part of the review workflow rather than a separate chore.
-
Open a classification in the review workspace and select the clip you want to label.
-
Open the Score tab. The label selector and comment field sit alongside the per-clip scores, so you can see the model’s confidence while you decide.
-
Select one or more labels. Choose from the standard labels or start typing to create and apply a custom label. Selections save as you make them.
-
Add a comment (optional). Use the comment field to explain the label (for example, “False alarm) wind moving a branch”. Comments are stored with the label and are visible to teammates reviewing the same result.
To browse and manage everything your team has labeled, open the Labels view. It lists labeled results with filtering, and it is also where you export labels as CSV or build a dataset: see Exporting Data.
Give feedback on a clip
Section titled “Give feedback on a clip”The Feedback section of the Score tab asks what you saw, not whether Gaard was right. You do not need to know what the model concluded to answer it.
-
Answer “Is this an intrusion?” with Yes or No.
-
If you answered Yes, answer “Is this a real incident?” An intrusion that was authorised (a contractor, a scheduled test, a keyholder) is still an intrusion, but not an incident. The question only appears for a declared intrusion.
-
Add a comment (optional) to explain what you saw.
-
Submit. The labels you selected in the labels section above are attached to the feedback as a snapshot, so there is no need to repeat them.
Submitting does not close the clip or move you on: you stay where you are and can submit again. Feedback is append-only, so a correction is a new submission and both are kept.
Gaard works out on its own whether it agreed with you, and records that as the verdict. You never enter it. When a clip cannot be assessed, for example because you submitted while classification was still running, the verdict is shown as Not assessable rather than being guessed.
Everything your team submits is listed in the Feedback view, which covers your whole history rather than a fixed time window. The same feedback can be submitted by integrations: see the Feedback API.
Label from the API
Section titled “Label from the API”Integrations can label results programmatically, which is useful when an upstream alarm platform or operator tool already knows the outcome.
Attach one or more labels and an optional comment to an existing classification with its classify_id:
curl -X POST https://vision.gaard.ai/api/label/66436fc66d24ab9cf81140eb \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{"labels": ["FP"], "comment": "False alarm - wind moving a branch"}'To discover which labels are available for your tenant (standard and custom) list them with OPTIONS /api/label.
For the full request and response schema, including field types and the recommended label values, see the Labels reference.