Review data quality, metric definitions and analytics evidence in one place
PugID examines Data & Analytics documents kept in Google Drive or SharePoint. A team member picks an analytics-specific question. PugID locates the relevant files and delivers a structured result drawn from those documents. The data team can then compare the result against source files and governed catalogue, warehouse, BI, lineage, access, pipeline or model systems before applying it in a review or decision.
Examine the documents behind analytics decisions
An analytics review may rely on data dictionaries, catalogue exports, metric definitions, dashboard inventories, quality reports, pipeline summaries, experiment readouts, model cards, access evidence and lineage documentation. When these documents are scattered across different folders, reviewers must first determine the dataset, metric, owner, environment, reporting period and approved version.
PugID operates at that document layer. It applies a selected analytics question to locate relevant material in connected Google Drive or SharePoint folders and return a structured result. It does not replace data catalogues, warehouses, lakehouses, BI, lineage, orchestration, access-governance, model-registry, monitoring or live business-intelligence systems. Current values, permissions, pipeline state and approved definitions stay in governed systems.
Select the analytics question you need to examine
The supplied catalogue contains focused questions for catalogues, dashboards, metric definitions, quality, lineage, access and models.
Move from approved folders to a result you can review
Connect approved folders.
Link the Google Drive or SharePoint locations that hold the documents pertinent to the analytics review.
Choose one analytics question.
Pick the prompt that matches the dataset, metric, dashboard, model, environment and reporting period.
Review the structured result.
Compare it against source documents and governed systems, resolve conflicts and obtain the required operational approval before use.
Keep source authority and data freshness in view
Document analysis can assist a review, but a summary may already be outdated when datasets, pipelines, permissions, dashboards or models change. Note the dataset or metric, environment, reporting period, refresh time, source owner and acceptance criteria. Confirm material findings in the authoritative analytics system before taking action.
PugID does not run queries, change pipelines, grant access, update dashboards, retrain models, certify PII status or assert that a metric is correct. If two documents disagree, check their definitions, timestamps, owners and approval status. A clean table can still conceal a disputed denominator; the governed definition stays the anchor.
Keep source access and data handling within scope
PugID states that connections are encrypted, credentials are not stored, and documents and results are not retained permanently. It also notes that temporary analysis data is deleted automatically after eight hours.
Before connecting data dictionaries, access evidence, model documentation, experiment readouts or privacy material, verify folder permissions, contractual terms, processing details and internal policies. Use approved, minimised test data. Do not put raw personal data, passwords, API keys, private keys, tokens or other secrets in connected documents.
Run one bounded analytics review
Start with a controlled task such as metric-definition conflicts, dashboard inventory or data-quality issues. Connect only approved folders, define the dataset, environment and date range, compare the result with governed systems and record exceptions before broadening the evaluation.