📔 Lesson 6.3: The Work Project — Onboarding, Policy & Documentation Hubs

The Permission Question — Read This First

Unlike a research paper you downloaded or a textbook you own, workplace documents often come with strings attached: confidentiality agreements, data-protection regulations, and company policies about which tools are approved. So before we build anything, the responsible move is to ask should this go in here at all? — and to make that a habit, not an afterthought. This is the "slightly advanced" part of this lesson, and it's advanced because it's about judgment, not buttons.

Here's the reassuring flip side: a huge amount of workplace knowledge is perfectly fine to work with — the public employee handbook, published SOPs, product documentation you're authorized to use, your own meeting notes, onboarding guides. For anything sensitive, note that Google offers enterprise editions of NotebookLM through Google Workspace with stronger data governance; if your organization has that, use it for work material rather than the consumer product. Google states that consumer NotebookLM content isn't used to train its models, but that assurance does not override your company's rules or a regulation — treat both as binding.

📥 Build the Reference Notebook

With permission settled, building the hub is the familiar sources work from Module 2 — just pointed at the documents that make a workplace run. The goal is a single notebook that can answer "how do we do X here?" and "what's our policy on Y?" without anyone digging through six shared drives.

Two habits make a work notebook trustworthy. First, keep it current: policies and SOPs change, and a hub answering from last year's handbook is worse than no hub, because it's confidently wrong. Note the version or date of each source, and plan to refresh them. Second, keep it scoped: one notebook for onboarding, another for a specific product, another for a policy domain — mixing everything dilutes the answers and makes citations harder to trust. A focused reference notebook is a sharp reference notebook.

💬 Ask Precise, Citable Policy Questions

Workplace questions have a higher bar than casual ones, because people act on the answers — they book the leave, follow the process, quote the policy to a customer. That means two things: ask precisely, and phrase the question so the answer is easy to verify. Vague questions get vague, harder-to-check answers; precise questions get specific, citable ones.

🎯 Precision in, precision out

Compare these:

• ❌ "What's the vacation policy?" — broad, invites a sprawling summary.
• ✅ "How many days of paid annual leave does a full-time employee accrue in their first year, and when can it be carried over? Cite the policy." — specific, and the citation lands on one checkable passage.

Notice the second question asks for the citation explicitly. In a work context, make that standard. Phrasings that pay off:

• "Answer only from the policy documents, and cite the exact section."
• "If the sources don't clearly state this, say so rather than guessing." — critical for policy, where a confident guess is dangerous.
• "Quote the sentence that establishes this rule."
• "Do any of these documents contradict each other on this point?" — real workplaces accumulate conflicting policies, and surfacing that is genuinely useful.

That last one matters more than it sounds. Organizations layer new policies over old ones, and an SOP can quietly contradict the handbook. Asking NotebookLM to surface conflicts turns your hub into a tool that finds problems, not just answers questions — the kind of thing that makes you look sharp in a meeting.

🔎 Verify Before Anyone Acts

In a study project, an unverified answer costs you a quiz point. In a work project, it can cost someone their leave entitlement, put the company out of compliance, or send a customer the wrong information. The stakes raise the standard: at work, you verify the citation before the answer leaves your hands.

It's the same three-part check from Lesson 6.1, and it's non-negotiable here. Click the citation and confirm the passage exists, that it genuinely says what the answer claims, and that it isn't ripped from context — a policy sentence that begins "except where clause 4 applies" changes everything that follows. Policy language is precisely the kind of dense, qualified, exception-laden text where an AI summary most easily drops a crucial "not" or "unless."

⚠️ Important Note: Never forward a policy answer to a colleague with "NotebookLM says…" Forward it with "Per the Remote Work Policy v3, section 4 — [link/quote]." You verified it; cite the source, not the tool. That habit is what makes your hub trustworthy instead of just convenient.

📄 Produce a Team-Ready Briefing or FAQ

A reference notebook that only you can query is useful. A cited FAQ or briefing built from it, that your whole team can read, is valuable — and it's the deliverable for this project. This is the studio work from Module 5 aimed at a real audience: the new hire on day one, the team that keeps asking the same five questions, the manager who wants the policy landscape summarized.

❓ A team FAQ from the questions people actually ask

Generate an FAQ in the Studio panel, then shape it around real needs. The generated FAQ is a strong first draft; improve it by feeding in the questions your team actually asks — the ones that clog the group chat and the onboarding calls. For each, capture the grounded, cited answer, verify it, and rewrite it in plain, warm language a new colleague can act on. The result is an onboarding FAQ that answers the recurring questions once, with the source attached to each answer.

📋 A briefing doc for the policy or process landscape

For a manager or a cross-team audience, generate a briefing doc — a structured summary of the key policies, processes, or product facts across your sources. Treat it, as always, as an assistant's first draft: read it against the sources, correct anything verification flags, and cut anything you can't stand behind. Then it's a briefing you can circulate with your name on it.

You can also generate an Audio Overview of an onboarding notebook — a friendly spoken walkthrough of "how things work here" that a new hire can listen to in their first week. Just apply the same honesty as everywhere: the audio is a warm orientation, not the authoritative policy text, so point people to the cited FAQ for anything they need to act on.

🤝 From Personal Hub to Shared Resource

You've built something a team would genuinely use — which raises the natural next question: how do you actually get it to them? NotebookLM lets you share a notebook with specific people as a viewer or an editor, so colleagues can ask their own questions of the same grounded sources without being able to alter them. A shared reference notebook can become a living team resource: one source of truth people query in their own words, each answer citable back to the official document.

That's a whole topic of its own, and it's exactly where we go next. Sharing well means thinking about access (who can see what), roles (viewer versus editor), and — back to where this lesson started — permission (whether the material is appropriate to share at all, and through which edition of the tool). We'll cover the mechanics and the judgment together in Module 7.

A cited answer one person can check is useful. A cited hub a whole team can query, each answer tracing to the official source, quietly kills a hundred "does anyone know our policy on…?" messages a month.

🎯 Project: A Cited Team FAQ

Build a real work or reference notebook and produce a team-ready FAQ or briefing where every answer is cited and verified. Use genuine material you're clearly permitted to use — a public handbook, published SOPs, product docs you're authorized to work with, your own notes. If you don't have work material you can use, build the same thing for a volunteer group, a club, or a community organization: the skill is identical.

Q: How much notice must I give for annual leave?
A: At least two weeks for leave longer than three days;
   shorter requests may be approved at manager discretion.
   Source: Employee Handbook v3 (Jan 2026), Section 5.2
   Verified: yes - checked passage, in context

Q: Can I carry unused leave into next year?
A: The sources do not clearly state a carry-over rule.
   Action: confirm with HR before relying on this.

Best Practices for Work Projects

✅ Do's

• Check permission first, every time. Confirm the material is allowed and non-confidential before it goes in.
• Ask precisely and request citations. Specific, cite-me questions get specific, checkable answers.
• Cite the source, not the tool. "Per the handbook §5.2," never "NotebookLM says."
• Keep it current and scoped. Date your sources, refresh them, and keep one notebook per domain.

❌ Don'ts

• Don't upload confidential or regulated data to a consumer tool without formal approval.
• Don't forward a policy answer you haven't verified. At work, an unchecked answer has real consequences.
• Don't treat the notebook as the authority on high-stakes calls — the official document and a human (HR, Legal) are.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built a workplace knowledge hub the responsible way — permission checked, sources scoped and dated, answers precise, verified, and cited to the official document. That combination of usefulness and judgment is exactly what makes AI an asset at work rather than a liability, and it's a reputation-maker. You didn't just make a notebook; you modeled how a thoughtful professional brings a new tool into an organization.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 7.1: Sharing & Collaborating on Notebooks — we open Module 7 by taking your personal hubs and making them shared. You'll learn to invite people as viewers or editors, understand what shared collaborators can and can't do, and weigh the sharing differences between the free tier and NotebookLM Plus — so the reference notebook you just built can become a resource your whole team relies on.

✅ Before the Next Lesson

• Finish your cited team FAQ or briefing and confirm every answer traces to a verified source
• Write down who would benefit from access to this notebook, and at what role (viewer or editor)
• Write your Learning Journal entry — especially the recurring annoyance your hub could solve

📚 Additional Resources

• notebooklm.google.com — build your reference hub
• NotebookLM Help Center (Google Support) — sharing & data handling
• NotebookLM on the Google blog — workplace & Workspace updates