Do these ten things first.
You do not need to learn the whole QMS before completing useful controlled work.
- Sign in with your BayesPharma account.
Your organization, Quality role and permissions determine what you can view, change, review and sign.
- Open Quality Command Center.
Start from My Quality Work rather than opening random modules.
- Review your assigned queue.
Prioritize overdue, high-risk and review-required work that belongs to your role.
- Open one controlled record.
Confirm record ID, record type, current revision, status, owner, due date, risk and linked evidence before acting.
- Read the audit/history context.
Understand what changed, who changed it and what prior evidence or decisions already exist.
- Complete only your assigned step.
For example: triage an event, investigate a deviation, implement CAPA, review evidence or perform an effectiveness check.
- Add the evidence that supports your work.
Use traceable files, source references, observations, measurements and rationale. Do not convert assumptions into facts.
- Use the available governed action.
BayesPeaQ shows the next server-permitted workflow states. Do not treat a missing action as permission to bypass the workflow.
- Route to the accountable next role.
Investigator, QA Reviewer, CAPA Owner, Approver or another configured role receives the next controlled task.
- Return to My Quality Work.
Confirm the action left your queue or changed state as expected, then move to the next assigned item.
Your role controls the actions you are allowed to perform.
BayesPeaQ is not a shared unrestricted spreadsheet. Access is organization- and role-scoped.
Use your own authenticated account. Do not share credentials or sign on behalf of another user.
Your configured role determines whether you can create/update records, investigate, review or electronically sign.
Only records within your authorized tenant and scope should be available to you.
Confirm the record is assigned correctly or ask your QMS administrator/Quality administrator to review the role assignment.
Use the command center as your daily starting point.
The command center is designed to show assigned work, risk, overdue actions and independent review needs.
Open items where your role is responsible for the next action.
Critical/high-risk, overdue and review-blocked records deserve early attention.
Do not make a decision from a queue label alone.
Make sure ownership and state changed as intended.
Read the record before you change the record.
A record is more than its title. The revision, workflow state, evidence and history determine what the current record actually means.
| Check | What it tells you | What you should do |
|---|---|---|
| Record ID | The durable identity of the quality object. | Reference it in evidence, comments and related records. |
| Revision | The exact version you are reviewing. | Re-open/review if the revision changes before approval or signing. |
| Status | The current governed workflow state. | Use only the permitted next action. |
| Owner / Responsible role | Who is accountable for the current work. | Do not perform another role’s approval step. |
| Risk | The current risk classification or not-assessed state. | Confirm the classification is supported; escalate when necessary. |
| Evidence | What supports the current conclusion. | Check source, relevance, completeness and version. |
| Audit trail | Who did what and when. | Use history to understand changes and prior decisions. |
Create the minimum accurate controlled record first.
Use New record or the Report an incident shortcut when it is available for your role and workspace.
Select the correct quality workflow: deviation, OOS/OOT, lab incident, complaint, CAPA, change control, document, training or another configured type.
Use a factual description of what happened. Avoid assigning root cause before investigation.
Add the affected context only when known and applicable.
Assign the accountable person or role according to your organization’s procedure.
Set a realistic controlled due date where required.
Use Not assessed until an authorized risk assessment supports a classification.
Record observable facts: what happened, when, where, who/what was affected and immediate containment. Keep hypotheses and conclusions clearly separate.
Avoid premature wording such as “operator error caused the failure” unless the investigation has established that conclusion.
Attach what supports the conclusion—not just what fills the form.
Evidence readiness is a signal for review. It is not automatic proof that the record is compliant or correct.
Where did the information come from? File, instrument, SOP, investigation note, external report or controlled reference.
Keep the evidence linked to the correct record, product, batch, site and revision.
State what the evidence supports and what it does not establish.
A qualified person assesses relevance, sufficiency, contradictions and limitations.
Good evidence practice
- Use traceable source files and references.
- Preserve exact versions and dates.
- Link evidence to the relevant record and revision.
- Explain contradictions or missing evidence.
- Keep reviewer rationale attributable.
Avoid
- Untraceable copied text.
- Replacing measured evidence with an AI summary.
- Calling a hypothesis a confirmed root cause.
- Approving based only on a completeness percentage.
- Deleting inconvenient contradictory evidence.
Follow the next governed action returned by the workflow.
BayesPeaQ uses workflow states rather than free-form “done” labels.
During an investigation
- Define the problem clearly.
Separate observed event, scope and impact from suspected causes.
- Collect relevant evidence.
Records, logs, analytical data, training, equipment, procedures, batch history and linked events as applicable.
- Generate and test hypotheses.
Use structured RCA methods where appropriate; Quality Copilot may assist with hypotheses but cannot establish root cause by itself.
- Assess product/process impact.
Document the basis for impact conclusions and any uncertainty.
- Route for independent review.
The reviewer should be able to see the evidence, reasoning and record history without reconstructing the story offline.
BayesPeaQ is designed to prevent an approval from silently applying to a different revision than the one reviewed.
Closure should depend on evidence that the action worked.
Completing an action item is different from demonstrating effectiveness.
Define the action, accountable owner, due date and implementation evidence.
Define what evidence and observation period will show that the action reduced the intended risk.
QA reviews implementation and effectiveness evidence before governed closure where required.
Review the exact decision and exact revision before signing.
Approval, release, rejection, effectiveness and closure may require electronic-signature authority depending on the configured workflow.
Do not share credentials, sign for another user or use the signature step merely to move a workflow forward.
Use the readiness view to find evidence gaps—not to self-certify compliance.
BayesPeaQ maps configured quality-system domains to controlled evidence and highlights verified domains and gaps.
Controlled evidence is linked for the configured requirement. Human review remains authoritative.
Expected evidence is missing or not yet verified. Assign corrective work instead of hiding the gap.
Shows whether the controlled evidence manifest is sufficiently assembled for review.
Reconstruct the evidence trail without changing operational records.
The Inspection Room is designed as a read-only evidence-oriented view for controlled records, critical/high risks, approval metadata and evidence-pack preparation.
- Review readiness and open high-risk items.
Understand what remains unresolved before assembling an inspection narrative.
- Open supporting controlled records.
Use record IDs, revisions, signatures and linked evidence as the primary source.
- Trace the history.
Show how the event, investigation, CAPA, review and closure connect.
- Do not fill missing evidence with generated text.
If evidence is absent, the gap should remain visible and be handled through the controlled process.
Use AI to investigate faster, not to transfer authority.
BayesPeaQ Copilot is most useful when the question is bounded to a record, evidence set or quality problem.
Keep task execution and independent approval visibly separate.
Exact role names can vary by organization; the separation principle should remain clear.
Reporter / Operator
Creates factual intake, records immediate containment and provides source evidence.
Does not establish final root cause or final QA disposition.Investigator
Investigates scope, evidence, hypotheses, root cause and impact.
Routes findings for independent review.QA Reviewer
Challenges evidence, reasoning, completeness and effectiveness.
Should remain independent from the work being reviewed where policy requires.CAPA Owner
Implements assigned corrective/preventive actions and supplies implementation evidence.
Implementation completion is not automatic effectiveness approval.Approver / QA Manager
Applies configured approval or closure authority and attributable e-signature.
Reviews the exact current revision and evidence before signing.QMS Administrator
Manages users, roles, workflow configuration and system administration.
Administrative access does not itself confer QA decision authority.A simple routine keeps BayesPeaQ useful.
The QMS becomes reliable when work is captured and handed off inside the governed record rather than reconstructed later.
Review overdue, high-risk, pending-review and assigned items.
Do not wait until closure to reconstruct the record.
Make the next reviewer’s task reconstructable.
Make sure incomplete work remains visible and correctly assigned.
Common situations and the correct response.
I cannot see the action I expected.
Confirm your role, the record’s current state and assignment. BayesPeaQ exposes only server-permitted governed actions. Ask the QMS administrator to correct role/assignment issues rather than bypassing the workflow.
The record changed while I was reviewing it.
Re-open the current revision and review the changed content/evidence before approving or signing. Do not rely on an earlier revision.
The readiness score is high. Can I close the record?
No. Readiness/completeness metrics help identify evidence posture; the configured workflow, human review and required approvals remain authoritative.
Quality Copilot produced a confident answer.
Open the cited controlled records and verify the evidence, revision, limitations and applicability. Do not treat confidence of wording as proof.
The API or page cannot load.
Preserve your source work outside an unsubmitted form if necessary, refresh the current record state and retry. Do not create duplicate controlled records merely because a response was slow.
I need to find a module quickly.
Use the left navigation search or Ctrl/Cmd + K command palette in the Quality Command Center.
Open your assigned Quality work and complete one record correctly end-to-end.
That is the fastest way to learn BayesPeaQ.