Review confidence scores and suggested entries

What confidence means

A confidence score estimates how strongly available context supports a proposed classification. It is not an accuracy guarantee and does not determine whether work is legally or contractually billable.

High confidence can still be wrong when two clients share names, a meeting covers several matters, forwarding changes email participants, or captured activity belongs to the wrong active company. Low confidence can still identify real work that simply lacks enough context.

Review high-confidence suggestions

Check the source, time range, company, client, project, and description. Look for an existing entry covering the same work. If your company uses automatic nightly actions, confirm that its threshold and action match the risk of the workflow.

Review low-confidence suggestions

Use the source activity to identify the work. Add the missing client or project, correct timing, and write a clear description. Save as a draft when approval or billing classification is uncertain.

Build safer automation

Start with Save, not Save & Submit. Compare several weeks of results before lowering a confidence threshold or increasing automation. Audit exceptions, not only successful matches.

Report a persistent classification problem

Capture the source type, date, proposed and correct client/project, confidence score, and whether a mapping or integration rule applied. Do not include confidential source content unless support specifically requests a secure method.