---
title: Website Review Process Streamlining — Google Doc Tracker Pattern
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2025-12-02-vcedc-website-meeting-105716500.md
tags:
- website
- project-management
- review-process
- client-communication
- workflow
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Website Review Process Streamlining — Google Doc Tracker Pattern

## Overview

Late-stage website projects frequently suffer from feedback fragmentation: clients send notes via email, chat, and verbal calls simultaneously, while the agency team struggles to track which changes have been applied and which pages are truly final. A shared Google Doc tracker with clearly defined status columns resolves this by creating a single source of truth that both sides can read and update in real time.

This pattern emerged from the [[clients/vcedc/index|VCEDC]] website pre-launch review process, where back-and-forth confusion threatened the December 15 launch timeline.

## The Pattern

### Two-Column Status System

Structure the tracker with at minimum two key status columns:

| Column | Owner | Meaning |
|---|---|---|
| **Ready for Review** | Agency | Page content and design are finalized on the agency side; client should now review |
| **Final Review** | Client | Client marks "Approved" or adds edits directly in the doc |

The agency controls the "Ready for Review" signal. The client controls the "Final Review" signal. Neither side should mark a page complete in the other's column.

### Rules of Engagement

- **All feedback goes in the doc.** No parallel email threads, no verbal-only changes. If it isn't in the tracker, it doesn't exist.
- **Agency cleans up resolved comments** before handing back to the client. Stale comments create noise and erode trust in the document as a source of truth.
- **Client marks "Approved" only when genuinely approved.** If edits remain, they note them in the doc rather than marking approved and following up separately.
- **Wrap text in all cells** so status notes are fully visible without column resizing.

### When to Apply This Pattern

This pattern is most valuable during the final 2–4 weeks before a website launch, when:
- Multiple pages are in different states of completion simultaneously
- The client needs to do a consolidated final review rather than page-by-page spot checks
- The agency is batching developer changes to minimize repeated touches

## Evidence

During the VCEDC pre-launch meeting (2025-12-02), the client explicitly flagged confusion from the existing back-and-forth process:

> "There's just so much back and forth right now. If I could get one link with everything updated, send it all back to me so I can give it one final look before we get it to our board."

The Google Doc tracker was already in use but inconsistently. Formalizing the two-column handoff system — with the agency marking "Ready for Review" and the client responding in "Final Review" — gave both sides a clear protocol for the remaining pre-launch sprint.

The agency also committed to cleaning up old resolved comments so the client could read the document as a clean final checklist rather than an archaeological record of earlier drafts.

## Implementation Notes

- **Notify on changes.** Google Docs comment notifications should be active for all parties so neither side has to poll the document manually.
- **Don't over-engineer.** Two columns (Ready for Review, Final Review) are sufficient. Adding more status states (In Progress, Needs Info, etc.) increases maintenance burden without proportional clarity gain.
- **Pair with a consolidated review link.** The tracker works best when the agency also provides a single staging URL — not page-by-page links — so the client can click through the full site in one session and cross-reference the tracker simultaneously.
- **Set a hard feedback deadline.** In the VCEDC case, the client agreed to complete her tracker review by EOW (Dec 5), giving the developer a clear window to implement final changes before the Dec 12 board preview link.

## Related

- [[clients/vcedc/index|VCEDC Client Overview]]
- [[clients/vcedc/meetings/2025-12-02-pre-launch-review|VCEDC Pre-Launch Review Meeting (2025-12-02)]]