Methodology

Methodology and product foundation

Learn how PRISMA works—from assessment to ongoing monitoring. Explore the six-module framework, the standardized tools that support each step, and where professional review remains essential. This page focuses on the PRISMA methodology, not individual credentials or client testimonials.

Operating sequence

M1 to M6 at a glance

PRISMA moves from intake through classification, governance, controls, monitoring, and transfer review. Each module has a role; none replaces licensed professional judgment.

PRISMA module sequence

  1. Diagnostic

    Structured intake of self-reported practice signals.

  2. Risk classification

    Organize findings with scoring and response-window guidance.

  3. Governance design

    Outline internal roles before implementation work.

  4. Implementation

    Track operating controls such as calendars and documentation.

  5. Monitoring and corrective action

    Make owners, due dates, and closure status visible.

  6. Transfer and autonomy

    Review handoff continuity without claiming certification.

Module overview

What each module is for

Concise purpose, primary output, key sources, and a professional boundary for each step.

Diagnostic

Purpose
Collect structured, self-reported practice answers.
Primary output
Intake signals ready for later classification.
Key sources
T-01
Professional boundary
No professional conclusion from illustrative answers.

Risk classification

Purpose
Classify findings for attention and response timing.
Primary output
Risk and opportunity categories with provisional priority.
Key sources
T-02, T-09
Professional boundary
Not a compliance determination or legal conclusion.

Governance design

Purpose
Shape internal ownership before controls are installed.
Primary output
Governance outline for the fictional demo company.
Key sources
T-10
Professional boundary
Design support only; not professional assignment.

Implementation

Purpose
Install and track operating control pieces.
Primary output
Control status across payroll, filings, documentation, and insurance views.
Key sources
T-03 to T-06
Professional boundary
Software tracking; filings and advice stay external.

Monitoring and corrective action

Purpose
Keep follow-through visible after issues are identified.
Primary output
Corrective actions with owners, dates, and review notes.
Key sources
T-07, T-08
Professional boundary
Tracking support; not certified remediation.

Transfer and autonomy

Purpose
Review operating handoff toward internal continuity.
Primary output
Transfer checklist and impact review in the demo.
Key sources
T-10, T-11
Professional boundary
Not certification or an autonomy declaration.

Source map

T-01 to T-12 by module

Modules map to internal instruments. Meanings below are product interpretation for demonstration. They are not a claim that packets are public or externally validated.

ModuleInstrumentsProduct interpretation
ModuleM1InstrumentsT-01Product interpretationBusiness intake questionnaire
ModuleM2InstrumentsT-02 and T-09Product interpretationRisk assessment matrix and escalation windows
ModuleM3InstrumentsT-10Product interpretationGovernance roles and competencies
ModuleM4InstrumentsT-03 to T-06Product interpretationPayroll, filings, documentation, and insurance controls
ModuleM5InstrumentsT-07 and T-08Product interpretationCorrective action tracking and management review view
ModuleM6InstrumentsT-10 and T-11Product interpretationTransfer continuity and impact indicators
ModuleAcross modulesInstrumentsT-12Product interpretationImplementation guidance

Source instrument labels differ from product interpretation. Full instrument files are not published in this public prototype.

Evidence boundaries

What is backed, interpreted, illustrative, or under review

Keep these four layers separate when you read the product or the demo.

Source-backed

Module-to-instrument relationships and scoring rules referenced in product configuration.

Product interpretation

Plain-language titles, UI labels, and operating sequences that explain how instruments are used in software.

Illustrative demo content

Fictional company records, seeded risks, controls, and corrective actions used only for demonstration.

Under professional review

Final licensed disclaimer text, canonical score-band presentation, and any future external validation.

Foundation

What this page covers

Product and methodology foundation only. This is not a professional credential profile.

What this page documents

PRISMA's operating sequence, source map, evidence boundaries, and the bilingual product work you can open on this site. External professional review still sits outside the software.

What is not represented here

  • Published personal licenses or memberships
  • Awards, client lists, or endorsements
  • Implied hidden credentials
  • Claims of external product validation

Development evidence

Concrete product work you can verify

These are existing surfaces in this prototype. They are not adoption metrics, pilots, or market outcomes.

  • Bilingual public diagnostic with provisional results
  • Functional illustrative M1 to M6 product demo
  • Source map across T-01 to T-12
  • Product-status page for external review
  • Documented QA and ownership regression tests
  • Documented design system and visual QA plans

Professional boundaries

Software supports organization. Licensed work stays external.

The product does not replace licensed professionals. Professional judgment, filings, advice, and final determinations remain outside the software. Illustrative demo records are not client records. Product statuses are not certifications. The product does not assign or contact professionals.

See what is built today

Product status lists what is functional, illustrative, deferred, and under review.