Follow a practical guide
A portable example for organizing shared project files.
This fictional Northstar Services example uses the Lakeside Open Day project. It demonstrates an everyday information-organizing approach, not a required storage product, access rule, or company policy.
For a related topic or authoritative source, visit Resource Hub. If the example does not fit or you cannot resolve a question, see how to prepare a support question.
Example: organize a shared project folder
A small, understandable structure makes it easier to find the working draft and final version.
For the fictional Lakeside Open Day project, the folder is for planning materials. Use names your team recognizes, and place information only in locations approved for that information.
-
1
State what belongs
Write a short purpose, such as “working materials for planning the Lakeside Open Day.” Use it to decide whether a file belongs here.
-
2
Create a few recognizable folders
Start with Planning, Drafts, and Final if those categories match the team's work. Add another folder only when it solves a real finding problem.
-
3
Name files for their content and state
For example, name a file “Lakeside Open Day - room plan - draft.” Avoid labels such as “new version” that do not distinguish it from other files.
-
4
Check whether the structure works
Ask a colleague who uses the folder to locate the room plan and explain which file appears to be the current draft. If they hesitate, clarify the folder or file names.
Match the guide to the task
Examples of useful inputs and observable outcomes.
| Task | Useful input | Expected result |
|---|---|---|
| Organize a shared project folder | The folder's purpose and recurring file types | A small structure a colleague can navigate |
| Distinguish a draft from other files | The file topic and its current state | A descriptive name that makes the distinction visible |
| Find the source for a workplace-process question | The process name and the question to resolve | The relevant authoritative source identified through Resource Hub |
Questions while following the example
Use the approach where it fits; do not guess when an important detail is unclear.
What if my tools use different names?
Use the equivalent labels in the tools your organization provides. This example describes a way to organize information, not a required product or configuration.
What if two files could be the current version?
Do not decide from the name alone. Check the relevant project context or authoritative source available to your team. If the uncertainty remains, describe the files and what you checked when you prepare a question on Request Support.
Where can I find a related process or policy?
Use Resource Hub to identify the topic and locate the authoritative source. This guide does not copy or replace policies, forms, or approved procedures.