When a job pack PDF says one thing and the live spreadsheet says another, the immediate question is not which file looks more official. It is which version was approved for the work.
A mismatch in a quantity, date, revision, approval status or customer instruction can affect ordering, production, site activity, invoicing and customer commitments. Treat it as a document-control issue until you can establish what happened and which artefact has authority.
Why Job Packs, PDFs and Spreadsheets Drift Apart
A spreadsheet is usually a working source. It can be edited, recalculated and updated as a job changes. A PDF is a fixed record of what was exported at a particular point in time. They can disagree when:
- the PDF was exported before a later approved change
- someone edited the spreadsheet after the PDF was issued
- the PDF came from a different copy of the workbook
- a formula, link or manual entry produced an incorrect value
- a revision or approval status was updated in one place but not the other
- the wrong document was saved, shared or printed
Neither file should automatically be treated as correct just because it is newer, fixed or held in a shared folder. The key question is whether it forms part of the approved release for that job.
If two job-pack artefacts disagree, pause affected decisions until you can identify the approved version and the source of the difference.
What to Do When You Find a Discrepancy
Start by preserving the evidence. Avoid immediately overwriting the spreadsheet or regenerating the PDF, as that can make it harder to establish how the discrepancy reached site, purchasing or the customer.
1. Record the Exact Difference
Capture the details of the mismatch, including:
- job number and pack identifier
- workbook file name and location
- PDF file name and location
- revision labels shown on each artefact
- the affected fields, rows, cells or PDF pages
- who found the issue and whether anyone has acted on it
- dates and times shown in the available file history or approval records
Be specific. “The pack is wrong” is difficult to investigate. “Job 1842 shows 40 units in the PDF and 48 units in the current approved worksheet” gives the team something concrete to trace.
2. Classify the Type of Difference
Not every discrepancy has the same consequence. Separate the visible difference into a useful category:
| Discrepancy type | Example | Why it matters |
|---|---|---|
| Value | Quantity, total or rate differs | May affect ordering, work or invoicing |
| Date | Delivery, installation or completion date differs | May affect programme commitments |
| Status | One file says approved and the other does not | May affect whether work should proceed |
| Revision | Files refer to different revisions | May indicate an outdated pack is in use |
| Identifier | Job number, customer name or item code differs | May create a traceability problem |
| Presentation | Pagination or spacing differs, but values match | Usually lower risk, but should still be understood |
A changed quantity, unit, date, approval status or safety-related instruction is usually more significant than a harmless layout difference. Record both, but do not handle them in the same way.
3. Trace the Disputed Field Back to Its Source
Work backwards from the field that differs. Check whether the spreadsheet value comes from a formula, a linked workbook, a manual input or a copied value. Establish whether the PDF was generated from the same workbook revision that is now under review.
Useful checks include:
- whether the relevant spreadsheet cell contains a formula or typed value
- whether nearby rows use a different formula pattern
- whether external workbook links or imports are involved
- whether there are hidden rows, sheets or named ranges affecting the result
- whether the workbook contains a revision record or approval marker
- whether the PDF was exported from a local copy rather than the controlled file
The aim is not simply to find a number that looks plausible. It is to establish the path from approved input to issued document.
4. Decide Which Artefact Has Authority
The latest timestamp is not necessarily the approved instruction. A recently edited workbook may be a working copy, while an earlier PDF may be the document formally issued to site or a customer.
Use the evidence around each artefact to decide authority. Look for a clear job identifier, revision reference, approval record, named owner and evidence of issue. If the difference relates to scope, specification or status and authority is unclear, send both artefacts and the recorded discrepancy to the person responsible for the decision.
Do not resolve an ambiguous difference by quietly choosing the file that is easiest to amend.
A Practical Reconciliation Check
For recurring job packs, define the fields that must be checked before issue. This is more reliable than asking someone to compare two documents visually and confirm that they appear similar.
| Field | Suggested control |
|---|---|
| Job ID and customer | Must match exactly |
| Revision and issue status | Must match the approved release record |
| Dates | Confirm against the authorised programme or instruction |
| Quantities and totals | Check against the approved source calculation |
| Units and descriptions | Check that labels and values agree |
| Approval information | Confirm the correct status is shown before issue |
Keep an exception record where a mismatch is found. It should state the spreadsheet value, PDF value, reason for the difference, decision made and person responsible. This provides a useful trail if the same issue is queried later.
Correct and Reissue, Rather Than Replace History
If a genuine error is confirmed, correct the approved source, create a new controlled revision and make the replacement clear to affected recipients. Retain the earlier artefacts and record why they were superseded.
Simply replacing a PDF in a shared folder can leave people working from downloaded, printed or emailed copies. A controlled reissue makes the change visible and gives the team a clear answer when asked which version should be used.
When Spreadsheet Controls Are Still Suitable
Excel remains useful for modelling, forecasting, ad-hoc analysis and flexible calculations. A spreadsheet can also remain appropriate for a job-pack process where changes are infrequent, responsibility is clear and the team can reliably control revisions and issue documents.
However, document control becomes harder when a recurring workflow involves several people, repeated approvals, changing job information and multiple handoffs between office, purchasing, production, site and accounts.
Warning signs include:
- staff regularly checking which file is current
- multiple local or emailed workbook copies
- repeated manual copying between the spreadsheet and job pack
- uncertainty about who can approve a change
- PDFs being regenerated without a clear revision trail
- teams spending time reconciling documents before acting
These are not necessarily signs that the spreadsheet is badly made. They may show that a working file is being asked to carry a repeatable operational process with more control requirements than it can comfortably support.
For a broader view of when a business process may have outgrown its workbook, see how to replace Excel.
Moving from File Reconciliation to Workflow Control
Where the same discrepancies recur, the long-term issue is often not the individual PDF. It is the gap between the live operational data, approval decisions and issued documents.
A managed custom web application can be a better fit where a business needs a repeatable process rather than a collection of files to reconcile. The goal is to make the workflow clearer, so the operational record, its status and the documents used by the team are managed as part of the same process.
Spreadsheet Upgrade builds fully managed custom web applications to replace business-critical operational Excel workflows. This can be relevant for job tracking, order management, production planning, approvals, inspections and other processes where teams need more dependable operational control than separate spreadsheet and PDF versions can provide.
The right approach depends on the workflow, the consequence of an incorrect release, the number of handoffs and the controls your team needs. It does not depend solely on company size, workbook size or how many people currently use the file.
For current commercial information, see pricing.
Start with the Current Mismatch
For the discrepancy in front of you:
- Preserve the spreadsheet and PDF as found.
- Record the exact fields that differ.
- Trace the values and revision history.
- Establish which artefact was approved for use.
- Correct and reissue through a clear revision process where necessary.
- Review whether repeated reconciliation is masking a workflow-control problem.
If an important spreadsheet has become central to how your business runs, a Free Fit Check can help you decide whether replacing that operational workflow is worth exploring.