# WorkTrack360 Commercial Launch Strategy and Product-Site Specification

**Version:** 0.7 — Checkpoint 1 draft  
**Date:** November 2026  
**Launch model:** United States nationwide · Five equal-priority institutional sectors  
**Product position:** Workforce Opportunity, Community Engagement, and Program Outcomes Platform  
**Primary line:** **Connecting People to Opportunity. Helping Programs Deliver Outcomes.**  
**Compact campaign line:** **Opportunity. Progress. Outcomes.**

> This document is the authoritative strategy and content source for the WorkTrack360 commercial product-site package. It is an internal planning and production artifact, not a statement that every described capability is deployed in every environment. Product, legal, privacy, security, accessibility, and customer-story claims require final review before public release.

---

## 1. Executive decision

WorkTrack360 will enter the market as **one customer-facing product** serving two connected markets:

1. **Individuals** create an approved account, discover jobs, learning and volunteering opportunities, document progress, receive support, and participate in sponsored programs.
2. **Institutions** sponsor access, organize programs, support participants, review documentation, govern operations, and measure authorized outcomes.

The customer never needs to understand the internal application boundary. Internally:

- The existing opportunity engine provides jobs, training, volunteering, organizations, applications, and opportunity discovery.
- The existing program-record engine provides activities, evidence, submissions, program review, messaging, governed assistance, and authorized reporting.
- The engines retain separate databases and controlled integration contracts.

Commercially, they are presented as **one WorkTrack360 platform, one account relationship, and one experience**.

### Launch principle

All five institutional sectors launch with equal commercial priority and equal content depth:

1. State Health and Human Services
2. Counties
3. NGOs and nonprofits
4. Universities
5. Hospitals and health systems

Equal priority does not mean identical messages. Each sector receives its own buyer problem, value proposition, real-world scenarios, buying-committee journey, objections, resource offer, package presentation, and call to action.

---

## 2. Evidence basis and claim discipline

### 2.1 Evidence reviewed

This strategy is grounded in the current ADO-tracked product sources and team decision records available on November 4, 2026:

- WorkTrack360 remote-tracking branch `origin/development-g3-design` at `d8b0b2b8`.
- G2 remote branch `origin/Nish/G2-final-enhancements` at `069e8d47a`.
- `Docs/G3-Enhancement-Coverage.md` from the WorkTrack360 branch.
- `Documentation/CODEX_PROJECT_HANDOFF_2026-10-30.md` from G2.
- `hybrid-role/00-decisions.md` and inventories `01` through `03`.
- Existing WorkTrack360 logo and brand defaults.

The WorkTrack360 feature matrix at the reviewed remote-tracking revision contains **288 Built**, **109 Partial**, **1 Not built**, **17 Outside code**, and **5 Prototype only** rows. Those labels are source-oriented evidence, not proof that each feature has passed database, browser, integration, accessibility, security, or production validation.

### 2.2 Internal evidence labels

Marketing, sales, product, and implementation teams will maintain these internal labels even though the public website presents one unified product vision:

| Internal label | Meaning | Public-language rule |
|---|---|---|
| Source-evidenced | Capability exists in current tracked source or approved contract | Describe the observable user task; avoid claiming a live customer result |
| Runtime verification pending | Source exists, but the current environment or end-to-end journey has not been verified | Use “designed to support” or “can be configured to support” |
| Integration-dependent | Value depends on a customer, agency, county, LMS, clinical, or partner system | Say that integration scope is established during discovery |
| Process-dependent | Certification, BAA, procurement, policy approval, staffing, or operating control is required | Describe the process; do not claim the external status |
| Illustrative scenario | Scenario demonstrates intended value without claiming a customer result | Label the scenario as illustrative |
| Approved customer evidence | Customer has approved the story, facts, wording, and publication scope | Use only the approved language and review date |

### 2.3 Claims that must not appear without separate proof

Do not claim or imply:

- A production deployment merely because source code, migrations, tests, or documentation exist.
- Eligibility determinations, benefits decisions, legal conclusions, academic credit decisions, clinical outcomes, or agency authority.
- Automatic filing, acceptance, or acknowledgement by a state, county, health plan, university, hospital, or partner system without a verified connection and receipt.
- HIPAA, SOC 2, Section 508, WCAG conformance, FedRAMP, FERPA, 42 CFR Part 2, or other certification unless the exact scope and current evidence have been approved.
- Customer savings, productivity gains, participation improvements, or outcome percentages without a validated baseline and written publication approval.
- A named or anonymous customer endorsement when the relationship and story have not been approved for publication.
- An AI eligibility prediction. WorkTrack360 assistance is positioned as administrative support with human authority retained.

---

## 3. Brand architecture

### 3.1 Customer-facing architecture

**WorkTrack360**  
One platform · One account relationship · One experience

**For individuals**  
Find opportunities · Follow progress · Get support

**For organizations**  
Sponsor programs · Coordinate services · Review progress · Measure authorized outcomes

### 3.2 Public site model

The commercial website is one domain with two distinct, connected site experiences:

- `worktrack360.com/individuals`
- `worktrack360.com/organizations`

The root `worktrack360.com` is a neutral audience gateway. Each experience includes a persistent menu link to the other.

### 3.3 Brand personality

**Human opportunity with institutional trust.**

- Individual pages feel clear, encouraging, practical, and respectful.
- Institutional pages feel credible, governed, measurable, and procurement-ready.
- The same WorkTrack360 identity connects both.

### 3.4 Visual direction

- Use the approved WorkTrack360 logo.
- Preserve the existing blue, navy, and green identity.
- Use deep navy and teal for trust and hierarchy.
- Use warm amber, coral, and soft green accents for people, progress, and calls to action.
- Combine a limited number of approved human-centered images with original vector explanations.
- Avoid generic dashboard mockups, decorative charts, or imagery that implies a real customer.
- Design mobile-first and target WCAG 2.2 Level AA.

---

## 4. Commercial market model

### 4.1 Connected markets

| Market | Core promise | Primary conversion |
|---|---|---|
| Individuals | Find opportunities and move forward with clear program support | Create an account and begin approval |
| Institutions | Coordinate participation, documentation, support, governance, and authorized outcomes | Schedule a demo |

Individuals use WorkTrack360 without a direct charge. Institutions fund the platform through program sponsorship and commercial agreements.

### 4.2 Geographic position

WorkTrack360 is positioned for the **United States nationwide market**. Public copy must state that program rules, authority, integrations, data boundaries, and implementation requirements are configured for the relevant jurisdiction and organization.

### 4.3 Primary differentiation by audience

**For individuals:** one journey from opportunity to personal progress.

**For institutional operators:** trusted documentation and program accountability.

**For institutional executives and funders:** program visibility and authorized outcome measurement.

### 4.4 Go-to-market motion

Use **account-based outreach supported by inbound content**:

- Build named account cohorts in all five sectors.
- Direct each prospect to its sector experience and resource offer.
- Use public content to support independent research and long buying cycles.
- Use the optional pilot planner to prepare a relevant conversation.
- Give qualified buyers immediate access to scheduling after the short demo form.
- Use the invitation-only commercial tour for deeper, controlled review.

---

## 5. Individual market strategy

### 5.1 Audience

The individual experience serves job seekers, learners, volunteers, residents, and sponsored-program members.

### 5.2 Primary message

**Find opportunities and follow your progress.**

Supporting copy:

> WorkTrack360 brings jobs, learning, volunteering, activity records, and program support into one clear experience. Create an account, complete program review, and see the next step when access is approved.

### 5.3 Access model

- Account creation is required before full opportunity exploration.
- Every new account requires Program Reviewer approval.
- While approval is pending, the person may browse opportunity details in read-only mode.
- Pending users cannot save, apply, submit activities, upload evidence, or use program services.
- The site must explain this before registration and on the waiting state.

Approved copy:

> **While your account is under review, you can read opportunity details. After approval, your program will explain how to take the next step.**

### 5.4 Individual value pillars

1. **Discover opportunity** — jobs, learning, volunteering, events, and community engagement.
2. **Understand the next step** — clear status, deadlines, missing information, and support routes.
3. **Document progress** — activities, hours, evidence, attestations, and submissions in the authorized workflow.
4. **Reuse information responsibly** — consent-aware reuse and provenance where supported.
5. **Receive human support** — messages, clarification requests, call-backs, and escalation paths.
6. **Stay in control** — accessibility preferences, language preferences where available, consent controls, manual paths, and human review.

### 5.5 Illustrative individual scenario

> **Illustrative scenario:** Jordan creates a WorkTrack360 account for a county-supported workforce program. While the account is under review, Jordan reads the details of a training opportunity. After approval, Jordan can take the program’s next step, keep an activity record, respond when a reviewer needs a clearer date, and follow the status of the program record. The program—not the website—retains decision authority.

### 5.6 Individual page copy

**Hero heading:** Find opportunities. Follow your progress. Get support when you need it.

**Hero body:** WorkTrack360 helps you move from discovery to participation with one place to understand your next step.

**Primary CTA:** Create my account  
**Secondary CTA:** Learn how approval works  
**Audience switch:** I represent an organization

**Section heading:** Opportunity starts with a clear next step.

**Section copy:** Explore jobs, learning, volunteering, and community opportunities. Your program reviews new accounts before full access. While you wait, you can read opportunity details and prepare for what comes next.

**Section heading:** Keep progress connected.

**Section copy:** When your program enables a workflow, WorkTrack360 can bring together participation, documentation, questions, support, and status in one experience.

**Section heading:** People remain part of the process.

**Section copy:** WorkTrack360 can organize information and explain next steps. Authorized people make program decisions, and a manual path remains available when automated assistance is unavailable or inappropriate.

---

## 6. Institutional market strategy

### 6.1 Institutional promise

**Support participants. Strengthen program accountability. See the outcomes your authorized data can support.**

### 6.2 Institutional buying committee

Every sector page addresses five buyer needs in one continuous story:

1. **Executive outcomes** — why the institution should act.
2. **Program operations** — how programs coordinate work.
3. **Frontline experience** — what participants, coordinators, and reviewers need.
4. **Data, trust, and governance** — access, privacy, auditability, accessibility, and AI oversight.
5. **Procurement and implementation** — package, pilot scope, responsibilities, and next step.

Sector pages use sticky in-page navigation on larger screens and an accessible disclosure menu on small screens.

---

## 7. Sector strategies and real-world scenarios

### 7.1 State Health and Human Services

**Primary value proposition:** A configurable pathway for workforce engagement, participant support, documentation, and agency-authorized reporting.

**Main buying decision:** Can this support statewide operations, local delivery, governance, accessibility, and program authority boundaries?

**Headline:** Give local programs a common way to support participation and document progress.

**Executive outcome:** Establish a shared program framework without erasing local operating responsibilities.

**Operational value:** Coordinate account review, opportunity participation, evidence, clarification, case support, program review, and authorized handoffs.

**Illustrative scenario:** A resident participates in training, documents the activity, and receives a request for a clearer date. A local reviewer follows the state-defined review path. State leadership sees approved aggregate information appropriate to its authority; WorkTrack360 does not determine eligibility.

**Primary objection:** Counties and programs use different rules.

**Response:** Begin with a shared minimum record, then document locally owned review steps, authority, integrations, and exceptions during discovery.

**Content offer:** State and Local Review Mapping Worksheet.

**CTA:** Schedule a State HHS demonstration.

### 7.2 Counties

**Primary value proposition:** Connect local employment and community services into one participant journey.

**Main buying decision:** Can we deliver, review, and measure outcomes locally without adding another disconnected process?

**Headline:** Give residents a clear next step when your program needs more information.

**Executive outcome:** Improve program visibility while preserving county decision authority.

**Operational value:** Connect opportunities, participant records, clarification, support, review status, and authorized reporting.

**Illustrative scenario:** A resident records a volunteering activity. A reviewer requests a corrected date. The resident responds, and the reviewer continues through the county’s established decision process. Any electronic filing or acknowledgement requires a separately verified county connection.

**Primary objection:** Staff will have to enter the same information into another case system.

**Response:** Map one accepted handoff, identify who owns each data entry, and include integration only where the receiving system and acknowledgement are verified.

**Content offer:** County Participant-to-Reviewer Walkthrough.

**CTA:** Schedule a county demonstration.

### 7.3 NGOs and nonprofits

**Primary value proposition:** Expand program reach, reduce administrative burden, and demonstrate funded impact.

**Main buying decision:** Can we serve more people effectively without making participants pay?

**Headline:** Help participants document the work they do with your organization.

**Executive outcome:** Increase program capacity while improving the consistency of participation records.

**Operational value:** Publish opportunities, coordinate participation, review appropriate evidence, support participants, and prepare approved program information.

**Illustrative scenario:** A participant finds a service opportunity, records a shift, and receives a coordinator’s request for clearer evidence. The program lead reviews what the organization is authorized to share with a funder.

**Primary objection:** Our staff cannot manage another large system.

**Response:** Start with one cohort, one program owner, and the essential evidence and support steps. Individuals do not pay for participation.

**Content offer:** Partner Participation Kit.

**CTA:** Schedule a nonprofit demonstration.

### 7.4 Universities

**Primary value proposition:** Connect education, employment pathways, community initiatives, and evaluated outcomes.

**Main buying decision:** Can we improve opportunity access and demonstrate results without replacing academic systems?

**Headline:** Connect community placements with a clear record of participation.

**Executive outcome:** Make experiential and community programs easier to coordinate and evaluate.

**Operational value:** Present opportunities, connect placement partners, organize participation evidence, support students, and provide approved program views.

**Illustrative scenario:** A student documents tutoring at a community partner. Program staff request clarification before using the record in the university’s review process. Academic credit remains with the institution’s authorized academic owner.

**Primary objection:** We already have an LMS and student-information system.

**Response:** Scope WorkTrack360 around opportunity access, community participation, evidence, and program coordination. Treat any academic-system transfer as a separately verified integration.

**Content offer:** Community Placement Evidence Worksheet.

**CTA:** Schedule a university demonstration.

### 7.5 Hospitals and health systems

**Primary value proposition:** Support community workforce pathways, social-needs referrals, and measurable community initiatives.

**Main buying decision:** Can we responsibly improve access and measure community impact without moving clinical or patient information into the wrong workflow?

**Headline:** Coordinate nonclinical community participation across partner sites.

**Executive outcome:** Strengthen community-benefit and workforce initiatives with clearer participation records and program oversight.

**Operational value:** Coordinate community opportunities, referrals where consent permits, partner activity, participant support, and approved program reporting.

**Illustrative scenario:** A volunteer documents time at a food-distribution event. A partner coordinator reviews the activity, and a program director uses approved program information for internal review. The scenario excludes patient information and does not claim a clinical outcome.

**Primary objection:** We cannot introduce patient-data or compliance risk.

**Response:** Begin with a nonclinical program, define prohibited information, use synthetic examples, and review data handling and contracts before launch.

**Content offer:** Nonclinical Volunteer Program Scope Template.

**CTA:** Schedule a health-system demonstration.

---

## 8. Multi-state MCO story strategy

### 8.1 Status

The first release contains a **clearly labeled placeholder** for an anonymous multi-state Managed Care Organization story. It must not be presented as customer proof until the client relationship, facts, qualitative outcomes, anonymity controls, and publication rights are approved.

### 8.2 Public summary copy

**Heading:** Coordinating community programs across states requires one clear operating story.

**Body:** Multi-state organizations often coordinate different programs, partners, participant needs, and reporting expectations. WorkTrack360 is designed to help institutions establish a common experience for opportunity access, participation records, support, review, and approved program visibility while respecting local authority and data boundaries.

**Disclosure:** Illustrative commercial scenario. Full client story pending factual and publication approval.

**CTA:** Request the full brief when available.

### 8.3 Protected full-story placeholder

The invitation-only area reserves the following structure:

1. Organization context
2. Multi-state coordination challenge
3. Participant and program-team journey
4. Operating model and authority boundaries
5. WorkTrack360 capabilities used
6. Qualitative operational observations
7. Implementation lessons
8. Approved next steps

No client name, state list, numerical outcome, logo, quotation, endorsement, savings claim, or performance claim appears until approved.

---

## 9. Commercial packages

All sectors receive the same complete package descriptions. Pricing is customized and is not published.

### 9.1 Pilot

**Best for:** An institution evaluating one defined program.

**Typical scope:**

- Configurable 90-to-180-day period
- One service or program
- One named executive sponsor
- One named program owner and reviewer structure
- A bounded participant cohort
- Synthetic workflow review before operational evaluation
- Agreed trust, accessibility, support, and evaluation responsibilities
- Balanced participant-and-institutional scorecard

**Next step:** Define the program, authority, cohort, review process, handoffs, and success measures.

### 9.2 Program

**Best for:** Ongoing delivery of one established institutional program.

**Typical scope:**

- One defined program and operating model
- Named program and review owners
- Participant access and support model
- Opportunity, participation, evidence, review, and reporting configuration appropriate to the program
- Regular operating and outcome-review cadence
- Trust and governance review
- Expansion plan based on approved evidence

**Next step:** Map the current participant-to-reviewer journey and implementation responsibilities.

### 9.3 Enterprise

**Best for:** One institution coordinating multiple programs, sites, departments, or partner organizations.

**Typical scope:**

- Multiple programs or sites
- Central governance owners
- Common evidence and review expectations
- Local operating roles and delegated responsibilities
- Organization-wide reporting definitions
- Integration and data-boundary discovery
- Controlled rollout sequence

**Next step:** Establish the enterprise governance model and sequence the first programs.

### 9.4 Statewide

**Best for:** A statewide sponsor coordinating regional and local operators.

**Typical scope:**

- Statewide governance sponsor
- Regional, county, or local operating organizations
- Defined authority boundaries
- Common minimum program record
- Local review and exception paths
- Accessibility, privacy, security, and oversight plan
- Phased rollout and support model
- Approved statewide and local reporting definitions

**Next step:** Convene state and local owners for a bounded discovery and launch plan.

### 9.5 Package guardrails

- Size and geography alone do not determine a package.
- Discovery determines program scope, participants, partners, reviewer structure, configuration, approved handoffs, support, and rollout.
- Do not publish list prices, contract terms, implementation times, entitlements, or integration service levels until approved.

---

## 10. Pilot evaluation framework

Every pilot uses a balanced scorecard agreed before launch.

### Participant measures

- Account and approval journey completion
- Opportunity exploration and participation
- Ability to understand the next step
- Documentation completeness and clarification burden
- Support responsiveness
- Accessibility and usability observations

### Institutional measures

- Review workflow clarity
- Documentation quality
- Time and handoffs required for review
- Support workload
- Program visibility
- Data-quality and governance exceptions
- Authorized reporting readiness

No target improvement, savings, or impact claim is published until the baseline, measurement method, sample, period, and customer approval are documented.

---

## 11. Website architecture

The production concept uses one domain with two paths. The prototype is one self-contained HTML file with route-like views.

### 11.1 Public routes

| Prototype route | Purpose |
|---|---|
| `#/` | Neutral audience gateway |
| `#/individuals` | Individual value, approval model, and getting started |
| `#/organizations` | Five-sector gateway |
| `#/organizations/state-hhs` | State HHS buyer journey |
| `#/organizations/counties` | County buyer journey |
| `#/organizations/ngos` | NGO/nonprofit buyer journey |
| `#/organizations/universities` | University buyer journey |
| `#/organizations/hospitals` | Hospital/health-system buyer journey |
| `#/organizations/packages` | Shared package comparison and explanation |
| `#/organizations/resources` | Guides, worksheets, webinars, and readiness assessment |
| `#/organizations/trust` | Public Trust and Governance overview |
| `#/organizations/stories/mco` | Public anonymous MCO-story summary |
| `#/organizations/demo` | Demo form, optional planner, and simulated scheduling |

### 11.2 Invitation-gated routes

| Prototype route | Purpose |
|---|---|
| `#/organizations/tour` | Guided commercial product narrative; no application simulation |
| `#/organizations/stories/mco/full` | Approved-story placeholder |
| `#/organizations/trust/documents` | Protected diligence-material placeholder |

The static prototype gate is a demonstration only. It offers **Request an invitation** and **Preview with a sample invitation**. Production requires individual email invitations with expiry, revocation, and user-level audit.

### 11.3 Explicitly out of scope

- Product dashboards
- Simulated application workflows
- Member, reviewer, case-manager, admin, or reporting application screens
- Real registration or sign-in
- Real invitations
- Real lead submission
- Real meeting creation
- Real Trust Center documents
- Customer data or PHI

---

## 12. Page-by-page content specification

### 12.1 Audience gateway

**Eyebrow:** One WorkTrack360 platform

**Heading:** Connecting People to Opportunity. Helping Programs Deliver Outcomes.

**Body:** Choose the experience that fits what you want to do today.

**Card 1:**

- Label: For individuals
- Heading: Find opportunities and follow your progress.
- Body: Create an account, complete program review, explore jobs, learning and volunteering, and see the next step.
- CTA: Continue as an individual

**Card 2:**

- Label: For organizations
- Heading: Sponsor programs and strengthen accountability.
- Body: Explore how WorkTrack360 can help institutions coordinate participation, documentation, support, governance, and approved outcomes.
- CTA: Continue as an organization

### 12.2 Organizations gateway

**Heading:** Which sector do you serve?

**Body:** WorkTrack360 is one platform with a buyer experience designed for the decisions, teams, and outcomes in your sector.

Sector order:

1. State Health and Human Services
2. Counties
3. NGOs and nonprofits
4. Universities
5. Hospitals and health systems

**Primary CTA:** Schedule a demo  
**Secondary CTA:** Explore the guided commercial tour

### 12.3 Sector-page shared sequence

1. Sector promise and buying decision
2. Real-world illustrative scenario
3. Executive outcomes
4. Program operations
5. Frontline experience
6. Trust and governance
7. All four package descriptions
8. Sector resource offer
9. Demo CTA

### 12.4 Guided commercial tour

**Heading:** See how opportunity, participation, review, and outcomes connect.

The tour explains four connected moments without reproducing the application:

1. A person discovers an opportunity.
2. A program supports participation and documentation.
3. An authorized reviewer asks for clarification or records the appropriate decision.
4. Leadership uses approved aggregate information to understand the program.

Each diagram includes an ordered text equivalent. No dashboard or application interface is shown.

### 12.5 Trust and Governance Center

**Public heading:** Start the trust conversation early.

**Public body:** WorkTrack360 buyers need clear answers about access, data boundaries, privacy, accessibility, auditability, AI governance, operations, and third parties. The public Trust Center explains the questions we address. Approved prospects can request detailed diligence materials.

Public topics:

- Identity and role-based access
- Tenant and program boundaries
- Information handling and retention
- Auditability and administrative oversight
- Accessibility target and testing scope
- AI registry, consent, human review, fallback, and incident controls
- Vendor and integration review
- Security contact and diligence request

Protected details must not appear in the self-contained HTML source.

### 12.6 Resources

Launch resources:

- State and Local Review Mapping Worksheet
- County Participant-to-Reviewer Walkthrough
- Partner Participation Kit
- Community Placement Evidence Worksheet
- Nonclinical Volunteer Program Scope Template
- Program Implementation Checklist
- Pilot Scorecard Builder
- Program Readiness Assessment
- Anonymous Multi-State MCO Story Summary
- Trust and Governance Overview
- Webinar: From Opportunity Discovery to Program Outcomes

### 12.7 Demo request

**Heading:** See WorkTrack360 through the program you want to improve.

Short form fields:

- First and last name
- Work email
- Organization
- Sector
- Role
- Optional business goals

Business-goals warning:

> Do not include personal, health, participant, case, or other confidential information.

After valid completion, the prototype displays placeholder scheduling times and states clearly that no information left the page and no appointment was created.

Optional pilot planner fields:

- Program or service
- Geography
- Approximate participant cohort
- Participating organizations or sites
- Who supports participants
- Who reviews documentation
- What the next authorized handoff is
- Primary implementation question

---

## 13. Invitation-only commercial tour strategy

### 13.1 Production model

- Individual email invitation
- Expiring link
- Revocable access
- User-level audit
- Sector and account context where approved
- No shared password

### 13.2 Prototype model

The offline prototype cannot provide real access security. Its gate demonstrates:

- Invitation explanation
- Request-invitation state
- Sample invitation state
- Return to requested protected content
- Expiry and revocation language

Only material safe for public distribution may be embedded in the HTML file.

Approved copy:

> For the live service, invited guests receive an individual email link that expires. This offline prototype uses a sample invitation and does not provide real access protection.

---

## 14. Trust, privacy, and analytics strategy

### 14.1 Privacy-first analytics

Measure only what is needed to improve the commercial journey:

- Site and sector selected
- Resource viewed
- Demo form started and completed
- Scheduler reached
- Optional planner completed
- Invitation requested
- Commercial tour completed

Do not collect participant information, health information, case details, program evidence, or sensitive personal data through marketing analytics or inquiry forms.

### 14.2 Inquiry-form safeguards

- Structured fields first
- Limited optional business-goals field
- Clear “do not include personal or confidential information” warning
- Retention and CRM routing policy before production
- Approved processors only
- Consent and preference controls as required

### 14.3 Accessibility

Target WCAG 2.2 Level AA. Do not publish a conformance claim until the tested scope, date, method, results, and exceptions are approved.

Prototype acceptance includes:

- 320 CSS-pixel reflow
- 200% text resize
- Keyboard-only navigation
- Visible focus
- Semantic headings and landmarks
- Accessible disclosures and dialogs
- Form labels, instructions, error summary, and focus recovery
- Contrast for text, controls, focus, and errors
- 44-pixel touch-target design goal
- Reduced-motion support
- Equivalent text for diagrams

---

## 15. Lead conversion and sales handoff

### 15.1 Primary institutional conversion

**Schedule a demo.**

The public site uses a short form and immediately exposes scheduling after valid completion. The optional pilot planner never blocks scheduling.

### 15.2 Contact channels

The first package contains placeholders for:

- Shared sales email
- Scheduling URL

They must be replaced with approved, monitored destinations before external release.

### 15.3 Lead routing

The selected launch design uses immediate scheduling rather than sector-based qualification before booking. CRM records should still preserve:

- Source and campaign
- Sector
- Organization
- Role
- Resource or page context
- Demo completion
- Optional planner completion

---

## 16. Content and campaign strategy

### 16.1 Launch model

All sector experiences go live together. Campaigns run in coordinated waves while maintaining equal investment and content quality.

### 16.2 Twelve-week campaign structure

**Weeks 1–2: Account and message preparation**

- Build comparable target-account cohorts in all five sectors.
- Identify sponsor, operator, reviewer, privacy/security, accessibility, procurement, and fiscal owners.
- Tailor first contact to one local or institutional program.
- Publish all five ungated sector briefs.

**Weeks 3–5: Education and guided review**

- Offer sector-specific worksheets.
- Invite champions to include an operational reviewer.
- Use the shared guided commercial tour.
- Track sector, account, source, and content engagement for institutional leads only.

**Weeks 6–8: Program scoping**

- Facilitate a one-program scoping session.
- Use the optional planner.
- Identify participant journey, evidence owner, review authority, next handoff, and prohibited data.
- Route trust and accessibility diligence through the Trust Center.

**Weeks 9–12: Pilot decision**

- Agree on pilot decision criteria.
- Document operating assumptions and unresolved handoffs.
- Select the appropriate package.
- Identify expansion prerequisites without publishing unverified outcome targets.

### 16.3 Campaign spotlight order

The website gives all sectors equal priority. Content spotlights follow the selected public-sector-first order:

1. State HHS
2. Counties
3. NGOs and nonprofits
4. Universities
5. Hospitals and health systems

Every wave includes activity in all five sectors; the spotlight controls the featured guide, webinar, and account-based sequence, not commercial eligibility.

---

## 17. Measurement framework

### Commercial funnel

- Target accounts engaged by sector
- Qualified institutional visitors
- Resource engagement
- Demo requests
- Held demonstrations
- Optional planners completed
- Scoped pilot opportunities
- Signed pilots
- Pilot-to-program or pilot-to-enterprise decisions
- Expansion decisions by sector

### Content performance

- Sector gateway selections
- Sector brief completion
- Trust Center engagement
- Commercial-tour invitations requested and completed
- Resource-to-demo conversion
- MCO story summary engagement

### Individual journey

- Account-start conversion
- Approval-information comprehension
- Pending-user return rate
- Read-only opportunity engagement while pending

No numerical target is included in Version 1.0 until current baselines, analytics governance, and ownership are established.

---

## 18. Mobile-first interaction specification

- Start at 320 CSS pixels and progressively enhance.
- Use one-column content flow on small screens.
- Keep primary actions visible without covering content.
- Convert sticky role navigation to a labeled disclosure on narrow screens.
- Disable sticky positioning on short viewports when it could obscure keyboard focus.
- Use large readable body text, short paragraphs, clear headings, and plain-language summaries.
- Make interactive targets at least 44 pixels where feasible.
- Do not require hover.
- Avoid horizontal scroll.
- Preserve Back, Forward, refresh, and copied deep links.
- After route changes, update the document title and focus the page heading.
- After intentional section jumps, focus the target heading.
- Preserve entered form values after validation errors and focus the error summary.

---

## 19. HTML package requirements

The deliverable is one self-contained HTML file containing:

- Embedded approved WorkTrack360 logo
- Embedded CSS and JavaScript
- Embedded vector illustrations
- Two connected site experiences
- Hash-based navigation
- Five sector pages
- Complete package content on every sector page
- Public Trust Center
- Resource center
- Public MCO story summary
- Sample invitation gate and protected placeholders
- Demo form, optional planner, and simulated scheduler
- No network writes
- No application dashboard or workflow simulation
- No PHI, secrets, credentials, client names, or customer data

The final package also includes this Markdown strategy and a ZIP for download.

---

## 20. Review checkpoints

### Checkpoint 1

- Strategy structure
- Product and evidence model
- Site architecture
- Core messaging
- Sector journeys
- Package framework
- Mobile design direction
- First clickable build

### Checkpoint 2

- Complete copy review
- Final visual polish
- Accessibility and mobile validation
- Cross-page consistency
- Placeholder inventory
- Offline package validation
- Private hosted-review validation
- Final ZIP

---

## 21. Production dependencies and placeholders

Before public release, owners must provide or approve:

- Shared sales email
- Scheduling URL
- Final privacy notice and cookie/analytics language
- Approved human imagery and usage rights
- Final anonymous MCO facts and publication permission
- Protected Trust Center material and access owner
- Analytics and CRM vendors
- Data retention and inquiry-routing policy
- Security, privacy, accessibility, and legal claim review
- Current production capability and environment validation
- Domain and routing plan for `/individuals` and `/organizations`

---

## 22. Decision register

| Decision | Selected direction |
|---|---|
| Site model | Two connected experiences under one domain |
| Root | Neutral audience gateway |
| Paths | `/individuals` and `/organizations` |
| Institutional entry | Five-sector gateway |
| Sector order | State HHS, Counties, NGOs, Universities, Hospitals |
| Sector depth | Equal depth and priority |
| Brand | Existing WorkTrack360 identity |
| Personality | Human opportunity with institutional trust |
| Tagline | Connecting People to Opportunity. Helping Programs Deliver Outcomes. |
| Geography | United States nationwide |
| Individual access | Account required; Program Reviewer approval required |
| Pending users | Read-only opportunity browsing |
| Individual funding | Free to individuals; institution-funded |
| Packages | Pilot, Program, Enterprise, Statewide |
| Pricing | Custom proposal; no public prices |
| Pilot length | Configurable 90 to 180 days |
| Pilot measures | Balanced participant/institutional scorecard |
| GTM | Account-based outreach plus inbound content |
| Campaign launch | All sector pages together; coordinated waves |
| Primary institution CTA | Schedule a demo |
| Demo flow | Short form, optional planner, immediate scheduling |
| Trust Center | Public overview; protected detailed materials |
| MCO story | Public summary; gated full placeholder; qualitative only |
| Guided review | Invitation-only commercial narrative, not product UI |
| Invitation model | Individual expiring email invitation in production |
| Analytics | Privacy-first; no participant or health data |
| Inquiry text | Structured fields plus restricted optional business-goals text |
| Language | English only for Version 1.0 |
| Accessibility | WCAG 2.2 AA target |
| Responsive design | Mobile-first mandatory |
| Prototype format | One self-contained HTML file |
| Delivery | Downloadable package plus private hosted review |
| Development sequence | Markdown and HTML developed together |
| Reviews | Two structured checkpoints |

---

## 23. Final approval statement

This strategy defines the commercial narrative and website experience. It does not authorize changes to G2 or WorkTrack360 application code, databases, environments, security settings, customer communications, analytics vendors, CRM systems, or public domains.

Public release requires a final review of claims, capability readiness, customer-story rights, contact destinations, privacy language, protected materials, accessibility results, and live links.
