Internal Standards and Governance

TheAccountingDr Design and Documentation Standards Manual

The official standards for TheAccountingDr webpages, client resources, PDFs, educational materials, marketing assets, digital experiences, internal systems, and the Practice Suite.

Document: TAD-STD-001 Version 1.1 Effective July 2026 Living Document

Governing principle: Every page, document, resource, system, and interaction should help answer: "What does the client or user need next?"

Brand Identity and Positioning

Standards governing how TheAccountingDr is described, presented, and represented.

1.1 Official Brand Name

The official business and brand name is TheAccountingDr.

Use the exact capitalization: TheAccountingDr.
Do not insert spaces into the official brand name.
Do not use alternative spellings unless required by a platform.
The approved professional name is Dr. Brian Routh.
Do not write "Dr. Brian Routh, PhD." The title and degree are redundant when used together.

1.2 Professional Positioning

TheAccountingDr is positioned as an educator-led, professional bookkeeping practice that helps business owners obtain clear, reconciled, and usable financial information.

Educator

More than 20 years of experience teaching accounting and helping people understand financial information.

Experienced Professional

Former North Carolina Assistant State Auditor with experience in financial oversight and accountability.

Modern Bookkeeper

Xero Certified Professional providing virtual bookkeeping, cleanup, reconciliation, reporting, and migration support.

1.3 Brand Voice

Clear, calm, professional, and educational.
Confident without appearing arrogant.
Helpful without oversimplifying important matters.
Direct without sounding abrupt.
Approachable without becoming overly casual.
Focused on clarity, informed decisions, and practical next steps.

1.4 Service Boundaries

Marketing, educational, and client materials must accurately reflect the services provided.

Services Provided

Monthly bookkeeping
Cleanup and catch-up bookkeeping
Account reconciliations
Monthly financial reporting
Inventory and product-sales bookkeeping
Xero migration and support
Financial Health Checks

Services Not Provided

Tax preparation
Audits or assurance engagements
Payroll processing
Bill payment
Collections
Cash management
Physical inventory counts

Visual Design System

Core rules for maintaining a consistent and recognizable visual identity.

2.1 Approved Brand Colors

Color	Primary Use	Suggested Value
Deep Navy	Headers, navigation, primary buttons, and strong contrast areas	#061F38
Brand Navy	Primary brand color, section headings, and card accents	#0B2D4F
Gold	Highlights, selected states, borders, and emphasis	#D4AF37
White	Primary backgrounds and text on dark surfaces	#FFFFFF
Light Gray	Cards, section backgrounds, and quiet visual separation	#F5F8FB
Body Text	Paragraphs and supporting content	#334155

Color restraint: Gold is an accent color. It should guide attention, not dominate every section.

2.2 Typography

Headings must be clear, strong, and easy to scan.
Body copy must prioritize readability over decoration.
Body text must not be justified.
Avoid excessively small text.
Do not introduce unrelated decorative fonts.
Use the fonts established by the applicable website theme whenever possible.

2.3 Alignment

Body paragraphs are left aligned.
Lists are left aligned.
Resource titles and descriptions are left aligned.
Major hero headings may be centered when the page design supports it.
Section headings may be centered when intentionally designed that way.
Long paragraphs must never be justified.

2.4 Cards, Borders, and Shadows

Cards should use consistent corner radii.
Shadows should be soft and restrained.
Border colors should be subtle and consistent.
Cards must have sufficient internal padding.
Spacing must be consistent across related cards.
Hover effects should clarify interactivity without distracting movement.

2.5 Button Standards

Primary Buttons

Use navy backgrounds, white text, strong contrast, and clear action-oriented labels.

Secondary Buttons

Use white or light backgrounds with navy borders and navy text.

Button labels should describe the action.
Avoid vague labels such as "Click Here."
Keep button sizing consistent within the same interface.
Buttons must remain usable on mobile devices.

2.6 Official Logo

The compass-based TheAccountingDr logo is the official logo. Obsolete logos should not be reintroduced into new materials.

Website and Blogger Standards

Technical and design rules for the main website, blog, and Client Resources site.

3.1 Platform and Theme Standard

TheAccountingDr websites are hosted on Blogger but do not use a stock Blogger theme as the governing design standard.

Official distinction: Blogger is the hosting and content-management platform. The visible website experience is governed by custom TheAccountingDr theme code, page layouts, CSS, navigation, and responsive behavior.

The main public website uses a custom TheAccountingDr modern Blogger theme.
The blog uses the same overall brand system with blog-specific components.
The Client Resources site uses its own custom resource-center theme.
The Client Resources theme does not use a right sidebar.
Page-level code must not replace or duplicate an existing theme.
The Practice Suite is governed separately as an application under Section 11.

3.2 Main Site, Blog, and Client Resources Distinctions

Main Public Pages

Designed for services, professional credibility, prospect education, and conversion.

Business-oriented navigation
Service-focused calls to action
Financial Health Check promotion
Professional certifications
Business-page right sidebar when applicable

Blog

Designed for educational posts, current content, search visibility, and reader discovery.

Recent posts
Labels or categories
Archive navigation
Blog-specific search tools
Blog-specific right sidebar

Client Resources

Designed for structured client education, documents, secure processes, and client next steps.

No right sidebar
Wide content area
Client Journey navigation
Status dots and action labels
Resource-focused page layouts

3.3 Right Sidebar Standards

Main Public Website Sidebar

The regular-page sidebar should support business conversion and professional trust. It may contain:

Complimentary Financial Health Check call to action
Contact information
Service highlights
Professional credentials
Xero certification
CPA referral information
Selected testimonials or next-step links

Blog Sidebar

The blog sidebar should support content discovery. It may contain:

Search
Recent posts
Popular posts
Labels or categories
Blog archive
Relevant social links

Client Resources Site

The Client Resources site does not use a right sidebar. Its content should remain full-width within the approved centered container.

Do not: Add a sidebar to an individual Client Resources page or create a simulated sidebar inside the page unless the resource-center theme is intentionally redesigned.

3.4 Blogger Bullet and List Problems

Blogger may add or preserve default list markers, indentation, or inherited theme styles even when custom icons or bullets are used. This has repeatedly caused double bullets, encoded symbols, gibberish, and malformed list layouts.

Permanent rule: Whenever custom bullets, checkmarks, icons, numbered circles, or other custom list markers are used, the CSS must explicitly suppress Blogger's default list markers.

Do not type decorative bullet symbols directly into the HTML.
Do not use special-character checkmarks as CSS content.
Do not use special-character X marks as CSS content.
Do not depend on Blogger to preserve custom Unicode symbols.
Use CSS circles, borders, lines, and counters to create markers.
Apply list rules only inside a unique page wrapper.

.page-scope ul, .page-scope ol{ margin:0; padding:0; } .page-scope li{ margin:0; padding:0; list-style:none; } .page-scope li::marker{ content:""; }

3.5 Blogger HTML Corruption and Gibberish Prevention

Blogger's visual editor may alter HTML, insert formatting, encode characters, move elements, or create malformed output.

Paste custom page code only while Blogger is in HTML view.
Do not switch to Compose view after inserting complex HTML.
Do not edit complex custom layouts through the visual editor.
Keep a clean master copy of every completed page outside Blogger.
Use one complete replacement block rather than repeatedly patching corrupted code.
Remove accidental duplicate style blocks before publishing.
Avoid decorative Unicode symbols in page code.
Use plain ASCII wording whenever a decorative symbol is unnecessary.
Confirm that HTML entities and punctuation display correctly.
Preview before publishing or updating the live page.

Recovery rule: When a page has become heavily corrupted, replace the page contents with the latest known-clean master HTML.

3.6 Scoped CSS Requirement

Every custom page must use a unique outer wrapper and scope its page-level CSS to that wrapper.

<div class="tad-resource-page"> Page content </div> <style> .tad-resource-page{ /* Page variables and base styles */ } .tad-resource-page .resource-card{ /* Component styles */ } </style>

3.7 Navigation Highlighting

Only the correct active navigation item may be highlighted.
Do not rely solely on Blogger's automatic page detection.
Training pages must not incorrectly highlight Bookkeeping Services.
Active-state code must be tested against the published URL.
Navigation logic should be maintained in the theme whenever it is truly global.

3.8 Page Width and Layout

Client Resources pages should use the available no-sidebar width.
Content must remain centered within a readable maximum width.
Pages must not become unnecessarily narrow on desktop or iPad.
Cards must not extend beyond the viewport.
Tables must use horizontal scrolling on small screens.

3.9 Responsive Testing

Desktop width
iPad landscape
iPad portrait
iPhone or comparable mobile width
Mobile Safari
Desktop Safari
Chrome or another Chromium browser

3.10 Blogger Quirks Log

Default bullets appearing behind custom bullets or icons
Encoded or corrupted bullet symbols displaying as gibberish
Inherited list indentation
Unexpected margins around paragraphs and headings
Different formatting between Blogger posts and pages
Visual editor corruption of custom HTML
Theme CSS overriding page-level formatting
Page-level CSS unintentionally overriding the theme
Wrong sidebar configuration appearing on a page
Incorrect navigation highlighting
Mobile padding and width changes
Unexpected font inheritance
Duplicate code after repeated edits
Anchor links scrolling to an awkward location
Buttons or cards wrapping incorrectly at tablet widths

Client Resource Standards

Rules for organizing and presenting resources within the TheAccountingDr Client Resources site.

4.1 One Resource, Multiple Formats

A webpage and its related PDF are not separate resources. They are different formats of the same resource.

Approved model:
What to Expect During Onboarding
Read Online | Download PDF

4.2 Client Journey Organization

Getting Started
Your First 30 Days
Managing Monthly Bookkeeping
Year-End and Tax Preparation
Forms and Authorizations
Policies and Reference Guides

4.3 Document Numbering

Prefix	Category	Example
TAD-ONB	Onboarding	TAD-ONB-001
TAD-MTH	Monthly Bookkeeping	TAD-MTH-001
TAD-YER	Year-End	TAD-YER-001
TAD-XER	Xero	TAD-XER-001
TAD-BUS	Business Education	TAD-BUS-001
TAD-MIN	Ministry and Nonprofit	TAD-MIN-001
TAD-FAQ	Frequently Asked Questions	TAD-FAQ-001
TAD-SEC	Security and Privacy	TAD-SEC-001
TAD-STD	Internal Standards	TAD-STD-001

4.4 Current Onboarding Sequence

Document Number	Resource
TAD-ONB-001	What to Expect During Onboarding
TAD-ONB-002	Client Onboarding Information Guide
TAD-ONB-003	Client Onboarding Questionnaire
TAD-ONB-004	New Client Document Request Checklist
TAD-ONB-005	Xero Migration Questionnaire

4.5 Resource Status System

The status dot belongs beside the resource title on the left. The right side is reserved for actions.

Available Now The client can access the resource immediately.

Completed During Onboarding The item is handled as part of the onboarding process.

Provided Through the Client Portal The item involves secure delivery or upload.

Provided When Applicable The item is conditional and not required for every client.

Coming Soon The resource is planned but not yet available.

4.6 Action Labels

Read Online
Download PDF
Open Guide
Complete Form
Upload Securely
Sent for Signature
Schedule
Contact
Watch Video
View eBooks
Open Assessment
Request When Needed

4.7 Standard Resource Entry

Status dot positioned beside the title
Document number clearly displayed
Clear resource title
Brief client-focused description
Action buttons or action links on the right
Consistent card spacing and typography
Responsive mobile stacking

4.8 Resource Page Toolbar

Return to Client Resources Home
Download PDF
Print or Save This Webpage

4.9 Related Resources

Resource pages should identify related documents, webpages, videos, forms, or next steps when doing so will help the client continue the journey.

PDF and Document Standards

Requirements for formal, downloadable, and printable documents.

5.1 Required Document Information

TheAccountingDr branding
Document title
Document number
Version number
Revision or effective date
Copyright notice when appropriate
Contact or support information when appropriate

5.2 Version Format

TAD-ONB-001 Version 1.0 July 2026

Use Version 1.0 for the first approved edition.
Use Version 1.1 for a minor content or formatting revision.
Use Version 2.0 for a substantial redesign or major change in purpose.
Do not erase prior version history.

5.3 File Naming

TAD-ONB-001_Onboarding_Guide.pdf TAD-ONB-003_Client_Onboarding_Questionnaire.pdf TAD-YER-001_Year_End_Document_Checklist.pdf

5.4 PDF and Webpage Relationship

The PDF should reference the corresponding webpage when practical.
The webpage should provide a direct PDF download when a PDF exists.
The PDF and webpage should use consistent titles and document numbers.
Material content should not conflict between formats.

5.5 PDF Layout

Use the approved navy, gold, white, and gray palette.
Maintain readable margins.
Avoid overcrowded pages.
Keep headings and body copy visually distinct.
Prevent text, logos, and footers from being cut off.
Use page numbers on multi-page documents when appropriate.
Test the final PDF at normal viewing size and print size.

Content and Educational Standards

Rules for articles, guides, scripts, checklists, FAQs, and client education.

6.1 Educational Approach

Explain why the topic matters.
Use practical business-owner examples.
Define technical language when it cannot be avoided.
Connect the topic to a clear decision or next step.
Do not present tax, legal, investment, or assurance advice outside the firm's service boundaries.

6.2 Standard Resource Structure

Clear title
Purpose or overview
Why the topic matters
Main guidance
Examples or explanations
Client responsibilities or next steps
Related resources
Appropriate call to action

6.3 Blog Post Standards

Search-focused title
Clear introductory problem or question
Scannable subheadings
Practical explanation
Related video or resource when applicable
About the author section
Financial Health Check or other appropriate CTA
SEO title, search description, and labels

6.4 Accessibility of Language

Materials should be written for intelligent business owners who may not have formal accounting training.

Marketing and Media Standards

Rules for videos, social media, thumbnails, promotion, and calls to action.

7.1 Calls to Action

Exact location in the spoken video script
Exact on-screen text placement
Exact placement in the YouTube description
Pinned comment wording
Blog post placement
Social caption placement
Thumbnail usage when appropriate

7.2 Long-Form Video Standards

Strong opening
Clear learning objectives
Professor-style explanation
Practical business examples
Teaching pauses and questions
On-screen callouts
Clear recap
Appropriate Financial Health Check CTA

7.3 Short-Form Video Standards

Target approximately 45 to 50 seconds unless the strategy changes.
Address one clear problem or idea.
Use a strong first sentence.
Keep the explanation educational rather than overly promotional.
Include an occasional, clearly placed CTA.

7.4 Social Platform Standards

Do not assume identical copy works equally well on every platform.
LinkedIn connection notes must remain within 200 characters.
X posts should be concise enough for the platform.
TikTok promotion should use short clips rather than an entire long-form lesson.
YouTube Community posts are separate from video descriptions.

7.5 Thumbnail Standards

Use the correct current photograph of Dr. Brian Routh.
Do not substitute an invented or unrelated person.
Use short, readable thumbnail text.
Maintain the approved navy and gold branding.
Keep the face and primary text away from cropping zones.
Do not use a low-resolution or repeatedly degraded photograph.

Security, Privacy, and Accessibility

Standards for protecting information and ensuring resources remain usable.

8.1 Sensitive Information

Never request full bank account numbers through ordinary email.
Never request full routing numbers through ordinary email.
Never request complete credit card information through ordinary email.
Never store complete payment credentials in a webpage or unsecured internal note.

8.2 Secure Delivery Wording

Provided Through the Client Portal
Upload Securely
Sent Electronically for Secure Review and Signature
Payment Authorization Completed Securely

8.3 Accessibility

Maintain adequate text contrast.
Do not use color as the only communication method when text is needed.
Use meaningful link and button labels.
Use logical heading order.
Provide alternative text for meaningful images.
Ensure controls are usable with a keyboard.
Maintain visible focus indicators.
Avoid unnecessarily small tap targets.

Quality Control and Never Again Rules

Final safeguards based on problems already identified and resolved.

9.1 Pre-Publication Checklist

Confirm the page uses the correct current theme.
Confirm page CSS is fully scoped.
Confirm Blogger default bullets are suppressed where custom markers are used.
Confirm no decorative Unicode markers are used for bullets, checkmarks, or X marks.
Confirm body copy is left aligned and not justified.
Confirm the correct navigation item is highlighted.
Confirm the correct sidebar behavior for the site area.
Confirm no Client Resources sidebar has been introduced.
Confirm buttons describe actions clearly.
Confirm status appears beside the resource title.
Confirm the action area does not repeat status wording.
Confirm desktop, tablet, and mobile layouts.
Confirm no text, buttons, or cards are cut off.
Confirm all links work.
Confirm version and revision information is current.
Keep a clean master copy before publishing.

9.2 Never Again

Never use justified body text.
Never allow Blogger's default bullets to appear behind custom bullets or icons.
Never use decorative Unicode characters as list markers in Blogger page code.
Never switch a complex custom HTML page into Compose view after inserting the code.
Never continue patching a severely corrupted page when a clean replacement is available.
Never place unscoped generic CSS into an individual Blogger page.
Never replace a functioning site theme when only a page needs to be created.
Never add a right sidebar to the Client Resources site without an intentional site-wide redesign.
Never rely blindly on Blogger's automatic navigation highlighting.
Never duplicate status information in the action area.
Never create a formal client resource without a document number.
Never reuse a retired or previously assigned document number.
Never finalize a page without mobile and tablet testing.
Never request sensitive payment or banking information through ordinary email.
Never use an incorrect or fabricated photograph of Dr. Brian Routh.
Never add "PhD" after Dr. Brian Routh when "Dr." is already used.

Governance and Revision History

How this manual is maintained as TheAccountingDr continues to grow.

10.1 Living Document

This manual is a living governance document. New standards should be added when a repeated issue is solved, a new resource type is adopted, or a better design or operational convention is approved.

10.2 Authority

The latest approved version of this webpage is the governing source for TheAccountingDr design and documentation standards unless a more recent written decision has been made and is awaiting incorporation.

10.3 Revision Process

Identify the needed standard or revision.
Determine whether the change is minor or major.
Update the applicable section.
Update the version number and effective date.
Add an entry to the revision history.
Retain a clean copy of the prior version.

10.4 Revision History

Version	Date	Summary
1.0	July 2026	Initial standards manual establishing brand, visual, website, Blogger, Client Resources, document, content, marketing, security, accessibility, and quality-control standards.
1.1	July 2026	Added comprehensive Practice Suite application standards and corrected alignment within the closing standards panel.

Practice Suite Application Standards

Governance, development, security, data-integrity, workflow, and release standards for the TheAccountingDr Practice Suite.

11.1 Application Classification

The TheAccountingDr Practice Suite is a business-critical operational application. It is not treated as an ordinary webpage, marketing page, or disposable prototype.

Application standard: Changes to the Practice Suite must preserve its established data, workflows, business rules, and operational continuity.

The Practice Suite includes or may include:

Relationship and contact management
Prospect and client records
Referral and professional partner records
Discovery workflows
Financial Health Check workflows
Pricing and proposal development
Client onboarding
Billing and payment setup
Active client workspaces
Monthly bookkeeping workflows
Dashboard priorities and reminders
Marketing Studio
Teaching Studio
Repurposing and publishing workflows
Practice operations and reporting

11.2 Master Baseline Standard

Development must begin from the latest approved master HTML baseline.
An uncertain, partial, outdated, or reconstructed file must not replace the approved baseline.
The current master must be identified clearly before material changes are made.
A clean pre-edit backup must be retained before each release.
The prior working version must remain available for rollback.
The application must not be rebuilt from scratch unless explicitly approved.

No conflicting baselines: Parallel or uncertain copies must not be treated as equal master versions. One approved file governs each release cycle.

11.3 Version Control

Every approved release receives a unique sequential version number.
The visible application version must match the delivered file version.
The file name should include the release version.
Material changes must be summarized in release notes.
Prior version numbers must not be reused.
Dated backups and checksums should be retained when practical.

TheAccountingDr_Practice_Suite_v8.10.21.html Visible Version: v8.10.21 Release Notes: Added Billing and Payment Setup fields and readiness logic.

11.4 Existing Functionality Preservation

A requested change must not silently remove, disable, or damage unrelated functionality.

Existing modules must continue to open and operate.
Stored records must continue to load.
Existing buttons and navigation must remain functional.
Data persistence must continue to work after save and reload.
Responsive behavior must not regress.
Related workflows must be retested after shared code changes.

11.5 Data Integrity

Records must not silently disappear.
Records must not duplicate without warning or deliberate action.
Saved values must not revert unexpectedly.
A record must not change identity after navigation or refresh.
A referral must not open as a prospect or client.
A client record must not display data belonging to another relationship.
Shared record fields must remain synchronized across modules.
Deletion must affect only the selected record.

11.6 Duplicate Detection

The application should identify possible duplicate businesses, contacts, prospects, clients, referrals, and partners before a new record is finalized.

Compare business or organization name.
Compare contact name.
Compare email address when available.
Compare phone number when available.
Display a possible-duplicate warning before saving.
Allow a legitimate duplicate only through a deliberate decision.

11.7 Workflow Integrity

Completion states must reflect the actual workflow.
Progress percentages must be based on understandable criteria.
Required steps must be visible to the user.
Readiness checks must explain what remains incomplete.
Unresolved requirements should link to the place where they can be completed.
Removing a required item may reopen the related workflow when appropriate.
A completed workflow must not continue generating an inappropriate reminder.
Statuses must be reversible when operationally appropriate.

11.8 Dashboard and Ranked Work

Dashboard recommendations must reflect actual practice priorities and the current condition of each record.

Client bookkeeping work must be eligible for Today’s Ranked Work.
Priority-close, standard-close, and custom-close windows must be respected.
Current bookkeeping periods must be clearly identified.
Completed or inactive relationships must not produce inappropriate action prompts.
Not Scheduled and No Current Action states must suppress unnecessary reminders.
Waiting on Client items should remain visible without appearing as overdue internal work.
Dashboard tasks should link directly to the relevant workspace.

11.9 Follow-Up and Relationship Status

Not every relationship requires a follow-up date.
No Current Action must be available as a valid state.
Inactive records must not continue producing active follow-up warnings.
Completed follow-up controls must perform the labeled action.
Referral and partner records must remain in their proper module.
Relationship type, activity status, and follow-up status must remain distinct concepts.

11.10 Discovery and Financial Health Check Standards

Discovery and Quick Financial Health Check must remain separate workflows.
Financial Health Checks should support a 15 to 20 minute review without requiring system access.
Health Check scoring must map consistently to approved result categories.
Health Check records must be saved, locatable, and deletable.
Conversion from a Health Check to Discovery must preserve relevant information.
Document requirements must be appropriate to the workflow being performed.
Completion indicators must update when the applicable step is satisfied.

11.11 Pricing and Proposal Standards

Pricing assumptions must be selectable and understandable.
Manual overrides must carry into the proposal correctly.
A zero one-time fee must not display a prior default amount.
Proposal totals must reconcile to selected services and overrides.
Proposal design must remain consistent with the rest of the application.
Proposal changes must not damage pricing logic or stored assumptions.

11.12 Onboarding Standards

Each onboarding step must have a clear purpose.
Progress must reflect visible requirements.
Accounts and records added during onboarding must be editable and deletable.
Readiness requirements must not be hidden by horizontal scrolling.
Critical blockers must explain why activation cannot proceed.
Links should take the user directly to incomplete requirements.
Client activation must depend on the approved readiness rules.

11.13 Billing and Payment Setup

The approved onboarding concept is Billing and Payment Setup, not merely Payment Method Established.

Relevant fields may include:

Billing Method
Payment Authorization Status
Authorization Date
Payment Platform
Reference containing last four digits only
Billing and payment notes

ACH and credit card methods require completed authorization before activation when applicable.
Invoice and check methods may automatically indicate authorization is not required.
Authorization requirements must be reflected in readiness logic.
Full payment credentials must never be stored.

11.14 Security and Sensitive Data

Never store complete bank account numbers.
Never store complete routing numbers.
Never store complete credit card numbers.
Never store card security codes.
Never expose sensitive payment information in dashboard summaries.
Never include sensitive credentials in exports or ordinary notes.

Limited reference data, such as the last four digits of an account or card, may be stored only when operationally useful and appropriately labeled.

11.15 Interface and Usability Standards

Primary controls must remain visible without unnecessary horizontal scrolling.
Save actions must provide immediate visual confirmation.
Buttons must perform the action their label promises.
Close buttons must close the applicable dialog or panel.
Delete buttons must clearly identify what will be deleted.
Long workflows should use clear sections and progress cues.
Required fields and optional fields must be distinguishable.
Important content must remain readable on iPad.
Floating navigation controls must not cover important content.

11.16 Save and Feedback Standards

A user should never be left wondering whether an action occurred.

Save Progress must provide visible confirmation.
Publish actions must indicate what was published and where.
Use Tomorrow or rescheduling actions must provide feedback.
Slow actions should show a working state.
Failed actions must provide a useful error message.
Success messages should disappear after a reasonable period without obscuring content.

11.17 Cross-Module Consistency

CRM, Prospects and Clients, Referrals and Partners, Discovery, Onboarding, Dashboard, and Active Client Workspace must remain synchronized.
A record opened from one module must retain the same identity in another.
Shared status labels must use consistent meanings.
Changes to contact information must update all relevant views.
Completed workflow steps must update dashboard and summary views.
Record counts and clickable header summaries must reflect current data.

11.18 Marketing Studio and Teaching Studio

Save, scheduling, publishing, and repurposing behavior should be consistent across both studios.
Publishing in a studio must clearly indicate any related Master Library update.
Flagged content should be locatable in a Repurposing Queue.
Repurposing records should identify the intended asset, target date, and status.
Teaching topics must be addable and editable.
Long-form lessons must support specific scheduling.
Scheduled teaching work should surface on the dashboard when appropriate.
Daily short instructions should reflect the current 45 to 50 second standard.

11.19 Refresh and Persistence Stability

Saved data must persist after browser refresh.
Repeated navigation must not produce record mismatches.
Opening and closing workspaces must not replace one record with another.
Application startup must restore the appropriate stored state.
New releases must remain compatible with existing saved data whenever possible.
Data migrations must be deliberate and tested when structures change.

11.20 Deletion Standards

Delete controls must identify the record or item affected.
The approved Financial Health Check wording is Delete Record.
Deleting a child item must not delete the parent record.
Deleting one account must not remove unrelated accounts.
Deletion should require a deliberate confirmation for important records.
After deletion, lists, counts, and related views must refresh correctly.

11.21 Release Validation

Every Practice Suite release should be checked for the following:

JavaScript syntax errors
Broken buttons and links
Save and reload persistence
Record creation
Record editing
Record deletion
Duplicate warnings
Navigation and tab behavior
Dashboard task accuracy
Workflow completion logic
Readiness calculations
Cross-module synchronization
Desktop layout
iPad landscape layout
iPad portrait layout
Existing client data preservation
Correct visible version number

11.22 Practice Suite Never Again Rules

Never rebuild the Practice Suite from scratch when modifying the approved baseline.
Never develop from an uncertain or outdated file.
Never remove or rename stored fields without considering existing saved data.
Never release a version without checking that existing records still load.
Never allow inactive, completed, or No Current Action records to generate inappropriate dashboard warnings.
Never hide required readiness information off-screen without a clear indication.
Never allow a save button to appear successful without confirmation.
Never store full payment credentials.
Never allow the same record to appear as unrelated entities in different modules.
Never deliver a new build without preserving the prior clean baseline.
Never change a shared workflow without checking every module that uses it.
Never permit deletion controls to affect a different record than the one selected.
Never mark a workflow complete when required conditions remain unresolved.
Never allow a visible application version to disagree with the delivered file version.

Design & Documentation Standards Manual