Reviewing and Approving Deliverables

Effective review and approval processes keep your project on track and ensure you receive deliverables that meet your expectations. This guide outlines PNP's review workflow and best practices for efficiently approving your project deliverables.

The PNP Review Cycle

Every deliverable follows this standard review process:

1. Delivery Notification

When a deliverable is ready for your review:

  • You'll receive a Teamwork notification
  • Your Customer Success Manager will email you
  • The task status will change to "Ready for Review"

Expected Response Time: 48 business hours

2. Review Process

Once notified, you can begin your review:

  1. Access the deliverable in Teamwork
  2. Review against project requirements
  3. Test functionality (if applicable)
  4. Gather internal stakeholder feedback
  5. Consolidate all feedback in one response

Pro Tip: Schedule a dedicated review time on your calendar to ensure thorough evaluation.

3. Feedback Submission

Provide your feedback using the appropriate method:

  • Design Deliverables: Use annotation tools directly on the designs
  • Technical Deliverables: Test and document specific issues
  • Document Deliverables: Use comments and track changes
  • Complex Deliverables: Request a review meeting with your PNP team

4. Revision Process

After receiving your feedback:

  • PNP team implements requested revisions
  • Your Customer Success Manager updates you on progress
  • Revised deliverable is submitted for another review
  • The cycle continues until approval

5. Final Approval

When you're satisfied with the deliverable:

  • Mark the deliverable as "Approved" in Teamwork
  • Your Customer Success Manager will confirm approval
  • The deliverable moves to the Final Deliverables folder
  • Project progresses to the next milestone

Types of Deliverables & Review Guidance

Different deliverables require different review approaches:

Visual Design Assets

What to check:

  • Brand consistency (colors, typography, imagery)
  • Design effectiveness for target audience
  • Alignment with project brief and goals
  • Technical specifications (dimensions, resolution)
  • Spelling and grammar in all text elements

Review tools:

  • Use Teamwork's visual annotation tools
  • Reference mood boards and approved concepts
  • Compare against brand guidelines

Website & Digital Products

What to check:

  • Functionality across devices and browsers
  • User flows and navigation
  • Content accuracy and placement
  • Loading speed and performance
  • Responsive behavior on different screen sizes

Review tools:

  • Use browser testing tools
  • Test on multiple devices
  • Follow testing scripts provided by your PNP team
  • Document issues with screenshots and browser details

Content Deliverables

What to check:

  • Messaging alignment with brand voice
  • Accuracy of information
  • SEO elements (if applicable)
  • Formatting and structure
  • Grammar and spelling

Review tools:

  • Use Teamwork's document markup features
  • Reference content strategy documents
  • Check against style guides

Technical Implementations

What to check:

  • Functionality matches requirements
  • Performance meets expectations
  • Integration with existing systems
  • Error handling and edge cases
  • Security considerations

Review tools:

  • Follow test scripts provided
  • Document specific steps to reproduce issues
  • Include error messages and system details

Approval Best Practices

Establish Clear Approval Hierarchy

Define who has final approval authority:

RoleApproval ResponsibilityProject SponsorOverall project direction and budgetDepartment LeadDomain-specific requirementsProject ManagerTimeline and scope adherenceSubject Matter ExpertsTechnical accuracy and standards

Create an Approval Checklist

For each major deliverable, use a checklist approach:

✓ Meets all requirements outlined in the project brief

✓ Aligns with brand guidelines and standards

✓ Functions correctly across required platforms

✓ Content is accurate and error-free

✓ Addresses all previous feedback appropriately

✓ Ready for public/internal use

Document Your Approval

When approving deliverables:

  1. Be explicit: "I approve this deliverable" (avoid ambiguous language)
  2. Note any minor issues that don't require another review cycle
  3. Specify any conditions of approval ("Approved with the understanding that...")
  4. Indicate any related items that still need attention

Handling Common Review Challenges

When Stakeholders Disagree

If your internal team has differing opinions:

  1. Refer back to the project goals and requirements
  2. Prioritize feedback based on user needs and business impact
  3. Consider A/B testing for major disagreements
  4. Hold an internal consensus meeting before providing feedback

When Revisions Don't Meet Expectations

If a revised deliverable still doesn't meet your needs:

  1. Be more specific about what isn't working
  2. Request a review call for direct discussion
  3. Ask for alternative approaches or options
  4. Reference examples that better reflect your vision

When Requirements Change Mid-Project

If your needs evolve during the project:

  1. Discuss with your Customer Success Manager first
  2. Understand the impact on timeline and budget
  3. Formally document the revised requirements
  4. Adjust review criteria to match new expectations

Managing Review Timelines

Standard Review Windows

Deliverable Type Review Time Revision Time
Design Concepts 2–3 business days 3–5 business days
Website Pages 2–3 business days 3–7 business days
Written Content 2 business days 2–3 business days
Technical Implementations 3–5 business days 5–10 business days

Expedited Reviews

Need faster turnaround?

  • Notify your Customer Success Manager in advance
  • Consider focused review meetings for immediate feedback
  • Prioritize critical elements first, then secondary items
  • Schedule dedicated review time on your calendar

Final Delivery & Handover

Once all deliverables are approved:

1. Final Package Assembly

PNP prepares your final deliverables:

  • All assets organized in agreed formats
  • Documentation and user guides
  • Source files and editable versions
  • Implementation instructions (if applicable)

2. Delivery Meeting

A formal handover session including:

  • Walkthrough of all deliverables
  • Training on usage and implementation
  • Questions and answers session
  • Discussion of maintenance and support

3. Project Closure

Completing the project cycle:

  • Final approval documentation
  • Project retrospective discussion
  • Setup of any ongoing support
  • Introduction to maintenance team (if applicable)

Need Help With Reviews?

If you need assistance with the review process:

  • Ask your Customer Success Manager about guided review sessions
  • Request templates for specific types of feedback
  • Schedule a demo of Teamwork's review tools
  • Set up a review planning call for complex deliverables