Managing Build Reviews in HubSpot

External Resources

HubSpot User Guide: Build Reviews for Specialists

Visual Walkthrough Guide

Overview

The Build Review process ensures quality and consistency before client launches. Product Specialists submit completed builds for Team Lead review, receive feedback, make any necessary revisions, and obtain approval before moving to the launch phase.

---

 

Submitting Your Build for Review

Before You Submit

Complete these steps:

1. Finish all build tasks in the advertising platform
2. Mark all build milestone tasks complete in HubSpot
3. Conduct your own quality check

Submit Build Notes

1. Navigate to your On-Boarding project
2. Click the "Submit Build Notes" tab (or "Playbooks" tab → "Open Playbook")
3. Complete the Build Notes playbook form
4. Click "Log Note" to save your documentation

Submit for Review

1. Locate the "Build Review Status" field in the left column of your project
2. Change the value to "Build submitted for review"
3. The project automatically moves to "Build Review" stage
4. A review task is created for your Team Lead

That's it. You'll receive a notification when the review is complete.

---

Understanding Review Outcomes

Your Team Lead will update the Build Review Status field to one of three outcomes:

✅ No Further Changes or Suggestions (Approved)

• What it means: Build is approved, ready for launch
• Your action: None required. Project moves to Build Completed stage automatically

⚠️ Build Changes Suggested (Approved)

• What it means: Build is approved for launch, but improvements are suggested
• Your action: Review suggestions and implement during launch or early optimization phase

❌ Build Changes Needed (Not Approved)

• What it means: Build requires revisions before approval
• Your action: Follow the revision process below

---

Handling Build Revisions

When changes are required:

1. Review feedback: Find your Team Lead's Build Review note in the activity feed
2. Make platform changes: Update campaigns in the advertising platform based on feedback
3. Update documentation: Either:
   • Edit your original Build Notes, OR
   • Add a comment to your Build Notes explaining what changed
4. Resubmit: Change Build Review Status back to "Build submitted for review"

The review cycle continues until your build is approved.

---

For Team Leads: Performing Build Reviews

Complete the Build Review

1. Receive task for Completing Build Review from On-Boarding Project
2. Navigate to the On-Boarding project
3. Click "Submit Build Review Notes" tab → "Open Playbook"
4. Review campaigns in the advertising platform
5. Review the Product Specialist's Build Notes
6. Complete the Build Review playbook:
   • Select "No Changes," "Change Needed," or "Change Suggested" for each section
     • Add specific feedback in text fields where changes are needed
7. Click "Log Note" to save your review

Make Approval Decision

Locate the "Build Review Status" field and select:

• "No further changes or suggestions" → Fully approved
• "Build changes suggested (approved)" → Approved with optional improvements
• "Build changes needed (not approved)" → Requires revisions

The appropriate workflow triggers automatically based on your selection.

---

Key Reminders

For Product Specialists:

• Complete your own quality check before submitting
• Provide thorough Build Notes explaining your strategy and decisions
• Respond promptly to revision requests
• Update the Build Review Status field—this is what triggers the workflow

For Team Leads:

• Be specific in your feedback
• Use "Change Suggested" for non-blocking improvements
• Update the Build Review Status field to finalize your decision

---

Frequently Asked Questions

Q: Can I edit my Build Notes after submitting? Yes. Click on the note in the activity feed, edit the text, and save. If resubmitting after revisions, clearly indicate what changed.

Q: Where do I find the Build Review Status field? Left column of the On-Boarding project record, in the "Build Review" card section.