\n\n\n\n
1. Initial Communication<\/h2>\n\n\n\n
When you get assigned a client-based project on Basecamp, you will find a copy of the client\u2019s original request in there. Sometimes that will contain enough information for you to start working. But if that is not the case, the following are a few things every first email to a client should always contain:<\/p>\n\n\n\n
- Subject Line<\/strong>: your subject line should be something short and simple that the client can recognize
- A good tip for this is to quote the client on their original request
- Use their words to make it easier for them to recognize<\/li><\/ul><\/li><\/ul><\/li>
- Greeting<\/strong>: always address the client, \u201cHello Valerie,\u201d and using their name as stated in their original request
- If they are a professor, best to address them as \u201cProfessor\u201d or if they have a doctorate, \u201cDr.\u201d unless they state they\u2019d rather be referred to as their first name<\/li><\/ul><\/li>
- Introduction<\/strong>: (if you haven\u2019t met in person yet) introduce yourself as the STA working on their request
- Re-state the project or explain what you\u2019re writing about to reaffirm what this email pertains to<\/li><\/ul><\/li>
- Content<\/strong>: whatever the purpose of this email is, make sure to ask specific questions. For instance, if you are designing something like a logo make sure to ask for clarification on the following (if it hasn\u2019t already been specified):
- The color palette<\/li>
- The preferred file size<\/li>
- The preferred file type
- .pdf, .psd, .ai, .png, .jpg, etc<\/li><\/ul><\/li><\/ul>
- The intended purposes of the design (web use or printing)
- This one is important to know what type of export you will have to make<\/li><\/ul><\/li><\/ul>
- The project due date
- Make sure that you have enough time to work on the project and if the due date does not<\/li><\/ul><\/li><\/ul>
- Feel free to to ask anything else that might be pertinent to your specific project<\/li><\/ul><\/li>
- Follow Up<\/strong>: close the email by stating whatever is next and assure the client that if they have any comments, questions, suggestions, or further requests they are welcome to contact you again (or reference someone else if needed)
- This can look something like \u201cIf you have any questions please contact myself or ________\u2026\u201d<\/li><\/ul><\/li>
- Signature<\/strong>: conclude the email with a formal goodbye and your official STA email signature
- If you do not have an STA signature yet make sure to set that up. Include:
- Your name and pronouns<\/li>
- Your position as an STA and the year<\/li>
- Your organization: specify LAITS<\/li>
- Your preferred form of contact<\/li>
- Something like this:<\/li><\/ul><\/li><\/ul><\/li><\/ul>\n\n\n\n
Jac Alford <\/strong>(she\/her)<\/em>
Design Student Technology Assistant<\/em>
Liberal Arts Instructional Technology Services \u2013 LAITS<\/em>
alfordjaclyn@utexas.edu<\/a>
(979) 406-0025<\/em><\/p><\/blockquote>\n\n\n\n- General Tips:<\/strong>
- Keep it short; respect your reader\u2019s time
- Read what you initially wrote; is there a way to write what you are trying to say in a shorter\/more efficient way (while still keeping a warm and professional tone fo course)?<\/li><\/ul><\/li><\/ul>
- If you mention something, link to it
- Even better if you include images, too<\/li><\/ul><\/li>
- Always CC Suloni and whoever else may be on that project (staff + other STAs) that way everyone is in the loop<\/li><\/ul><\/li><\/ul>\n\n\n\n
This is an example of what one of these emails could look like:<\/p>\n\n\n\n
![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2022\/04\/KB-ClientComm-Mail-1-1024x768.png\")
<\/figure><\/div>\n\n\n\n
\n\n\n\n2. Specs Communication<\/h2>\n\n\n\n
These emails are follow-ups for the client\u2019s requests. They include specifications you might not have clarified yet. Is there anything else you would like to ask or inform the client about? This is your moment to do so.<\/p>\n\n\n\n
For these emails \u2013other than using a similar email format as demonstrated in the previous section\u2013 you will need to be more specific concerning what your plan of action is. The client must know what they should expect from you by the time you turn in your final designs.<\/p>\n\n\n\n
IMPORTANT<\/strong>: If you are attaching images or documents, make sure to properly name any attachments<\/strong> as clear as possible. Not all attached files are visible when receiving an email. Your client needs to know what each attachment is going to be even if they are not able to see the file without downloading it.<\/p>\n\n\n\n
The following is a general guideline for file naming conventions:<\/p>\n\n\n\n
\n![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2022\/04\/KB-ClientComm-NamingAttachments-1024x576.png\")
<\/figure><\/div>\n<\/div><\/div>\n\n\n\nFurthermore, this is an example of what one of these emails could look like:<\/p>\n\n\n\n
![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2022\/04\/KB-ClientComm-Mail-2-1024x697.png\")
<\/figure><\/div>\n\n\n\n
\n\n\n\n3. Final Communication<\/h2>\n\n\n\n
Finally, this will be the last email you are expected to send to the client. In this email you should attach whatever final deliverable(s) you worked on. Most of the time these deliverables should be uploaded into a Box folder that you will link in the email.<\/p>\n\n\n\n
In addition, you are expected to include a usage guideline file. In this document you shall explain in full detail how your designs should be included in their corresponding contexts. The following are a few things every pdf guide should include:<\/p>\n\n\n\n
- Introduction<\/strong>: an introduction of the guide\u2019s content<\/li>
- Naming<\/strong>: a description of the naming conventions and how\/why the name of each of the files you uploaded into the Box folder are different from each other<\/li>
- Mock-Ups<\/strong>: include mock-ups of your design in different formats so that the client can view your work in the corresponding context
- Make sure to explicitly reference the name of the design file used in each mock-up<\/strong><\/li>
- Also, if you find it useful, feel free to add explanations for the client to understand why each design is used in their respective mockup
- If the designs are interchangeable in context make sure to say that<\/li>
- If not, explain why each one has its own specific purpose<\/li><\/ul><\/li><\/ul><\/li><\/ul>\n\n\n\n
The following is a good example of what you could include in a pdf guidance document:<\/p>\n\n\n\n
![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2020\/10\/Client_Communication_GOVLogo_Guide_1-232x300.png\")
<\/a><\/figure><\/li>![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2020\/10\/Client_Communication_GOVLogo_Guide_2-232x300.png\")
<\/a><\/figure><\/li>![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2020\/10\/Client_Communication_GOVLogo_Guide_3-235x300.png\")
<\/a><\/figure><\/li>![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2020\/10\/Client_Communication_GOVLogo_Guide_4-232x300.png\")
<\/a><\/figure><\/li>![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2020\/10\/Client_Communication_GOVLogo_Guide_5-232x300.png\")
<\/a><\/figure><\/li><\/ul><\/figure>\n\n\n\nSome other important new information you should include in this final communication email are:<\/p>\n\n\n\n
- Introduction<\/strong>: a description of what you worked on
- Link the Box folder!
- Brief description of what is in the folder<\/li><\/ul><\/li><\/ul><\/li>
- PDF Guide<\/strong>: comment on how you included a guide for them
- Link or attach the guide<\/li><\/ul><\/li>
- Assurance<\/strong>: assure the client that if they have any more comments, questions, or further requests they are welcome to contact you again<\/li>
- Signature<\/strong>: conclude the email with a formal goodbye and your email signature<\/li><\/ul>\n\n\n\n
This is an example of what one of these final communication emails could look like:<\/p>\n\n\n\n
![\"\"](\"https:\/\/sites.la.utexas.edu\/kb\/files\/2022\/04\/KB-ClientComm-Mail-3-1024x768.png\")
<\/figure><\/div>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
Client-based projects are a very common thing you will face working as a Student Technology Assistant for LAITS. Therefore, it must be emphasized that for every one of those projects you get assigned to, maintaining proper communication with the client … Continue reading
- Signature<\/strong>: conclude the email with a formal goodbye and your email signature<\/li><\/ul>\n\n\n\n
- Link the Box folder!
- Also, if you find it useful, feel free to add explanations for the client to understand why each design is used in their respective mockup
- Naming<\/strong>: a description of the naming conventions and how\/why the name of each of the files you uploaded into the Box folder are different from each other<\/li>
- Introduction<\/strong>: an introduction of the guide\u2019s content<\/li>
- If you mention something, link to it
- Read what you initially wrote; is there a way to write what you are trying to say in a shorter\/more efficient way (while still keeping a warm and professional tone fo course)?<\/li><\/ul><\/li><\/ul>
- Keep it short; respect your reader\u2019s time
- General Tips:<\/strong>
- If you do not have an STA signature yet make sure to set that up. Include:
- Make sure that you have enough time to work on the project and if the due date does not<\/li><\/ul><\/li><\/ul>
- The project due date
- This one is important to know what type of export you will have to make<\/li><\/ul><\/li><\/ul>
- The intended purposes of the design (web use or printing)
- .pdf, .psd, .ai, .png, .jpg, etc<\/li><\/ul><\/li><\/ul>
- A good tip for this is to quote the client on their original request