Dottie guidance must stay separate from the quality decision
Dot Compliance presents Dottie as an AI quality and compliance guide within its life-sciences eQMS, alongside ready-to-use modules and quality workflows. Guidance may accelerate review, but the regulated record still needs attributable source evidence, qualified judgment, approval authority, and a preserved path from suggestion to decision.
Editorial figure by RegQuality Review. Source context: Dot Compliance eQMS.
An AI guide and an authorized quality conclusion have different roles
Dot Compliance's current eQMS page presents a life-sciences quality system with ready-to-use process coverage, pre-built modules, and Dottie, described as an AI quality and compliance guide. That positioning can support an efficient operating question: where can generated guidance organize work, highlight missing information, or suggest a next step without becoming the regulated conclusion that a qualified person or quality unit must own?
A generated summary, classification, recommendation, draft investigation text, or proposed action is an output from a configured system. A quality decision addresses a defined record and product or process scope under applicable procedures, evidence, competence, and authority. The system should not let a reviewer acceptance click erase which language was generated, which evidence supported it, what the person changed, or why the authorized conclusion differed.
Preserve evidence, configuration, and output provenance
Every AI-assisted record should identify the source documents and record versions used, excluded or unavailable inputs, retrieval time, model or service identity and version where available, configured instruction or task type, output time, generated content, confidence or limitation signals, user edits, reviewer identity, and downstream records that consumed the output. Correcting a source should create a new evaluation rather than silently revising the prior suggestion.
The evidence boundary also needs access and retention rules. A system should prevent generated text from being mistaken for an original observation, laboratory result, complaint statement, supplier response, investigation finding, or approved procedure. If a source conflicts with another record, the output should expose the conflict or route it for review instead of combining the two into a fluent answer that hides uncertainty.
Define stops, review authority, and change control
Owners should specify which tasks permit drafting, recommendation, classification, or automation; which require independent verification; and which may never proceed without a named qualified role. Stop conditions can include missing critical evidence, product-impact uncertainty, reportability questions, conflicting specifications, adverse trends, patient or subject risk, supplier disputes, data-integrity concerns, and output behavior outside the validated or approved use.
Changes to the AI service, connected data, module configuration, procedure, taxonomy, or approval workflow need impact assessment proportional to the intended use. The record should show testing, acceptance criteria, approved release, effective date, training effects, open-record treatment, rollback, and periodic review. A vendor's ready-to-use or compliance-oriented positioning does not define the customer's intended use or remove the customer's validation and quality-system responsibilities.
Test a persuasive recommendation that is wrong
A representative evaluation should load a quality event with one missing document, request an AI summary and proposed classification, add conflicting evidence, have a qualified reviewer reject part of the recommendation, revise the source record, and route a product-impact decision to the proper authority. Reviewers should reproduce both outputs, identify every source and edit, explain the final conclusion, and show that downstream actions used the approved record rather than the first generated answer.
Dot Compliance's official page supports the described life-sciences eQMS, module, process-coverage, Salesforce, and Dottie guidance positioning, but no customer record, source evidence, model, output, workflow, validation package, quality decision, configuration, implementation, or outcome was independently tested here. Regulated organizations and their qualified quality, regulatory, manufacturing, validation, clinical, IT, data-integrity, and legal owners retain their decisions.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.