Refresh Continuation — 57 Tickets, 73 Days, Dental — White-Label Delivery for a US Marketing Agency

What a Refresh Continuation Is

57 tickets across 73 days for a dental practice refresh already mid-stream — the agency’s homepage was live, but header and footer had not propagated to the other 33 pages, four new service pages were waiting on approved Figma designs, and a change-request queue had already started to form. Three work streams ran concurrently from day one: propagation, new-page builds, and the change queue, each gated individually through Site Checker before close.

Snapshot

The Brief

The agency had already published a refreshed homepage for Evergreen Grace Dental Care before our engagement started. The brief opened with that fact: “We already published a refreshed homepage… But we need to double-check whether the header and footer were transferred to the other pages.” The homepage design was done — our job was everything that came after it.

Three things needed to happen in parallel. First, the new header and footer had to propagate across the remaining 33 pages; the agency’s sitemap listed 34 URLs and the homepage was the only one where the refresh had fully landed. Second, four new service pages needed to be built from approved Figma designs and a Google Drive folder of copy docs — Clear Aligners, Veneers, Teeth Whitening, Endodontics — against the agency’s existing Service Page template. Third, a queue of change requests was already forming: gallery link bugs, duplicate images, a booking-link update, padding adjustments, footer Instagram logo placement, final menu additions.

The ask was not a single handoff with a cutover date. It was cadence: work through three simultaneous streams without tripping over each other, gate every change through QA before close, and respect the agency’s template system throughout.

Operational Integrity at handoff

The Redmine record carries 41 QA-pass sub-tickets with a -qa suffix — one per work item, generated before each ticket returned to the agency — batched across six sequential invoices (#24–#29) so the hours-to-tickets reconciliation happened invoice by invoice rather than once at engagement end. Pre-ticket-close QA ran through Site Checker — see our QA approach for the categories and the zero-fail bar each ticket had to clear. After handoff the agency ran its own checks, and we cleared each item it raised before signing off on each ticket.

How We Did It

1. Header / footer propagation across the 34-URL sitemap. The agency’s Website Sitemap tab listed 34 URLs alongside their assigned templates (Homepage · Services Lander × 9 · Service Page × 23 · About Us). The refresh had landed on the homepage; we audited header and footer placement on each of the remaining URLs, applied the refreshed design sitewide, and logged any page that required a manual deviation back to the agency. The constraint was typical of continuation work: parts of the site had been touched by a prior developer and the line between “changed” and “not changed” was not always crisp — the team’s rule was not to touch anything the agency had not asked us to touch.

2. Four new service pages built against Figma + copy docs. The agency supplied approved Figma frames for each new service page and a Google Drive folder with copy docs. We mapped those into the agency’s existing dental template (Service Page template) — Clear Aligners, Veneers, Teeth Whitening, Endodontics — keeping each page in draft until the agency released it to the menu. We chose the template path over custom page layouts because the site already ran 34 URLs on the agency’s template system, and divergent page structures would have broken the visual consistency the agency needed across the full sitemap. A constraint surfaced during build: the copy docs and Figma frames covered layout and copy but did not supply images for the new service pages, and meta descriptions were absent from every draft page — both had to be sourced from the legacy site and inserted manually before each page could leave draft status.

3. Change-request queue — worked in parallel with the design and build streams. Change requests came through Redmine while the propagation and new-page work was still active: “Gallery link is not working (change request)”, “Duplicate images (change request)”, “Footer Instagram Logo”, “Booking Link update”, “Too much padding”. Each ticket was scoped, developed, QA’d internally through Site Checker, returned to the agency, and closed on their sign-off. The interleaving of streams is what distinguishes a continuation from a clean refresh — the queue did not wait for the design propagation or the new pages to finish.

4. Two-stage QA — Site Checker pre-ticket-close + agency post-handoff. Every ticket, regardless of which stream it belonged to, was gated through Site Checker before close: fail-zero on core settings, content and SEO surface, URL structure, content-language sanitization across pages, posts, Elementor data, menus and widgets, and multi-resolution screenshots. The agency’s AutoQA layer then ran post-handoff — Phone audit · Links audit · Contact-Email audit · Content-AI check · OpenAI visual check across three viewports — and surfaced any remaining issues into the shared SEO + CX backlog for our fix loop. The 84-item launch / QA checklist was worked against each batch of changes before agency acceptance.

Four streams — header/footer propagation, new service pages from spec, change-request queue, and per-ticket QA — run concurrently because that is the shape of a refresh continuation. Keeping them from interfering with each other is the work.

Results

In a line: design propagated across 34 URLs, four new service pages shipped from approved Figma, and 57 change requests carried from raised to closed — all across three concurrent work streams over 73 calendar days, each ticket gated individually through Site Checker before close.

Process

Phases overlap heavily — the change-request queue was active from week one, and design-propagation tickets continued to arrive through the new-page batch. This concurrent shape is characteristic of continuation work, where three streams run at once rather than sequentially.

Team

Delivery team

• Nikita Tumasevic — developer on core refresh work
• Pavel Sazhin — development + QA on change requests
• Timur Arbaev — development + QA on new pages and change requests
• Lyudmila Travkina — agency-side account / client liaison
• Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)

Agency-side project management, design approval, and client-facing communication remained with the partner agency throughout. Evergreen Grace Dental Care saw the refreshed site, not the developers who shipped it; every ticket reached them under the agency’s name.

For agencies commissioning a white-label WordPress refresh