All use cases

Prepare a report from Veeva quality records.

Use permitted Veeva records and document versions to draft a sourced quality report in Seal, with query scope and missing evidence visible.

Book a demo
Illustration of a seal examining a circled change in a trace alongside run, sample and procedure records.

You: Prepare a quality report from the permitted Veeva records. Show the overdue work and the procedure versions involved.

neil

VV-311-A is an open investigation referencing VV-SOP-17 v04. VV-311-B has a passed due date with no completion returned. The query is limited to the supplied product/site scope, and attachments are outside the available permission scope.

A report linked to permitted sources
A report linked to permitted sources. Veeva Query scope, VV-311-A Investigation, VV-311-B Follow-up. Example records.VeevaQuery scopeVV-311-AInvestigationVV-311-BFollow-up

You: Can the report say there is no completion evidence?

neil

It should say no completion was returned within this query, not that none exists anywhere. I would retain the product/site filter and attachment-access boundary, then request the missing evidence through an authorised route. I cannot inspect inaccessible attachments or substitute the current SOP for the recorded v04 reference.

You: Write this up for review, with the sources and the follow-up work we need.

neil

Here is the draft. I have kept the supported finding separate from the open questions, and prepared the evidence requests for the responsible roles.

Veeva product/site quality reportReview draft · source evidence and assessment

Veeva product/site quality report

The query returns selected product-and-site records, including an overdue action, but its permissions exclude attachments. The defensible statement is that completion evidence was not returned—not that none exists in Veeva. Retain query scope and source references in the report. Request permitted access or an authorised evidence export before deciding whether the action's recorded status reflects the completed work.

Source evidence and search scope

VV-311-A (Deviation record); VV-311-B (Linked action); QUERY-311 (Query scope)

VV-311-A / Deviation record

Recorded evidence
Investigation open; procedure VV-SOP-17 v04 referenced

VV-311-B / Linked action

Recorded evidence
Due date passed; completion evidence not returned

QUERY-311 / Query scope

Recorded evidence
Selected product and site only; attachments outside permission scope
Inputs needed for your own records
  • Configured Veeva connection and permitted query scope
  • Record identifiers, reporting period and report question
  • Relevant documents, versions and linked action records

The operator authorises configured actions and reviews the report. Connection scope may limit completeness; drafting in Seal does not update or approve Veeva records.

Fictional source snapshots. No live query, assignment or approval.

Follow-up work and evidence requests2 proposed tasks · not assigned

Evidence to request

Confirm the overdue item's current state
Quality record owner
Provide the current VV-311-B completion/status evidence and explain any difference from the supplied query snapshot.
Verify scope and source versions
Report reviewer
Review the product/site filters, selected records and VV-SOP-17 v04 reference. Obtain permitted attachment evidence before making claims that depend on it.
Example conversation · prepared replies

See this job with your team.

Tell us how your team handles this job today. We’ll walk through the analysis, supporting evidence and review steps in a demo.

Book a demo
What to bring for this job
  • Configured Veeva connection and permitted query scope
  • Record identifiers, reporting period and report question
  • Relevant documents, versions and linked action records

Source access, permissions and permitted actions are agreed for your environment.

Source excerpt

VV-311-A

Deviation record

Recorded evidence
Investigation open; procedure VV-SOP-17 v04 referenced

Selected fictional record, not a live source-system view.