Research question and scope

This protocol measures how often a shared drive file follows the agreed naming standard. The unit is one file in one folder family. A compliant name matches the written pattern for that family and contains the required fields in the required order. The measure describes naming discipline, not the quality of the file contents.

Set the scope to one drive, one folder family, and a fixed period. Record the naming pattern and the exception list in force. If the pattern changes during the period, split the sample at the effective date. A different pattern creates a different denominator.

Keep the measure separate from a retrieval or duplicate-file count. A well-named file can still be hard to find if the folder structure is poor, and a badly named file can be found by someone who already knows it. The purpose is to test the written standard. Report retrieval separately.

Name the decision the result will support before collection starts. The client may use it to decide whether to retrain, revise the pattern, or migrate a folder. A report that cannot change a decision adds work without value. Write the intended action beside the scope.

Name the folder families that will be excluded before the sample is drawn. A shared drive often holds personal folders, archived projects, and system exports that should not be judged by the current standard. Record the exclusion list and the owner who approved it. An unexplained exclusion looks like cherry-picking.

Population and unit of analysis

Define the population as every file saved in the selected folder family during the period. Include files created by the client team and files created by the outsourced team. The unit is the file, not the folder. A batch of ten reports is ten units when each file has its own name.

Include files in subfolders and shared links that point to the same drive. Mark the source folder and the creator where the drive records it. Exclude temporary files, lock files, and system-generated exports with a fixed name. Report the excluded count so the denominator is visible.

Exclude a file that was renamed during the period from a noncompliant to a compliant name. Count it at its final state and record that a rename occurred. A migration that fixes names is not the same as a team that follows the pattern at save time. State the rule before sampling.

Decide whether a deleted file counts in the population. A deleted file can still show a naming habit, but it no longer affects retrieval. Exclude it and report the count separately. The rule should be written down so the next reviewer does not reopen the question.

Decide how to treat a file that matches the pattern but uses a nonstandard separator or date format. Score each required field separately and report the format issue as its own category. A single compliant or noncompliant label hides which part of the pattern is hard to follow. Record the sub-scores in the export.

Definitions that make the measure reproducible

Define the written pattern as the exact field order, separator, and date format published for the folder family. Define a compliant name as one that matches every required field with no extra free text. Define a partial name as one missing a required field or using the wrong order. Publish one example of each before sampling.

Define the required fields by folder family rather than by the whole drive. A support folder may need client, queue, case, and period, while a payroll folder may need client, pay period, and run type. Record the field list beside each family. A universal rule applied to unrelated work produces false failures.

Define an approved exception as a name on the written exception list with an owner and a reason. A name that looks unusual but is not on the list is noncompliant. Record the exception reference. This prevents a reviewer from accepting a familiar name without evidence.

Decide how to handle a file with a personal name in it. Score the naming pattern first, then report the privacy issue separately. Personal data in a filename is a different risk from a missing period field. The two findings need different owners and fixes.

Agree how to score a name that is correct but unreadable because it is very long. Add a length limit to the pattern and report an over-length name as a format issue. Record the limit in characters. A technically complete name that the interface cuts off does not help the reader.

Sampling and data collection

Draw the sample from the drive inventory export for the full period. Record the export date, the folder filters, and the row count. Do not build the sample from a list of files someone remembers. A memory-based sample overrepresents recent and unusual work.

Capture the file path, the folder family, the creator, the save date, the current name, the required fields found, the missing fields, and any exception reference. Store the inventory export with the report. The name and the folder family are the core evidence. Keep the original export so a reviewer can recompute the score later.

Check a small overlap sample with a second reviewer. If the reviewers disagree about whether a field is present, the pattern is ambiguous. Rewrite the pattern and retest before the full sample. Agreement matters more than sample size.

Record the time spent classifying each file. A report that requires opening every document will not be repeated. Note whether the drive exposes the creator and save date in the export. The collection cost belongs beside the result.

Sample across the whole period rather than the most recent month. A recent-only sample may reflect a migration or a new template instead of the steady habit. Record the date range and the number of files from each week. The spread shows whether the result is stable.

Measuring naming compliance

Report the share of files with a compliant name, a partial name, and a noncompliant name. Show the counts behind each share. The three groups describe different levels of adherence and should not be collapsed. A single compliance rate hides the file that is missing only one field.

Break the result down by folder family, creator group, and month. A newly migrated folder may show a temporary drop. A client-created folder may follow a different habit. Compare only groups with the same pattern and a similar volume.

Report the most common missing fields and the most common format errors. A missing period field may point to a template that omits it. A separator error may point to a person who learned an older rule. The pattern should lead to one specific fix.

Report the share of files that were renamed after creation. A high rename rate suggests the team knows the standard but saves before applying it. Include the median time to rename. The rename is evidence of a recovery step, not compliance at save time.

Compare the rename rate with the share of files that were never touched after saving. A team with a high rename rate and a low untouched rate may be saving first and checking later. Record both numbers together. The pair describes the workflow better than either measure alone.

Limitations and next action

The measure cannot show whether a file was easy to find or whether its contents were correct. It also cannot show a file that was renamed outside the drive history. Treat the result as a measure of current names. Note the folder families and export gaps that were not included.

Give the result to the operations owner and the drive owner with one change to test. The change might be a save template, a shorter field list, or a rename step at the end of each shift. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.

Review the boundary cases before tightening the pattern. A few legacy folders may explain a large share of partial names. Fix the migration or the exception list first if that is the pattern. The goal is a name the next person can find, not a lower number by definition.

Write a one-page summary with the sample size, the main gap, and one action. Give the action an owner and a review date. Record the next sample date in the same note. A report that ends without a date will be remembered as a complaint rather than a plan.