# File upload experience survey

Find confusing requirements and errors in an upload workflow.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. Was the required file format clear?

Answer: ____________________

## 2. Which upload step was difficult?

Answer: ____________________

## 3. Did an error explain what to change?

Answer: ____________________

## 4. Was completion clearly confirmed?

Answer: ____________________

## 5. What would help you prepare a file correctly?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Format clarity determines whether users can prepare an acceptable file before starting. Check how restrictions are presented and distinguish permitted file types from confidential file contents.
2. A difficult upload step locates friction in selection, transfer or processing. Record the stage and instruction involved without requesting the actual document or assuming a backend defect.
3. Recovery guidance should connect an error with a correction the user can make. Examine whether the message identifies the requirement and next step rather than merely naming failure.
4. Completion signals should distinguish transferred, processing and usable files. Compare the user's understanding with actual states before changing confirmation copy or claiming that the file was accepted.
5. Preparation guidance can prevent avoidable retries by explaining size, type or structure requirements beforehand. Choose examples based on the reported gap and use synthetic files only.

Interpretation caution: Do not request confidential file contents to explain the problem.