Approval Workflow: Approve or Request Changes

The approval section sits near the top of the delivery page, directly below any banners, so clients see it immediately after opening the link. What the section shows depends on who is viewing and the current approval state. Clients who are the linked customer on the project see a 'Review Delivery' card with two action buttons: 'Approve Delivery' and 'Request Changes.' Members of the media organization who do not have the canApprove flag see a read-only message — either 'This delivery is pending review by the customer' or 'Changes have been requested. The customer will be notified.' Visitors who are not signed into Vremly see a prompt to sign in, with a link that redirects back to the delivery page after login.

When a client clicks 'Approve Delivery,' the backend records the approval timestamp and approver, updates the project's clientApprovalStatus to APPROVED, and triggers the post-approval flow. A green banner immediately replaces the approval card: 'Delivery Approved,' with the approval date shown below. The post-approval flow is a sequential dialog sequence: first a star rating dialog (if a team is associated with the delivery), then a review prompt (if the organization has configured review platforms and the rating meets the configured threshold), then a satisfaction survey (if one has been activated for the org). Each step can be skipped — closing a dialog moves to the next step in the sequence.

The star rating dialog prompts the client to rate the experience with one to five stars across the organization's configured rating dimensions. After rating, if the score meets or exceeds the review threshold, the review prompt dialog appears, showing the configured review platforms (Google, Yelp, or custom links). This is the built-in net promoter step — clients who rate highly are nudged toward leaving a public review. If the rating falls below threshold, the review prompt is skipped. The survey step presents the organization's custom satisfaction survey questions, collected and stored for internal analysis. Completing or skipping any step advances to the next, and the sequence ends when all steps are exhausted.

When a client clicks 'Request Changes,' a dialog appears with a free-text Textarea asking 'Please describe the changes you need...' Submitting the form sets the project's clientApprovalStatus to CHANGES_REQUESTED and notifies the media team. The approval section then displays 'You previously requested changes. Review the updates and approve when ready.' — the client can still approve in a subsequent visit after the team has addressed the feedback. Back in the job detail panel, the DeliveryPanel's Client Approval Status badge changes to 'Changes Requested' in red, alerting the team immediately. The team can see the feedback via the Discussion bubble on the delivery page or through the job's internal chat.

After a delivery is approved, the green banner also shows two optional buttons for clients: 'Rate your experience' (if they have not rated yet) and 'Take Survey' (if a survey is active and unanswered). These buttons let clients complete parts of the post-approval flow they may have dismissed initially. There is also a 'Go to Dashboard' button for signed-in users, which navigates to their Vremly dashboard. On the iOS app, the client approval state is surfaced in the Deliverables tab's 'Customer Review' card, which shows the approved-by name, timestamp, star rating, and any written feedback. Company staff can see approval status in real time without opening the delivery page.