Public build note generator
A cautious template for turning small changes into public notes with evidence, review, and limits.
Tools
A small set of owned tools I use for calm planning and clean handovers across websites, local profiles, DNS/email, and documentation.
Start Here
These pages are designed to be useful even if you never hire me. They do not ask for passwords, MFA codes, customer data, or private documents.
A cautious template for turning small changes into public notes with evidence, review, and limits.
A source-led checklist for setup, cleanup, and ongoing profile maintenance, with official references.
A recurring checklist for website, domain/email, backups, profile accuracy, and account access basics.
Pre-publish checks for small NZ websites: content, forms, domain/email, backups, profiles, and post-launch notes.
Plain, fair review request wording patterns with guardrails: no incentives, no pressure, no fake activity.
Next step
A tool is most useful when it points to a clear next action. Use these routes when a checklist exposes a website, DNS, email, SEO, networking, or SME handover issue that needs deeper notes.
Start here when the checklist result crosses several areas and needs a simple, calm triage path.
Use this when the issue is crawlability, metadata, structured data, sitemap coverage, internal links, or Search Console evidence.
Use this reading path for launch checks, canonicals, redirects, analytics, and post-launch handover notes.
Use this when a checklist uncovers unclear registrar access, DNS ownership, MX records, or rollback gaps.
Use this when SPF, DKIM, DMARC, bounces, spam-folder placement, or third-party senders need structured review.
Use this when nameservers, TTL, redirects, partial reachability, routing, or provider escalation evidence are involved.
Use this when the checklist result points toward fibre, Wi-Fi, VPN, SIP/VoIP, router, or provider handover issues.
Use this when the checklist exposes a wider website, email, phone, account, or enquiry-capture setup problem.
Support lanes
Some checklist results point to a precise next step: Microsoft 365 recovery, remote support evidence, device repair, or a project proof loop. These routes keep the handoff clear.
Use this when access, MFA, mailbox rules, shared mailboxes, or admin ownership become the next support task.
Use this when the best next step is structured remote triage, screenshots, reversible changes, and a provider-ready note.
Use this when a tool or checklist points to a device-specific issue, local Windows problem, backup concern, or repair handoff.
Use this topic hub when the problem needs a checklist path across repair, laptop, upgrades, backups, and Wi-Fi symptoms.
Use this when a project site needs repository metadata, canonical proof, case-study links, source archive links, and Search Console checks.
Use the projects hub when the tool output should become public project evidence, a case-study update, or a clearer owned proof asset.
Need a practical fix or a calm plan?