Service page file upload instructions should tell a customer what to send, why the business needs it and how to know the upload worked. “Attach your documents” leaves too many questions unanswered when the customer does not know which files are useful.
Write the instructions from your actual service process. Confirm requirements with the team receiving the files and check what the live form accepts. The page, form and confirmation message should describe the same task.
Name the files needed for the next step
Start with the purpose of the request. A repair estimate might need photographs that show the item and the issue. A design enquiry might need an existing brief or reference document. Explain the specific next decision those files support instead of collecting material simply because the form has an upload field.
Separate required files from optional supporting material. If a customer can request an initial conversation without a document, say so. Your service preparation checklist can link to these instructions without repeating a different set of requirements.
State formats, size limits and file counts
List only the formats the live form supports. Say whether the size limit applies to each file or to the whole submission. If there is a maximum number of attachments, explain it before customers start selecting files.
Do not invent limits for the website copy. Test representative sample files through the approved testing process and have the team confirm the current restrictions. Use ordinary names alongside technical abbreviations when they help the intended reader.
The W3C form-instructions tutorial recommends explaining required and optional inputs, expected formats and other relevant information. Keep essential instructions visible beside the upload task; a disappearing placeholder is a poor place for information the reader needs while checking their submission.
Explain what makes a useful attachment
Describe the content rather than merely demanding “high quality”. For a photograph, the team might need the whole item and a separate close view of the relevant detail. For a document, the team might need the complete brief rather than an image of its first page. Confirm the actual requirements before publishing either example.
Use a short checklist that customers can act on. Explain whether multiple pages belong in one document and whether a particular filename is helpful. Avoid complicated naming rules unless the receiving process genuinely needs them.
If some information is unnecessary, say what customers can leave out. Route any sensitive material through the business’s established appropriate channel instead of asking people to post attachments in public comments.
Make success and failure clear
Distinguish selecting a file from submitting the form. A filename appearing beside a field may mean the file is selected, while the enquiry still needs to be submitted. Explain the final action and the confirmation the customer should expect.
When an upload fails, help the customer identify the next step. A useful message might name the unsupported format or exceeded size limit, based on what the system can actually detect. Provide a contact route when the customer cannot resolve the problem.
Keep response expectations aligned with your service turnaround information. Do not promise an immediate review just because the upload itself completes immediately.
Use a short wording pattern
This fictional example demonstrates the structure. Replace the file requirements and contact details with information your team has approved.
“Attach the files requested for this service, then submit the enquiry form. The guidance beside the upload field lists the accepted formats and limits. After submission, look for the confirmation message. If the upload does not complete, contact the team using the help link and tell us which step failed.”
Use more specific wording wherever the real requirements are known. A customer should not need to open several pages to find one file-size limit.
Review the instructions as a customer
- Find the upload task from the service page on a phone.
- Check that required files, formats and limits are visible.
- Confirm that selection, submission and success are distinct.
- Review failure messages and the help route.
- Compare the wording with the team’s current receiving process.
Add recurring questions to the service page FAQ and update the instructions whenever the workflow changes. Clear file requests help customers prepare a useful submission and give the receiving team the information it actually needs.