Legacy Excel VBA Code Audit
Budget: $250 – $750 USD
I have a large, business-critical Excel workbook that relies on old-school VBA macros. The original author is long gone, so before I touch anything I need a clear, developer-ready map of what the code is doing. My sole goal right now is maintenance, not new features.
Scope
• Walk through every macro, subroutine, and function, with special attention to the data-processing logic that drives our financial calculations and the built-in data-validation steps.
• Identify how data flows between sheets, modules, and any external references (files, databases, add-ins).
• Flag any risky practices—hard-coded paths, implicit conversions, unhandled errors—so I know where to focus future refactoring.
Deliverables
1. A well-structured technical document (Word or Markdown) that explains:
– Overall architecture of the workbook
– Detailed breakdown of each module and procedure
– Call hierarchy diagrams or flowcharts for the financial-calculation and validation routines
2. The original VBA code annotated with clear, maintainable comments (either inline or in a separate commented copy).
3. A short read-out highlighting quick wins or critical issues I should address first.
Acceptance Criteria
• I can open the document and instantly trace any financial-calculation or data-validation path from start to finish.
• All external dependencies are listed and verified.
• No functional changes have been introduced—just documentation and comments.
You are free to use tools such as the VBA IDE, Rubberduck, or any static-analysis utilities, but everything must run client-side; I cannot send the workbook to a cloud service.
Scope
• Walk through every macro, subroutine, and function, with special attention to the data-processing logic that drives our financial calculations and the built-in data-validation steps.
• Identify how data flows between sheets, modules, and any external references (files, databases, add-ins).
• Flag any risky practices—hard-coded paths, implicit conversions, unhandled errors—so I know where to focus future refactoring.
Deliverables
1. A well-structured technical document (Word or Markdown) that explains:
– Overall architecture of the workbook
– Detailed breakdown of each module and procedure
– Call hierarchy diagrams or flowcharts for the financial-calculation and validation routines
2. The original VBA code annotated with clear, maintainable comments (either inline or in a separate commented copy).
3. A short read-out highlighting quick wins or critical issues I should address first.
Acceptance Criteria
• I can open the document and instantly trace any financial-calculation or data-validation path from start to finish.
• All external dependencies are listed and verified.
• No functional changes have been introduced—just documentation and comments.
You are free to use tools such as the VBA IDE, Rubberduck, or any static-analysis utilities, but everything must run client-side; I cannot send the workbook to a cloud service.