☁️ Lesson 7.3: Project — A Project Hub Tying Word, Excel & PowerPoint Together

What a Project Hub Is

Think about the last real project you worked on — a trip, an event, a report, a side venture. Its files were probably scattered: a plan in Word somewhere, a budget in an Excel file emailed around, a slide deck on someone's laptop, notes in three different apps. Nobody could see the whole thing at once, and "where's the latest version?" was a constant question. A project hub fixes that by giving a project a single home.

A project hub is simply one OneDrive folder that holds everything a project needs — the documents, the numbers, the presentation, the notes, and an index that ties them together — shared with the people involved. Because all the Microsoft 365 apps save into OneDrive (Lesson 6.3), the Word doc, the Excel workbook, and the PowerPoint deck can genuinely live side by side in one folder, open to the same people, always current. The hub is where OneDrive stops being "storage" and becomes the thing that makes a whole project cohere.

Step 1 — Create the Hub Folder

Everything starts with one folder. In onedrive.com (or File Explorer on Windows), go to a sensible spot — usually inside your Projects area from your personal file system, or in a Team library if this is work — and use New > Folder. Name it clearly and specifically: Spring Fundraiser 2026 beats Project, because a good name is the first thing that tells everyone what the hub is.

For most projects, a flat hub works best: the handful of key files sit right in the folder, easy to see at a glance, with no digging. Only add subfolders when a project genuinely needs them — an Assets folder for images, a Drafts folder for old versions, an Archive for finished pieces. The instinct from Module 2 holds: start flat and shallow, add depth only when it earns its keep. A hub you can take in at a single glance is a hub people actually use.

Step 2 — The Word, Excel & PowerPoint Files

Now fill the hub with the three files that carry almost every project: something to say it (Word), something to track it (Excel), and something to present it (PowerPoint). The magic — and the whole reason the hub works — is that you create each one right inside the folder, so it saves into OneDrive automatically. There's no "save to the cloud" step to remember and no stray copy on a laptop.

The easiest path is to create them from OneDrive itself. Open the hub folder on the web and use the New button (labeled + Add new or Create or upload in some versions), which offers Word document, Excel workbook, and PowerPoint presentation right there. Each new file is born in the hub, in the cloud, ready to share. You can also create them from within the apps — just make sure you're saving into the hub folder in OneDrive, not a local Documents folder that isn't backed up.

What goes in each file

• Word — the brief. The project's purpose, goals, who's involved, key dates, and running notes. This is the "what and why" anyone can read to get up to speed.
• Excel — the tracker. Whatever needs counting or scheduling: a task list with owners and due dates, a simple budget, or a timeline. Numbers and status live here so they're never buried in prose.
• PowerPoint — the deck. The summary you'd show someone: a few slides that tell the story at a glance. Even a rough three-slide deck makes a project feel real and shareable.

Notice the through-line from Lesson 6.3: these aren't three separate worlds. They're three views of one project — words, numbers, and story — all sitting in one folder, all opening from the same OneDrive, all shareable with the same link. That's the coherence a hub creates. If you've taken the Word, Excel, or PowerPoint courses in this series, this is exactly where their files come to live.

Step 3 — Write the Index That Ties It Together

A pile of files in a folder is better than files scattered across apps — but an index is what turns the pile into a hub. The index (call it 00 Start Here or Index) is one short Word doc that explains what the project is, lists each file with a sentence about what it's for, and — the powerful part — links to each one. Anyone who opens it can reach the whole project without hunting.

To link a file from the index: in OneDrive, select the file and choose Copy link. Before you paste, check the link settings it shows (the line or gear under the copied link) and set it to the right sharing scope — the same people who have the hub, never "Anyone" by accident. Then paste that link into the index doc. Now the brief, the tracker, and the deck are one click away from a single starting point. This is the same "one link, one place" idea as the README from the last lesson, made richer: a genuine map of the project.

PROJECT HUB — Start Here

Project: [name]
Owner: [you]        Team: [names]
Goal: [one sentence]

WHAT'S IN THIS FOLDER
- Project Brief (Word) — goals, plan, and notes    [link]
- Tracker (Excel) — tasks, owners, dates, budget   [link]
- Summary Deck (PowerPoint) — the story at a glance [link]
- Project Notes (OneNote) — running notes           [link]

HOW WE WORK HERE
- New files go in this folder, named clearly
- Everyone edits together — AutoSave keeps it current
- Old versions are safe in Version history
- Questions? Ask [owner]

Keep it short. The index earns its place by being the one file people open first — the front door to the hub. Update it when you add a major file, and it stays the reliable map of the whole project. Many teams pin the hub folder or the index link somewhere handy (a Teams tab, a bookmark) so it's always one tap away.

Step 4 — Share, Co-author & Trust Version History

A hub is meant to be shared, so this is where the sharing habits from Module 4 and the last lesson pay off. You don't share the four files one by one — you share the folder once, and everything inside inherits that access. Open the hub folder, choose Share, pick Specific people (or add team members), and give the right role: Can edit for people actively working on the project, Can view for those who only need to follow along.

Once shared, the hub comes alive. Two people can open the same Word brief or Excel tracker at once and see each other's changes appear live — that's co-authoring, and it works precisely because everyone opens the one cloud copy in OneDrive rather than passing files around. No more "report_v2_FINAL" email chains; there's one real version, and it's always current.

And if something goes wrong — a section deleted, a spreadsheet overwritten — version history has your back. Every file in OneDrive keeps a history you can open with Version history, letting you view or restore an earlier version. This is the safety net that makes co-authoring feel safe: mistakes are recoverable, so people can work boldly. We'll go deep on version history and recovery in the very next lesson, Lesson 8.1 — the hub is the perfect place to appreciate why it matters.

Step 5 — Optional Glue: OneNote & Loop

The Word/Excel/PowerPoint/index hub is complete on its own — but two optional pieces of "glue" make it even more of a living workspace, both introduced back in Module 6. Add them if they fit; skip them if they don't.

A OneNote notebook

A OneNote notebook in the hub is a great home for the messy, running side of a project: meeting notes, ideas, links, to-dos, quick screenshots. Where the Word brief is the tidy "official" document, OneNote is the shared scratchpad. Create it in the hub folder (or via the New menu), and it syncs and shares just like everything else. Many teams find the notebook becomes the most-used file in the hub.

A Loop component

A Loop component is a small live snippet — a task list, a table, a paragraph — that stays in sync everywhere it's pasted. Drop one into the index or a Teams chat and it updates for everyone in real time, wherever it appears. For a project hub, a Loop task list is a lovely way to keep "what's next" visible in more than one place without it ever going stale. Loop is newer and evolving, and it's strongest on work/school accounts, so treat it as a bonus rather than a requirement.

Step back and look at what you've assembled. One folder. A Word brief, an Excel tracker, a PowerPoint deck, maybe a notebook, and an index that links them. Shared once with the team, always current, fully recoverable. Four apps, one coherent thing — and that's OneDrive doing exactly what it's for. You've just built, in miniature, the kind of organized-and-shared space the whole course has been leading toward.

🎯 Project: Your Project Hub

Build a real one. Pick a genuine project — an event, a trip, a report, a class assignment, a side venture — and assemble its hub in OneDrive end to end. Don't worry about polished content; a rough brief, a three-row tracker, and a three-slide deck are plenty. The skill you're proving is assembling a multi-app project into one shared, coherent place. If you have no one to share with, simulate it with a second address you own or a willing friend, and clean up afterward.

Project Hub — build checklist

Project: ...
Where it lives: Projects area / Team library

THE FOLDER
- [ ] Hub folder created, clearly named
- [ ] Kept flat (files at the top, easy to see)

THE FILES (all created INSIDE the hub)
- [ ] Word brief  — goals, plan, notes
- [ ] Excel tracker — tasks / budget / dates
- [ ] PowerPoint deck — the summary
- [ ] (optional) OneNote notebook

THE INDEX
- [ ] 00 Start Here.docx sorts to the top
- [ ] Describes the project
- [ ] Copy link to each file pasted in

SHARE + SAFETY
- [ ] Shared the FOLDER once (not files one by one)
- [ ] Specific people, right role (edit vs view)
- [ ] Links match the hub's sharing scope
- [ ] Opened Version history to see the safety net
- [ ] Removed any simulated/test access after

Best Practices for Project Hubs

✅ Do's

• Keep the hub flat and glanceable. A few clear files at the top beat a maze of subfolders.
• Create files inside the hub. Born in OneDrive means AutoSaved, backed up, and shareable together.
• Write an index and pin it to the top. A 00 Start Here doc is the front door everyone opens first.
• Share the folder once, at the right roles. One invite, consistent access, files inherit it.

❌ Don'ts

• Don't scatter files across apps and laptops. The whole point of a hub is one home.
• Don't mix sharing scopes. Links in the index should match how the folder is shared.
• Don't over-build. Add OneNote or Loop only if the project truly needs them.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You built a project hub that pulls the whole Microsoft 365 story into one coherent place — words, numbers, and story, side by side in a single shared folder, always current and fully recoverable. That's a genuine capstone-warmup: you've now organized personal files, shared a library safely, and tied a multi-app project together. The through-line of the entire course — Store → Organize → Find → Share → Sync, all in one home base — is something you can now do, not just describe.

❓ Common Questions at This Stage

🔭 Looking Ahead

In the next lesson — Lesson 8.1: Version History, Recovery & the Recycle Bin — Getting Files Back — we open the safety net you glimpsed while co-authoring. You'll learn exactly how to view and restore earlier versions of a file, recover deleted items from the recycle bin, and understand the retention windows, so that "you can't really lose anything" becomes a skill you can rely on. It's the reassuring backbone under every project you'll ever build.

✅ Before the Next Lesson

• Finish building your project hub — folder, Word, Excel, PowerPoint, and an index
• Share the folder with at least one person and confirm the links match the hub's scope
• Open one file's Version history so you've seen the safety net first-hand
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• OneDrive Help & Learning (Microsoft Support)
• Collaborate & co-author files in Microsoft 365
• Microsoft 365 apps overview on microsoft.com