# Pavleur

> Pavleur is an AI meeting copilot: it captures your calls — transcript, requests, questions — so nothing said in a meeting is lost. Recordings live on your machine or your own Google Drive, never on our servers.

## Pages

- [Home](https://pavleur.com/): what Pavleur does and how it works
- [Who it's for](https://pavleur.com/for): pain-first pages per role and platform
- [Pavleur for In-Person Meetings](https://pavleur.com/for/in-person-meetings): Conference rooms have no recording bot. The client visit, the whiteboard session — Pavleur captures them from the laptop already in the room.
- [Pavleur for Microsoft Teams](https://pavleur.com/for/microsoft-teams): Five Teams calls a day means five chances to drop a commitment. Pavleur turns every Teams meeting into a searchable record kept on your machine.
- [Pavleur for Zoom Meetings](https://pavleur.com/for/zoom): The question you missed on Zoom becomes the deadline you miss next week. Pavleur captures every Zoom call — transcript, requests, answers — on your machine.
- [Pavleur for Consultants](https://pavleur.com/for/consultants): Back-to-back client calls, every one billable. Pavleur captures every requirement and shared screen, then writes the recap that seeds your deliverable.
- [Pavleur for Customer Success](https://pavleur.com/for/customer-success): QBRs, onboarding, renewals all day. Pavleur captures every commitment and shared screen, then writes the recap so no account detail slips.
- [Pavleur for Engineering Managers](https://pavleur.com/for/engineering-managers): Stop taking notes in standups and 1:1s so you can actually manage. Pavleur captures every decision, action item, and shared screen — then writes the recap.
- [Pavleur for Founders](https://pavleur.com/for/founders): Investor calls, discovery, hiring, team syncs — all in one day. Pavleur captures every commitment and shared screen, then writes the recap so nothing slips.
- [Pavleur for Product Managers](https://pavleur.com/for/product-managers): Run discovery, roadmap reviews, and standups without losing a requirement. Pavleur captures every decision and shared screen, then writes the recap.
- [Pavleur for Remote Teams](https://pavleur.com/for/remote-teams): When the meeting is the only room you share, losing it is expensive. Pavleur captures every call and shared screen, then writes the recap the team relies on.
- [Pavleur for Sales Teams](https://pavleur.com/for/sales-teams): Stay present on the call, not in your notes. Pavleur captures every discovery detail, the demo screen, and the next steps — then writes the follow-up recap.

## Comparisons

- [Pavleur vs Granola — Meeting Copilots Compared](https://pavleur.com/compare/pavleur-vs-granola.md): How Pavleur compares to Granola for botless meeting capture: full visual records and local storage versus polished notes, mobile capture, and calendar briefs.
- [Pavleur vs Read.ai — Meeting Copilots Compared](https://pavleur.com/compare/pavleur-vs-read-ai.md): How Pavleur compares to Read.ai: botless local capture and a full visual record versus bot-based meeting coaching and engagement analytics.
- [Pavleur Alternatives: Honest Meeting-Copilot Options](https://pavleur.com/compare/pavleur-alternatives.md): Looking at alternatives to Pavleur? A fair rundown of the meeting-assistant field and who each approach actually fits.
- [Pavleur vs Fathom — Meeting Copilot Compared](https://pavleur.com/compare/pavleur-vs-fathom.md): How Pavleur compares to Fathom for meeting notes: privacy-first local capture, video and screenshots, and automatic post-meeting reports.
- [Pavleur vs Fellow — Meeting Copilot Compared](https://pavleur.com/compare/pavleur-vs-fellow.md): How Pavleur compares to Fellow for meeting notes and agendas: privacy-first local capture, video and screenshots, and automatic post-meeting reports.
- [Pavleur vs Fireflies — Meeting Copilot Compared](https://pavleur.com/compare/pavleur-vs-fireflies.md): How Pavleur compares to Fireflies for meeting notes: privacy-first local capture, video and screenshots, and automatic post-meeting reports.
- [Pavleur vs Otter — Meeting Copilot Compared](https://pavleur.com/compare/pavleur-vs-otter.md): How Pavleur compares to Otter for meeting transcription: privacy-first local capture, video and screenshots, and automatic post-meeting reports.
- [Pavleur vs tl;dv — Meeting Copilot Compared](https://pavleur.com/compare/pavleur-vs-tldv.md): How Pavleur compares to tl;dv for meeting recording: privacy-first local capture, video and screenshots, and automatic post-meeting reports.

## Meeting templates

- [Customer Discovery Call Template for Better Product Interviews](https://pavleur.com/meeting-templates/customer-discovery-call-template): A practical customer discovery agenda for testing a hypothesis, walking through the current workflow, probing willingness to pay, and preserving exact evidence.
- [Quarterly Business Review Template for Customer Success Teams](https://pavleur.com/meeting-templates/quarterly-business-review-template): A practical QBR agenda for connecting usage to value, reviewing goals and outcomes, discussing roadmap and risk, finding expansion opportunities, and assigning next steps.
- [Sales Call Notes Template: Discovery to Close](https://pavleur.com/meeting-templates/sales-call-notes-template): A structured sales call notes template for capturing buyer context, needs, objections, pricing, competitors, and next steps from discovery through close.
- [All-Hands Meeting Agenda Template That People Actually Watch](https://pavleur.com/meeting-templates/all-hands-meeting-agenda): A structured all-hands agenda that earns attendance by putting the topics people actually need on screen first and cutting everything that should have been an email.
- [Board Meeting Minutes Template for Early-Stage Companies](https://pavleur.com/meeting-templates/board-meeting-minutes-template): A structured board meeting agenda and minutes format that captures what boards actually need — decisions and rationale — not a transcript of every slide.
- [Daily Standup Agenda Template (That Engineers Actually Use)](https://pavleur.com/meeting-templates/daily-standup-agenda): A 10-minute daily standup agenda for engineering teams, with the exact prompts and what an AI copilot fills into the recap.
- [Engineering Postmortem Template (Blameless, Actionable)](https://pavleur.com/meeting-templates/engineering-postmortem-template): A structured incident postmortem template with six sections and the ordering mistake most teams make that turns a learning exercise into a blame session before it starts.
- [One-on-One Meeting Template for Engineers and EMs](https://pavleur.com/meeting-templates/one-on-one-meeting-template): A structured 1:1 agenda covering the five sections that make the meeting useful, the one section that always gets cut, and why 1:1 commitments are the hardest thing to capture.
- [Project Kickoff Meeting Agenda for Engineering Teams](https://pavleur.com/meeting-templates/project-kickoff-agenda): A structured project kickoff agenda with six sections and the one question most teams don't answer in kickoff that comes back to bite them at the halfway point.
- [Skip-Level Meeting Template for Engineering Leaders](https://pavleur.com/meeting-templates/skip-level-meeting-template): A structured skip-level agenda covering what senior leaders actually need to hear, and the listening mistake that turns skip-levels into a morale-monitoring exercise with no output.
- [Sprint Planning Agenda Template for Engineering Teams](https://pavleur.com/meeting-templates/sprint-planning-agenda): A structured sprint planning agenda with five sections, hard time boxes, and the capacity-before-commitment step that prevents overloaded sprints.
- [Sprint Retrospective Template for Engineering Teams](https://pavleur.com/meeting-templates/sprint-retrospective-template): A structured sprint retrospective agenda with five sections, hard time boxes, and the opening step most teams skip that explains why nothing ever changes.
- [Weekly Team Sync Agenda That Earns Its Slot on the Calendar](https://pavleur.com/meeting-templates/weekly-team-sync-agenda): A structured weekly team sync with four sections and the one design question most teams never ask: what does this meeting do that standup and Slack don't?

## Guides

- [MCP and Meeting Data: What Agents Could Do With Meetings](https://pavleur.com/guides/mcp-meeting-agents): What it means to point AI agents at meeting data (transcripts, decisions, requests) via MCP, what that unlocks, and what to watch on privacy.
- [Building an AI Copilot Habit: A 30-Day Plan](https://pavleur.com/guides/building-an-ai-copilot-habit-30-day-plan): A week-by-week plan to integrate an AI meeting copilot into your workflow as an engineering manager, PM, or staff IC — without the notification fatigue, transcript graveyard, and over-reliance that kill most adoption attempts.
- [How to Run an AI-Augmented Standup (Without Being Annoying About It)](https://pavleur.com/guides/how-to-run-an-ai-augmented-standup): A field-tested guide to adding AI to your daily standup in a way that helps the team rather than performing innovation. Includes an agenda template and the failure modes you'll hit in the first month.
- [The Complete Guide to Meeting Recap Quality (For PMs and EMs)](https://pavleur.com/guides/the-complete-guide-to-meeting-recap-quality): A serious treatment of what makes a meeting recap useful versus useless, with a five-part structure, examples of good and bad recaps, and a practical workflow for editing AI-generated output.
- [The Engineering Team's Guide to Meeting Productivity in 2026](https://pavleur.com/guides/the-engineering-teams-guide-to-meeting-productivity-in-2026): A practical playbook for engineering managers and ICs who want fewer meetings, better outcomes, and a healthier ratio of synchronous to asynchronous work.

## Blog

- [Never Miss an Action Item Again](https://pavleur.com/blog/never-miss-action-items.md): The request that sinks you is never in the agenda. It is said once, mid-call, while you are typing. Here is the system that catches it.
- [Surviving a PIP: A Concrete 30-Day Plan](https://pavleur.com/blog/surviving-a-pip.md): A performance improvement plan is survivable. What kills people is vagueness: about expectations, about evidence, about what was actually said.
- [From transcript to product spec: a 20-minute workflow](https://pavleur.com/blog/from-transcript-to-product-spec.md): You had the conversation. The decision is there in the transcript. Turning it into a spec used to take half a day. Here is the 20-minute version.
- [How privacy works when your AI copilot listens to every meeting](https://pavleur.com/blog/how-privacy-works-with-an-ai-copilot.md): Putting an AI listener in every meeting raises real privacy questions. Here is the honest version of how a meeting copilot should handle data — and where most tools fall short.
- [Otter vs Read.ai vs Pavleur: an honest breakdown for engineering teams](https://pavleur.com/blog/otter-vs-read-vs-pavleur.md): Three meeting copilots, three different bets on what matters. Here's how they actually compare when an engineering team uses them daily for a quarter.
- [Pavleur for engineering managers: the underrated workflow](https://pavleur.com/blog/pavleur-for-engineering-managers.md): Most meeting copilot marketing targets ICs. The real power user is the engineering manager — and the workflow looks different than you’d expect.
- [Real-time AI assist in meetings: useful tool or distraction?](https://pavleur.com/blog/real-time-ai-assist-in-meetings.md): A live AI suggestion panel during a meeting sounds either revolutionary or maddening. We ran it for a quarter across a dozen meeting types. The honest answer is: it depends.
- [Searching 6 weeks of meetings to find one decision: why we built it](https://pavleur.com/blog/searching-6-weeks-of-meetings.md): A product manager needed to find the meeting where we decided to deprecate the v1 API. It took her two days. That two days is why we built meeting search.
- [Standup notes that don't suck: a 90-day experiment](https://pavleur.com/blog/standup-notes-that-dont-suck.md): We ran a controlled experiment across two engineering teams: one wrote standup notes by hand, one had them auto-generated. The results were uncomfortable.
- [The 4-minute standup recap that became our team's most-read document](https://pavleur.com/blog/the-4-minute-standup-recap.md): Our standup recap started as a throwaway summary at the bottom of a meeting transcript. Three months later, it had more readers than any wiki page we owned.
- [The case against meeting-free Fridays (and what to do instead)](https://pavleur.com/blog/the-case-against-meeting-free-fridays.md): Meeting-free Fridays sound great. They don't actually reduce meeting load — they compress it. Here's the data, and what to do instead.
- [The meeting tax: how much time engineers actually lose to bad recaps](https://pavleur.com/blog/the-meeting-tax.md): A simple model for the cost of bad meeting hygiene on a 50-person engineering org. Run it on your own numbers — the hidden cost is usually bigger than the obvious one.
- [What to do with meeting transcripts (besides letting them rot in a folder)](https://pavleur.com/blog/what-to-do-with-meeting-transcripts.md): Most teams generate meeting transcripts and then do nothing with them. The transcripts pile up, untouched, like a graveyard of attention. There are better options.
- [Why we use a copilot for every 1:1 (and what it actually catches)](https://pavleur.com/blog/why-we-use-a-copilot-for-every-1-1.md): A meeting copilot in your 1:1s sounds invasive until you see what it catches: missed follow-ups, repeated themes across reports, and the questions you forgot to ask.

## Glossary

- [Glossary index](https://pavleur.com/glossary): 40 meeting and workplace terms, defined
- [Action Item](https://pavleur.com/glossary/action-item): A specific, owned task that emerges from a meeting and requires follow-up work afterwards. A well-formed action item names a single owner, describes the outcome (not the activity), and includes a due date. AI meeting copilots extract action items by listening for commitment language — "I'll send that over by Friday," "Can you ping the design team?" — and surface them in the post-call recap so nothing is lost between the call and the follow-up email. Action items differ from decisions (which record what was agreed) and from open questions (which capture what's still unresolved). The most common failure mode is action items with no owner, or owners with no due date — both of which guarantee the item will resurface in next week's meeting with no progress.
- [Active Listening](https://pavleur.com/glossary/active-listening): A communication discipline in which the listener focuses fully on the speaker, signals understanding through verbal and non-verbal cues, and reflects back what they heard before responding. In meetings, active listening looks like: paraphrasing the speaker's point before pushing back, asking clarifying questions instead of jumping to solutions, and resisting the urge to draft your reply while the other person is still talking. For non-native English speakers, active listening also includes asking the speaker to slow down or rephrase when needed — a habit many professionals avoid because they fear losing credibility, but which actually signals confidence and reduces costly misunderstandings. AI meeting copilots support active listening by handling the cognitive load of note-taking, freeing participants to engage with the conversation in real time.
- [All-Hands](https://pavleur.com/glossary/all-hands): A company-wide meeting at which leadership shares strategic updates, financial performance, hiring news, and major decisions with all employees. All-hands meetings typically run weekly, biweekly, or monthly depending on company size, and reserve a portion for live Q&A from employees. The format is part-broadcast, part-dialogue: leadership speaks to a passive audience for most of the call, then opens the floor. Distributed and async-first teams often pre-record the broadcast portion and reserve the live time entirely for questions, which respects time zones and lets employees watch on their own schedule. AI meeting copilots are particularly useful here: they transcribe the call, generate a recap that can be shared with absent employees, and capture the Q&A in searchable form so anyone can revisit specific answers later.
- [Async-First](https://pavleur.com/glossary/async-first): An operating principle where written, asynchronous communication is the default mode of work, and synchronous meetings are the exception reserved for high-bandwidth conversations (debates, brainstorming, urgent decisions). Async-first teams write more than they talk: they document decisions in shared docs, raise issues in long-form threads, and reserve real-time calls for moments when written words genuinely won't suffice. The benefit is time-zone independence, deeper thinking, and a permanent record of why decisions were made. The risk is over-correcting into excessive documentation overhead. Meeting copilots help bridge the two modes: they convert the meetings you do hold into searchable async artifacts (transcripts, recaps, action items) that the rest of the team can consume on their own schedule rather than having to be in the room.
- [Asynchronous Communication](https://pavleur.com/glossary/asynchronous-communication): Any communication where the sender and receiver are not engaged at the same time — emails, Slack threads, Loom videos, GitHub issues, recorded standup updates. Async communication respects the receiver's time and attention by letting them respond when they have the bandwidth to think clearly, rather than interrupting their flow. Done well, it reduces meeting load, improves decision quality (because thoughts are written down), and accommodates global teams. Done poorly, it produces endless threads with no resolution and leaves urgent items buried. Effective async communication requires explicit norms: a Service Level Agreement on response times, a clear escalation path for urgent items, and the discipline to write self-contained messages with full context rather than "can we hop on a call?"
- [Audit Log](https://pavleur.com/glossary/audit-log): An immutable, timestamped record of every action taken in a system — who accessed what, when, and from where. Audit logs are foundational to security and compliance: they let auditors verify that access controls work, let security teams investigate incidents after the fact, and demonstrate to regulators that the organization can answer "who did this and when." For a meeting copilot, the audit log typically records transcript access (every time a user views or exports a transcript), retention events (when transcripts were deleted), permission changes, and admin actions. SOC 2 and HIPAA both require audit logs with specific retention periods and tamper-evidence. The log itself must be append-only — a system that lets users edit or delete audit entries is, by definition, no longer an audit log.
- [BAA (Business Associate Agreement)](https://pavleur.com/glossary/baa): A contract required under HIPAA whenever a covered entity (such as a hospital or health insurer) shares Protected Health Information with a third-party vendor. The BAA legally binds the vendor to handle PHI according to HIPAA's privacy and security rules — including breach notification timelines, employee training, encryption requirements, and limits on subcontractor access. For meeting copilots used in healthcare, signing a BAA is typically the gating requirement before any clinical conversation can be recorded or transcribed. Vendors who can't or won't sign one are effectively unusable in healthcare settings. Note that a BAA is not the same as being "HIPAA compliant" — there is no formal HIPAA certification, only attestation of controls — but the BAA is the contractual mechanism that makes a vendor accountable.
- [Code-Switching](https://pavleur.com/glossary/code-switching): The practice of shifting between different languages, dialects, registers, or communication styles depending on the audience. In multinational workplaces, code-switching often means moving between casual English with peers, formal English in customer calls, technical English in engineering reviews, and one's native language at home — sometimes all in the same day. The cognitive load is real and often invisible: non-native English speakers report exhaustion after a day of meetings that native speakers don't experience. Awareness of code-switching helps managers run inclusive meetings: slow down for non-native speakers, share agendas in writing ahead of time, and use AI transcription so participants can re-read what was said rather than relying on real-time comprehension under pressure.
- [Context Window](https://pavleur.com/glossary/context-window): The maximum amount of text an LLM can process in a single request, measured in tokens (roughly, words plus punctuation). A model with a 200,000-token context window can consider about 150,000 English words at once — enough to fit an entire meeting transcript, the participants' calendars, and the team's project documentation in a single call. Larger context windows let meeting copilots ground their suggestions in more material: not just "what was said in the last five minutes" but "what was said five meetings ago and what's in the linked spec." The trade-off is latency and cost: bigger contexts take longer to process and consume more tokens per request. Modern copilots increasingly rely on RAG to avoid stuffing irrelevant context into the window when only a small slice actually matters.
- [Data Residency](https://pavleur.com/glossary/data-residency): The requirement that customer data be stored and processed within a specific geographic jurisdiction. EU customers under GDPR often require data to stay within the EU; Canadian healthcare systems often require data to stay within Canada; some defense customers require data to stay within the US. Data residency is not the same as data sovereignty (which adds requirements about whose laws apply) but the two are often confused. For meeting copilots, data residency typically requires running infrastructure in the customer's region (EU-hosted clusters for EU customers), keeping transcripts and recordings in regional object storage, and ensuring that the model inference itself happens within the region — which can be challenging when the LLM provider only has US-region endpoints.
- [Data Retention](https://pavleur.com/glossary/data-retention): The policy that defines how long an organization keeps customer data before deleting it. Retention policies balance regulatory requirements (some industries mandate minimum retention of audit logs and communication records) against privacy principles (GDPR's data minimization says keep no more than necessary). For meeting copilots, retention typically covers raw audio recordings (often deleted within days), transcripts (often kept months to years for searchability), generated recaps (kept indefinitely as user-owned artifacts), and embeddings (kept as long as the underlying transcript). A good retention policy specifies the trigger (date created, last accessed, user-requested deletion), the holding period, and what "deletion" actually means — soft delete that can be restored, or hard cryptographic erasure.
- [Decision Log](https://pavleur.com/glossary/decision-log): A persistent, append-only record of decisions made in meetings, with enough context that someone joining six months later can understand both what was decided and why. A good decision log entry captures: the decision itself in one sentence, the alternatives that were considered, the trade-offs that were discussed, the people involved, and the date. Decision logs are the institutional memory of a team — without one, teams relitigate the same trade-offs every few months as new members join. AI meeting copilots extract decisions from transcripts by detecting phrases like "let's go with," "we're decided," "final call is." The output of every meeting where any non-trivial choice was made should include a decision log entry in the recap.
- [Diarization](https://pavleur.com/glossary/diarization): The process of segmenting an audio recording by speaker — answering the question "who spoke when?" Diarization is what lets a meeting transcript show "Alice: Let's ship it. Bob: Not yet." rather than an undifferentiated stream of words. Good diarization is harder than it looks: speakers interrupt each other, audio quality varies across mic setups, and accents and prosody throw off the speaker-embedding models that drive most diarization systems. State-of-the-art systems combine acoustic embeddings (what does this voice sound like) with speech-recognition signals to assign each utterance to a speaker label. Once labels are stable across the meeting, they can be mapped to real names using the participant list from the calendar invite or a one-time enrollment voice sample.
- [Distributed Team](https://pavleur.com/glossary/distributed-team): A team whose members work from different physical locations, time zones, or both. Distributed is broader than "remote" — a team can be remote (all working from home) but still co-located in one city, while a distributed team spans multiple regions even if some members share an office. Distributed teams require deliberate practices: overlapping working-hours windows for sync work, written-first communication, recorded meetings for those who can't attend live, and explicit norms about response times. Meeting copilots are core infrastructure for distributed teams because they convert the synchronous meetings (which by definition exclude some time zones) into searchable async artifacts that everyone can consume on their own schedule.
- [Embeddings](https://pavleur.com/glossary/embeddings): A numerical representation of text (or audio, or images) in a high-dimensional vector space, such that semantically similar inputs end up close together in the space. The sentence "let's reschedule" and "can we move this?" have very different surface words but produce embeddings that are close neighbors. Embeddings power semantic search in meeting copilots: instead of asking users to remember the exact words they used in a meeting, you embed both the query and every transcript chunk, then return the chunks whose embeddings are closest to the query's. Embeddings are also the substrate of RAG — the retrieval step is typically a vector-similarity search over an embedding index. Modern embeddings (1024 to 3072 dimensions) capture nuance well enough to distinguish related-but-distinct concepts.
- [Encryption at Rest](https://pavleur.com/glossary/encryption-at-rest): The practice of storing data in encrypted form on disk, so that an attacker who gains physical access to the storage medium (or, more commonly, a cloud-storage misconfiguration) cannot read the data without the encryption keys. For a meeting copilot, encryption at rest typically covers raw audio files, transcripts in the database, and generated recaps. Industry-standard practice is AES-256 with keys managed by a dedicated Key Management Service (AWS KMS, Google Cloud KMS) and rotated on a regular schedule. Encryption at rest is distinct from encryption in transit (TLS for data moving over the network) and from application-level encryption (where the application encrypts each record with a user-specific key before the database ever sees it). SOC 2 and most enterprise security questionnaires consider encryption at rest a baseline requirement.
- [Filler Words](https://pavleur.com/glossary/filler-words): The "um," "uh," "like," "you know," and "sort of" that appear when speakers are thinking out loud or buying time. Filler words are universal across languages and speakers — even professional broadcasters use them, just less audibly — and they serve a real purpose: they signal "I'm still talking, don't interrupt" while the speaker assembles the next sentence. In moderation, fillers are invisible. In excess, they undermine perceived confidence and authority. Coaching guidance for executive presence often focuses on replacing fillers with deliberate pauses, which feel uncomfortable to the speaker but signal command of the material to the listener. Meeting copilots can surface filler-word frequency in post-call analytics, giving speakers a private feedback loop without the awkwardness of asking a colleague to tally their "ums."
- [GDPR Consent](https://pavleur.com/glossary/gdpr-consent): Under the EU General Data Protection Regulation, consent to process personal data must be freely given, specific, informed, and unambiguous, and the user must be able to withdraw it as easily as they gave it. For meeting copilots operating in the EU, GDPR consent typically requires: a clear disclosure that the meeting will be recorded and transcribed, the identity of the data controller, the legal basis for processing, the retention period, the user's rights (access, deletion, portability), and an explicit opt-in action — pre-checked boxes don't count. Implicit consent ("by attending this meeting, you consent...") is on shaky legal ground; best practice is an explicit join-time prompt that participants must actively dismiss to enter the call.
- [Grounding](https://pavleur.com/glossary/grounding): The practice of giving an LLM access to verified source material at inference time, so its outputs cite specific evidence rather than relying on parametric knowledge that may be wrong, stale, or fabricated. In meeting copilots, grounding typically means: when the user asks "what did Alice commit to in the standup?" the system retrieves the relevant transcript chunks (via RAG), feeds them into the prompt, and instructs the model to answer only from the provided context — with citations back to the timestamp. Grounding is the primary defense against hallucination: a grounded model that doesn't find supporting evidence should say "I don't see Alice committing to anything in the available transcripts" rather than inventing a plausible-sounding commitment.
- [Hallucination](https://pavleur.com/glossary/hallucination): A failure mode where an LLM generates output that is fluent and confident but factually wrong or entirely fabricated. In meeting copilots, hallucinations show up as: invented action items that nobody committed to, misattributed quotes, summaries that contradict the transcript, and made-up participant names. Hallucinations are particularly dangerous in meeting contexts because the output is plausible and the consumer often won't catch the error — a recap that says "Alice agreed to ship by Friday" looks authoritative even if Alice never said it. Defenses against hallucination include grounding (force the model to cite specific transcript chunks), explicit "I don't know" instructions in the system prompt, and post-generation verification where each claim in the output is checked against the source transcript before the recap is delivered.
- [Hedging](https://pavleur.com/glossary/hedging): Softening language used to indicate uncertainty, openness to other views, or politeness — "I think," "perhaps," "it might be the case that," "correct me if I'm wrong, but…" Hedging is essential in collaborative discussion: it lowers the social cost of being wrong and invites correction. Over-hedging, however, undermines authority and signals lack of conviction; an engineer who hedges every technical claim sounds uncertain even when they're right. The skill is calibration: hedge when you're actually unsure, state plainly when you're not. Non-native English speakers often over-hedge as a politeness habit imported from their first language; their contributions get discounted as a result. Meeting copilots that analyze post-call communication patterns can help speakers see their own hedging frequency and decide whether to recalibrate.
- [LLM (Large Language Model)](https://pavleur.com/glossary/llm): A neural network trained on massive text corpora to predict the next token in a sequence, which turns out to be a remarkably general primitive for generating coherent text, answering questions, summarizing, translating, and more. Modern LLMs (GPT, Claude, Gemini, Llama) range from a few billion to over a trillion parameters and are the core engine behind every AI meeting copilot. The LLM is what turns a raw transcript into a useful recap, identifies action items, drafts follow-up emails, and answers questions about past meetings. LLMs are not databases of facts — they're probabilistic next-token predictors that have absorbed patterns from training data — which is why grounding and RAG matter so much for meeting-copilot use cases where factual accuracy about specific conversations is critical.
- [1-on-1](https://pavleur.com/glossary/one-on-one): A recurring meeting between a manager and a direct report, typically weekly or biweekly, dedicated to the report's career growth, blockers, feedback, and longer-arc topics that don't fit the team's group rhythm. Well-run 1-on-1s belong to the report (they set the agenda), not the manager (who facilitates and listens). The conversation should run in roughly this order: how are you, what's blocking you, what's coming up, what's on your mind, and finally — only if there's time — anything the manager needs to push. Skipping 1-on-1s is the single most common manager failure mode in distributed teams; the meetings feel skippable because nothing breaks immediately, but the lack of regular individual contact compounds over months into disengagement and surprise departures.
- [PII (Personally Identifiable Information)](https://pavleur.com/glossary/pii): Any data that can be used to identify an individual, either by itself or in combination with other data. PII includes obvious identifiers (name, email, phone number, SSN) but also less-obvious combinations: a job title plus a company plus a city can uniquely identify someone even with no name attached. Meeting transcripts are dense in PII — names are spoken constantly, plus customer names, account numbers, salaries, and personal anecdotes. Responsible meeting copilots offer PII redaction options for sensitive contexts (clinical conversations, recruiting interviews, sales calls with regulated industries) and apply data-minimization principles to embeddings and analytics — strip PII before indexing if the use case doesn't need it.
- [RACI](https://pavleur.com/glossary/raci): A decision-rights framework that assigns four roles to every task or decision: Responsible (does the work), Accountable (owns the outcome and has final say), Consulted (must be asked before the decision), and Informed (must be told after the decision). A common failure pattern is having multiple Accountables, which guarantees deadlock — by definition exactly one person is Accountable. RACI is most useful when introduced lightly: a one-line annotation in a project plan or in the meeting notes for a contentious decision. Overapplied, it becomes bureaucratic theater. Underapplied, teams discover three weeks later that nobody actually owned the migration and it's now blocking the launch.
- [RAG (Retrieval-Augmented Generation)](https://pavleur.com/glossary/rag): An architecture where an LLM, before generating its response, first retrieves relevant documents from an external knowledge base and includes them in the prompt. Instead of relying solely on what the model learned during training, RAG lets the model answer using up-to-date, customer-specific, or proprietary information. In meeting copilots, RAG is what makes "what did we decide about the API redesign last quarter?" actually work: the system embeds the query, finds the most relevant transcript chunks via vector search, and passes them to the LLM with an instruction to answer only from the retrieved context. RAG is also the primary defense against hallucination in long-tail factual questions — if the right transcript isn't retrieved, a well-designed RAG system should say so rather than guess.
- [Real-Time AI Assist](https://pavleur.com/glossary/real-time-ai-assist): AI features that operate during a live meeting, with sub-second latency, rather than after the call is over. Examples: a private prompt-coach that suggests follow-up questions to the user as their counterpart speaks, on-the-fly definitions of unfamiliar acronyms, live translation overlays, and instant pull-up of relevant prior-meeting context when a name or topic is mentioned. Real-time assist is technically harder than post-call processing because the model has only milliseconds of context, must run continuously, and must not distract the user. The user-experience design is at least as important as the model — a real-time assist that pings the user every ten seconds is worse than no assist at all. The bar for shipping is high; the value when done well is also high.
- [Recap](https://pavleur.com/glossary/recap): A concise summary produced at the end of a meeting that captures the key decisions, action items, and open questions discussed. In an AI meeting copilot, recaps are typically generated automatically from the transcript within seconds of the call ending and sent to participants via email or a shared channel. A good recap is short enough to be read in under a minute, lists action items with owners and due dates, and links back to the relevant timestamps in the transcript for anyone who needs more context. Recaps are the single most-used artifact from a meeting copilot because they convert an hour of talk into a few paragraphs that absent stakeholders can absorb asynchronously — and because they let the participants themselves verify, days later, what was actually decided.
- [Recording Disclosure](https://pavleur.com/glossary/recording-disclosure): The legal and ethical practice of informing all participants on a call that the meeting is being recorded or transcribed. Recording-disclosure laws vary by jurisdiction: many US states require only one-party consent (the person initiating the recording), while California, Florida, and most of the EU require all-party consent. In practice, responsible meeting copilots disclose recording at join time with a visible banner, an audio chime, or both — even in jurisdictions where one-party consent is sufficient, because the trust cost of a participant feeling surreptitiously recorded is far higher than the friction cost of disclosure. The disclosure should name what's being captured (audio, transcript, AI-generated summaries) and give participants a clear path to object.
- [Retrospective](https://pavleur.com/glossary/retrospective): A team meeting held at the end of a project, sprint, or incident, where participants reflect on what worked, what didn't, and what to change next time. The classic format is three columns: keep doing, stop doing, start doing — though variants abound (sailboat, 4Ls, mad/sad/glad). Retrospectives only work if participants feel safe being candid, which means the meeting must be structured to surface uncomfortable truths without punishing the messenger. Action items from retrospectives should be specific and few — three concrete commitments are worth more than fifteen vague intentions. AI meeting copilots help retrospectives by capturing the conversation itself (so participants can listen back to themes they noticed in the moment) and by extracting and tracking the resulting commitments through to the next retro.
- [Right to Erasure](https://pavleur.com/glossary/right-to-erasure): Under GDPR Article 17, the right of an individual to have their personal data deleted by a data controller upon request, in defined circumstances. For meeting copilots, the right to erasure typically means: when a participant asks for their data to be removed, the vendor must delete the audio recording, the transcript, any embeddings derived from that transcript, any AI-generated artifacts (recaps, action items) that quote the participant, and any backups — and must do so within the legally required timeline (usually 30 days). This is more complex than it sounds because erasure must propagate through caches, search indexes, vector databases, and analytics warehouses, none of which are typically designed for selective deletion of individual records.
- [Sentiment Analysis](https://pavleur.com/glossary/sentiment-analysis): A class of NLP techniques that classify text or speech along an emotional dimension — positive, negative, neutral — and increasingly along finer-grained axes like confidence, frustration, or engagement. In meeting copilots, sentiment analysis powers features like "the customer's tone shifted negative at minute 23" or "this stakeholder seemed disengaged for the second half of the call." Sentiment is harder than it looks: sarcasm, deadpan humor, and cultural communication norms (a Dutch participant's bluntness is not anger) all confound naive models. The most useful applications of sentiment analysis in meetings are private and reflective — surfacing patterns to the speaker themselves rather than scoring participants for managers — because the latter creates a chilling effect where people perform emotions for the algorithm.
- [Signposting](https://pavleur.com/glossary/signposting): Explicit verbal cues that tell listeners where you are in your argument and where you're going — "there are three things I want to cover; first…" or "let me give you the bottom line, then the reasoning." Signposting is one of the highest-leverage communication skills in meetings: it costs the speaker a few seconds and saves the listener significant cognitive load. Without signposting, listeners have to infer your structure from context; with it, they can budget attention and ask better questions. For non-native English speakers, signposting is especially valuable — it makes your message robust to imperfect pronunciation or grammar, because listeners know what to listen for. The opposite of signposting is stream-of-consciousness, where the speaker thinks out loud and the listener has to assemble the structure themselves.
- [Skip-Level](https://pavleur.com/glossary/skip-level): A meeting between an employee and their manager's manager (skipping the direct manager). Skip-levels serve two functions: they give senior leaders a less-filtered view of what's happening on the ground, and they give employees a channel to surface issues their direct manager can't or won't escalate. Skip-levels work best when they're routine (not crisis-driven), explicitly not for performance feedback about the direct manager (which would poison the dynamic), and short — 20-30 minutes is usually plenty. Many organizations institutionalize skip-levels as a quarterly or biannual rhythm. AI meeting copilots help skip-levels by producing a low-friction record of recurring themes across many one-off conversations — patterns that are invisible in any single meeting but obvious across twenty.
- [SOC 2](https://pavleur.com/glossary/soc-2): A widely-recognized auditing standard developed by the AICPA that evaluates a service organization's controls related to security, availability, processing integrity, confidentiality, and privacy. A SOC 2 Type II report covers an extended observation period (typically six to twelve months) and is the de-facto baseline that enterprise buyers ask for before signing meeting-copilot contracts. The report is a several-hundred-page narrative of the vendor's controls and the auditor's tests; in practice buyers care about the executive summary and the absence of significant exceptions. SOC 2 is not a one-time event — it requires ongoing operation of the documented controls and an annual re-audit. For a meeting copilot, the most-scrutinized controls usually involve encryption, access management, employee background checks, vendor risk management, and incident response.
- [Speaker Labels](https://pavleur.com/glossary/speaker-labels): The human-readable names attached to each utterance in a transcript — "Alice," "Bob," "Customer" — as opposed to the raw "Speaker 1, Speaker 2" labels that diarization produces by default. Mapping anonymous speaker clusters to real names is a separate step from diarization itself, and there are several approaches: matching speakers to the calendar invite (works when the participant list is short and known), one-time voice enrollment (a participant speaks a brief sample once, and their voice is recognized in future meetings), or post-hoc manual labeling. Speaker labels make transcripts dramatically more useful — a recap that says "Alice committed to the timeline" is far more actionable than "Speaker 3 committed to the timeline."
- [Standup](https://pavleur.com/glossary/standup): A short, daily team meeting — traditionally held standing up to keep it short — where each participant covers what they did yesterday, what they're doing today, and what's blocking them. Standups originated in agile software development but have spread broadly. Done well, they take ten to fifteen minutes and surface blockers before they become emergencies. Done poorly, they balloon into thirty-minute status meetings that ignore the third question entirely. The async-first version replaces the live call with a written update in a shared channel, which respects time zones and tends to produce more thoughtful blockers. AI meeting copilots that listen to the live version can produce a written digest after the fact, giving you both modes for the cost of one.
- [Time-Boxing](https://pavleur.com/glossary/time-boxing): The discipline of allocating a fixed amount of time to a topic or activity, and stopping when the time is up regardless of completeness. In meetings, time-boxing means agendas with per-topic minutes ("15 min: API redesign, 10 min: hiring plan, 5 min: open Q") and a facilitator who actually enforces the boundaries. Time-boxing forces prioritization and prevents the most-vocal topic from absorbing the whole meeting. It also makes meetings feel respectful of participants' time, which is more than aesthetic — it materially affects engagement. The hard part is the enforcement: when a topic runs over, the facilitator must either close it (with an action to follow up async) or explicitly trade time from another topic, not just let the agenda silently slip.
- [Transcript](https://pavleur.com/glossary/transcript): A written record of everything spoken in a meeting, attributed to individual speakers and timestamped. Transcripts are the foundational artifact that every other meeting-copilot feature is built on: recaps, action-item extraction, search, sentiment analysis, and Q&A over past meetings all run against the transcript rather than the raw audio. Transcript quality depends on speech-recognition accuracy, diarization quality, and the meeting environment (clear audio, single speakers, minimal cross-talk). A transcript with 95% word-accuracy and clean speaker labels is far more useful than one with 99% word-accuracy but mis-attributed speakers — the second creates plausible-but-wrong quotes that consumers can't easily detect. Transcripts are also the highest-PII artifact a copilot produces, which makes their storage, retention, and access controls a primary security concern.
- [Working Backwards](https://pavleur.com/glossary/working-backwards): A planning discipline, originally documented at Amazon, where teams start by writing the press release and FAQ for a feature as if it had already launched, then work backwards to figure out what to build. The exercise forces the team to answer the hardest product questions first — who is this for, what does it do, why does it matter — before any code is written. The artifact is usually a one-to-six-page narrative document, read silently at the start of the meeting, followed by structured discussion. Working backwards pairs naturally with async-first cultures: the document does the heavy lifting; the meeting refines the edges. The most common failure is teams that write the doc but never actually use it to make trade-offs once development starts.

## Changelog

- [Changelog](https://pavleur.com/changelog): what's new in Pavleur, release by release

## Tools

- [Salary Negotiation Calculator](https://pavleur.com/tools/salary-negotiation-calculator): compare a tech job offer against market salary data and get negotiation talking points

## Legal

- [Terms of Service](https://pavleur.com/terms)
- [Privacy Policy](https://pavleur.com/privacy-policy)