<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1" xmlns:video="http://www.google.com/schemas/sitemap-video/1.1" xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
    <url>
    <loc>https://projecthubs.net/blog</loc>
    <lastmod>2026-11-03T00:00:00+00:00</lastmod>
            </url>
    <url>
    <loc>https://projecthubs.net/blog/tag/planning</loc>
    <lastmod>2026-11-03T00:00:00+00:00</lastmod>
            </url>
    <url>
    <loc>https://projecthubs.net/blog/tag/governance</loc>
    <lastmod>2026-11-03T00:00:00+00:00</lastmod>
            </url>
    <url>
    <loc>https://projecthubs.net/blog/software-change-request-template</loc>
    <lastmod>2026-11-03T00:00:00+00:00</lastmod>
    <image:image>
    <image:loc>https://projecthubs.net/images/blog/software-change-request-template/cover.jpg</image:loc>
    <image:caption>Conceptual illustration: assess a request against the agreed scope before recording the selected outcome.</image:caption>
    <image:title>An agreed scope folder beside a new request and symbols for approval, decline, deferral and a scope swap.</image:title>
</image:image>
<image:image>
    <image:loc>https://projecthubs.net/images/blog/software-change-request-template/scope-swap.jpg</image:loc>
    <image:caption>Conceptual illustration: a scope swap updates the feature commitment and its acceptance criteria. Effort and dependencies still need assessment.</image:caption>
    <image:title>A saved-view calendar and CSV sheet on separate trays, with exchange arrows and revised specification sheets.</image:title>
</image:image>
        </url>
    <url>
    <loc>https://projecthubs.net/blog/client-changes-after-approval</loc>
    <lastmod>2026-11-02T00:00:00+00:00</lastmod>
    <image:image>
    <image:loc>https://projecthubs.net/images/blog/client-changes-after-approval/cover.jpg</image:loc>
    <image:caption>Conceptual illustration: retain the earlier approval while assessing a new request and preparing a separate revision.</image:caption>
    <image:title>A preserved approval folder beside a new request sheet, with an amber path leading to a separate revision folder.</image:title>
</image:image>
        </url>
    <url>
    <loc>https://projecthubs.net/blog/bug-vs-change-request</loc>
    <lastmod>2026-10-30T00:00:00+00:00</lastmod>
    <image:image>
    <image:loc>https://projecthubs.net/images/blog/bug-vs-change-request/cover.jpg</image:loc>
    <image:caption>Conceptual illustration: compare the report with the approved requirements before choosing the next action.</image:caption>
    <image:title>An approved specification beside three document trays representing a bug correction, a proposed addition and an unresolved clarification.</image:title>
</image:image>
        </url>
    <url>
    <loc>https://projecthubs.net/blog/weekly-client-project-update-template</loc>
    <lastmod>2026-10-30T00:00:00+00:00</lastmod>
    <image:image>
    <image:loc>https://projecthubs.net/images/blog/weekly-client-project-update-template/cover.jpg</image:loc>
    <image:caption>Conceptual illustration: carry an unanswered decision into the next report while recording completed work and revised proposals separately.</image:caption>
    <image:title>Two weekly report sheets connected by an amber pending-decision card, with a separate completion check and calendar tile.</image:title>
</image:image>
        </url>
</urlset>
