Skip to main content

NEOS Operations Manual

NEOS Operations Standard · Version 1.0

NEOS Operations Manual

Standard procedures for operating, reviewing, supporting, and improving the NAPPSA digital ecosystem.

1. Daily Operations

  • Review platform health, failed jobs, security alerts, editorial queues, and broken-link reports.
  • Confirm critical conference, membership, intelligence, and Foundation services are functioning.
  • Escalate incidents according to severity and document actions taken.

2. Content Operations

Content follows Draft, Review, Approved, Published, Review Due, Archived, and Removed states. Every governed item must have an owner, audience, source, review date, and expiration rule when time-sensitive.

3. Editorial Workflow

Submissions must pass title quality, source reliability, duplication, relevance, accessibility, taxonomy, link, media, and rendering checks before publication. Failed checks route to review rather than publishing automatically.

4. Member and Entitlement Operations

Membership benefits and access must be derived from authoritative records, reconciled regularly, and handled through documented exception procedures. Manual overrides require an owner, reason, effective period, and audit entry.

5. Conference Operations

Conference information must be maintained from a canonical schedule and faculty dataset. Public agenda, speaker, CE, venue, transportation, and registration displays must not conflict across pages.

6. Incident Management

Classify incidents as Critical, High, Moderate, or Low. Critical incidents affecting security, transactions, authentication, or public misinformation require immediate containment, executive notification, recovery action, and post-incident review.

7. Change Management

Changes require a defined request, owner, risk level, test plan, approval, deployment window, rollback method, and verification record. Emergency changes must be documented after stabilization.

8. Access Reviews

Administrative and privileged access must be reviewed quarterly and whenever leadership, staff, contractor, or committee responsibilities change.

9. Monthly Review

Review uptime, failures, content freshness, accessibility defects, security findings, search performance, conversions, automation accuracy, support issues, and unresolved risks.

10. Annual Review

Produce a State of the Digital Platform report covering outcomes, risks, investment needs, governance compliance, architecture health, and the next-year roadmap.