Version control for calculation spreadsheets

Your best calculation methods are getting lost in project folders nobody searches. Your team keeps rebuilding IP they already have.

GitCalc is where your team's IP lives and learning compounds.

Berth 7, Quay Wall Design · diff

v4v5

	A	B
1	Design wave Hs	3.20
2	Safety factor	1.50
3	Wave load	=B1B2Cd

Signal · formula changedNoise · inputB3 method updated · B1 is project data

The problem, stated the way you already feel it

Your firm tried to move off spreadsheets. It didn't work.

The calcs are where the real engineering judgement lives, and no platform has ever been good enough to replace them. So the spreadsheets stay, and they stay ungoverned.

Your most valuable IP, the methods your practice runs on, has no version history, no record of what changed or why, and no way to tell an improvement to the method from a number someone typed in for one job. The knowledge from every iteration evaporates. Your QA is signatures and PDFs bolted onto files nobody version-controls.

You don't need to leave the spreadsheet. You need to govern it where it lives.

How it works

The spreadsheet stays. The knowledge stops leaking.

Grab the current version soon

Every calc has one authoritative version your team pulls from. No more hunting through folders for the file with the most _FINAL suffixes.

Push back what you actually used

When a project tweaks a calc, that version goes back into GitCalc as a new version. The method captures the iteration instead of losing it.

See what really changed

GitCalc separates a change to the method (a formula, the calculation logic) from a change to project data, the inputs for one job. Method changes surface. Data entry recedes. You see at a glance whether someone improved the calc or just ran it on a different site.

Green your inputs, and it gets sharper

Mark input cells green, the convention good spreadsheets already follow, and GitCalc treats them as project data so the method changes stand out cleanly. It works without it; it's precise with it.

Sign off when it's clean soon

A checked, approved version is marked QA'd. Grab a QA'd version and you're on solid ground. Take an unQA'd fork and you can; you just record what you did and what you checked. Deviation is allowed. It just has to be owned, the way real engineering already works.

Download is always the real file

GitCalc stores your exact spreadsheet and gives it back byte-for-byte. Formulas, named ranges, macros and formatting are never touched, because GitCalc never rebuilds your file. It keeps it.

Why it's different

You've seen tools that touch parts of this. Here's where GitCalc isn't them.

not a spreadsheet replacement

Tools that move your calcs into a browser environment ask your engineers to abandon Excel. They won't. GitCalc comes to the spreadsheet instead of replacing it.

not Git for your team

Excel version-control that runs on Git assumes your engineers will commit, branch and push. They never will, and those tools don't know a method change from a project input anyway. No Git, no migration, nothing new to learn.

not a desktop diff utility

Comparing two files on your machine tells you what changed once. It doesn't store your history, hold your team's source of truth, or produce a record you can stand behind.

not enterprise surveillance

Governance platforms watch your spreadsheets from above and sell to a compliance department over months. GitCalc is a tool an engineer adopts on a Tuesday, where the governance falls out of doing the work.

Who it's for

Engineering practices where the calcs are the intellectual property.

Where the honest answer to “where's the current version of this method, and what changed since last time” is a shrug and a shared drive. If your firm has ever tried to wean itself off spreadsheets and quietly failed, GitCalc is built for exactly that reality.

Start with one calc