Read recognition and explore supporting evidence¶

This guide follows the intended 06 Final Screens journey. The frontend is still being built, and the current service needs delivery and access-boundary verification plus fixes to some filters, counts and explanations. Use these steps when the feature is available in your workspace; the designed screens do not establish that the connected experience already works.

Before you begin¶

Open the correct workspace with HiveOrbit access. Recognition and Evidence Explorer require separate permissions. If a destination is missing, ask the administrator to check your product access, employee identity and permission for that view. Access to an organization dashboard or a recognition card does not automatically grant evidence or document access. HiveOrbit must also meet the workspace's current setup and operating conditions; an authorized administrator can investigate a service that is not currently enabled.

Check the displayed Workspace calendar before interpreting dates. The examples in the inspected designs use Africa/Lagos; your workspace's calendar is authoritative. The service supports days, weeks, months and years, but open picker options, mobile interactions and a connected prototype were not verified in this pass.

Administrators should resolve the current sharing-boundary limitations described in the overview before using these views for a restricted audience. Choosing a person or category filter is a way to refine information, not a permission change.

Open the recognition wall¶

1. Choose Recognition under Explore in the HiveOrbit navigation.
2. In View context, choose Period and Selected period.
3. Choose Sort by. The intended choices are Newest first and Oldest first.
4. Check the workspace calendar, then choose Update view.
5. Read Recognition shared this period and the returned cards. Use Previous and Next when available to move through the results.

Recognition uses one selected period. There is no history-length control in this journey. The current reader supplies badge awards only, so the inspected screen does not show a recognition-type selector. Do not expect another award type, a create-award action, reactions or an export action from this page.

The summary shows recognition entries, available recognition type and an issue-date summary. A date taken from the current page is not necessarily the newest award across every page or sort order. Read the card dates and chosen order before quoting it. Loading placeholders are not measured zero values.

Read a badge and its supporting evidence¶

Read the person's name, award title, badge level, qualifying-month count and recognition date together. The issue date tells you when recognition was recorded, while the supporting work may have occurred earlier. “Shared with your organization” describes the intended audience; it is not a statement that the award is published on the internet.

When the card contains Supporting evidence, review the source, related work and explanation. Choose View supporting evidence only when that action is available. Recognition permission alone is insufficient: the intended action also requires access to Evidence Explorer. If no action appears, keep the available context and ask for the appropriate access rather than trying to construct a destination.

An absent evidence panel does not establish that an award has no basis. It means the page has not supplied that supporting item. The current wall does not reconstruct every historical sharing decision, and complete automated wall population has not been verified.

Find recorded work in Evidence Explorer¶

1. Choose Evidence Explorer under Explore, or use an authorized View supporting evidence action when supplied.
2. For a list search, set Period, Selected period, History shown and Sort in View context.
3. Check the timezone and choose Update view. Wait for the selected view to finish loading.
4. Under Refine evidence, choose from the filters actually available in this view.
5. Read the result rows and use View on the evidence you want to inspect. Use Previous and Next for available continuation.

The designs show closed filter controls, not an opened picker or a separate filter confirmation. They do not establish a save-filter step, free-text search, bulk selection or a create/import action. Clear filters removes the optional refinements; it does not remove evidence.

The table brings together evidence/work, people, source, outcome, occurrence, proof, correction state and the View action. A record can contain more than one contributor. Check the detail before assigning its entire outcome to a single person. The current reader matches contributors to employee records at the event's occurrence time. If no single match can be established, the name remains unavailable and an employee filter may exclude that event. Clear the filter to inspect the available authorized records; do not guess the person or treat the missing name as an empty claim.

Filter choices and counts are based on the loaded evidence window. Each filter's counts can describe alternatives while leaving that filter's own selection out. Some current counts and dimension/recognition associations need correction. The total can also decrease as you move forward through pages. Treat the rows as an inspection aid, not an accepted organization-wide statistical report; do not infer a known last page from Page 1.

If the page asks for a shorter period, reduce History shown or select a narrower period and update the view. Adding a person filter may not solve it because the service limits the evidence it loads before applying the optional filters.

Inspect an evidence record¶

1. Choose View on the intended row.
2. Confirm the work title, contributor, occurrence time and Evidence overview match the item you intended to open.
3. Read Contributor claim for each contributor's participation, claim, claimed outcome, available points, processing state and proof action.
4. Read Why this counted for the available calculation and control explanation.
5. Read Work context, then Correction history, before reaching a conclusion.

The detail view shows Period, Selected period, Correction order and Update view. It does not have the list's history-length selector. The current service retrieves a specific record by its identity even when its occurrence is outside the selected period, so check Occurred rather than assuming the period label proves the record falls within that period.

View related work is conditional on a supplied destination. It opens the related work's own experience and access rules. Use the Evidence Explorer breadcrumb to return to the list; the unavailable companion also offers Back to evidence. A connected implementation still needs to preserve your list context through those handoffs.

Understand proof and calculation states¶

The supporting document used to assess controllability and the broader claim/calculation proof are separate. The current data can restrict the first while still supplying the second. The final design's general restricted treatment needs this distinction resolved; do not promise that all proof actions are hidden or that one available link grants access to everything.

The Control assessment explains whether the recorded cause was within the contributor's control and how the record is described as affecting the result. A non-penalizing or pending explanation is not an independently verified recalculation. Use it with the available evidence, not as a judgment about the person's effort or intent.

Manager, department and eligibility information inside recorded proof describe the retained context for that proof. They can differ from today's directory. Missing work timing, quality or dependency information must not be inferred from a populated example. The current reader can label absent rework information as No rework, so that label alone does not prove the source explicitly verified it.

Review later corrections¶

Read each Correction history row's occurrence, update type, reason, reported point change and available proof. A later record can explain a change while the original summary still says Not corrected. The original event and the correction remain different records.

Use Correction order and the correction section's own Previous and Next controls where available. The current reader has an unresolved oldest-first ordering issue; compare the displayed dates before assuming ascending order. The page count and proof fallback also need verification in sparse cases.

For example, a displayed original entry of 64 and a later row of −8 do not, by themselves, prove that the currently accepted net balance is 56. The reader selects ledger entries and does not reconstruct every adjustment or prove that all downstream projections have caught up.

These screens have no submit-correction action. If a fact looks wrong, keep the workspace, source, related work, occurrence time and observed discrepancy together, then ask the responsible source owner or authorized support contact to investigate. Include only information the recipient is entitled to see.

Recover from empty, missing or failed views¶

This is a reviewable guide for the intended journey. Connected navigation, access enforcement, corrected filters/counts, proof destinations, mobile behavior and the initial reader walkthrough remain unverified.