Read your contribution and your team's insights¶
This guide follows the personal and team families in 06 Final Screens, including their empty, loading and recovery states. The frontend is still being built. Use the steps as the intended experience and confirm that the connected feature is available in your workspace. Current response gaps are identified below so sample design values are not mistaken for working product behavior.
Before you begin¶
Use the intended workspace and an account with HiveOrbit access. My Orbit needs permission to view your own information; Team Orbit needs team-view permission and a current employee/reporting identity. A manager may see a team summary without permission to open a person's wider employee view.
Have the period you want to investigate in mind. Distinguish when work happened from when a recognition-point entry was issued. If you are reviewing a disputed result, retain the original work reference and dates so support can investigate the same evidence.
Open My Orbit and choose a period¶
- In HiveOrbit's navigation, open My Orbit under Personal.
- In View context, choose Period, Selected period and History shown. The inspected examples use Month, August 2026 and six months; these are examples, not mandatory selections.
- Check Workspace calendar. Its timezone is context for this view, not a personal timezone-editing action.
- Choose Update view and wait while the view is updating.
- Confirm the selected period and history before interpreting the returned result.
The service supports calendar days, weeks, months and years. The inspected closed controls do not prove every picker option or interaction. There is no verified arbitrary start/end date picker, saved view or full-text search in this family.
History includes the selected period and preceding periods. For a single month, request one month of history when that choice becomes available in the connected frontend. A longer history also widens the current points-entry window. Historical views currently use the workspace calendar in effect when you open them; original calendar settings for every old period are not guaranteed.
Understand your contribution¶
Read the Contribution score, its period and availability together. Then review Contribution score by month, Evidence context, Contribution dimensions and What shaped this result.
| Item | How to use it |
|---|---|
| Current score | Treat it as a recorded contribution measure for the displayed context. It is separate from recognition points. |
| History | Compare supported periods. A gap means no supported measure is available; it is not zero and is not interpolated. |
| Change | Check whether the comparison is available. Selecting only one history period can leave no previous period in the returned comparison. |
| Dimensions | Read each returned value and effective weight. An unavailable dimension remains unavailable. |
| Confidence and coverage | Check the actual supporting detail. A confidence label alone does not establish that every source is healthy or complete. |
| Explanation | Read its caveat and the periods it uses before drawing a conclusion. Use supporting evidence only when available and authorized. |
The populated designs show source counts, coverage percentages and a comparable-role group. The current personal/team read does not fully supply those details. It must not show the illustrative counts or calculate a comparison from missing values. If the evidence panel is unavailable, retain that limitation when discussing the result.
View supporting evidence is an intended handoff. Its availability depends on the returned evidence and your access to the receiving view. The inspected frames do not establish a working frontend handoff or permission to every linked record.
Read supported signals¶
Signals summarize specific evidence. They do not assess a person's intention, health or worth. A missing signal does not prove the opposite, and an unavailable signal is not a negative finding.
| Signal | Meaning and prerequisites |
|---|---|
| Improving, Declining, Stable | With complete, closed and comparable periods, an increase of at least five in the contribution measure gives Improving; a fall of at least five gives Declining; a smaller change gives Stable. These labels have stronger requirements than a simple displayed difference. |
| Quality-safe speed | Both speed and quality are required for the role, the closed period has complete evidence, and both measures are at least 80. |
| Speed at quality risk | Under the same evidence conditions, speed is at least 80 while quality is below 70. Review the underlying work before acting. |
| Quality without speed | Quality is at least 80 while speed is below 70, with the same role and evidence conditions. |
| No strong pattern | The eligible quality/speed measures do not meet those three patterns. It does not mean there was no contribution. |
| Under recognized | Two consecutive, comparable closed months each have a measure of at least 80 and positive contribution evidence, with no badge, milestone, recognition level or achievement title in either month. It is a prompt for review, not a promised award. |
| Blocked | Verified evidence records a qualifying dependency, system failure or blocked cause outside the employee's control. It does not assign employee fault. |
| Overload | Comparable recorded workload exceeds an effective role standard in a complete, closed period. Insufficient or bounded evidence can make the comparison unavailable. |
| Review together | A qualifying decline or speed/quality concern warrants discussing the evidence, only when the required comparison is supported. It is not a blame or coaching diagnosis. |
Role, work type, complexity, model and comparison-group compatibility matter. A new role or incomplete comparison can suppress a signal even when two visible numbers differ. The current workload read uses bounded evidence; it deliberately withholds an exact workload comparison when that bound is reached.
Review recognition and points¶
- In My Orbit, review Recognition for the selected-period points total, lifetime points and recent recognition.
- Check the issue date of each recent award. The recent selection can include awards outside the chosen history window.
- Read milestone Progress and its target only when the target is available. No completion date is predicted.
- In Recent points, choose View points history for the intended ledger journey.
Contribution-category totals currently cover lifetime retained entries. Recent points cover the chosen history window, which may span several periods. Do not assume that the category totals, the current page's entries and the selected-period points total must match.
Recognition can be empty when the read is allowed but no records exist. It can instead be unavailable because the visibility policy cannot be verified. An unavailable panel does not establish that you received no recognition.
Use points history when connected¶
Points history is not yet connected correctly and may fail to load. The following describes its intended final-screen journey; successful loading through the application has not been established.
- Check View context and choose Update view if you change it.
- Read each entry's Issued date, Entry, Category, Points and Correction information. A negative correcting entry changes the net amount; it is not automatically a new penalty or a new work event.
- Use Next only when another page is available. The design also shows Previous and the current page; it does not provide a verified jump to a known last page.
- The calculation-detail variant places a selected entry beside Calculation details. Review the details actually supplied. The precise row-selection interaction remains unfinished in the connected frontend.
- Use the My Orbit breadcrumb to return to the overview when that navigation is connected.
The current ledger supplies points, issue time, rule identity, correction linkage and some control evidence. It does not provide a complete base-value/factor calculation, resolved role context, approved calculation decision or full correction proof. The populated design's sample breakdown must not be treated as actual returned evidence. Ask support about an unexplained entry using its original reference; these screens do not offer an edit, dispute submission, recalculation or award action.
The page is ordered by issue time. An entry issued now may relate to earlier work. Changing the period or ordering requires a fresh collection; pages are not a permanent snapshot if entries are added between reads. A visible page total must not be used as the complete selected-window total when more entries exist.
Review your current team¶
The team database query has an unresolved compatibility concern and has not been proved against the production database. Treat the following as the intended journey until the connected view is verified. Use Employee Contribution for the intended authorized View handoff.
- Open Team Orbit under People insights.
- Choose Period, Selected period, History shown and Sort direct reports. The inspected default example is Name A–Z.
- Check Workspace calendar, then choose Update view.
- Review Team contribution average, Direct reports, Evidence confidence and Team Contribution History together.
- Read Team Signals with its current-page denominator, then examine the individual rows in Direct Reports.
- Open View only where it is offered and your additional access permits it. Continue with Next when more direct reports are available.
The current roster includes active people reporting to you now. Selecting an earlier period does not recreate the team you managed then. History uses available measures across that current roster, while Team Signals counts only members on the current page. For example, “2 of 6” on one page does not mean two of all people in a larger team.
Team averages exclude unavailable scores. An unavailable member should remain visible without an invented zero. A change in the average can reflect changes in available members, measures or role context; do not attribute it to improved or declining team performance without checking those factors.
The current team summary does not verify combined source coverage or a common scoring basis for every member. Its private recognition restriction is intentional: Recognition isn't available in team view means historical visibility cannot be safely established there. Team signal evidence links are also withheld. Do not ask the frontend to reveal them simply because a person appears in the roster.
Recover from empty, limited or failed views¶
| What you see | What to do |
|---|---|
| No contribution records yet | Check the selected period, then choose another available period and update the view. This does not prove no work occurred. |
| No points entries for this period | Check both selected period and history length. No entries is different from an unavailable connection or an inaccessible panel. |
| Limited evidence | Review which information is actually available. Leave missing measures and comparisons unavailable; do not infer completeness from a sample panel. |
| No direct reports to show | Confirm the workspace and current reporting record. If the reporting line changes, update the view after it is available to HiveOrbit. |
| Loading or Updating | Wait for a result. Loading is not an empty or zero result. |
| My Orbit is temporarily unavailable | Choose Try again. These reads do not change work records or issue points. If failure persists, contact support. |
| Team Orbit is temporarily unavailable | The design retains your selected period and name order. Choose Try again; do not recreate reporting relationships as a workaround. |
| Access denied or expected view missing | Ask the administrator to check product access, the relevant view permission and employee identity. Repeated refreshes cannot grant access. |
| Evidence or calculation unavailable | Retain the unavailable state. Ask support to inspect the original record and current integration; a link or a populated design example is not proof of a complete calculation. |
For support, provide the workspace, view, selected period, history length, timezone, approximate time of the problem and the original record reference where available. Share private work details only through an authorized support channel. A local reload is not a promise of immediate source synchronization or a historical rebuild.