Reviewing Completed Work

Development requests are implemented by the DCS platform team. Your role as the site owner is to review the work as it lands, give feedback in the request's Conversation, and publish the finished release to production when you're happy with it.

How Work Reaches You

Each request's detail page shows a four-step Progress stepper:

Step	Meaning
Acceptance	Request submitted and awaiting initial review
Development	Implementation in progress
Draft Release	Changes ready for review
Production Release	Production release in progress or live

When a request reaches Draft Release, the change has been built and is ready for your review before it ships.

Previewing Changes

Completed work lands on the site's release branch, and pushing a release/** branch deploys the site's Preview environment on Azure Static Web Apps (see Deployment). Production doesn't change until you publish the release.

You can also see staged text and content edits as pending changes in the site's Release Management view before publishing.

What to Check

Visual Review

• [ ] Layout matches the request
• [ ] Colors and fonts are correct
• [ ] Images display properly
• [ ] Responsive on mobile and tablet

Functional Review

• [ ] Links work correctly
• [ ] Forms submit properly
• [ ] Interactive elements function

Content Review

• [ ] Text content is accurate
• [ ] No placeholder content
• [ ] Spelling and grammar correct

Providing Feedback

There are no approve/reject buttons on a request — feedback flows through the request's Conversation. Post a comment describing what needs to change, and the team iterates. You can also react to individual comments with a thumbs-up or thumbs-down.

Good Feedback

The testimonials section looks great, but I need a few adjustments:

1. **Photo size** - Make the customer photos smaller (60px instead of 80px)
2. **Quote formatting** - Add quotation marks around the quotes
3. **Background color** - Change from white to light blue (#e6f0ff)
4. **Spacing** - Add more padding between cards

Please also fix the broken link on the third testimonial name.

Feedback Best Practices

• Be specific about what needs to change
• Reference exact elements or locations
• Provide correct values (colors, sizes, text)
• Prioritize critical issues first

Publishing to Production

Completed work goes live through Release Management, not from the request itself:

1. Open the site's Release Management view.
2. Review the pending changes listed against the Development version.
3. Click Publish and confirm.

DCS releases the pending changes and deploys the Production version. See Release Management for the full flow, and Releases & Version History for the portal walkthrough.

Rollback

If a problem appears after a release goes live:

1. Open Version History for the site.
2. Select the earlier version you want to return to.
3. Start a rollback, provide a reason, and confirm.

The rollback runs as a tracked request rather than an instant flip, and rolls the site down through every version between the current release and your target. See Releases & Version History for details.

Best Practices

Review Promptly

• Requests waiting on your feedback hold up the release
• Prompt reviews keep work moving

Be Thorough

• One careful review beats multiple quick ones
• Test on different devices
• Check edge cases

Communicate Clearly

• Specific feedback reduces iterations
• Reference exact locations
• Use the Conversation so there's a record

Next Steps

• Tracking Progress — Monitor request status
• Submitting Requests — Create new requests
• Releases & Version History — Publish, compare, and roll back