Frequently asked, honestly answered.

TeachSmartHQ™ is an educator workflow platform built to generate the documents and materials teachers actually have to produce, not just give vague suggestions. Right now the live platform centers on the PLAAFP Generator™, with the Worksheet Generator™ positioned across the site as in active build and included in current paid tiers, and the broader ladder built around the Lesson Delivery System, Parent Update Generator™, Enhanced PLAAFP, and Adaptive Lesson Generator™ (ALG) as tiers expand.

In plain language, that means TeachSmartHQ™ is meant to help with work like:

• present levels and documentation drafts
• differentiated worksheets and student practice materials
• lesson-delivery materials and structured planning
• parent-facing updates as those higher-tier tools come online
• connected workflow across planning, differentiation, documentation, and support

What it is not trying to be is a generic chatbot, a prompt marketplace, or a replacement for your school systems. TeachSmartHQ™ is built as a workflow layer that sits alongside the tools schools already use.

No. TeachSmartHQ™ is being built for educators who want better outputs, not a side hobby in model settings, prompt engineering, or keeping up with the AI discourse of the week.

What “you do not need to know AI” looks like here is simple:

• you work inside a structured generator instead of writing a blank-box prompt from scratch
• the platform asks for classroom-relevant inputs, not technical ones
• the output comes back in an educator-facing format you can review and revise
• the system is built to absorb the AI complexity so the teacher can stay focused on the student, the lesson, or the document

AI literacy is a moving target. The average teacher should not have to learn a new vocabulary every six weeks just to make a worksheet or draft a PLAAFP faster. TeachSmartHQ™'s job is to carry the technical load under the hood and give the educator something usable on the surface.

No. TeachSmartHQ™ is framed across the site as being for the people doing educator work, not just people with one specific job title. A classroom teacher, a special educator, a paraprofessional, a tutor, and a homeschool educator may all need structured materials, but they do not use them in the same way.

• Classroom teachers usually get value from planning support, worksheet generation, lesson structure, and cleaner workflow across an already-crowded day.
• Special educators get a different kind of value: documentation support, PLAAFP drafting, differentiation, scaffolds, and materials that reflect real learner variation instead of one-size-fits-all pacing.
• Paraprofessionals are not usually the final signer on formal documents, but they still carry a lot of instructional support, adaptation, and day-to-day implementation load. For them, the value is often structure, clarity, usable materials, and better support for the actual students in front of them.
• Tutors benefit from fast differentiation, small-group and 1:1 materials, and cleaner lesson prep without rebuilding everything by hand.
• Homeschool educators often need multi-grade flexibility, printable materials, and support that works across subjects and age levels without forcing a traditional school model onto home instruction.
• Instructional leaders, coaches, and team leads may care less about one draft and more about whether the system is useful, trainable, and realistic for adoption.

Who is it not really for? Someone looking for a student-facing LMS, a gradebook, a district SIS, or a fully autonomous “do school for me” product. TeachSmartHQ™ is an educator workflow platform. If you want something that replaces professional judgment, district systems, or direct teaching, this is the wrong tool.

They solve different problems.

The Worksheet Generator™ is the classroom-material engine. Its job is to create differentiated, teacher-quality worksheet artifacts that are ready for real use. Across the site, it is described as scaffolded, accessible by default, and built for multiple output modes rather than one flat printable.

The Adaptive Lesson Generator™ (ALG) is the flagship, higher-tier system. Its job is not just to make a worksheet. It is meant to generate per-student adaptive lessons that respond to the learner, support multiple interaction modes, and feed richer performance data back into the broader workflow.

A practical way to think about it:

• Worksheet Generator™ — “I need a differentiated practice artifact.”
• ALG — “I need a student-specific learning experience that adapts and closes the loop with data.”

That is why ALG is bundled only in Premiere™ Max and Team Premiere™ Max on the current ladder. It is positioned as the most advanced part of the platform, not as a default feature everyone gets on day one.

The honest answer depends on the feature. TeachSmartHQ™ uses status language on purpose. Some tools are live, some are in active build, and some are still on the roadmap. That is healthier than pretending everything is already done.

Current public positioning:

• PLAAFP Generator™ — live now
• Worksheet Generator™ — in active build, included in current paid-tier framing
• Lesson Delivery System — included starting at Premiere™ on the pricing ladder
• Parent Update Generator™ — coming soon in Premiere™ Plus and up
• Enhanced PLAAFP — coming soon in Premiere™ Plus and up
• Adaptive Lesson Generator™ (ALG) — included in Premiere™ Max and Team Premiere™ Max, and also part of school/district pathways

TeachSmartHQ™ is consistently positioned as an upgrade, not a replacement.

Most educators do not need one more platform demanding to become the center of the universe. They already have a stack: an LMS, an SIS, an IEP system, maybe a district AI tool, maybe Google Classroom, maybe Microsoft Copilot, maybe something ancient and slightly haunted that only loads correctly in one browser.

The live Plans page explicitly says TeachSmartHQ™ works alongside tools like:

• Infinite Campus
• PowerSchool
• Skyward
• Goalbook
• Google Classroom
• Microsoft Copilot
• Kami
• IEP systems
• LMS platforms

The practical model is this: TeachSmartHQ™ helps create better drafts, materials, and workflow outputs. You still use your school systems for the things those systems are built to do, like official records, enrollment data, gradebook functions, and district-controlled environments.

The short version: it is being built around the work SPED educators actually carry. That shows up in several ways:

• the PLAAFP Generator™ is live and clearly central
• documentation and educator workflow are treated as real work, not side quests
• differentiation is framed as a built-in design principle, not an afterthought
• accessibility and inclusion are treated as part of the product direction, not optional garnish

A general classroom teacher might mainly care about prep time, lesson structure, or faster materials.

A special educator often cares about all of that plus things like:

• writing documentation in a way that respects both time and professional standards
• generating differentiated artifacts without manually rebuilding everything six times
• keeping learner support visible and explicit
• using tools that understand the reality of IEP-linked workflow rather than pretending a classroom is one average student repeated 25 times

That is a materially different value story, and the platform is strongest when it acknowledges that directly.

For paraprofessionals, the value is not usually about being the final account owner of every formal workflow. It is about having better structure for the support work they actually do.

That can include:

• helping prepare or adapt classroom materials
• supporting differentiated instruction in small groups or 1:1 settings
• contributing observations and student-facing support details that inform stronger drafts
• working from clearer, more usable materials instead of piecing supports together in the moment

A teacher may use TeachSmartHQ™ to draft and finalize a broader workflow. A para may use it to make that workflow more workable on the ground. Those are not the same use case, and pretending they are would flatten the real roles people play in classrooms.

Yes, if the need is structured planning, differentiated materials, documentation support, or multi-learner workflow. The site consistently includes homeschool educators and tutors in its target audience.

For homeschool educators, the obvious fit is flexibility:

• multi-grade use in one household
• printable or structured materials without rebuilding from scratch
• support across subjects and pacing levels
• workflow help that is not locked to one traditional classroom model

For tutors, the fit is often even more direct:

• fast prep for 1:1 or small-group sessions
• differentiated materials without a ton of manual formatting
• better workflow for repeatable student support

The honest limit: if someone wants a homeschool recordkeeping system, a parent portal, or a student-facing tutoring marketplace, that is outside the core purpose here. TeachSmartHQ™ is still the educator workflow layer.

TeachSmartHQ™ is built around a very specific privacy posture: it is an educator workflow platform, not a student information system. Across the site, the public rule is clear: educators should use generic learner references such as “Student A” rather than real student identifiers.

The core safeguards are:

• educators are instructed not to enter student PII into generators
• the backend applies server-side PII scrubbing before text reaches the AI layer
• the public privacy position says inputs and outputs are not used to train AI models
• the platform maintains audit logging and privacy-conscious controls as part of its district-readiness baseline
• retention posture includes soft-delete / removal from active storage within a defined window, typically 30 days

That scrubbing layer is the important procurement detail. The platform's model is not just “please be careful.” It performs server-side substitution of student names, initials, contact details, dates of birth, and address fragments before any text reaches the API, replacing learner references with generic tokens such as “Student A.”

No privacy answer should promise magic. But this is stronger than a rules-only policy — it is a rules-plus-safeguards model, and that is the right way to describe it. See the Privacy Policy for the full posture.

The careful answer is: TeachSmartHQ™ is built to support FERPA-aligned use, but it is not marketed as a student information system and it still depends on proper educator and district use. That is not a dodge. It is the honest answer.

The public site makes a few key points:

• TeachSmartHQ™ does not ask educators to input student names or identifying student data as part of normal use
• generic student references are the expected workflow
• backend scrubbing exists as a safeguard
• DPA / NDPA review is available for districts that need formal documentation

FERPA is partly about vendor posture and partly about actual data practice. A district reviewer will want to know whether the platform is designed to minimize student PII exposure, whether the vendor has a workable contract path, and whether the product is trying to be a system of record. The public answer to all three is favorable.

Under the normal intended workflow, TeachSmartHQ™ is designed not to collect, store, or process real student identifying information as part of ordinary use.

That is why the site repeatedly says educators should use generic references like “Student A” or “the student.” It is also why the privacy posture is tied to server-side scrubbing and not just to policy language.

The more nuanced answer is this:

• the platform is built to avoid student PII as a normal input type
• the platform includes safeguards to scrub accidental PII before AI processing
• saved files and drafts are still the educator's responsibility, which is why the legal language reminds users not to save PII-loaded content into the system

So if someone asks, “Does TeachSmartHQ™ work with student context?” yes, in a generalized, de-identified workflow sense. If they ask, “Is this intended to be a database of named student records?” no.

The public Privacy Policy and FAQ language says account data and saved drafts are stored on secure, US-based cloud infrastructure, with payment data handled by Stripe rather than stored directly by TeachSmartHQ™.

On retention, the clearest procurement-grade phrasing is:

• active account data is retained to deliver the service
• payment data is handled through Stripe
• when accounts are canceled or terminated, content is not treated as instantly vaporized in the UI sense, but the legal posture supports soft-delete / removal from active storage within a reasonable window, typically around 30 days
• audit logging and access controls are part of the district-readiness baseline described publicly on the site

This is an area where public-facing pages are being unified for consistency, but the core posture is understandable: privacy-conscious storage, no training on customer content, and defined retention rather than endless uncontrolled keeping.

No. TeachSmartHQ™ is powered by Anthropic AI, whose Commercial Terms of Service prohibit using customer inputs and outputs to train Anthropic's models. That is a contractual posture, not just a TeachSmartHQ™ promise about itself.

Multiple live pages also state that inputs, outputs, and saved drafts are not used to train AI models. That is one of the most important trust anchors on the site, especially for educators and district reviewers who are rightly tired of vague language around AI data use.

The Schools & Districts page gives a pretty clean first-pass diligence picture already. TeachSmartHQ™ is publicly framed as:

• educator-facing, not student-account-first
• privacy-review friendly
• willing to discuss DPA / NDPA requirements
• responsive on school / district inquiries
• structured around pilots rather than forcing a district straight into a full rollout

For a procurement reviewer, the useful framing is this: TeachSmartHQ™ appears to understand that the district is evaluating not just features, but also privacy posture, implementation realism, billing path, and support expectations.

The right next step is usually not “buy now.” It is “start with the school/district inquiry path, bring the privacy and contract questions early, and scope the pilot to the actual decision the district is trying to make.”