Understand the request. Know who receives your work.
Get the context and sources you need to complete an assignment. OrgRelay keeps AI assistance close to the task, helping you check the result and pass a clear next step to your colleague.
Begin with the result your colleague needs.
The goal brief identifies the output and its purpose. The AI Chief connects related assignments, while the managers’ workflow shows how a supervisor agrees the work. Ask about the source, the review and the time available before accepting the handoff.
Monday: take on a customer requirement summary.
In a 28-person distributor, an employee needs to assemble the current requirements for a delivery review. The Procurement Agent organises supplier conditions and the Sales Agent gathers customer context. The employee checks which sources apply before combining their contributions.
Give the Agent a focused contribution to make.
Use the company knowledge design to identify applicable references. An Operations Agent can organise the handoff; a Support Agent can organise a case question. State the output you want and the colleague who will review it.
A task tells you what to return and to whom
Check the important conditions against the original material.
Look at specifications, dates and the scope of a proposed statement. Keep a question beside any condition needing confirmation. The approval design explains how the reviewed version connects to a person’s permission for the next action.
Wednesday: a new request needs a supervisor’s decision.
Use an exception note to state the request, its source and the affected part of your work. Your supervisor can decide the ordinary adjustment or use the owners’ scenario for a reserved choice. The trust page keeps the receiving roles clear.
Know the role you are using at each step.
A Finance Agent helps with record questions and an HR Agent helps with onboarding information. The product overview connects these contributions to their human reviewers and the actions they support.
| Preparation you may be assigned | Review by the responsible person | Decision responsibility |
|---|---|---|
| Summarise or compare | Relevant colleague checks the basis | Purchasing commitment follows actual authority |
| Draft a customer response | Account owner reviews conditions | External promise follows the company procedure |
| Identify an open question | Source owner clarifies the material | Policy changes reach the designated decision-maker |
Return the result with the question the reviewer should answer.
The resource guides help record the source version, checked content and remaining conditions. The dashboard concept shows who receives it. A professional-services page illustrates how specialist contributions depend on the same scope reference.
Friday: leave the next colleague a usable starting point.
State which version is ready for review and what still needs an answer. A small-business scenario may have one receiving manager; a growing-company scenario may have several. Each should be able to find the basis and the next responsibility.
Use the material selected for this assignment.
Read the security page when discussing the information involved. You can describe your process through the company-interest preview or demo using its roles and source categories. Integration requirements and plan scope help frame the scope around the actual work.
Questions, answered.
What should I check when receiving a task?
Its intended output, source basis, review responsibility and agreed timing.
How should I use an Agent?
Give it a focused contribution, then check important statements against the applicable material.
How do I raise an unclear instruction?
Identify the missing condition, its effect on your work and the person who can clarify it.
What should accompany my result?
The applicable version, checked sources, open questions and the decision requested from the reviewer.