Skip to content
EMPOBase
en

How to organize NGO documents so people can find them

By the EMPOBase team · · 4 min read

Short answer

Organize NGO documents with a small number of top-level spaces by function, a folder pattern that repeats inside each, one file naming rule, a clear way to mark the current version and access rules by sensitivity. Name an owner for each space and clean up once a year. If people cannot guess where a file lives, the structure is too complicated.

Key points

  • Use few top-level spaces, organized by function, such as Finance, People and Programs.
  • One naming rule, applied by everyone, beats a perfect folder tree.
  • Keep one current version and mark old ones clearly.
  • Set access by sensitivity, and name an owner for each space.

Why do files get lost?

Files go missing for ordinary reasons. Each team builds its own folder tree. Names like “final_v2_new” multiply. Important documents sit in personal inboxes. A staff member leaves, and nobody knows where their files went. In a donor audit, the search for one signed agreement can take a day.

The fix is not a perfect system. It is a small set of rules that everyone follows.

How should you structure the spaces?

Choose top-level spaces by function. A common set:

SpaceTypical contents
FoundationalRegistration, constitution, board documents
Strategy and planningStrategy, annual plans, risk register
FinanceBudgets, financial reports, audit reports
People and HRPolicies, templates, contract models
OperationsProcurement, assets, logistics procedures
Programs and MEALProgram documents, reports, evidence

Inside each space, repeat one pattern, for example by year and then by type. Repeating the pattern means a person who knows one space can find their way around another.

How do you name files?

Pick one rule and write it on a single page. A good rule has:

  1. Date first, as year-month-day. This sorts files in time order.
  2. A short subject. Say what it is.
  3. The version, if it changes. For example “v03”.
  4. No spaces or odd symbols. Use hyphens.

Example: 2026-03-15-partner-agreement-district-clinic-v02. Test the rule on ten real files before you announce it.

How do you handle versions?

Many teams keep five copies of a policy and nobody knows which is current. Use these habits:

  • Keep one current version in the main space. Move earlier versions to an “Archive” folder inside it.
  • Put the version number and date in the file name and on its first page.
  • Use a review step for documents that others will rely on. A draft becomes current only when a named person approves it.
  • Link to documents instead of attaching copies to emails. A link always points to the current version.

Who should see what?

Set access by sensitivity, not by convenience.

  1. Open to all staff: policies, templates, forms, procedures.
  2. Restricted by team: finance records, program data, HR files.
  3. Highly restricted: personal data, case files, legal matters.

Check access before uploading confidential records, and do not assume a folder name makes a file private. Review who has access at least once a year and when people change roles. Our article on giving auditors access without emailing files covers the external side.

How do you keep it tidy?

  • Name an owner for each space. The owner decides what belongs and what goes to the archive.
  • Run a yearly clean-up. Archive closed projects, remove duplicates and fix names.
  • Train new staff. Put the naming rule and the space map in the induction pack.
  • Make search work. Good names make search find the right file first.

For records you must keep for a set time, see how long an NGO should keep its documents.

A short example

A finance officer needs the signed agreement for a partner. In a messy system, she searches three drives and two inboxes. In an organized one, she opens the Operations space, goes to the year, then to the partner folder, and finds 2026-03-15-partner-agreement-district-clinic-v02. The name tells her the date, the type, the partner and the version. She is done in a minute.

The gain comes from habit, not from clever design. Teach the naming rule on the first day. Show new staff the space map. Ask managers to check a folder or two each quarter. Small, regular attention keeps the structure alive.

If you are starting from a large pile of old files, do not try to fix it all at once. Set the new structure for everything created from today, move active documents over as people touch them, and archive the rest in bulk.

Where EMPOBase fits

EMPOBase has a Documents area with spaces such as Foundational, Strategy & Planning, Finance, People & HR, Operations and Programs & MEAL, plus Project Files, Global Search, a Templates Library, Pending Review and an Expiry Tracker. Access depends on the space, the category and the permissions you assign. Read more on the platform page or contact us. The tool offers the structure, but your team still needs a naming rule and an owner for each space.

Questions people ask

Should folders follow projects or functions?

Use both, but in layers. Organization-wide documents sit in function spaces. Each project then has its own space for files that belong only to that project.

How deep should folders go?

Three levels is usually enough. Deeper trees hide files and make people save to the wrong place.

What do we do with the old shared drive?

Do not move everything. Move what is still in use, archive what you must keep, and delete only what your retention rules allow.