Work can now start three ways in Zayvro
Assign a task now, place repeat work on a schedule, or let a supported business event start the run, without changing the controls around the worker.
Published by the Zayvro team
The same responsibility can arrive in different ways
Operational work does not always begin with someone typing a request. A weekly report begins because Friday arrived. An invoice check begins because a document landed. An account review may begin because an operator asks for it before a meeting.
Zayvro now expresses those starting conditions as three clear modes: assigned, scheduled, and event-triggered. The start changes; the governed worker, approved context, action boundaries, and result record remain the same.
A trigger starts a responsibility. It does not expand what the worker is allowed to see, decide, or send.
Assigned work stays immediate
A person can give the worker a task when the work is irregular, judgement-heavy, or best initiated with fresh context. The assignment can include the intended finish line, useful references, and any constraint that matters for this run.
This mode is designed for work such as preparing an account brief, reviewing a newly received project file, or reconciling a set of records before a deadline. The worker returns the result alongside the steps and approvals that shaped it.
- A clear human request starts the run.
- The worker uses only approved company context and software.
- High-impact actions still stop at the configured approval boundary.
Scheduled work gives recurring responsibilities an owner
Repeat work can be placed on a cadence where scheduling is configured: a weekday queue review, a monthly operating pack, or a renewal brief prepared ahead of a known date. Each scheduled run follows the same mapped process rather than improvising a new one.
The point is not simply to run something on a timer. It is to preserve the inputs, decisions, exception paths, and delivery expectations that make the recurring responsibility trustworthy.
Events can start work close to the moment it matters
When a supported connected system exposes the right signal, an event can begin the responsibility. A new invoice can start an exception review. A status change can begin a follow-up. A newly added document can start a completeness check.
Event availability depends on the system and access approved during implementation. Zayvro confirms the signal, the safe response, and the fallback path before the workflow is enabled in production.
- Signal: a supported event is observed.
- Context: the worker gathers the approved records and rules.
- Result: the work is completed, routed for approval, or returned with a clear exception.