Standardize your team's meeting notes with one reusable AI summary template (Lenses)

A Lens is your team's house summary format applied to every meeting automatically. Instead of each person freelancing notes or pasting a static template, you build one reusable AI summary template once and share it, so every meeting comes back in the same structure — decisions, action items, risks — filled in consistently across the whole team.

If you manage more than a handful of seats, you already know the failure mode: ten people record ten meetings and you get ten different note shapes. One rep leads with next steps, another buries the decision in paragraph four, a third writes nothing the day they're slammed. To standardize meeting notes across the team, you don't need a stricter style guide — you need the structure to be produced for everyone, every time, without anyone remembering to follow it.

A Lens is a reusable custom AI summary template that's applied automatically to a meeting's transcript. You define the sections you want — decisions, action items, risks, next steps — and the AI fills them in from what was actually said. That's the difference that matters: a Lens is not a document you hand to people, it's a format the product produces on their behalf.

A static template is an empty shell. Someone has to open it, read the transcript or remember the meeting, and type each section by hand. It standardizes the headings and nothing else — the moment a teammate is busy, distracted, or new, the shell comes back half-filled or skipped entirely. The template only works as well as the most disciplined person on your worst day.

A Lens removes the discipline requirement. Build it once, share it, and it auto-fills the same structure for every team member on every meeting. The reusable AI meeting summary template for teams stops being something people opt into and becomes the default output. Capture happens locally on each person's machine — mic plus system audio, no bot in the call — and the transcription runs in the cloud through our processor (Soniox, 60+ languages) under a data-processing agreement, so the Lens has accurate text to work from before it ever fills a section.

One shared Lens beats a free-for-all because it makes every note comparable. When each person formats their own way, you can't scan a folder of meetings and find the decisions — you have to read each one on its own terms. Inconsistent notes break cross-team search, slow handoffs, and force managers to re-read instead of skim. A consistent meeting summary format company wide turns a pile of meetings into a dataset you can actually move through.

The handoff row is where the cost shows up first. When a rep goes on leave or an account changes hands, predictable sections mean the next person finds the open action items and the named risks exactly where they expect them. With freelance notes, that context lives in someone's head or in a paragraph nobody knows to look for.

Standardizing is a one-time setup, not an ongoing enforcement job. You build the format once and the team inherits it. Here's the sequence:

1. Define the sections your team needs. Keep it to the things you actually act on — decisions made, action items with owners, risks or blockers, and next steps. Resist the urge to add fields nobody reads.
2. Build the Lens once. Write the structure and the instructions for how the AI should fill each section. This is the only time anyone touches the template.
3. Share it to the workspace or teamspace. Now it's available to the seats who should use it — not just on your machine, but as a team-level format.
4. Let it auto-apply. From there, every meeting comes back in that structure. The custom meeting notes template every rep uses is now simply the output they get, not a step they perform.

The payoff is a team meeting notes template that fills itself in. New hires don't reinvent the format — it's built into their first recording. Veterans don't drift — the structure is produced for them whether they're focused or fried.

The right Lens depends on what your team does after the meeting. A few patterns that map cleanly to real rituals:

• Sales — a discovery or qualification recap: pain, current solution, success criteria, decision process, and next step, so every rep's calls are comparable and coachable.
• CS and account management — an account update and handoff: usage themes, risk flags, open commitments, and renewal signals, so an account can change hands without losing context.
• Agencies and consulting — a standardized per-client recap: decisions, scope changes, deliverables, and dates, identical across every client so the whole book of business reads the same way.
• Product and engineering — a decisions-and-tickets format: what was decided, the action items, and the open questions, structured so they're ready to turn into work.

A shared Lens standardizes format, not access. Sharing the Lens to your workspace means everyone gets the same summary structure — it does not mean everyone can read every note produced with it. Reline is private-by-default: a workspace role alone grants no access to any individual note or folder. Every viewer needs an explicit grant to see a given note, regardless of their title.

That holds even at the top. An "open" teamspace gives Members edit access to its content — but Owners and Admins get no silent reach into notes they weren't granted. And web-publish is a separate, deliberate public link, not a side effect of workspace visibility. So you can standardize the format across hundreds of seats while access stays scoped note by note.

Consistency alone isn't enough — a uniformly wrong note is still wrong. The reason a Lens beats a copy-paste template isn't just that the structure matches; it's that every filled section links back to the exact transcript moment it came from. The summary is citation-backed, so anyone reading it can click a line and jump to where it was actually said.

That changes how you trust the output. A manager reviewing twenty discovery calls can skim the standardized sections and, when a claim looks off, verify it against the transcript in one click instead of relistening to the whole call. The AI can still make mistakes — no summary model never errs — but a citation-backed one is checkable, which a hand-typed template never is. You get consistency plus verifiability, not just consistency. And to be clear: we don't train on your meetings.

Don't try to standardize everything at once. Pick one ritual where inconsistency hurts most — usually all discovery calls, all client check-ins, or all weekly syncs — and build a single Lens for it. Run it for a couple of weeks, watch where the sections come back thin or noisy, and refine the template. One ritual, dialed in, teaches you what the rest of the team needs.

Then expand. Add the next call type, share the new Lens to the right teamspace, and let the format propagate the same way. Because the structure is produced automatically, scaling from one ritual to ten doesn't add work for your reps — it just adds formats to the library they already inherit. That's how you standardize meeting notes across the team without turning it into a change-management project.

You can start free: the Free plan includes 10 hours of transcription a month and 2GB of storage. Professional is $15/user/month ($12 annual) for teams that record constantly, and Enterprise ($32/user/month, $26 annual) adds the audit log, policy locks, and a DPA for organizations that need the private-by-default architecture backed by formal controls.

Standardizing your team's notes isn't about asking people to write the same way. It's about producing the same structure for them, every meeting, with each section traceable back to the transcript. Build one Lens, share it, and let consistency be the default instead of the exception.