The website changes are ready. The developer has finished their work. But the page is still waiting to go live.
The reviewer has not checked the latest version. Someone has shared feedback in a separate chat. The person responsible for the launch is unsure whether they can proceed.
A task can reach this point even when everyone has done their part. What is missing is a clear answer to three questions:
This is where a clear review process helps. Orbyna, Metaveo’s project management platform, provides tools for keeping task responsibilities, progress and related information together.
When someone says a task is finished, explain what that means.
For a website update, it might mean the changes are ready for someone else to check. The reviewer still needs to confirm that the content is correct and the page works as expected.
Before starting the work, agree on:
This gives the team a shared understanding of what needs to happen before the work can be used.
The following is a fictional example. The stage names describe a suggested process; the exact setup depends on your Orbyna workspace.
Maya is updating an enquiry form. Ravi will review it. Noor will publish the approved changes.
Here is how they can organise the work.
Maya finishes the update and prepares a clear review note:
Ready for review: the updated enquiry form is available at the preview link. Please check the required fields, mobile layout and confirmation message by 3 pm.
The note includes the preview link and a short explanation of what changed.
Ravi can begin checking the form without first asking where to find it or what needs attention.
Ravi tests the form and notices that the confirmation message does not clearly explain whether the enquiry was sent.
Instead of writing “Please fix the message,” he gives a specific request:
After a successful submission, show: “Thank you. Your enquiry has been sent.” Please update this before approval.
Maya now knows exactly what to change. The feedback also makes it clear that the form is still waiting for approval.
After making the change, Maya shares the updated preview and explains what she fixed.
Ravi checks that version. Keeping the latest link and review notes together helps the team avoid checking an older version by mistake.
If the correction changes the planned launch time, the team updates the deadline and lets Noor know.
Once the checks are complete, Ravi records a clear approval:
Approved: the latest preview has been checked. The required fields, mobile layout and confirmation message are ready for publication.
The decision identifies what was reviewed. Noor can see which version is approved and what the approval covers.
Noor publishes the approved version and records the live page link.
The team can now see that the review is complete and the page is live. Each stage has a named person responsible for moving it forward.
Orbyna supports tasks with owners, deadlines and statuses, alongside related files, comments and instructions. Managers can see work waiting for review or approval and identify tasks that need attention.
It also supports workflow actions based on selected triggers and conditions. These can include notifications, assignments, reminders and status updates. Your team’s configuration determines which actions run. A notification tells someone to act; the reviewer still needs to check the work and record their decision. These capabilities are described on Metaveo’s Orbyna product page.
For this example, a useful setup would make it easy to find the latest preview, understand Ravi’s feedback and see who needs to act next.
Before sending any task for review, check these five things:
Check | What to make clear |
|---|---|
Reviewer | Who will check the work and make the decision? |
Review material | Where is the latest version, and what needs checking? |
Deadline | When is feedback or approval needed? |
Decision | Is it approved, waiting for changes or still under review? |
Next owner | Who acts after the decision, and what should they do? |
The same checklist can help with a design, report, campaign or internal document.
Choose one task that regularly gets stuck after the first person finishes their work.
Agree on the reviewer, the checks and the next owner. Then use that example to explore how Orbyna could support your team.