I am preparing Test Plan and trying to include some of User Acceptance Tester Responsibilities.
Some of them which i included are.,,,
Validate system set-up for transactions and user access
Confirm use of system on business critical functions
Verify performance on business critical functions
Confirm integrity of converted and additional data
Access and sign off go-live readiness
Validating that the requirements that they signed off on have been implemented - 'I got what I asked for not what I wanted'
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
I also try to encourage the users to write their own tests. They think of things I wouldn't have, catching bugs that the test team might miss because of the difference between how the system was designed and how it is actually used. By executing their own tests they will also be more confidant of the system functionality.