The Change Request Folder: Where Panic Goes to Die
When the project hits a crisis, everyone starts uploading files 'just in case.' The Deal Room becomes a swamp. Use this folder structure to stop the noise.
The “Just In Case” Explosion
It is 48 hours before the deal closes. A discrepancy is found in the inventory valuation. Panic sets in. The Associate uploads the new inventory list. The Analyst uploads a revised valuation model. The Tax Advisor uploads a new risk assessment.
They all dump these files into the root folder 04_Final_Docs because they want to be “fast.”
Now the Client CEO logs in to sign the deal. She sees:
Inventory_correction.xlsxValuation_v99.xlsxMemo_Tax_URGENT.pdf
She calls you. “Paolo, are these the final numbers? Why are there three new files? Is the deal changing?”
Basta. You didn’t just share data; you shared your internal panic. You made the room look unstable. “Ugly” is a risk factor, but “Chaotic” is a deal killer.
The Blocker: The Unfiltered Feed
The problem is that we treat the Deal Room like a Dropbox—a dumping ground for files. It should be a Product. A Product has a release cycle. You don’t push code to production just because you finished typing it. You test it. You stage it.
When everyone uploads to the main folder, you create noise. The client cannot distinguish between “Work in Progress” and “Signed Off.”
The Ship: The Three-State Machine
We solve this with a dedicated folder called 99_Change_Requests.
Inside, we have three sub-folders. This is the machine.
-
01_Received (The Inbox): “Put the new files here.” Anyone can upload here. The Analyst, the Partner, the Lawyer. Client view: They see activity. They know we are working. But they know these are inputs, not outputs.
-
02_In_Review (The Lab): I move the files here when I am checking them. Does the model match the memo? Are the formulas broken? Client view: “Paolo is validating.”
-
03_Approved_for_Publish (The Launchpad): Once I stamp it “OK,” it goes here for a final sanity check. Then, and only then, do I move it to the official
04_Final_Docsfolder and overwrite the old version.
By using this structure, you contain the panic.
The main folders—01_Legal, 02_Financials—remain pristine. They only contain truth.
The 99_Change_Requests folder contains the noise.
You segregate the mess so the client sees the order. That is how you keep the signature on track, even when the building is on fire. Assolutamente.
FAQs
Why can't I just overwrite the old file?
Because if the new one is wrong, you have lost the baseline. Never destroy the past until the future is approved.
Who manages the Change Folder?
The Engagement Manager. You are the gatekeeper. Nothing leaves that folder without your blessing.
Does the client see the 'Received' folder?
Yes. Transparency is key. They see we have the file, but they know it is not 'Live' yet.