ProjectConnections Print View
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.
Learn more about ProjectConnections and who writes our content.
Site Help
| Content Levels | |
 | Register for free access to papers, case studies, and almost 50 templates. |
 | Subscribe for complete access: $14.95 monthly or $149/year |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Customer Acceptance Checklist
Quick Summary
Checklist format for customer to use while walking through a review and test of a pre-release system, for example before going through with a purchase. Allows customer to record issues, indicate which must be resolved before acceptance, and ultimately sign off on accepting the new system.
What this is
Template for a checklist and signoff form that can be used by a customer or user reviewing a new system's functionality and other attributes before closing a purchase order or accepting a delivery. It includes checklist areas for functional tests, documentation reviews, issue recording, enhancement requests.
This form can be used standalone for this purpose, or it can be used as the short-form checklist and signoff form accompanying a written User Acceptance Test Plan or Beta Test Plan (see our templates for those 2 documents).
NOTE: This form can also be adapted for review and acceptance of any deliverable between a customer and a provider. Whether the deliverable is a recommendations report from consultants, a user manual from a technical publications firm, a physical hardware system, a software application, a plan for a marketing campaign, etc., this form can be used to list what's expected by the customer, record results of the acceptance review or tests, record open issues to be corrected, and ultimately document acceptance by the customer.
Why it's useful
Especially when purchasing expensive new systems that have just been released, customers may want to ensure that the system functions as promised before committing funds and accepting delivery. This checklist provides a way for the customer to work with the developer of the system to test key functionality, note any issues that must be corrected before the customer will accept the system, and ultimately provide an official record of the system's acceptance.
How to use it
Create your own version(s) of this form to reflect the kinds of products or services you buy, for which a formal acceptance of the deliverable from the vendor is important.
When preparing to accept a deliverable—system, product, report, etc.—from a supplier, fill out your version of this form to include the items you want to test and/or review. If possible, consider ahead of time whether any discrepancies will be acceptable for each item. Schedule the review/tests with the supplier and discuss expectations. When you perform the reviews or tests, mark the performance of each item and indicate whether each result is acceptable—will the deliverable be accepted with this issue? Fianlly, review overall results with supplier, timeline for issue resolution, and whether re-test will be required.
Once the acceptance criteria have been met, sign the form along with the vendor.
Issue Resolution Status Report
Format for reporting progress on work to resolve one or more open issues (e.g. project or technical issues).
Change Control Form
Form for requesting and documenting changes to a project or project elements.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy