Access by approved implementation.

Pilot readiness

Pilot Readiness

A plain-language gate map for what is required before a controlled pilot, what remains before production scale, and how institutions approve rollout before anyone buys.

Access is provisioned through approved institutional implementation.

AnchorGrey Workspace

Director workspace

Spring 2026 cohort

Tenant provisioned
42Learners
24Complete
8Action needed
Reviewer workflow5
Program review11
Expiration watch7

Learner checklist

TB documentation
MMR record
Program form

Reviewer queue

Correction needed
Escalation

State model

Marketing, pilot, and production are different states.

This page keeps the implementation path visible so a polished product site still respects approval, legal, security, and operational gates.

Marketing site state

  • Institutional product positioning
  • Approved implementation conversations open
  • Sample interface visuals
  • Implementation approval path
  • Direct buyer conversation
  • No self-serve purchase path
  • No public onboarding workflow

Controlled pilot state

  • Real auth enabled
  • Student roster import enabled
  • Signed upload flow enabled
  • Quarantine and scan workflow enabled
  • Reviewer queue enabled
  • Program status dashboard enabled
  • Paubox generic notifications enabled
  • Stripe sensitive records-free billing enabled

Production state

  • Multi-program tenancy
  • Monitoring and alerts
  • Support operations
  • Retention and deletion workflows
  • Backup and restore evidence
  • Security review
  • Repeatable onboarding
  • Contract templates

Gate table

Nothing moves to real uploads until these gates are explicit.

Pilot requirements identify the work that must be approved before a private rollout becomes an institution's records operating layer.

Gate Owner Current status Required before pilot
Google BAA AnchorGrey owner Not part of public site Yes
Google Cloud project Technical lead Implementation planning Yes
Covered services review Counsel + technical lead Implementation planning Yes
FERPA/HIPAA counsel review Counsel Issue-spotted Yes
Consent or authorization language Counsel Implementation planning Yes
Access control matrix Technical lead Draft model Yes
Retention policy Counsel + operations Planning only Yes
Incident response SOP Operations Planning only Yes
Secure notification policy Operations Planning only Yes
Stripe metadata policy Technical lead Planning only Yes
Malware scan workflow Technical lead Implementation planning Yes
Backup and restore test Technical lead Implementation planning Yes

Buyer walkthrough

A buyer walkthrough for the implementation conversation.

1

Homepage

Start with the product category and institutional buyer problem.

2

Product overview

Explain guided compliance readiness and role-based navigation.

3

Director dashboard

Show status-only visibility, missing counts, and minimum-necessary reporting.

4

Learner dashboard

Show clearer next steps and correction loops.

5

Reviewer queue

Show the document-review nuance lane with sample records states.

6

Requirement builder

Show program-defined templates and status-only visibility defaults.

7

Pilot architecture

Show the Google-centered implementation architecture.

8

Billing

Frame pilot economics as a direct approval conversation.

9

Pilot readiness gates

Close with the gates required before real student workflows.