How to govern Perplexity
AI research and answers with cited sources, and the checks that keep those citations honest.
Perplexity · Reviewed when the vendor ships a capability change or a customer declares the tool
How Perplexity is used
We see three common ways businesses use Perplexity, and we govern each one on its own terms. If your team uses it differently, that is fine: you describe the use in your own words and Certrak works out the governance from what it actually does.
General productivity assistance
Consequence to people: LowDrafting, summarising, brainstorming, internal Q&A - day-to-day help with internal work
Document analysis and review
Consequence to people: LowReviewing contracts, reports, or technical documents
Internal data analysis and insights
Consequence to people: LowAnalysing business data, surfacing insights, building dashboards
Governing Perplexity in practice
- Name one person who owns Perplexity in your business. Governance starts with a name.
- Write down what Perplexity is used for. Certrak recognises 3 common uses: General productivity assistance, Document analysis and review and Internal data analysis and insights. Yours may differ; write down yours.
- Decide what Perplexity may and may not be given. Internal business information is in scope, so name what stays out.
- Agree that a person reviews every output before it is used, and name who.
- Look at this again once a year, and sooner on any of these: industry incidents and vendor model updates.