Example content is fictional and for demonstration only. No account needed to view this page.
Table of contents
1Getting Started in Your First WeekPreviewed below
2Key Terms and Systems You Will UsePreviewed below
3Operating Principles and Team NormsPreviewed below
4Examples, Scenarios, and Common MistakesIn full pack
5First-Month Checklist and Key ContactsIn full pack
Knowledge Pack preview
Chapter 01
Getting Started in Your First Week
Give a new starter a clear path through week one: what to set up, who to meet, and where the key information lives.
Your first week is about orientation, not output. The kickoff call and the onboarding handbook agree on the same priorities: get your access set up, meet your immediate team, and read the documents you will rely on most.
Complete account and tool access on day one so nothing blocks you later.
Meet your manager and immediate team, and note who owns what.
Read the handbook sections that apply to your role.
Shadow one live process before you are asked to run it.
Note
Keep a running list of questions as they come up. New starters who write questions down ramp up faster than those who try to hold everything in their head.
Key points
Week one is for orientation: access, people, and the documents you will rely on.
Set up all tool and account access on day one to avoid later blockers.
Keep a running list of questions instead of trying to remember everything.
Quick checks
Do you know who owns each system you will use?
Can you find the handbook section for your role without asking?
Define the internal terms, tools, and systems a new starter needs so company language is clear from day one.
Every team has its own shorthand. These are the terms and systems referenced most often in the kickoff call and the handbook, with a plain definition for each.
Standup: the short daily check-in where the team shares progress and blockers.
Runbook: a step-by-step document for handling a recurring process or incident.
Source of truth: the single system or document that holds the authoritative version of a record.
Escalation path: the agreed order of who to contact when a blocker cannot be resolved.
Note
When a term is unclear, check the handbook glossary before assuming. The same word can mean different things across teams.
Key points
Learn the team's shorthand early so you can follow conversations.
Each record has one source of truth: know which system holds it.
Use the handbook glossary when a term is ambiguous.
Quick checks
Can you name the source of truth for customer records?
Do you know the escalation path for a blocked task?
Capture the working rules and norms the team expects everyone to follow.
Operating principles are the decisions the team has already made so individuals do not have to re-decide them each time. The kickoff call frames them as how we work when no one is watching.
Default to written updates: record decisions and progress so anyone can catch up asynchronously.
Escalate blockers early: raise anything blocking you within one working day rather than waiting.
Keep the source of truth current: update the system of record as soon as something changes, not later.
Final note
Principles only hold if they stay visible. Revisit them in your first month and flag any that no longer match how the team actually works.
Key points
Default to written updates so progress is easy to follow asynchronously.
Escalate blockers within one working day instead of waiting.
Keep the system of record current rather than updating it later.
Quick checks
When you hit a blocker, do you know who to tell and how quickly?
Are your updates written somewhere the team can find them?
The full Knowledge Pack continues with 2 more sections. Create a free preview to generate your own.
Source Check
Every section maps back to the source material it was built from, so your team can review that the output is grounded in your own documents.
Getting Started in Your First WeekPeople Operations
Key Terms and Systems You Will UsePeople OperationsCompany handbook
Operating Principles and Team NormsCompany handbook
Web Evidence
Key claims can be cross-checked against external sources, each with a confidence rating, so your team can review what is supported before relying on it.
Structured first-week onboarding is associated with faster time-to-productivity for new starters.
Supported
Multiple HR and operations sources agree that a clear, structured onboarding process improves ramp-up speed and early retention.
Structured onboarding: overview
Written-first updates improve knowledge retention across distributed teams.
Mixed
Some studies support written-first communication for async teams, but results vary by team size and culture. Treat as a tendency, not a rule.
Outcome varies by team. Review against your own ways of working.
Async communication case notes
Evidence links shown here are illustrative for this sample.
Source Companion
Groundable keeps an archive of your source material and runs a coverage check, flagging concepts that appear in your sources but are light in the Knowledge Pack.
86%source coverage 24 key terms covered
Most significant source concepts are well represented. A few security and access terms appear in the sources but are only lightly referenced in the pack.
Lightly referenced: Security and Access
Security and access terms appear in the sources but are lightly covered in the pack. You could add a section on data handling and access reviews.
Example sources are fictional. Thumbnails fall back to a document icon because no real recording is referenced.
Export-ready output
Download the finished Knowledge Pack as DOCX, PDF, or TXT: clean, formatted, and ready to share or deliver. Exporting is included with Starter and Professional.
DOCXPDFTXT
Why not just use generic AI chat?
Generic AI chat answers one prompt at a time. Groundable turns a whole set of business sources into a structured, checkable, export-ready Knowledge Pack, and shows its working.
A source basket, not one prompt
Collect several documents, transcripts, and call recordings, then generate one coherent Knowledge Pack from all of them, instead of pasting fragments into a chat box.
Structured Knowledge Pack output
You get a titled, chaptered Knowledge Pack with modules, key points, and checks, not a wall of chat text you have to reformat yourself.
Source Check
Every section shows which of your sources it was built from, so your team can see the output is grounded, not invented.
Web Evidence
Cross-check key claims against external sources with a confidence rating, so your team can review what to trust before sharing.
Source Companion
A coverage report flags concepts that appear in your sources but are light in the Knowledge Pack, a safety net a chatbot does not give you.
Export-ready DOCX / PDF
Download a clean, formatted document ready to share or hand to your team. No copy-paste cleanup.
Build a Knowledge Pack like this from your own sources
Create a free account to generate and preview your full Knowledge Pack in-app. No card required.