Workbench demo

Documentation control demo: reorganising an overgrown file directory.

The scenario uses Cedar & Vale Legal Services, a fictional demo client. The workbook and examples are synthetic, but they are based on common real-world directory-control problems found in operational and administrative environments.

The demo shows how I would turn a messy working area into a controlled mini-project: clarify the request, define scope, inventory the current structure, identify risks, create registers, map the change and leave a handover note.

Output: a reviewed target directory structure, supporting workbook, decision trail, action log, risk register and handover note.

Problem

A working folder structure has become too dependent on memory.

Client request

Cedar & Vale asked for its shared working directory to be reviewed and reorganised so staff could find current material more quickly, reduce duplicated routes, improve handover and support better governance.

The immediate issue was efficiency. The wider issue was control: unclear folders make it harder to know which record is current, what should be archived, who owns a change and whether the structure could support future workflow or automation.

Example before structure

Shared Drive
├── Admin
├── Admin old
├── Admin new
├── Meeting notes
├── Minutes
├── Policies
├── Policies old
├── Forms
├── Forms - use this one
├── Sarah temp
├── Barbara
├── New folder
├── New folder (2)
└── 2023 stuff

How to read the demo

The workbook is a completed synthetic demonstration pack.

What the workbook represents

The workbook shows the control record after the demonstration project has been worked through: request, scope, current-state inventory, task board, decisions, actions, risks, rename map, before/after structure, handover and client review checkpoint.

In a live project, these records would be updated step by step as the work progressed and client decisions were confirmed. Here they are shown together so the method is visible in one place.

Workbook: Download the demonstration workbook

How the target folders were named

I began by identifying the types of material in the existing directory, rather than copying the existing folder names. The aim was to group work by durable business function: administration, meetings, policies, forms, reports, projects, archive and handover/control.

I then reduced the top level to the minimum useful set of lead folders, using numbered names so the order is predictable and easy to scan. Detailed material can sit in subfolders, but the first level should stay simple enough for a new starter, cover colleague or manager to understand quickly.

Linked control workbook

The linked control workbook turns the request into manageable work.

Workbook tabs

  • 00_README — project summary and data note.
  • 01_Current_Task — close-out summary for the controlled work item.
  • 02_Project_Scope — scope in, scope out, assumptions and acceptance criteria.
  • 03_Task_Board — visible project tasks, status and outcome evidence.
  • 04_File_Inventory — current folders, issue type, risk and agreed treatment.
  • 05_Decision_Log — decisions, options considered and reasons.
  • 06_Action_Log — actions taken, owner, due date and completion note.
  • 07_Risk_Issue_Log — risks/issues, mitigation, owner and status.
  • 08_Rename_Map — old folder names mapped to new routes or review decisions.
  • 09_Before_After — before and after directory structures.
  • 10_Handover_Note — maintenance rules and handover guidance.
  • 11_Client_Review — client review and approval checkpoint.

Why these registers matter

A folder clean-up can look simple from the outside. In practice, it can affect current work, archive routes, access assumptions, naming conventions and staff confidence.

The registers make the work traceable: what exists, what changed, why a decision was made, what risk was controlled and what the client would need to review before implementation.

Process

The route from problem to solution.

Working method

  1. Capture the client request and business reason.
  2. Define scope, exclusions and acceptance criteria.
  3. Inventory the current folder structure.
  4. Identify duplicates, unclear names, archive candidates and specialist-review items.
  5. Design a simple target structure.
  6. Track decisions, actions and risks.
  7. Map old folders to new routes.
  8. Prepare handover guidance and client review points.

Client review checkpoint

Before live changes, the client would review the target folder structure, archive approach, retention/deletion boundaries, access/permissions implications and implementation route.

Nothing in the demo assumes deletion, live migration, permission redesign or external publication without authority.

Result

A cleaner structure that is easier to understand and hand over.

Example after structure

Shared Working Area
├── 00_Read_Me_First
├── 01_Service_Admin
├── 02_Meetings
├── 03_Policies_And_Procedures
├── 04_Forms_And_Templates
├── 05_Reports_And_Registers
├── 06_Projects
├── 07_Archive
└── 99_Handover_And_Control

What this demonstrates

Documentation control, scope definition, task discipline, decision logging, action tracking, risk awareness, handover thinking, information organisation and practical service-improvement judgement.

The aim is not to prove that I can rename folders. The aim is to show how I approach messy operational information and turn it into a controlled, reviewable and maintainable solution.

Continue Reading

Next sections.

Workbench · Method · CV · Contact