Waiting for approval is also a work status that needs context, an owner and a next step.
Check what the delivery is actually waiting for
Consider a consultancy that sends an implementation proposal and hears, “we are reviewing it.” The document arrived, but nobody knows whether it needs technical validation, a budget decision or simply reading time. Asking again whether it is approved can prolong the same conversation. The account owner needs to identify the pending decision and who participates in it. Distinguish a content review from commercial authorization: each requires different materials and people.
Make the review request easy to answer
Sending the entire file with “I look forward to your feedback” leaves too much interpretation to the recipient. Accompany the delivery with a precise question: what they should validate, which version they are reviewing and what happens after their response. If several departments must comment, agree who will consolidate their feedback. A proposed date starts a conversation about the commitment; it does not create approval. When a comment arrives, connect it to the corresponding version so nobody edits a document that someone else has already replaced.
Reviewing is also deciding
Approval needs context and a clear next step when a proposal is not suitable.
Understand what is being proposed.
Separate the blocker from the team’s next action
A task can be waiting for the client while an internal action remains pending: preparing an explanation, checking a question or confirming a review meeting. Record the reason for waiting and give that action an owner. During follow-up, check which other deliveries depend on this approval. If the schedule needs to change, tell the people affected. Do not leave an earlier date in place as though nothing happened, or treat the client’s silence as an instruction to proceed.
Keep the review with the project in Wiwo.Ops
Wiwo.Ops brings tasks, files, comments and deliverables together within the project and records blockers with their reasons. With the agreed access, the client portal allows clients to review deliveries and approve or reject them. This organization helps people return to the right material. The team still needs to define who reviews and what approval means. To evaluate the process, bring a typical delivery to the demo: check how it is shared, how the response arrives and how work continues when the client requests a change.
Frequently asked questions
Does a missed deadline count as approval?
No. Approval must follow the agreement with the client. A missed date means the commitment needs review, the blocker needs to be understood and its consequences discussed.
What should appear in the client portal?
The version requiring review, the materials needed for a decision and the status the client should be able to consult. Permissions and visible information must be defined for that working relationship.
