Approvals

The moment it fixes

Approvals often disappear from the process at the exact moment they become important. Someone asks for a review in Slack. A client replies in email. A manager says yes in a meeting. Later, the team has to remember what was approved, who approved it, and what changed.

EleWave keeps the decision where the work is happening. The request, context, evidence, comments, reviewer, and next step remain part of the same activity path.

How EleWave changes it

An approval activity pauses the journey until the right person makes a decision. The reviewer can approve, reject, ask for changes, return the work, or escalate the request. The flow can continue only when the decision is clear.

That keeps human control where judgment matters, without letting the process stall in a private thread.

A review in motion

A creator submits a private draft. EleWave sends the review activity to the workspace owner with the draft attached, the decision options visible, and the comment field ready. The owner requests changes, the creator updates the file, and the approval returns to the reviewer.

When the final approval happens, the release step opens automatically. The record shows the path from first request to final decision.

What stays visible

Approvals carry the details teams usually lose: reviewer, requester, decision time, comments, attachments, evidence, related activity, follow-up action, and escalation state.

The result is not just a yes or no. It is an explainable decision connected to the work that required it.

Product moment

A consultancy sends a client deliverable for review. The client approves inside the activity, the internal team gets the next handoff task, and the account lead can see the decision without searching through email. No side-channel approval. No missing context.