The contact form shows a success message, but no request ever reaches your company. A finished look doesn't always mean a finished project. For a corporate website handover, test the real user journeys. Take delivery of the access, the documents and the responsibility for fixing defects. Base acceptance on test evidence and a signed record, not just on approving how the site looks.
What should you receive and check at a corporate website handover?
In the handover meeting, check the agreed pages and features, real delivery of form submissions, the mobile display and the final content. Also collect access to the domain, hosting and admin panel, the agreed files and licenses, a backup and a working guide. Then record the defects, who fixes them, the retest results and the conditions for starting support in the handover record.
My suggestion is to start with a single shared copy of the corporate website handover checklist. Without a shared reference, each side may have a different picture of where the work stands. Next to each item, write the status, who is checking it and where the evidence lives. The table below works for printing and a first pass. The details of each group are in the matching section.
Check group | Status | Checked by | Evidence location |
|---|---|---|---|
Pages and features | □ Approved □ Defect □ N/A | … | … |
Forms and mobile | □ Approved □ Defect □ N/A | … | … |
Access and assets | □ Approved □ Defect □ N/A | … | … |
Technical report and training | □ Approved □ Defect □ N/A | … | … |
Acceptance and support | □ Approved □ Defect □ N/A | … | … |
“N/A” is only for items outside the contract. It isn't for tests you haven't run yet. Mark anything still unchecked explicitly as “pending review.” For evidence, record the location of a file, screenshot or report that the responsible people can actually open.
Seeing the final version vs. a complete project handover
A visual walkthrough, the public launch, handing over access and final acceptance are four separate events. They may all happen on the same day, but none of them replaces another. Seeing the site on the developer's screen proves neither that you have independent access nor that the forms are ready.
Say the form works fine on the staging (test) address. After the move to the main domain, the email-sending settings change. The earlier test result doesn't cover the new settings, so check the send-and-receive path again.
□ Record the exact address of the version under test. List the staging and live addresses separately.
□ Note the review date and the version identifier, so it's clear which build each result belongs to.
□ Name the authorized approver. A passing comment from any colleague shouldn't change the acceptance status.
□ After launch, run a short, targeted retest of the main form, menu, contact details and file downloads.
So in your corporate website handover plan, set aside a specific slot for a post-launch check. If the developer changes anything after testing, recheck the affected path. This is a point I always stress: until the acceptance decision is made, no change to the reviewed version should go unrecorded.
Matching pages and features against the agreed scope
Scope is the list of what the project committed to deliver. The contract and its approved changes are the basis for acceptance. A verbal wish list is a poor reference for settling disagreements.
□ Link every page, language, form and integration to a contract clause or an approved change request.
□ For each commitment, note the live URL and the test evidence. A page name on its own isn't enough.
□ For features that depend on another service, decide who provides the account and connection details.
□ Record the review result and the name of the approving representative on the same row.
For example, a hypothetical “Services page” row might also include a consultation request form. In that case, a screenshot of the page isn't enough evidence for acceptance. You also need to record the message arriving in the company inbox. The client's representative should sign off on both.
Adding a new language or a new integration, however, isn't necessarily a defect fix. If there's no commitment for it, it needs a separate change request and estimate. To make that boundary clear, use the guide to writing a website design contract.
The complexity of integrations, the number of languages and the quality of the materials you supply also affect the time and cost of review and fixes. Incomplete content delays content acceptance, even when the template is ready. If you're starting a project with Niasa, the corporate website design with a clear delivery scope page is the starting point for a conversation about deliverables. Before signing, pin down the list of commitments, who supplies the content and the acceptance criteria.
Testing the contact form and real delivery of requests
Pre-handover website testing should follow a request all the way to delivery and the ability to reply. A success message only shows what the site's interface chose to display. You still have no evidence that the request reached your company.
Start with dummy data and a tag such as “Acceptance test 01.” Then follow the message to the destination inbox or the CRM (customer relationship management system), the system where customer requests are logged and followed up.
□ Try a valid submission. Note the time sent, the destination and who checked receipt.
□ Leave a required field empty. The error should be clear and shouldn't wipe out the user's correct entries for no reason.
□ Enter an invalid email address. Compare the form's behavior with the agreed rules.
□ Confirm real delivery at every agreed destination. Check the spam folder too.
□ Reply to the message. The reply address should take you to the right sender.
□ Test an allowed attachment. Check file type and size against the stated limits.
□ Define how sending failures will be reported. Who will notice the problem, and through which channel?
Not every notification failure is equally serious, though. If the request is saved in the system but the notification email doesn't arrive, check the fallback path. When nobody looks at the system daily, that same glitch can stall sales follow-up entirely.
Test storage of requests in the admin panel only if it's a contractual commitment. The absence of this feature isn't automatically a defect. Once the corporate website handover is complete, delete the test data according to the agreed procedure and record the test on the live domain.
Checking content, files and the mobile experience
Check content against the company's approved version, not just that the page isn't empty. An old phone number or an outdated catalog sends users the wrong way, even on a beautiful site. Decide from the outset who approves business content.
□ Match phone numbers, address, service descriptions and team members against the approved source.
□ Search pages and shared sections for placeholder text, temporary images and old files.
□ On a real phone, find a service, open the menu and tap the phone number.
□ Fill in the form using the phone's keyboard, then open the downloadable file.
□ Check fonts (Persian ones in particular), long text, screen rotation, zoom and badly proportioned images.
□ On a multilingual site, check labels, text direction and where the language switcher leads.
For example, say the catalog opens without errors, but the service specs belong to the previous version. The link test passes. The content test doesn't. Record these two results separately in your corporate website handover list.
Shrinking the browser window is no substitute for a real phone either. The keyboard, touch input and download behavior can reveal different problems. So write down the device model and browser next to each defect.
This simple check doesn't replace a full accessibility assessment, meaning a check of whether people with different abilities can use the site. To define a specialist assessment, refer to the Web Content Accessibility Guidelines and agree on the assessment scope separately.
Controlling domain, hosting and site admin access
Having access to an account isn't the same as owning it. Hosting is the space where the site's files live and run. Holding its password doesn't necessarily give you the authority to renew or recover the account. In a corporate website handover, check both.
□ Record the domain registrant, the hosting account owner and who pays for renewals.
□ Set the recovery email and renewal owner for each service. Notifications must reach someone who will act on them.
□ Have a company representative log into the panel independently. Logging in on the developer's device doesn't count.
□ Make a low-risk edit and check the result, then restore the previous value.
□ Separate the content manager's account from the super admin, so day-to-day work never touches sensitive settings.
□ Restrict or revoke the developer's access according to the support contract. Don't leave anonymous shared accounts behind.
With shared or managed hosting, though, full server access isn't a general requirement. Clarify the limits of your access, what you can export and how you'd move to another provider. The time to check these limits is before acceptance, not when the relationship ends.
Owning your site isn't just holding the password. It means being able to take the account back.
So don't treat the admin panel handover as done once you've received a username. Change the initial password and check the recovery options. Don't write passwords into a shared handover record. Send them through a secure channel, to authorized people only.
Checking documentation, licenses and project assets
Organize the handover documents into five groups: assets, the admin guide, required settings, backups and license status. For each group, set a storage location and an owner. A folder full of unnamed files isn't a usable handover package yet.
□ Record where the agreed design and code files are, the version identifier and how to run them.
□ Note the usage restrictions on each asset. Check file ownership and permission to use separately.
□ For themes, plugins, images and fonts, define the license holder, renewal date and who pays.
□ Check whether licenses can be transferred. Buying a tool doesn't necessarily give you the right to transfer the account or resell it.
□ Get a backup that fits how the site is built. The necessary files and data must be in it.
For example, a backup of the files without the form data and stored content may not be enough to restore the site. Ask the technical lead to walk you through what's in the package. Transfer confidential information and integration keys separately and securely.
One question I recommend for every corporate website handover: “If we parted ways, what could the next team run and maintain with this package alone?” The answer should reveal any remaining dependencies. Not every dependency is a problem, but an unknown one will derail a migration plan.
Handing off specialist SEO and security testing
Technical SEO means preparing the site's infrastructure so search engines can reach and understand it. You don't need to run every specialist test yourself, but you should get a report you can understand and follow up on.
□ The technical report should include the date, test scope, version reviewed and the reviewer's name.
□ Specify open items, their likely impact and who fixes them. A list of scores isn't enough.
□ For fixes, ask for retest results. Announcing that the work is done is different from confirming the result.
For the details of this part, include technical SEO checks for a corporate website before launch in your acceptance plan. The report should state which version was reviewed, because changing settings after the review can invalidate some of the results.
Nor can security be signed off with a browser padlock or a score from a single tool. The report should spell out the test boundaries, the accounts reviewed and the remaining risks. To scope an assessment request, the Web Security Testing Guide is a solid specialist reference.
So leave intrusive testing to a qualified specialist, and only with written authorization and a written scope. These tests simulate attacker behavior to find weaknesses. Don't experiment on the live site on your own initiative. Accepting the report as part of the corporate website handover is not a guarantee of search rankings or permanent security.
Training the content manager and the recovery scenario
The yardstick for client training after a website build is doing the work, not attending a session. The content manager should carry out routine tasks with their own account. A quick demo of features by the trainer isn't enough, because it doesn't prove they can work independently.
□ The content manager edits a service and previews the result before publishing.
□ They create a test news item, replace an image and attach a suitable file.
□ They go through the request review flow, if the contract includes it.
□ Get a short guide or video. It must not contain passwords or sensitive information.
□ Decide where the guide is kept and who keeps it up to date.
For example, imagine the content manager accidentally deletes the services page. They need to know where to report it and who will restore it. The source of the backup should be known too. “We have a backup” isn't a good enough answer.
Leave the restore test to the technical lead, though, and have it run in an environment separate from the live site. Restoring an old version can wipe out newer data. That's why, before any real restore, you check the backup's timestamp and what has changed since.
Agree on backup frequency and how quickly you need to be able to restore, based on how often content changes and how sensitive the incoming requests are. A site that rarely changes doesn't have the same needs as one receiving requests every day. To set this schedule, use the guide to scheduling regular backups. Add the restore test result to your corporate website handover documents.
Logging defects and setting final acceptance criteria
Each defect report should be clear enough for someone else to reproduce it. “The form has a problem” isn't enough to start a fix. Write down the URL, device, steps and expected result, and attach a screenshot or proof of receipt.
The table below is entirely hypothetical. Fill in each due date when you agree on it. This example doesn't suggest any timelines.
ID | Page and device | Steps to reproduce | Expected | Evidence | Severity | Owner | Agreed due date | Retest |
|---|---|---|---|---|---|---|---|---|
D-01 | Contact; test phone | Fill in and submit the form | Received in the company inbox | Message ID and non-receipt report | Blocker | Form technical owner | Pending agreement | Not done |
D-02 | Services; test computer | Open the page | Heading spacing matches the design | Comparison screenshot | Minor | UI owner | Pending agreement | Not done |
□ Set severity by impact. Lost requests or unauthorized access block acceptance.
□ A minor visual defect may stay open only with a written agreement, an owner and a due date.
□ Ideally, the person who fixes a defect and the person who confirms the result should be different.
□ Change “Fixed” to “Closed” only after a retest.
Being told it's fixed doesn't close a defect. A retest has to confirm it.
So the acceptance rule I suggest for a corporate website handover is this: no blocking defects, the main journeys work, you have the assets, and every remaining item has a clear plan. The contract is still the final reference. If a dispute comes up, go back to the test evidence and the commitment clause. Keep a change in taste separate from a missed commitment.
نمونهکارهای ما در همین زمینه
Corporate site
Copywriting and photography are not in the base price; if you need them, they are estimated separately.
The handover record and the start of the support period
In the handover record, write what you've accepted and what is still open. “The site has been delivered” isn't enough, because it says nothing about the outstanding commitments. Copy the template below and fill it in according to your contract.
Parties and authorized representatives: …; site URL: …; version: …; date: …
Attached documents: …; test status and evidence location: …
Open items, severity, fix owner, due date and approver: …
Acceptance type: final / conditional / not accepted; conditions for changing status: …
Support start and duration: …; reporting channel: …; responsible for responses: …
Response time, how resolution time is set and services not covered: …
Effect of acceptance status on payment and support per the contract: …; signatures of both parties: …
Here's an entirely hypothetical example. Version 1.0 receives conditional acceptance on 30 April 2026. The request delivery test passed, but the minor heading-spacing defect stays open. The front-end owner (front-end being the visible part of the site) follows up the fix, and the agreed review date is 2 May 2026. These dates are for illustration only and are not a commitment from Niasa.
Don't treat conditional acceptance as final acceptance. The effect of each status on payment and on the start of support must match the contract. Also write response time and resolution time separately. The first means acknowledging the report and starting work on it. The second means getting to a result, and the two aren't necessarily the same.
For the next meeting, prepare the list of pages and features, the completed checklist and the open defects. Next to each item, write the evidence and the decision needed. A corporate website handover meeting should end with clear responsibilities, not just another run-through of the pages.
فهرست امکانات و انتظارات تحویل را برای گفتوگو درباره طراحی سایت شرکتی با نیاسا آماده کنید.
Frequently asked
5Is receiving the admin panel password enough for a website handover?
No. You need to be able to log in with a company account and carry out the agreed tasks. The status of the domain, hosting and account recovery, and your ability to obtain the project assets, also have to be clear.
If the form shows a success message, is the test done?
No. Send a specific test request and check that it arrives at the agreed destination. The recipient must be able to read the information and reply to the sender through the right channel.
Do all defects have to be fixed before acceptance?
Defects that break a main user journey or carry serious risk shouldn't be accepted without a clear decision on how they'll be handled. A minor defect can stay open only if its impact, owner, due date and effect on the type of acceptance are recorded and agreed.
Should the code and design files be handed over to the client?
That depends on what the contract commits to and on the usage rights to the assets. Before accepting, check that the agreed deliverables are usable and that any license restrictions on tools or third-party assets are clearly stated.
When does the website support period start?
The start date should be set by the contract or a valid handover record. Going live doesn't settle it on its own. If the handover is conditional, write down separately how open defects affect the start of the period and who is responsible for fixing them.








