What Qualio reads from MasterControl and Veeva

MasterControl

From MasterControl, Qualio reads each document's number, title, revision, status (Draft, In Review, Approved, Released or Obsolete), owner, site and dates. It reads the document file too, so the assessment works from the procedure itself.

Veeva

From Veeva Vault, Qualio reads the viewable PDF rendition and each document's name, title, type, status, description and major and minor version. It reads the current version only; earlier versions, source files and other renditions stay in the vault.

Connect a read-only user and point it at the standard

Connect a Vault user's login and URL, or a MasterControl URL and API token. Pick the framework and a rule on document fields. Save it and the first read starts; Veeva Vault is read every three hours, MasterControl every hour.

Clause-level assessment, without moving a document

Qualio assesses each clause against the procedure that answers it

Qualio attaches the documents that answer a requirement as evidence and puts a severity and a recommended fix on every gap.

A new revision is reassessed when it lands

A revision in MasterControl or Veeva arrives on the next read. Qualio reassesses the clauses it answers and flags any gap it opens.

The audit pack exports by clause

Export the pack when the auditor comes: each control and its evidence under its clause, with a report of the requirements, controls, gaps and tasks.

Read-only, in practice

Qualio reads documents only. Training records, change requests, quality events and the audit trail stay in MasterControl or Veeva. It writes nothing back, and every status, revision, field and comment stays as your team left it.

When the connection breaks

An expired password or a revoked token marks the integration Disconnected: reads pause, and a tag and a banner on the Integrations page in Qualio say so. Reconnect and the reads resume where they stopped.

Deletions

Retire a document and its new status arrives on the next read; under a Released-only rule it drops out of the framework. Delete one outright and Qualio does not notice: the copy it holds stays until you remove it.