Transform fragmented PR documents into a structured communications review
PugID analyses Public Relations (PR) documents stored in Google Drive or SharePoint. A team member selects a PR-specific question. PugID locates the relevant files and delivers a structured result drawn from those documents. The PR team can then compare the result against source files and governed media-monitoring, contact-management, publishing, event, finance or approval systems before using it in a communications review or decision.
Before: gather coverage, messages and actions manually
A PR review may rely on media-monitoring reports, press plans, embargo calendars, briefing books, message frameworks, interview feedback, event recaps, crisis playbooks and reputation-risk registers. When these documents are spread across different folders, reviewers first need to establish the market, audience, outlet, period, owner, status and approved version.
Select the PR question you need to review
The supplied catalogue includes focused questions for coverage, press, spokespersons, crisis readiness, messages, events and reputation risk.
Progress from approved folders to a reviewable result

Connect approved folders.
Link the Google Drive or SharePoint locations that hold the documents authorised for the PR review.
Pick one PR question.
Select the prompt that fits the market, audience, channel, reporting period and review task.
Review the structured result.
Compare it against source documents and governed systems, resolve conflicts and obtain the required communications, executive, legal, privacy or brand approval before use.
After: review a single structured result against authoritative sources
PugID operates at that document layer. It uses a chosen PR question to identify relevant material in connected Google Drive or SharePoint folders and produce a structured result. It does not replace media-monitoring, social-listening, contact-management, publishing, event, finance, approval, legal-review or live business-intelligence systems. Current coverage, contacts, sentiment, budgets, approvals and published statements stay in governed systems.
Maintain visibility of source authority and publication status
Document analysis can assist a review, but coverage, contacts, embargoes, messages and reputation signals shift. Log the market, audience, outlet, channel, reporting period, extraction date, source owner and approval status. Confirm material findings in the authoritative monitoring or publishing system before taking action.
PugID does not monitor live media, contact journalists, publish statements, enforce embargoes, approve messages, determine sentiment, calculate authoritative share of voice or manage a crisis. If documents conflict, examine their scope, dates, owners and approval status. A structured result is review material, not a communications decision.
Keep confidential communications and data handling within scope
PugID states that connections are encrypted, credentials are not stored, and documents and results are not kept permanently. It also states that temporary analysis data is automatically deleted after eight hours.
Prior to connecting embargoed materials, unreleased statements, journalist or influencer contact data, crisis plans, executive briefings or legal-review notes, verify need-to-know access, privacy requirements, contractual terms, processing details and internal policies. Use approved, minimised test data. Do not put passwords, API keys, private keys, tokens or other secrets in connected documents.
Pilot one bounded PR review
Start with a bounded task such as a closed-period media-coverage summary, an approved briefing-book assembly or a response-playbook review. Connect only approved folders, set the market, audience and date range, compare the result against governed systems and record exceptions before widening the evaluation.
