The team may elect to utilize a process that is different from the steps below. If not otherwise specified, follow the steps outlined here.

Steps for Proofing

1. You will receive email notification that a proof is ready for you in Wrike. If you are expecting a proof request but don’t see it, check your junk email folder, and whitelist the noreply@wrike.com address for future communications.
2. Click “Proceed to Review”.
3. Click through the tutorial popups if you are unfamiliar with the markup process or watch this quick, 1-minute video which demonstrates some tools.
4. Mark anything that needs to be modified, added, or removed, type out your thoughts and what you want changed in the comment box, then click “Changes Required” on the bottom right. If no changes are required, click the green “Approve” button. NOTE: IF APPROVAL OR CHANGES ARE NOT SUBMITTED WITHIN 5 BUSINESS DAYS YOUR TIMELINE WILL BE EXTENDED BY ONE WEEK WHICH MAY IMPACT THE DATE YOU RECEIVE THE FINAL PRODUCT. If you know that you will be out of the office, please contact Jared (jgwest@purdue.edu) or Kayla (clark384@purdue.edu) for assistance in schedule adjustments.
5. Following your approval, we will move forward with your project's next step whether that is publishing, printing, or sending it to you.

Notes on Providing Feedback

• Please be sure to provide all feedback through Wrike.
• All email or Teams communication with the designer should also include Kayla. (clark384@purdue.edu). This is because some of our designers have variable schedules. If Kayla is copied on the communication, we can guarantee a quicker response than if she is not.
• If you are struggling to use Wrike for proofing, please reach out to Jared (jgwest@purdue.edu) or Kayla for assistance. They are happy to walk you through the process!
• All feedback should be specific, both in terms of what is wrong and what you want changed.
  • Good- “Adjust the color of the car to be green instead of blue.”
  • Bad- “The color of the car is wrong.” 

Types of Projects

Graphic design projects are organized into three tiers:

• Tier 3
  • Graphics updates to pre-existing projects or simple graphics, pure production work based on templated work, minor updates/revisions, repurposing, etc.
  • 1-2 Weeks
• Tier 2
  • New deliverables based on an approved creative concept
  • 2-4 Weeks
• Tier 1
  • New overarching strategy, projects that require a creative brief, etc.
  • 4 weeks or more, pending the department's workload and established priorities. Discussion and transparent project timelines would be set during the initial project request setup or launch meeting. Varies by project.

Tier 3 and most tier 2 projects are almost exclusively handled by the graphic design team and the entire process takes place through Wrike. 

Tier 1 and some tier 2 projects are typically managed by a project manager who handles much of the communication between yourself and the marketing team. All proofing of graphic design work will follow the same process even if someone outside of the design team is your main point of contact.

The team may elect to utilize a process that is different from the steps below. If not otherwise specified, follow the steps outlined here.

Steps for Proofing

1. You will receive email from Matt (mvader@purdue.edu) notifying you that your proof is ready. This email should include a OneDrive link. Click on that link to view your proof.
2. Please check facts and review quotes as you read through the copy. When proofing, if you see something that needs to be changed highlight the words and click the comment button on the right side of the page, or the comment button on the right side of the popup.
   
3. Once you have marked everything that you would like to be changed or are ready to approve, please respond to Matt in the email chain. If no review is provided within 10 business days we may move forward on your project so as not to delay other clients.

Notes on Providing Feedback

• Please be sure to provide all feedback through OneDrive. SAVING THE FILE AND SENDING BACK A WORD DOC MAY RESULT IN SOME OF YOUR EDITS GETTING LOST. If all edits, especially when more than one person is providing feedback, are on the same document we can avoid unnecessary confusion.
• All feedback should be specific and actionable, both in terms of what is wrong and what you want changed.
  • Good- “This sentence should go at the end of the paragraph.”
  • Bad- “I don’t like the placement of this sentence.”
• Common edits include changes in accordance with the Purdue Editorial Style Guide and other AP formatting guidelines. Please ask Matt for clarification if needed. Some examples:
  • Dr. is only used as a title for medical doctors. Professor is the preferred term for all others according to the AP Stylebook.
  • Alumnus means one man. Alumna means one woman. Alumni means plural men or plural for a group containing men and women. Alumnae means plural women.

Web proofs feedback may be completed through email communication or via the Wrike Web Content Extension. The Wrike Web Content Extension requires Google Chrome and the installation of an extension for that browser. (Please contact Andi Hedrick (hedricka@purdue.edu) or Jared West (jgwest@purdue.edu) if you need assistance with the installation.)

However, the team may elect to utilize a process that is different from the steps below. If not otherwise specified, follow the steps outlined here.

NOTE: For very small web updates (ie. updating a phone number or a few words on a page), sending a proof for every minor change may not make sense. The Student Life web team reserves the right to complete minor tasks and close the ticket without sending a proof first. Requesters will be notified that their requested change is complete.

METHOD 1: Steps for Proofing through email communication

1. You will receive email from Wrike (noreply@wrike.com or wrike@wrike.com) notifying you that your proof is ready. If you are expecting a proof request but don’t see it, check your junk email folder and whitelist the noreply@wrike.com and wrike@wrike.com addresses for future communications.
2. If the web team hasn’t received a reply within a few days, you will receive a follow-up email from Danielle (dfawbush@purdue.edu) or Patrick (pkleckne@purdue.edu) reminding you that your proof is ready. Locate the Wrike proof email and reply.
3. Emails will contain a link to the new or updated webpages that you requested. Review the webpages and reply to the email with your feedback on anything that should be added, changed, or removed. If no further edits are necessary, reply to the email with your approval so that the project can proceed.

METHOD 2: Steps for Proofing through the Wrike Web Content Extension

1. Download Wrike Web Content Extension for Google Chrome
2. Open the email requesting your review and click on “Proceed to Review” and open the link in Google Chrome. If you do not use Google Chrome, you will be unable to review the website. Navigate the website just like normal. Use the markup tools at the bottom of the page to suggest edits. Please watch this quick, 1-minute video to learn about the available markup tools. Be sure to comment exactly what should be changed and what it should be changed to.
3. Once you have completely reviewed the website and added your comments click “Changes Required” on the bottom right. If no changes are required, click the green “Approve” button.

Notes on Providing Feedback

• Please provide all feedback through either email or Wrike extension. You can do this by replying to the proof request email that was sent via the Wrike project system, or by using the Wrike Web Content Extension.
• Questions can be directed to Danielle (dfawbush@purdue.edu) or Patrick (pkleckne@purdue.edu).
• All feedback should be specific, both in terms of what is wrong and what you want changed.
  • Good- “Edit the text in this section to be in bullet points instead of paragraph form”
  • Bad- “The format of this section should be changed.”

Types of Projects

Web design projects are organized into three tiers:

• Tier 3
  • Minor web updates. For example, a tier 3 web design project could involve changing the wording on an existing page, updating images, and so on.
  • Timeline: 1-2 Weeks
• Tier 2
  • More complex web updates. For example, a tier 2 web design project could involve the creation of new pages under an existing web structure. This will likely require a meeting between the client and the web team.
  • Timeline: 2-4 Weeks or longer depending on complexity
• Tier 1
  • New website creation or overhaul project. For example, an entirely new website for a new department, or a refresh of an entire department’s website. Projects of this magnitude typically require multiple meetings with the requester, timeline planning, and determination of prioritization between Student Life Marketing staff, leadership, and Purdue IT.
  • Contact the Student Life Marketing team for more information on timelines. New website creation or overhauls depend heavily on SL Marketing’s workload and established priorities. Discussion and transparent project timelines would be set during the initial project request setup or launch meeting. Varies by project.

Tier 3 and some tier 2 projects are almost exclusively handled by the SL Marketing web team and the process takes place within Wrike. This is with the exception of very minor updates (quick changes to wording, etc.) and may not require a proof. See the note in the Web Design proofing introductory section above.

Tier 1 and some tier 2 projects are typically managed by a project manager who handles much of the communication between yourself and the marketing team. All proofing of graphic design work will follow the same process even if someone outside of the web team is your main point of contact.

The web team also handles emails and they may elect to utilize a process that is different from the steps below. If not otherwise specified, follow the steps outlined here.

Steps for Proofing

1. You will receive an email notification that a proof is ready for you in Delivra (our email marketing system). If you are expecting a proof request but don’t see it, check your junk email folder. The email will come from an email address similar to collaborate-1003799-1148251@lists.n-email1.net.
2. Reply to the proof email from the Delivra system with any feedback. Replying to the proof email  is important to be sure that your feedback is captured by the Delivra system so that it can be acted upon, and so that everyone copied on the proof receives the same feedback. If you have no feedback, please respond that the email is approved for sending.
3. NOTE: IF APPROVAL OR CHANGES ARE NOT SUBMITTED WITHIN 5 BUSINESS DAYS YOUR TIMELINE WILL BE EXTENDED BY ONE WEEK WHICH MAY IMPACT THE DATE YOU RECEIVE THE FINAL PRODUCT. If you know that you will be out of the office, please contact Danielle (dfawbush@purdue.edu) or Patrick (pkleckne@purdue.edu) for assistance in schedule adjustments.
4. Following your approval, we will move forward with your email’s next step for distribution.

Notes on Providing Feedback

• Please be sure to provide all feedback by replying to the proof email sent by Delivra.
• All feedback should be specific and actionable, both in terms of what is wrong and what you want changed.
  • Good- “Edit the text in this section to be in bullet points instead of paragraph form.”
  • Bad- “The format of this section should be changed.”

The social media team may elect to utilize a process that is different from the steps below. If not otherwise specified, follow the steps outlined here. Note that not all social posts require proofs.

Steps for Proofing

1. If a proof is necessary for your social media post or campaign, you will receive an email from Wrike (noreply@wrike.com or wrike@wrike.com) notifying you that your proof is ready. If you are expecting a proof request but don’t see it, check your junk email folder and whitelist the noreply@wrike.com and wrike@wrike.com addresses for future communications.
2. Click “Proceed to Review”.
3. Click through the tutorial popups if you are unfamiliar with the markup process or watch this quick, 1-minute video which demonstrates some tools.
4. Mark anything that needs to be modified, added, or removed, type out your thoughts and what you want changed in the comment box, then click “Changes Required” on the bottom right. If no changes are required, click the green “Approve” button. NOTE: IF APPROVAL OR CHANGES ARE NOT SUBMITTED WITHIN 5 BUSINESS DAYS YOUR TIMELINE MAY BE EXTENDED BY ONE WEEK WHICH COULD IMPACT THE DATE YOU RECEIVE THE FINAL PRODUCT. If you know that you will be out of the office, please contact Jared (jgwest@purdue.edu) or Gina (ypleshka@purdue.edu) for assistance in schedule adjustments.
5. Following your approval, we will move forward with your project's next step whether that is publishing, printing, or sending it to you.

Notes on Providing Feedback

• Please be sure to provide all feedback by replying to the proof email sent by Wrike.
• All feedback should be specific and actionable, both in terms of what is wrong and what should be changed.
  • Good- “Edit the text in this section to be in bullet points instead of paragraph form.”
  • Bad- “The format of this section should be changed.”