Manage Deliverables, Reviews, Approval, and Final Release

Deliverables separate work-in-review from final delivery. Versions are immutable, review decisions refer to one exact version, and release creates a durable client-facing record.

Permission required

Manage Project reviews creates deliverables, versions and review requests. Release Project deliveries releases finals. Override Project controls can bypass an Invoice or payment release gate with a recorded reason; it cannot invent approval or a final asset.

Create a deliverable and version

Open Delivery → Deliverables & Reviews. Define whether review is required and which milestone the deliverable supports. Add a version using a private file, a safe external URL or text content. The review asset and final asset may be different, but both remain attached to the version.

Once created, a version is preserved. Corrections or new work create the next version; they do not alter what the client already reviewed.

Request formal review

Collect a decision on an exact version

1. Confirm the latest version is review-ready.
2. Select the authorised client reviewer and request review.
3. The client opens Customer Account → Projects → Reviews.
4. They choose Approve or Request changes and may add a decision note.
5. If changes are requested, create a new version and send a new review request.

Client-visible comments help discussion, while internal comments remain hidden. A comment does not approve or reject. The formal response action is the decision of record.

Plan availability

When review annotations are enabled, authorised participants can anchor comments to a page, region or time reference on the exact version. Annotations add context; they do not replace the formal decision.

Prepare final release

Only the latest version can be released. It must have a final asset and be marked final-ready. If review is required, the exact version must be approved. The release policy then applies:

• No Payment Gate: release when delivery controls are ready.
• Paid Stage · Manual Release: wait until the linked stage is paid, then release manually.
• Paid Stage · Automatic Release: Yepsta releases when final readiness and payment are both satisfied, whichever happens last.

Release produces the authorised Customer Account download or open action. It does not expose a raw storage URL.

Important information

Payment does not approve a deliverable, and approval does not record payment. Both records can be required before release.

Handle exceptions and reversals

An authorised override can bypass the linked Invoice or payment gate only after all other release conditions are satisfied and a meaningful reason is recorded. A payment reversal after release does not erase historical delivery; Yepsta keeps the release and raises attention for the changed commercial state.

Warning

Never upload a changed file over an approved version. Create a new version and, when review is required, request a new decision.

Complete the linked milestone

A mandatory milestone may still be blocked by a missing required deliverable version, open required review or unreleased final. Resolve those source records, then complete the milestone explicitly.

Tip

Before requesting review, open the client-facing asset yourself and verify the reviewer, version number and visibility. This avoids an unnecessary revision round caused by the wrong file.

Related guides

• Use Project documents and private files
• Manage billing and payment release gates
• Use the client workspace
• Complete milestones and the Project

Last reviewed: 1 September 2026