PDF vs Excel vs Word vs JSON: Choosing the Right Export

You have finished the estimate. The math is right, the assumptions are documented, and now it has to travel — to a client, an accountant, a bid platform, or your own archive. This is the moment most estimators stop thinking, hit “PDF” out of habit, and hope for the best. That habit quietly costs you: a proposal that arrives as an editable spreadsheet looks unfinished, a bid that arrives as a locked PDF frustrates the estimator who needs to load it, and an estimate with no backup means retyping everything when the client asks for a change.

The format is not an afterthought. It is the difference between numbers that land intact and numbers that get mangled in transit. ConstrCalc exports as PDF, Excel (XLSX), Word (DOCX) and JSON, and each exists for a specific job. Here is how to choose.

PDF — to present and to lock

Use for: client-facing proposals, formal bids, anything attached to an email, and anything destined for print. A PDF renders identically on every device and is not casually editable, which is exactly what you want when the document represents a commitment. When you send a price to a client, you want them to see the price you set — not a version someone nudged in a spreadsheet cell. PDF is your presentation and your paper trail.

Excel (XLSX) — to compute and to reconcile

Use for: your accountant, your cost controller, and any bid platform that ingests tabular data. Excel is a working format: the recipient can sort, filter, pivot and reconcile the line items against their own systems. If the person on the other end needs to do arithmetic with your numbers, send Excel. Sending them a PDF forces a re-key, and every re-key is a chance to introduce an error into your carefully checked figures.

Word (DOCX) — to narrate

Use for: long-form RFP responses and proposals where the cost estimate is one section inside a larger written argument. Public tenders and institutional clients frequently want context, methodology and terms wrapped around the numbers. Word lets the estimate live inside that narrative, formatted to match the surrounding document, in a way neither PDF nor Excel is designed to support.

JSON — to back up and to re-load

Use for: your own backup, version control, and re-loading an estimate into ConstrCalc to keep editing later. JSON is a structured snapshot of the estimate’s underlying data — not a document for a client, but a working file for you. Reload it and every input, quantity and rate returns exactly as you left it, ready to revise. Think of it as the source file behind the deliverables.

At a glance

Construction planning insights

Treat exports as a small workflow, not a single click. On a live project an estimate is rarely final on the first pass — clients revise scope, quantities shift, rates update. Build a habit that survives those revisions:

• Keep JSON as your source of truth. The PDF and Excel are outputs; the JSON is the estimate. Lose the JSON and you lose the ability to revise cleanly.
• Match the format to the reader’s next action. Ask what the recipient will do with the file. Present, compute, or narrate — the answer picks the format.
• Version deliberately. Name exports with a revision marker so the client and your own records never disagree about which estimate is current.

A workflow tip worth building in

Before you send any client-facing PDF, export a JSON snapshot first. It takes a second and it changes everything about how revisions feel. When the client comes back with changes — and they will — you reload the JSON, adjust, and re-export a fresh PDF in minutes, with no retyping and no risk of transcription error. Estimators who skip this step end up rebuilding estimates from a flattened PDF, which is slow and dangerous. The snapshot is cheap insurance against the most common time-sink in reporting.

Global construction standards

Format expectations vary by market and client type, so read the room. Public-sector and institutional tenders across most countries specify a required submission format — frequently PDF for the binding offer, sometimes Excel for a priced bill of quantities, occasionally a portal that ingests structured data directly. Private clients are often more flexible but still form an impression from the format: a polished PDF reads as professional; a raw spreadsheet reads as a draft. Whatever the market, the principles hold — PDF to present, Excel to compute, Word to narrate, JSON to preserve. For the reporting features in context, see the platform Features and the Knowledge Center Planning Guide.

Professional tips

• Never send your only copy as a PDF. Keep the JSON; the PDF is a snapshot, not a source.
• Respect the client’s systems. If they run cost control in Excel, meet them there rather than forcing a re-key.
• Lock what should be locked. Binding prices belong in PDF, where a stray keystroke can’t change them.
• Standardise your export routine. JSON snapshot, then the client format — the same two steps on every job build a reliable, auditable trail.

Frequently asked questions

Should I send an estimate as PDF or Excel?

PDF when it is a client-facing proposal or a bid you want presented exactly and not casually edited. Excel when the recipient needs to work with the numbers — accounting, cost control, or a bid platform. PDF to present, Excel to compute.

Why export a JSON file?

JSON is a structured backup of the estimate itself. It lets you reload and revise later without retyping and acts as a lightweight version snapshot. It is a working file for you, not a client deliverable.

When is Word the right format?

When the estimate is one section of a larger narrative document, such as a formal RFP response or a proposal with substantial written content around the numbers.

Conclusion

There is no single “best” export — there is only the right format for where the estimate is going. Present with PDF, compute with Excel, narrate with Word, and preserve with JSON. Build the small habit of snapshotting to JSON before every send, match the format to what the reader will do next, and your carefully built numbers will arrive intact, look professional, and stay easy to revise. The math earns the job; the format makes sure it survives the trip.