Understand case, project, meeting and leave facts¶
HiveAI has read-only tools intended to help you find relevant work and check a small set of facts from its owning application. They cover due cases, project activities and milestones, meeting starts, and leave requests. Reading these facts does not approve, complete, reschedule or change the underlying work.
Current availability: the application remains in progress. Some facts from cases, projects, meetings and leave records do not yet reach the assistant correctly. Use the owning application's current record for decisions. This page explains the facts and their limits; it does not promise a complete assistant answer or confirm that the experience is available in your organization.
Choose the right kind of information¶
A list of work items answers a different question from an organization metric. Ten returned cases are ten items in that result, not necessarily all cases in the organization. An adoption percentage, a dashboard section and an executive briefing have their own definitions.
Use the organization-intelligence guide for management measures and briefing guide for produced briefings. The current briefing composer does not automatically include these four fact lists.
Check access and scope¶
You need the relevant HiveAI capability, current organization access and permission to read the source information. A manager or executive title does not grant access to every case, project, meeting or leave record.
The tools retain source restrictions. Protected HR cases need their additional authority; project membership matters; meeting facts require participation and eligible product access. Leave information is limited to the permitted person and current organizational scope. These reads do not reveal hidden records merely to explain why they were omitted.
Confirm the organization and intended work before using a result. Never treat a limited list as a list of everyone else's work.
Describe the question and time period¶
Identify the type of work, the dates you mean and whether you need work due within those dates or earlier work that remains outstanding. Include your timezone when a day boundary matters.
The tools work with exact time boundaries. Their fact windows do not use the dashboard's historical-period rule. More importantly, the different sources apply the window differently. A heading such as “this week” is insufficient without the selection rule.
| Source | What the period selects | Important distinction |
|---|---|---|
| Cases | Open cases with a due date; due dates within the period or earlier outstanding dates according to the selection | Closed cases and cases without due dates are absent |
| Projects | Eligible execution items and milestone gates with due or target dates | An activity is not a whole project; completed work is outside the selected active states |
| Meetings | Published, compliant meeting-series starts under the selected date rule | A series start is not an individual recurring session or a follow-up deadline |
| Leave | Eligible requests whose effective dates overlap the period | The accompanying balance is current, not the balance during that historical period |
Broad open, active or upcoming selections can include dates before the period starts. An overdue selection uses dates before the requested start, while an urgency label can be calculated against the current time. Those are different comparisons.
Interpret case facts¶
The case source supplies a reference, title, current status, due date, overdue indication and your assignment relationship. It omits case notes and party details. The priority is a fixed normal label in this fact path; it is not an independent assessment of case risk.
Only open cases with a due date qualify. Confidentiality, participation and protected HR scope can remove cases from the result. A missing case therefore does not establish that the case was deleted, completed or never existed.
Use the case guide and current case detail to check the actual issue, permitted next action and deadline. A due-case fact does not authorize an HR decision or disclose a protected notice.
Interpret project facts¶
Project results combine eligible execution items with milestone gates. Read the item type before counting or acting: several results may belong to the same project.
The source uses project ownership or membership to establish visibility. Being assigned an individual activity does not, by itself, establish visibility through this particular read. State, due date and your relationship provide context; they do not prove that a milestone has been achieved or reviewed. This fact path does not return the activity's business priority.
Consult the project guide for current execution and milestone state. The assistant's returned reference must be resolved to the right project context; a complete user-facing deep-link journey remains unverified.
Interpret meeting facts¶
Meeting facts describe published, compliant plans where you are recognized as an internal participant. They contain the title, scheduled start, publication status and participation relationship. They do not include recordings, transcripts or meeting artifacts.
The read does not expand recurring plans into all their sessions or remove a plan merely because a session ended. Its “upcoming” selection can include an earlier start. A follow-up-status fact currently describes publication status, not whether agreed follow-up work was completed.
Use the meetings guide to confirm the actual meeting and session. Do not infer attendance, recording availability or completion of follow-up work from this list.
Interpret leave facts¶
The leave source selects pending, approved or ongoing requests that overlap the chosen dates. It can supply effective start and end dates, current state, policy label and available balance. It omits medical details, reasons, attachments and comments.
The balance comes from current ledger entries for the applicable person and policy. It is not a historical balance for the selected period or a projection of future accrual. It is expressed in the policy's leave units; do not automatically label every value as days.
Several requests can show the same policy balance. Do not add those repeated balances together. An empty list does not prove a zero balance: a person may have a balance without a qualifying request in the period.
The current assistant cannot reliably return these leave details. Use the leave guide and authorized leave records. Reading the facts does not submit, approve, cancel or amend leave.
Read partial and empty results correctly¶
A result contains a limited number of items. At most 100 can be read per request, and the assistant normally asks for 25. Receiving a full-looking list does not prove that all matching work was returned.
The result can indicate that more items exist, but continuing through them in the conversation is not currently supported. Do not assume that “show more” retrieves the remaining results without repeating the first page. Use the source application's supported listing for a complete operational review.
An empty authorized result means that no qualifying visible items were returned under that selection. It is different from access denied, source unavailable, a response that could not be used, or privacy withholding.
Check freshness against the source¶
Returned timestamps do not all mean “last checked.” Cases use their update timestamp; project facts can use assignment, review, achievement or due dates; meetings use creation time; leave uses its last recorded state change or submission time.
A leave balance can change without changing the request's displayed timestamp. A planned project date can also be in the future. These facts cannot establish that every field was refreshed together.
Before a time-sensitive decision, consult the current authorized record. If the assistant contradicts it, preserve the safe reference and ask support to investigate; do not change the record merely to match the answer.
Recover when facts are missing or unavailable¶
- Confirm the intended organization, source type and dates.
- Distinguish a limited or empty result from an explicit failure.
- Check the owning application's permitted record or listing.
- If access is denied, ask the administrator to check the source permission and current scope.
- If the source is unavailable or the answer lacks dates or details, use the authorized source and provide support with the safe request reference, approximate time and visible explanation.
A missing fact must remain unknown. Do not ask the assistant to invent a deadline, estimate someone's balance or infer a hidden record.
These tools read information. Their failure does not mean a source action was rolled back or completed. If a separate action was attempted, follow that action's own recovery process.
Use the information responsibly¶
Use work facts to find and understand authorized work. Do not use them to rank individuals, infer protected personal information, recommend employment decisions or reconstruct information withheld by privacy controls.
The safeguards can also withhold an innocent request. Report that through support with safe context. Rewording to evade a safeguard is not a recovery method.
Managers should retain the selection, scope, missing information and freshness when sharing a summary. Executives should use approved organizational reports when they need complete totals or evidence for a business decision.
Understand usage and support responsibilities¶
Read-only describes the source action. It does not mean the surrounding AI conversation is free. Normal access, provider, budget and credit controls still apply.
Administrators and support staff should distinguish source access, current capability policy, delayed or invalid responses, missing assistant fields and an incomplete frontend journey. Asking for broader permissions will not repair a delivery gap.
Keep private record contents out of a public support request. Engineers and operators have a separate restricted integration reference; users should receive a plain-language explanation and a safe next step.
Example: review work due this week¶
A project manager receives a short list containing three activities and one milestone from two projects. They record the requested dates and note that the result is partial. They check the source projects for current state and use the normal project list for the complete review.
They do not report four projects, assume that earlier overdue work is excluded, or treat a milestone reference as proof of delivery. The assistant result helps direct attention while the owning records establish the decision.