Internal Wiki for Remote Teams: What to Document First
The first ten pages every remote team wiki needs, how to write for readers in other time zones, and how to set it up in Google Drive.

In an office, people learn by overhearing. In a remote team, anything that isn't written down has to be asked, often across time zones, and waiting half a day for an answer adds up. Start your remote team's wiki with the pages that answer the most frequent questions: how we communicate, who does what, how work gets done, and what a new person needs in week one. Ten pages cover most of it.
The first ten pages to write
| # | Page | Answers |
|---|---|---|
| 1 | Start here | Where is everything? |
| 2 | How we communicate | Which channel for what, expected response times, when to call instead of write |
| 3 | Working hours and time zones | Who's online when, overlap hours, how to show you're away |
| 4 | Team directory | Who does what, who to ask about each area |
| 5 | Meetings | Which recurring meetings exist, who attends, where notes go |
| 6 | Tools and access | What we use, how to get access, who administers it |
| 7 | Onboarding: first week | What a new hire does each day, and who helps |
| 8 | How we make decisions | Who decides what, how proposals are written, where decisions are recorded |
| 9 | Time off and expenses | How to request leave, how to claim expenses |
| 10 | Security basics | Passwords, devices, what to do if a laptop is lost |
Write these in a week, short and imperfect, and improve them as questions come in. Every question asked in chat that a page could have answered is a signal for the next page.
Writing for async readers
Remote readers can't lean over and ask what you meant. A few habits help:
- Lead with the answer. The first line says what to do; context comes after.
- Be explicit about defaults. "Reply within one working day" beats "reply promptly".
- Write time zones out. "15:00 CET / 09:00 ET", never just "3pm".
- Show, don't describe. A two-minute Loom of a process saves a page of steps.
- Record decisions where people look. Decisions made in calls go into the wiki the same day, or they didn't happen for anyone who wasn't there.
- Invite comments. Ask readers to comment on anything unclear; it's how the wiki improves without meetings.
Setting it up in Google Drive
If your remote team already works in Google Workspace, put the wiki in a shared drive: one folder per section from the table above, shared with the whole team. Everyone already knows how to write and comment in Google Docs, so there's nothing new to learn.
To make it feel like a wiki, connect the folder to Spaceli:
- Navigation for people who weren't there. A sidebar with your folder structure, a table of contents on every page, and Cmd+K search across everything.
- Videos where they belong. A YouTube link on its own line becomes a player right on the page, and a Loom recording embeds with its embed code.
- Easy to join. Colleagues on your Google domain join automatically or request access; contractors can be invited to specific spaces as external collaborators.
- Edit without switching. Open the Google Docs editor right inside Spaceli; changes sync with Drive.
- Comfortable at any hour. Light and dark mode for late-evening reading in another time zone.
FAQ
What should a remote team document first?
How you communicate, who does what, and what a new person needs in their first week. These answer the most frequent questions.
How do remote teams keep documentation current?
Give each page an owner, record decisions in the wiki the same day, and review the most-used pages once a quarter. More in how to keep team documentation up to date.
Is a wiki better than a shared drive for a remote team?
A shared drive stores files; a wiki makes them easy to navigate and search. Using Google Drive with a wiki layer gives you both.

Writes about wikis, documentation and how teams keep their knowledge easy to find.
Keep reading
All articles →Engineering Documentation in Google Docs: Runbooks, ADRs and Onboarding
A folder structure and templates for runbooks and architecture decision records in Google Docs, plus how to make Docs work for engineers.
Internal Wiki and Public Docs from One Google Drive
Run your internal wiki and customer-facing docs from one Google Drive: how to split folders and access, and publish both without a second tool.
How to Keep Designs, Boards and Docs in One Place
Figma, Miro, Loom, Sheets and Docs scattered across tools? Organize by topic in Google Drive and bring them into one knowledge base.
Your knowledge base is already in Google Drive.
Give your team a better way to organize, find, and share knowledge. Keep your documents right where they are.
Start for FreeFree during the beta. Get started in about a minute.
Spaceli only accesses the folders you choose.