Micro BVs face concealed liability when decisions live in people’s memories rather than in documented records.
A decision log captures date, decision, rationale, supporting documents, and approver for every material choice.
Without it, you lose proof in audits, disputes, and compliance checks. Dutch law requires 7 years of records.
Poor documentation costs small companies €41,000 yearly in wasted time and compliance friction.
Start logging decisions within 24 hours. Five fields, 60 seconds per entry.
Core answer:
- Decision logs create institutional memory and prevent expensive reconstruction of previous decisions.
- Dutch BVs must maintain 7 years of business records, or directors face personal liability.
- Log five elements: date, decision, rationale, supporting documents, and approver.
- Material decisions include vendor selection over €1,000, contract changes, policy updates, and financial commitments.
- Poor documentation costs organizations with 10 employees roughly €41,000 per year in lost productivity.
A micro BV has one hidden liability: decisions live in people, not in the company.
When you decide something, the reasoning feels obvious. Do you remember why you chose the vendor, accepted the contract clause, and approved the spend?
Then time passes.
A bank asks a question. An insurer asks for a rationale. An auditor asks who approved. A partner dispute forces you to explain what was agreed. A team conflict shows two people remember the same decision differently.
And you discover the real problem.
The company has no way to repeat the reasoning later. No way to prove the reasoning to anyone else. You reconstruct the past from fragments. Emails. Old PDFs. Half-sent messages. Someone’s memory. Someone else’s denial.
McKinsey’s 2025 research found that 53% of companies don’t maintain records of board resolutions, and 48% have no formal corporate governance procedures. The documentation gap exists even in established organizations.
A decision log stops reconstruction. Creates institutional memory.
When you didn’t write the decision down, the decision didn’t happen. When the decision did happen, you had no way to defend it.
Why do decision logs matter for Dutch BVs?
Dutch business law requires basic business records to be kept for at least 7 years. Proper administration is legally required for all BVs. When you don’t maintain adequate records, you trigger the director’s liability in case of bankruptcy if annual accounts aren’t filed on time.
The legal presumption is clear: when you don’t show proper management through documentation, you become personally responsible.
This isn’t theoretical. Directors face personal liability when the Tax Administration discovers missing records or late filings. When you don’t notify the Belastingdienst within two weeks of tax payment problems, you become personally responsible for the company’s tax debts.
The mechanism is simple: weak documentation creates legal exposure. Strong documentation reduces it.
Bottom line: Weak documentation creates personal liability for directors. Strong documentation protects you.
What does poor documentation cost?
Most founders underestimate the financial impact of missing decision records.
Research shows that a small organization with 10 employees loses roughly €41,000 per year because of poor documentation. This scales up: organizations with 100 employees lose €410,000 per year.
The cost breaks down into predictable categories:
Time waste. Knowledge workers spend 2.5 hours per day searching for information. That’s 30% of the workday hunting for decisions instead of retrieving them instantly.
Compliance friction. IDC research found 36.2% of organizations failed to meet compliance or regulatory requirements due to inefficiencies in document-driven business processes, while 20.4% were pulled into major audits.
Repeated debates. When decisions aren’t documented, teams relitigate the same questions. Energy drains into reconstruction instead of execution.
Vendor disputes. Without documented scope decisions and acceptance logic, you lose leverage in conflicts. The vendor remembers what the vendor wants to remember. You need proof.
Institutional memory loss. When employees leave, knowledge leaves with them. Organizations repeat the same experiments, rediscover the same constraints, and relearn the same lessons.
Reality check: Poor documentation feels cheap until regulatory compliance friction or an audit makes it expensive.
What does a decision log actually do?
A decision log isn’t a diary. It’s a structured record of material decisions affecting the company’s operations, compliance, or risk exposure.
Each entry captures five elements:
1. Date. When the decision was made.
2. Decision. What was decided, in clear language.
3. Rationale. Why was this decision made? What factors were considered? What alternatives were rejected and why?
4. Supporting documents. Links to contracts, quotes, emails, risk assessments, or other evidence that informed the decision.
5. Approver. Who made the decision or who authorized it?
The outcome is precise: for every material decision, you retrieve the entire context in under 60 seconds.
How do you build a decision log?
What counts as a material decision?
Not every decision needs logging. Set a threshold.
Material decisions typically include:
- Vendor selection above €1,000
- Contract acceptance or amendment
- Policy changes (HR, compliance, data administration)
- Financial commitments or budget deviations
- Risk acceptance decisions
- Structural changes (bank accounts, signatories, registered address)
- Hiring, termination, or role changes
- Software or tool adoption that touches customer data or financial systems
Set your threshold based on risk tolerance and regulatory context. Simple rule: when you’d need to explain something to an auditor, bank, or partner later, log the decision now.
Rule of thumb: When an auditor, bank, or partner asks about the decision later, log it now.
Which tool should you use?
The tool matters less than consistency. Pick one place where decisions live.
Options include:
- A shared spreadsheet (Google Sheets, Excel)
- A simple database (Airtable, Notion)
- A document management system with version control
- A dedicated governance platform if you scale beyond micro
Minimum requirement: the log must be searchable, accessible to authorized people, and backed up.
Avoid scattered systems. When decisions live in email, Slack, WhatsApp, and a notebook, you don’t have a log. You have chaos.
Critical point: Scattered systems create chaos. One central log creates control.
When should you log decisions?
The best time to log a decision is within 24 hours of making the call. The reasoning is fresh. The documents are open. The context is clear.
Delayed logging introduces memory distortion. You start editing the rationale to fit the outcome. You forget the alternatives you considered. You lose the detail.
Make logging part of the decision process. Before you close the vendor contract, log the selection rationale. Before you approve the invoice, log the approval path. Before you change the policy, log the reason.
Timing matters: Log within 24 hours while reasoning is fresh and documents are open.
How do you separate facts from judgment?
A good decision log splits objective facts from subjective judgment.
Facts: “Vendor A quoted €5,000. Vendor B quoted €6,500. Vendor A has a 3-day delivery. Vendor B has a 7-day delivery.”
Judgment: “We chose Vendor A because speed matters more than the €1,500 difference in this case.”
This separation protects you later. When the decision turns out poorly, you show that the reasoning was sound, given the available information. You weren’t reckless. You were deliberate.
Protection mechanism: Splitting facts from judgment proves your reasoning was sound, not reckless.
How do you link supporting documents?
The log entry ought to reference the proof, not replace the proof.
Store contracts, quotes, emails, risk assessments, and approvals in a structured folder. Reference them in the log entry with a direct link or file path.
This builds a chain of evidence. The log says what was decided. The documents show why.
Without the link, the log becomes opinion. With the link, the log becomes proof.
Evidence chain: Log says what. Documents show why. Together, they create proof.
Who owns each decision?
Every decision needs an owner. The person who made the call. The person who approved the choice. The person who takes responsibility when things go wrong.
Shared ownership is no ownership. “The team decided” is not a decision log entry. “Jan approved after consulting the team.”
This isn’t about blame. This is concerning accountability. When the decision needs revisiting, you know who to ask. When the decision needs defending, you know who made the call.
Accountability rule: Shared ownership equals no ownership. Name the decision maker.
How often should you review the log?
A decision log isn’t write-only. Needs periodic review.
Quarterly review allows you to:
- Discover patterns in decision-making.
- Spot repeated issues that need structural fixes.
- Confirm that decisions are still consistent with the company’s direction.
- Verify that supporting documents are still accessible.
- Train new team members on how decisions are made.
This review takes minimal time. One hour per quarter stops weeks of reconstruction later.
Prevention math: One hour quarterly saves weeks of reconstruction later.
How do you protect the decision log?
The decision log contains sensitive information: vendor pricing, internal rationale, risk assessments, and personnel decisions.
Restrict access to authorized people. Automate backups. Follow Dutch legal requirements (minimum 7 years retention).
When the log leaks, you lose negotiating leverage. When the log disappears, you lose proof. Treat the log accordingly.
Security principle: Treat decision logs like financial records. Restrict access, automate backups, and retain for 7 years.
What are the common mistakes?
Logging too much. When every trivial choice goes into the log, you get noise. Focus on material decisions.
Logging too late. Reconstructing decisions weeks later produces fiction, not documentation.
Skipping the rationale. A log entry saying “we chose Vendor A” without explaining why doesn’t help. The value lives in the reasoning.
Using the log as a blame tool. When people fear the log, they stop using the log. The log exists to protect the company, not to punish people.
Ignoring the log during disputes. When you don’t reference the log during conflicts, the log loses credibility. Use the log or lose the log.
Pattern recognition: These five mistakes destroy log credibility. Avoid them.
What does good decision logging look like?
A well-maintained decision log gives you three outcomes:
Audit readiness. When the Belastingdienst, an insurer, or a partner requests proof, you provide it in minutes. No panic. No reconstruction. No exposure.
Internal clarity. Team members know how decisions were made and why. Disputes are resolved faster when the record exists.
Decision quality improvement. When you log decisions, you start noticing patterns. You see where you rush. You see where you over-deliberate. You see where you ignore red flags.
Research backs this up. The Journal of Systems and Software found that codebases with high-quality documentation reduce defect rates by 21% and increase productivity by 19%. The same principle applies to business decisions.
Documentation improves outcomes by forcing transparency before commitment.
Evidence-backed outcome: Documentation forces transparency before commitment, improving decision quality by 19%.
What is the decision line?
When you don’t prove a decision, you don’t own the decision. You only remember it.
Memory fades. Documents endure. The decision log is your company’s proof of deliberate operation, not reactive scrambling.
Start with one simple rule: before you close a material decision, log the decision. Date, decision, rationale, documents, approver. Five fields. Sixty seconds.
Build the control once. Save the panic forever.
Structure is cheaper than recovery.
Frequently asked questions
Do I need a decision log when I’m the only person in my BV?
Yes. The log protects you from your own memory gaps. When the Belastingdienst asks why you made a vendor choice three years ago, you need proof, not recall. Solo founders carry the same liability as larger teams.
What happens when I don’t maintain a decision log?
You face personal liability when you fail to demonstrate proper management through documentation. Dutch law holds directors personally responsible for company tax debts when records are missing or incomplete. Outside legal risk, you lose time reconstructing decisions and lose leverage in disputes.
How long does it take to maintain a decision log?
Sixty seconds per material decision. Logging right after making a decision takes less time than reconstructing decisions weeks later. Quarterly reviews take one hour and stop weeks of panic in audits.
Which decisions should I log?
Log material decisions: vendor selection over €1,000, contract changes, policy updates, financial commitments, risk acceptance, structural changes, hiring or termination, and software adoption touching customer data or financial systems. When an auditor asks about the decision, log the decision.
Where should I store my decision log?
Pick one central location: shared spreadsheet, simple database, or document management system. The tool matters less than consistency. Make sure the log is searchable, accessible to authorized users, automatically backed up, and retained for at least 7 years.
What happens when a decision turns out to be wrong?
The log protects you by showing that your reasoning was sound based on the available information at the time. Split facts from judgment in entries. This proves you were deliberate, not reckless, even when outcomes disappoint.
Can I use email as my decision log?
No. Email creates scattered records that are hard to search and easy to lose. You need one central system where all material decisions live with a consistent structure: date, decision, rationale, supporting documents, and approver.
How detailed should the rationale be?
Detailed enough to defend the decision later. Explain what factors you considered, what alternatives you rejected, and why. A log entry saying “we chose Vendor A” without reasoning doesn’t help. The value lives in the why.
Key takeaways
- Decisions living in memory create hidden liability. A decision log creates institutional memory and proof for audits, disputes, and compliance checks.
- Dutch law requires 7 years of business records. Directors face personal liability when documentation is missing or incomplete.
- Poor documentation costs organizations with 10 employees roughly €41,000 yearly in wasted time, compliance friction, and repeated debates.
- Log five elements for every material decision: date, decision, rationale, supporting documents, and approver. Takes 60 seconds.
- Material decisions include vendor selection over €1,000, contract changes, policy updates, financial commitments, and structural changes.
- Log within 24 hours while reasoning is fresh. Delayed logging produces memory distortion, not documentation.
- Use one central system. Scattered records in email, Slack, and notebooks create chaos, not control.
