Recognition and supporting evidence¶
HiveOrbit connects recorded work with contribution explanations and recognition. Recognition shows badge awards shared through the organization's recognition view. Evidence Explorer helps an authorized reader inspect recorded work, contributors, available proof, calculation context and later corrections. Together they help people ask what was recorded, why it counted and what still needs explanation.
These are read-only views. Reading a record does not issue an award, approve a claim, change points, repair a source or correct the underlying work. Recognition points are distinct from the contribution measures in personal and team insights and department and organization insights.
The intended steps come from 06 Final Screens. The frontend is unfinished, and the current service has unresolved delivery, visibility and evidence-interpretation gaps. These pages describe design intent and source behavior, not a verified live experience. Confirm availability and approved access with your administrator. Start with the recognition and evidence guide.
Use contribution and recognition configuration to understand role expectations, policy versions, sharing choices and campaigns. The administration guide explains intended changes and their current limits; reading insights or evidence does not grant permission to change settings.
What each view is for¶
| View | Purpose | What it does not establish |
|---|---|---|
| Recognition | Read a person's badge, issue date, qualifying-month count and supporting evidence when supplied. | A ranking, entitlement to an award, full achievement history or evidence access. |
| Evidence Explorer | Find recorded contribution evidence using period context and the available filters. | That every work event has arrived, every filter/count is currently reliable or every person is within an enforced narrower audience. |
| Evidence detail | Inspect one recorded event, its contributor claims, work context, available explanation and later corrections. | A complete recalculation, a net points balance or automatic permission to view a supporting document. |
Users can understand their recorded work when granted access. Managers and executives can examine the evidence behind a discussion. Administrators and support can identify whether a question concerns access, missing records, proof, calculation or source correction. The feature's scope is evidence interpretation; it does not make employment decisions.
Access and sharing¶
HiveOrbit product access, a resolved employee identity and the particular view permission are required. The workspace must also meet its current setup and operating conditions. A saved setup or an existing award does not guarantee that the reporting service remains available after workspace access, required settings or source readiness change. Recognition access and Evidence Explorer access are separate. A recognition card can show provenance while its supporting-evidence action is absent because the reader lacks evidence access. A further document or work destination can have its own access requirements.
“Public recognition” in this product means the organization's recognition view, not an anonymous internet page. The current wall reader returns badge awards only when the currently effective visibility policy has organization sharing as its default. A missing policy or another default audience produces an empty wall; that result does not explain why it is empty. Selecting an old period still uses the current policy.
The implementation does not yet prove the intended per-award visibility history or current eligibility of every person shown. Evidence reads also need their intended person and license boundaries reconciled with the information they return. Administrators must verify those boundaries before relying on a department-only or licensed-person-only audience. These unresolved limits are documented privately for engineering; the guide does not promise that selecting a filter enforces confidentiality.
Understand the evidence lifecycle¶
- Work produces a recorded event with a source, occurrence time, work reference and contributor information.
- Contributor claims describe participation and the outcome attributed to a person. A claim can await required context.
- Available proof and recorded ledger entries provide calculation and eligibility context. Missing proof and a restricted supporting document are different conditions.
- Later correction evidence can refer to the original event. The detail view can show that later record and a reported adjustment without overwriting the original displayed facts.
The reading journey does not establish that every producing service, recognition projection or repair process is connected and running. A work item can exist while no corresponding evidence appears yet. A received event can wait for setup or employee eligibility checks, or fall outside an admitted processing period. Receipt, processing, recognition issuance and sharing are separate outcomes; evidence eligibility and recovery explains those distinctions. Source recovery and recognition administration have separate ownership; refreshing this page does not trigger them.
Read recognition in context¶
The wall selects awards by the chosen period. A badge's qualifying-month count describes the recorded qualification, not months within the currently displayed page. Its issue time is separate from the date of supporting work. Names and award labels come from stored recognition records and may differ from a person's current directory entry.
A supporting-evidence panel identifies the returned source and work reference. It is not proof that all qualification evidence is present, that the award has been independently reviewed or that the reader can open every related item. Other achievement types and campaign administration are outside this wall's current badge-only reader.
What the recognition types mean¶
The platform records several kinds of recognition. Understanding them helps explain a result even when that type is not available in the current recognition view.
| Type | Meaning | How to interpret it |
|---|---|---|
| Milestone | A recorded achievement instance, such as a first verified contribution, a qualifying month or a recognition-points threshold. | The achievement's definition determines whether it can occur once or have separate instances. |
| Recognition level | A recorded recognition-points threshold reached by a person. | It is distinct from their job grade, product access and monthly contribution measures. |
| Badge | Recognition for a qualifying contribution pattern under a badge family's rules. | Bronze, Silver and Gold correspond to 1, 3 and 6 qualifying months. Elapsed employment time alone does not qualify a month. |
| Achievement title | Recognition linked to a qualifying Gold badge. | The recorded title and its supporting badge have separate identities; a title is not a new job title or permission. |
An award keeps the definition and supporting context used when it was issued. It does not establish that every related record is currently accessible or that all later corrections have been reflected. Immediate recognition and monthly recognition use different checks; completing work is not a promise of an award. Recorded recognition, sharing in the wall and receiving a notification are separate outcomes. Questions about eligibility or a missing award need the period, relevant work and authorized support review, rather than repeated page refreshes.
Read evidence and points carefully¶
Complete proof means the reader found proof for each returned claim. It does not certify that all work was captured, that a document is accessible or that a calculation is independently correct. The current implementation can even mark a record complete when it contains no claims; inspect the claims rather than relying on the label alone.
The displayed claim points currently come from the latest recorded ledger entry for that claim. They are not necessarily its lifetime net total. Calculation factors and work context explain available recorded values, but the current view does not reconstruct a verified end-to-end equation. A correction's reported point change likewise needs review before it is treated as a net balance adjustment.
The original record can retain Not corrected while later correction evidence appears below. Read the correction history. A correction record's existence does not by itself establish that every downstream total has been rebuilt. Missing values should remain unavailable rather than becoming zero or a negative judgment about the contributor. For evidence details and employee filters, the current reader matches a person at the time the work occurred. Missing or ambiguous matches leave the person's display unavailable; they do not remove the recorded claim or prove that the person did no work. This matching rule does not resolve the separate sharing limits described above.
Decisions and unresolved limits¶
For a review, keep the selected period, timezone, source, occurrence time, person, claim and correction context together. Distinguish a missing record from missing proof and a failed page from a successful empty result. Discuss an inconsistency with the person responsible for the source work and your authorized support contact.
Current gaps affect delivery, subject visibility, some filters and counts, detail period labeling, correction ordering and calculation interpretation. The intended interface must handle them honestly until repaired and verified. The public guide and private engineering reference remain drafts; connected frontend behavior, deployed delivery and the initial reader walkthrough have not been accepted.