Know who did what
Record submissions, approvals, rejections, changes, and check-ins against an identifiable person, with a server-side time record that can be reviewed later.

Quality and GxP foundations
When a critical quality decision has to be made, the records need to be there, correct, attributable, and ready to review. INQ. helps teams keep the evidence clear: who did what, when they did it, which version was used, what was approved, and what changed, in a Microsoft 365 operating environment.
INQ. provides configurable platform controls. Your organisation remains responsible for intended use, procedures, risk assessment, validation, training, and the evidence required for its operating context.
The controls behind that trust
Record submissions, approvals, rejections, changes, and check-ins against an identifiable person, with a server-side time record that can be reviewed later.
Keep document versions, effective dates, change history, and linked records clear so people can see what was approved and what is in use.
Preserve records and their history so the evidence remains attributable, legible, contemporaneous, original, accurate, and available for review.
Use Microsoft 365 identity, role and group-based permissions, and controlled administrative actions so people can only perform the work they are authorised to do.
Keep approval decisions, signatures, comments, and outcomes connected to the quality record or document they concern.
Show assigned work, status, due dates, notifications, comments, and process activity so teams can act, review, and follow up.
Applicable quality contexts
The core INQ. controls remain stable. The risks, evidence expectations, validation decisions, and operating procedures depend on your quality context and intended use.
Interpret GMP, Annex 11, Part 11, data integrity, CSV, and validation decisions.
Explore the interpretationConnect documented processes, responsibilities, corrective action, records, change, and improvement.
Explore the interpretationConsider medical-device quality processes, risk, training, records, corrective action, and controlled change.
Explore the interpretationExplore food-quality procedures, traceability, corrective action, supplier evidence, and customer requirements.
Explore the interpretationWhy these controls matter
An audit trail is useful because it shows the history of a record, not simply because a system has a log. Version history prevents people from working from an obsolete document. Attributable approvals show who accepted a decision. Controlled access reduces the chance that the wrong person changes the wrong record. Together, these controls support evidence that is trustworthy and usable when a team needs to investigate, review, or demonstrate how work was completed.
Next step
Bring your quality processes, evidence expectations, and Microsoft 365 context to a focused product conversation.