Assess earnings, guidance and investor materials with disclosure boundaries preserved
PugID examines Investor Relations documents held in Google Drive or SharePoint. A team member selects an investor-relations-specific question. PugID pinpoints the relevant files and delivers a structured result drawn from those documents. The Investor Relations team can then check the result against source files and governed finance, disclosure, filing, market-data, shareholder, approval or publishing systems before using it in an investor communication or decision.
Bring the evidence for an investor review to light
An investor review may rely on approved financial materials, earnings scripts, guidance records, analyst notes, shareholder questions, disclosure logs, conference calendars, board-approved language and meeting feedback. Before reaching a conclusion, the reviewer must confirm the reporting period, currency, unit, metric definition, segment scope, source owner, version, approval status and publication or filing date.
PugID operates at the document layer. It applies a selected Investor Relations question to surface relevant material in connected Google Drive or SharePoint folders and return a structured result. It does not replace finance or consolidation systems, disclosure management, regulatory filing tools, market-data services, shareholder registers, investor CRM, legal review, approval workflows, publishing systems or live business intelligence. Official figures, filings, disclosures, guidance, approvals and published statements stay in governed systems and with accountable professionals.
Select the Investor Relations question you need to review
The supplied catalogue contains targeted questions for earnings, guidance, analysts, shareholders, disclosures, calendars and investor feedback.
Go from folders to a reviewable result

Connect approved folders.
Link the Google Drive or SharePoint locations that hold the Investor Relations documents relevant to the review.
Select one Investor Relations question.
Pick the prompt that fits the reporting period, audience and governed source set.
Review the structured result.
Compare it against authoritative finance, filing, market-data, shareholder and approval records; resolve conflicts and get accountable review prior to use.
Establish the control model before testing
A controlled trial can gauge retrieval effort, source coverage, exceptions surfaced, review acceptance and actions assigned. Log the document set, reporting period, currency, units, metric definitions, segment scope, source owners, version status, confidentiality, review owner and acceptance criteria before testing. These are suggested assessment measures, not promised financial, investor or market outcomes.
A polished summary can still be incorrect when it blends reporting periods, currencies, adjusted and unadjusted metrics, internal forecasts, unapproved language or superseded filings. If files conflict, pause and examine the governing source. PugID does not compute authoritative results or valuation, issue guidance, determine materiality, make disclosure decisions, file documents, contact investors or analysts, publish statements, enforce quiet or blackout periods, approve safe-harbour language, or offer investment, legal or accounting advice.
Retain market-sensitive information and access controls within scope
PugID states that connections are encrypted, credentials are not stored, and documents and results are not kept permanently. It further states that temporary analysis data is removed automatically after eight hours.
Earnings drafts, guidance, internal forecasts, consensus comparisons, shareholder information, material disclosures, unpublished KPIs, quiet-period or blackout materials and investor meeting notes may be highly confidential or market-sensitive. Before connecting them, verify need-to-know access, insider-information controls, classification, privacy, legal and finance approval, processing terms and retention requirements. Use approved, minimised test data. Do not include passwords, API keys, private keys, tokens or other secrets.
Run one bounded Investor Relations review
Start with a controlled task such as an earnings-preparation pack, guidance-versus-results review or Investor Relations calendar. Connect only approved folders, set the reporting period and authoritative sources, compare the result with governed systems and log every exception before widening the evaluation.
