Update Checks Guidelines

The First Round Check is requested by Web Content Specialists after completing a self-check.

1. The last step of a project’s Initial Build task is to complete a self check. Once you’ve finished building in Wordpress, export a checklist copy of these criteria to guide your self check.
2. After making any edits to match the checklist, submit your site for an official First Round Check.
   1. Move your Initial Build task status to “Complete” in the SBMM Tasks table.
   2. Move your Onboarding Project status to “First Round Check” in the SBMM Onboarding table.
   3. Navigate to the #checks_fhs Slack channel.
   4. Open the channel workflows and select the First Round – Update option.
   5. Fill out the form:
      1. Type of Check
      2. Provide a link to the SBMM Onboarding project.
      3. Select the Project Coordinator assigned to the project in Airtable.
      4. Provide the shortname from the Airtable field: Shortname (Intake Form).
      5. Provide the site build URL (fareharbor.me URL).
      6. Fill the “Were there any best practices not followed? Why?” field with any client demands or technical challenges that impacted your ability to meet checks criteria. Checkers should not leave you any feedback concerning exceptions noted here.
   6. Your project coordinator will fill out the check form and your feedback will be delivered to you in the Airtable Onboarding project. The project will be passed to Copy for their check before it finally reaches the Checks Feedback status.
   7. Please make any necessary changes once the project has been assigned back to you in Airtable.

The First Round Check requested by Web Content Specialists will tag the Update project’s PC. Team Leads will monitor the channel to make sure Project Coordinators are responsive or pick up checks where needed.

1. The WCS assigned to your project will submit the First Round check workflow from #checks_fhs, tagging you in the post.
2. Read through the “Notes for Checker” field. WCS should explain why certain pieces of feedback may be inapplicable to their build.
3. Post in a reply thread that you are beginning your check.
4. Open the First Round Checks form and the site linked in the post. (Optional: Export a checklist copy of FRC criteria to guide your check).
5. Compare all major pages (listed below) against the checklist’s related criteria, marking the check form when an issue is spotted. Use the text fields to explain where on the page the issue is. If there are multiple pages or places on the page where the issue is present, note it in the text field.
   1. Homepage
   2. Segmentation (All Activities, All Categories, or Category pages)
   3. Activities (yes, every single activity page)
   4. Any “top-most” foundational pages (first in their menu dropdown if there are multiple related to a topic)
      1. About Us
      2. Contact Us
      3. Etc.
6. Make sure to check each page mentioned above for general criteria as well:
   1. Color scheme
   2. Button/Link function
   3. Mobile friendliness
7. Pressing Submit will post the feedback to the Airtable card for the project.
8. Return to the project in Airtable and change its status to Copy Check. A copywriter will claim the check and forward the project to the WCS when completed.

The Live Round Check will be requested by the Project Coordinator and will tag the WCS and the WCS check partner. The check will be completed by a WCS (the WCS check partner) who did not complete the update project.

1. The PC of the project will submit the Live Check – Update workflow from #checks_fhs, tagging the WCS and the WCS check partner in the post.
2. Please complete the Tech Audit as soon as possible. If there are errors present, correct them. Restart the Tech Audit to confirm there are no errors, then post a message in the original #checks_fhs thread to say so.
3. The WCS check partner will post a reply in the thread that they are beginning the check.
4. Open the Live Round Check form and the site linked in the post.
5. Complete the check with the checklist’s criteria, marking the check form when an issue is spotted. Use the text fields to explain where on the page the issue is. If there are multiple pages or places on the page where the issue is present, note it in the text field.
6. Pressing Submit will post the feedback to the Airtable card for the project.
7. Return to the checks post in #checks_fhs, noting that the live check is complete.

1. After completing any Go-Live prep, the Project Coordinator will post a Live Round check in #checks_fhs using the Live Check – Update to ask for a Tech Audit. The post will tag the WCS and WCS check partner.
2. Once the live check is complete, the WCS check partner will notify the PC on the post in #checks_fhs.
3. The PC will implement any feedback from the live check and notify on the #checks_fhs thread when complete.