How to Manage Revisions, Testing and Handover With Outsourced Developers

Your agency has outsourced a client's website development.

The designs are approved, the developer has started building the website, and the client is expecting a review soon.

Then the feedback begins.

The client wants a different mobile layout. Your designer notices spacing issues. The developer says a requested feature wasn't included in the original scope. Meanwhile, nobody is completely sure who is responsible for testing the contact forms.

These situations are common in website projects, whether development happens internally or through an outsourcing partner.

The problem isn't necessarily outsourcing itself.

It's often the absence of a clear process for managing revisions, testing and handover.

For agencies, that process matters because your client holds your business responsible for the finished website, even when another team completes the development.

A reliable workflow helps you manage expectations, reduce unnecessary rework and review the finished website before handing it to your client.

In this guide, we'll explain how agencies can manage outsourced web development projects from the first development milestone through final testing and handover.

Why Outsourced Website Projects Need a Clear Delivery Process

When your agency works with an external development team, responsibilities are shared.

Your agency may handle:

• Client communication
• Website strategy
• Design
• Content
• Project management
• Client approvals

Your development partner may handle:

• Frontend development
• WordPress or Shopify implementation
• Custom functionality
• Technical integrations
• Development testing
• Agreed launch tasks

The exact responsibilities depend on the project.

Problems can arise when both parties assume the other is responsible for something.

For example, your agency might expect the developer to upload all website content, while the developer's quotation only includes template development.

Or the developer might consider the website complete after functional testing, while your agency expects a separate visual review against the approved Figma designs.

These issues are easier to prevent when responsibilities and acceptance criteria are agreed before development begins.

1. Start With an Approved Development Brief

Before assigning work, make sure the development team has the correct requirements. Consult our website development brief guide to structure deliverables.

A good brief should include:

• Project objectives
• Website platform
• Approved designs
• Page list
• Required functionality
• Responsive requirements
• Content responsibilities
• Integrations
• SEO requirements
• Testing expectations
• Timeline
• Handover deliverables

The brief becomes the reference point for the project.

When someone requests a change, you can compare it against the agreed scope.

When the developer submits completed work, you can check it against the same requirements.

Avoid Using Chat Messages as the Only Project Specification

WhatsApp, Slack and email are useful for communication.

However, important requirements can become difficult to track when they're scattered across long conversations.

Keep the approved scope in one accessible document or project management system.

Use messages to discuss decisions, then update the project record when something changes.

2. Define Who Is Responsible for Each Stage

An outsourced project should have a clear owner for every important activity.

For example:

This is an example, not a fixed rule.

Your agency may outsource more responsibilities or manage more work internally.

The important point is that no essential task should be left without an owner.

3. Use Development Milestones Instead of Waiting Until the End

One mistake agencies make is reviewing the website only after development is nearly complete.

By then, misunderstandings about layout, functionality or content editing can affect several pages.

Milestone reviews help identify problems earlier. For design-to-code project staging, review our Figma to WordPress development guide.

Milestone 1: Development Setup

Confirm the development environment, access arrangements and technical approach.

Milestone 2: First Page or Template

Review the homepage or another representative template.

Check typography, spacing, responsive behaviour and component implementation.

Milestone 3: Remaining Templates

Review reusable templates, navigation and common website elements.

Milestone 4: Functionality

Test forms, integrations, CMS editing and custom features.

Milestone 5: Internal Quality Assurance

The development team completes its agreed checks.

Milestone 6: Agency Review

Your agency reviews the website against the approved brief.

Milestone 7: Final Revisions

Agreed issues are corrected and retested.

Milestone 8: Launch and Handover

The website is deployed and the agreed materials are transferred.

The number of milestones should match the project.

A small landing page doesn't need the same process as a large ecommerce website.

4. Collect Client Feedback in One Place

Client feedback can quickly become difficult to manage.

A client may send comments through email, WhatsApp, a video call and a design review tool.

If your agency forwards every message directly to the developer, the instructions may become repetitive or contradictory.

Instead, collect the feedback and prepare one consolidated list.

Each item should be specific enough for the developer to understand and verify.

Avoid Vague Feedback

Instead of: "The mobile version doesn't look right."

Write: "On the mobile homepage at approximately 390px viewport width, the heading overlaps the hero image. Please adjust the layout to match the approved mobile design."

Specific feedback reduces unnecessary clarification.

5. Separate Bugs, Revisions and New Requirements

Not every client request is the same. A clear classification helps agencies manage scope and cost.

Bug or Defect

Something doesn't work as agreed.

Example: A contact form fails to submit.

Revision

An adjustment to work already included in the agreed scope.

Example: Correcting spacing so a section matches the approved design.

New Requirement

Something that wasn't included in the original project.

Example: Adding a customer dashboard after the website development scope was approved.

Content Change

An update to text, images or other content. Whether content changes are included depends on the agreement.

Why This Matters

A development partner may be responsible for correcting defects within the agreed scope.

New features may require a separate quotation and additional time.

Your agency should define these categories in its project agreement (see our white label development agreement guide) rather than deciding them only after disagreements arise.

6. Establish a Revision Approval Process

A useful revision process can follow five steps.

• Step 1: Collect feedback. Your agency gathers comments from the client and internal team.
• Step 2: Review and classify. Identify defects, included revisions and possible scope changes.
• Step 3: Confirm the work. The developer reviews the feedback and identifies any technical questions or commercial impact.
• Step 4: Implement approved changes. The development team works from the confirmed list.
• Step 5: Retest and close. Your agency checks the changes and marks the items complete.

Avoid adding new requests to an active revision list without identifying their impact.

For larger projects, use a formal change request process.

7. Define What Website Testing Includes

Website testing is more than opening the homepage and checking whether it looks correct.

The required testing depends on the project, but several categories are commonly relevant.

Visual Testing

Compare the implemented website with approved designs. Check typography, colours, spacing, alignment, images, reusable components and responsive layouts.

Functional Testing

Verify that the agreed features work. Examples include navigation, forms, buttons, search, accordions, filters, booking features and custom interactions.

Responsive Testing

Review the website across agreed screen sizes.

Browser Testing

Check the supported browsers specified in the project brief.

CMS Testing

Confirm that the agency or client can edit the content areas identified in the scope.

Integration Testing

Test connections with CRM systems, payment providers, email platforms or other required services.

Technical SEO Testing

Review the agreed SEO implementation requirements.

Accessibility Testing

Assess the website against the accessibility requirements agreed for the project.

A test should have an expected result, not simply a checkbox saying the feature was viewed.

8. Create a Website Quality Assurance Checklist

Your agency can use a repeatable checklist for every outsourced website project.

This checklist should be adapted to each project.

A Shopify store, for example, requires ecommerce testing beyond a standard service website.

9. Test WordPress Websites Before Handover

WordPress projects often involve CMS editing, themes, plugins and custom functionality.

Your agency should confirm that the website works for both visitors and content editors.

WordPress-Specific Checks

• Can authorised users log in?
• Can agreed page content be edited?
• Do forms work?
• Are menus manageable?
• Are required plugins configured?
• Do custom content types work?
• Are user roles appropriate?
• Are important SEO settings correct?
• Are any required licences documented?

If the client expects to manage content without developer assistance, test that workflow.

A website that looks correct but is difficult to update may not meet the client's requirements.

10. Test Shopify Stores Before Handover

Shopify projects require additional attention to ecommerce functionality.

Depending on the scope, check:

• Product information
• Product variants
• Collection pages
• Navigation
• Cart behaviour
• Checkout testing
• Shipping configuration
• Payment configuration
• Discounts
• Customer accounts
• Required apps
• Inventory integrations

Use supported testing methods and appropriate test modes where available.

Don't assume that a store is ready for launch simply because the product pages look correct.

The agency and client should approve relevant commercial settings before publication.

11. Review the Website Before Showing It to the Client

Your agency should conduct its own review before inviting the client to inspect the finished website.

This is particularly important when the project is delivered under your brand.

The development partner may have completed technical testing, but your agency still needs to verify the result against the client's expectations.

A Practical Agency Review Process

• Open the agreed review environment.
• Compare the main pages with approved designs.
• Test important functionality.
• Review mobile layouts.
• Check content accuracy.
• Verify the agreed SEO requirements.
• Record any issues.
• Submit one consolidated feedback list.
• Retest completed fixes.
• Approve the website for client review.

This creates a clear distinction between development completion and agency acceptance.

12. Manage Client Approval Carefully

Once the agency review is complete, the client can inspect the website.

Set expectations before sharing the review link.

Explain:

• Which pages are ready
• What functionality can be tested
• Whether content is final
• How feedback should be submitted
• When feedback is requested
• Which changes may affect the agreed scope

Ask the client to consolidate feedback where possible.

If several stakeholders are involved, identify who has final approval authority.

Without a clear decision-maker, conflicting requests can delay completion.

13. Prepare the Website Handover

Handover is the point where the agreed project materials and responsibilities transfer to the agency or client.

It shouldn't be treated as an informal final message containing a website login.

Depending on the project, the handover may include:

• Website administrator access
• Hosting access arrangements
• Source code
• Repository access
• Theme files
• Custom plugin information
• CMS editing instructions
• Integration documentation
• Licence details
• Backup information
• Deployment notes
• Known limitations
• Agreed testing records

The exact deliverables should be defined in the project agreement.

A simple handover record helps ensure nothing important is forgotten.

14. Clarify What Happens After Launch

Clients may report issues or request changes after a website goes live.

Your agency should know what support is included.

For example:

• Correction of agreed defects
• Assistance with deployment issues
• Additional content updates
• New functionality
• Plugin or theme updates
• Security maintenance
• Hosting support

These are different types of work.

Not every development quotation includes ongoing maintenance or unlimited post-launch changes.

Define the support scope, reporting process and any applicable response expectations.

15. Protect Client Access and Project Information

Outsourced developers may need access to WordPress, Shopify, hosting, repositories and third-party services.

Access should be managed carefully.

Practical steps include:

• Use individual accounts where possible
• Grant only the permissions needed
• Share credentials through an appropriate secure method
• Use multifactor authentication where supported
• Avoid unnecessary access to client data
• Review access after project completion
• Remove permissions that are no longer required

The agreement should also address confidentiality and appropriate handling of project information.

16. Measure the Quality of Your Outsourcing Process

Agencies can improve delivery by reviewing what happened after each project. For partner evaluation guidance, see how to choose a white label partner.

Useful questions include:

• Was the original scope clear?
• Were milestones completed as expected?
• How many defects were found during review?
• How many requests were outside the agreed scope?
• Was client feedback consolidated effectively?
• Were handover materials complete?
• Were there repeated communication problems?

You don't need a complicated reporting system.

A short internal review can help your agency identify patterns and improve future briefs.

For example, if several projects have mobile layout misunderstandings, your agency may need clearer responsive design specifications.

If handovers regularly lack documentation, add those deliverables to future agreements.

The goal is to improve the process rather than assign blame.

A Simple Outsourced Development Workflow for Agencies

Here's a repeatable process you can use across client projects.

For smaller projects, some stages can be combined.

For complex applications or ecommerce stores, additional stages may be necessary.

Common Mistakes Agencies Make When Managing Outsourced Developers

Sending Feedback From Multiple People

Conflicting instructions create confusion. Use one approved feedback list.

Starting Development With Unfinished Requirements

Unclear scope can lead to unexpected work and delays.

Reviewing Only at the End

Early milestone reviews can identify misunderstandings before they affect the entire website.

Treating Every Change as a Bug

Separate defects from new requirements and content changes.

Skipping Agency Testing

Your agency should verify the website before client approval.

Leaving Handover Until the Final Day

Required access, documentation and files should be agreed in advance.

Assuming Post-Launch Support Is Included

Clarify support responsibilities before launch.

Failing to Record Decisions

Important approvals and scope changes should be documented.

Frequently Asked Questions

How do agencies manage outsourced web developers?

Agencies can use a clear development brief, agreed milestones, centralised feedback, quality assurance checks and a documented handover process.

Who should manage client feedback in white label development?

In a typical white label arrangement, the agency collects and consolidates client feedback before sharing approved changes with the development provider.

What is the difference between a bug and a revision?

A bug is a failure to meet agreed functionality or requirements. A revision is an adjustment to work within the agreed scope. The contract should clarify how both are handled.

Should outsourced developers test websites?

Testing responsibilities should be agreed before development begins. The provider may perform technical testing while the agency conducts its own acceptance review.

What should a website handover include?

Depending on the project, it may include administrator access, source code, documentation, integration details, licence information and other agreed deliverables.

How many revision rounds should an agency allow?

There is no universal number. Revision arrangements should reflect the scope, project complexity and agreement.

Can agencies outsource WordPress testing?

Yes. WordPress testing can be included in the development scope or assigned separately, but responsibilities should be clearly defined.

Can agencies outsource Shopify testing?

Yes. Testing may cover storefront functionality, product pages, cart behaviour, supported checkout testing and integrations.

Should agencies use a project management tool?

A shared project management tool can help, but the important requirement is a reliable record of tasks, feedback, decisions and approvals.

What happens if the developer doesn't complete the agreed handover?

The parties should refer to the contract and acceptance requirements. Missing deliverables should be documented and addressed through the agreed resolution process.

Need a Development Partner for Your Agency?

If your agency already has client projects and needs support with WordPress, Shopify, WooCommerce or custom web development, White Label Agency can review your requirements.

We work with agencies that want to keep their client relationships while outsourcing technical delivery.

Share your project brief, approved designs, functionality requirements and expected timeline. Learn more about how our process works.

We can discuss the development scope, review process and handover expectations before work begins.

Our services are intended for agencies outsourcing technical work for existing client projects, not freelancers looking for employment or agencies seeking customers.