Start here as a manager or process owner¶
Your main responsibility is to make the work understandable: who owns the next step, what decision is needed, what outcome counts as complete and how an exception reaches the right person.
Zerohive provides different structures for requests, projects, cases, correspondence and retained records. Choose the guide for the actual work rather than treating every task, approval or status as interchangeable.
Draft and availability: This guidance summarizes reviewed feature documentation. The frontend remains in progress, and intended screens can be ahead of connected delivery. It does not establish a deployed management experience or an accepted reporting result.
Choose the responsibility you need to address¶
| Responsibility | Start with |
|---|---|
| Define a repeatable process and its participants | Process ownership and workflow authoring |
| Understand a submitted request or pending decision | Requests and tasks |
| Maintain decision and signing responsibilities | Governance authority |
| Understand due dates and escalation | Timing policies |
| Coordinate longer-running delivery or investigation | Projects and cases |
| Understand your current team's recorded work | Personal and team insights |
| Interpret department or organization information | Department and organization insights and interpreting insights |
| Help a colleague enter the correct workspace | Account and workspaces |
A management title does not itself grant every product permission. Your team relationship, organization-head responsibilities, approval-body membership and product permissions describe different scopes. Read membership and authority when access needs review.
Start with the current work¶
Before intervening, identify the workspace, request or business item, current task, responsible person and recorded reason for delay.
One approved task does not necessarily finish a request. A completed workflow can still have a receiving process to confirm. A cancelled approval task can result from refreshed routing rather than rejection of the request.
When authority changes, open the current request and read its decision history. The authority-change explanation describes replacement tasks, retained decisions and possible suspension. Do not use an old notification as proof that its task remains actionable.
Explain deadlines accurately¶
An SLA policy expresses configured timing targets. The task can retain its own saved timing and calendar even after the reusable policy changes. A reassignment or replacement task does not automatically receive a new full period.
Use deadlines and escalation and the current task's due/pause information. Identify the condition and responsible owner when work is suspended. A notification being queued or sent does not prove the responsible person has completed the task.
Discuss contribution with context¶
Before using an insight, establish its scope, period, included people, available evidence and calculation limits. Current-team and organization views do not necessarily reconstruct the workforce as it existed in a past period.
An unavailable measure is not zero work. A group average can exclude people without a measure. A comparison label does not independently prove that roles, scoring contexts or evidence are comparable.
Use interpreting insights to prepare the discussion and recognition evidence when you need to inspect a supported result. These views do not make employment decisions or explain every cause behind a change.
Keep recovery and communication accountable¶
When a result is uncertain, preserve the original work and reference. Establish whether the action completed before repeating it. Involve the process owner, organization administrator or authorized support owner according to the failed boundary.
Tell participants what is confirmed, what remains pending and who is handling it. Use the relevant feature's actual recovery instructions. A generic reset, new request or access change can create a different problem without resolving the original one.
Continue with process ownership, interpreting insights or the capability map.