NNS Installation: Build Manual & Testing
TEACH · BUILD MANUAL
TEACH · BUILD MANUAL
This page shows the Master Build Manual I wrote in Google Docs to standardize every NNS installation. You’ll see the nine-area testing checklist, an end-to-end test record, the eleven-step installation procedure, and the log of known gaps.
Every installation has several moving parts: the Google Sites website, the Client Control Center, Google Drive folders, Tally forms, Stripe payment, and access to the client’s Google account. Even when each piece worked on its own, one missed connection or permission could affect the whole installation. The manual defines what gets built, what must be tested, and what the client receives. Each install is checked against the same standard, including a payment-to-intake test with a $0 promo order. When testing reveals something I overlooked, I document it, correct it, and add the lesson to the manual.
I didn’t want quality to depend on memory. My goal is a process that gets more reliable and consistent every time I build it.
Every NNS installation has several moving parts, and even when each piece worked on its own, one missed connection or permission could affect the whole installation.
Relying on memory to catch those problems meant quality could vary from one install to the next.
The Master Build Manual defines what gets built, what must be tested, and what the client receives. It includes a nine-area testing checklist, an eleven-step installation procedure, a build record for each client, and a log of findings and product decisions.
1. The package is set by business type
Each installation follows the Master Build Manual, using the approved package and sequence of steps for that business type.
2. The procedure runs in order
Eleven steps take every install from confirming the client’s home-base account to client acceptance.
3. Every install is tested
A nine-area testing checklist covers account ownership, permissions, links, forms, and devices before delivery.
4. The handoff is tested end to end
The payment-to-intake handoff is tested with a $0 promo order before release.
5. Findings change the standard
Each defect is logged. Fixes become permanent steps in the manual, and anything not yet fixed goes to the known-gaps log with what would resolve it.
When I tested the handoff, I learned that building a site and files inside a client’s Drive folder doesn’t make the client their owner. Google keeps ownership with whoever created each item. So I added a step: I transfer ownership of the site and every file separately, the client accepts each transfer, and then the client removes my access. I confirmed the client could still edit everything afterward. That test became part of the installation procedure.
Google Docs · Google Drive · Tally · Stripe · Google Sites · Google Apps Script · ChatGPT · Claude
Findings like the Drive ownership gap become permanent steps in the manual, so every installation after it starts with that problem already solved.