Every proposal, scope, fee table, and contract Northstar Design Collaborative produces becomes part of the firm's institutional memory only if it can be found again. A document saved with a random name in the wrong folder is functionally lost: the hours that went into it cannot be reused, the precedent it sets cannot be cited, and the next person who needs it rebuilds it from scratch. File discipline is what separates a firm that compounds its knowledge from one that repeats its work.

This module codifies the conventions that make every Northstar Design Collaborative document findable: the Year-Month-XX naming standard introduced in Section G, the project folder structure, the way a file is named and versioned from first draft through signed contract, how confidential work is protected, and the filing cadence that keeps the system current. These are not suggestions. They are the operating standard, and the cost of ignoring them is measured in lost hours and lost documents.

The core of the system is the Year-Month-XX convention introduced in Section G. Every proposal file is named in the format YYYY-MM-NN, where YYYY is the year, MM is the two-digit month, and NN is the sequential number of that proposal within the month. Because the date leads, sorting a folder alphabetically also sorts it chronologically. There is no separate step to organize by date; the name does it automatically.

A full file name extends the date stem with the information a reader needs to identify the document without opening it. After the date sequence comes a confidentiality flag where required, then the project name, the location in US state abbreviation form, and the document type. A name built this way is a complete label: anyone scanning the folder knows what each file is, who it concerns, and whether it is sensitive, at a glance.

The file name identifies the document; the folder structure groups documents by the project they belong to. Each engagement has a single project folder, and everything that engagement produces, the proposal, the scope, the fee table, correspondence, the signed contract, lives inside it. The result is that the complete history of a project sits in one location, and no one has to assemble it from scattered files when a question comes up months later.

Every proposal moves through stages: an internal draft, the version reviewed by the project lead and principal, the version sent to the client, and finally the signed contract. The filing convention carries through all of them, with the same date stem so they stay together, and a clear marker of stage so the current version is never in doubt. The goal is that anyone opening the folder can tell at a glance which file is the live one and which are superseded.

A naming convention is only as good as the storage everyone shares. Northstar Design Collaborative keeps project files in the firm's shared storage system, not on individual desktops or personal drives. A document saved only to a local machine is invisible to everyone else and lost the moment that machine is unavailable. Saving to the shared system is what makes the naming and folder conventions actually function, because the whole firm is looking at the same set of files.

One project generates more than a proposal. There is the cover letter and proposal, the scope of work, the fee calculation, supporting correspondence, and the eventual contract. The convention keeps them unified by carrying the same date stem across all of them, while the document-type portion of the name keeps each one distinct. The whole set sorts together in the folder, and the type label tells you which is which without opening anything.

Not every project is public knowledge. A new restaurant location, an unannounced renovation, or a sensitive client relationship may be confidential until the client says otherwise. The convention handles this by carrying a CONFIDENTIAL flag in the file name itself, placed right after the date stem. The marker travels with the file everywhere it goes, so the sensitivity is visible at the folder level, before anyone opens the document or forwards it.

Northstar Design Collaborative's standard turnaround from RFP receipt to a proposal in the client's inbox is three business days. Filing is built into that cadence rather than treated as cleanup afterward. The file is named and saved to the project folder when it is created, the sent version is preserved when it goes out, and the signed contract is filed when it returns. Because filing happens at each step, the record is always current and nothing is left to a later catch-up pass that may never come.

Completed projects move from active to archived, but archived is not gone. A client may call about a kitchen Northstar Design Collaborative designed years earlier, an architect may reference a past engagement, or the firm may want to reuse a proven approach. Because every file was named with the Year-Month-XX convention and kept in its project folder, retrieval years later is a search, not an excavation. The discipline applied at creation is what makes the document findable long after everyone has forgotten the details.

Filing failures are predictable. The same errors appear again and again, and each one carries a real cost the moment a document needs to be found. The table below maps the recurring mistakes to what they cost the firm, so the discipline is not abstract: each rule in this module exists to prevent a specific, expensive failure.

File discipline is a habit, and habits hold when they are reduced to a checklist run every time. The list below consolidates Section K into the few checks that matter on every document. Run it as the file is created and again before it is sent, and the filing system stays current and complete without any separate cleanup effort.