Paper Job Sheets Are a Math Problem.
Here's How to Solve It in One Step.

The Math Problem Inside Every Paper Job Sheet

A technician finishes a service call. They grab the paper job sheet off the clipboard, scribble down what they did — 2.5 hours of labor, replaced a capacitor ($38.50), added two pounds of R-410A ($42/lb), a service call fee. They get the customer's signature and move on to the next call.

At the end of the day, those sheets land on a desk in the office. Someone — a dispatcher wearing a billing hat, the owner working late, a part-time bookkeeper — picks up the first one and starts doing math:

This is the math problem hiding in plain sight. Not a complicated one — multiplication and addition, nothing beyond middle school arithmetic. But when you do it 30 times in a row at 7pm on a Thursday, the fourth digit of a part number starts to blur. A misplaced decimal point costs you money. A forgotten markup costs you margin.

The American Productivity & Quality Center (APQC) benchmarks manual invoice processing at an annual error rate of around 2%. For a field service company processing 500 jobs a month, that's 10 jobs with calculation errors every month — overcharges that generate dispute calls or undercharges you never catch. And as one plumbing business owner put it on Reddit's r/Plumbing: "The biggest pain point I hear about isn't really dispatching, it's tracking what jobs actually made money after materials and time."

The data extraction step — reading the job sheet and getting numbers into a spreadsheet — is only half the work. The other half is doing the math on those numbers. And for most small service businesses, the math still happens inside someone's head, on a calculator, or in a spreadsheet formula that has to be re-created for every batch.

What Computed Columns Bring to the Equation

Most document extraction tools are built to extract — they find data on the page and place it into spreadsheet cells. You tell them to look for "hours worked" and "hourly rate" and they'll dutifully pull those numbers out of every job sheet. What they won't do is multiply them together. That part is left to you, in Excel, after the extraction is done.

Computed columns change that division of labor. They let you define the calculation before extraction happens, so the AI performs the math at the same moment it reads the document. Instead of extracting Hours and Rate into two columns and then creating a third column with a formula, you define one column that does both:

This isn't a post-extraction formula applied to already-extracted data. It's an extraction-time computation — the AI reads the document, finds the relevant fields, performs the math, and outputs the result as the cell value. There is no second step.

Two ways to define these computations exist. The column name method — writing the math directly into the column header like Line Total (Qty × Unit Price) — works immediately in the demo, no login required. The Rule Format (available to logged-in users) lets you keep column names clean while defining multi-step computation logic in a JSON rule behind the scenes — useful when a single result depends on three or four extracted fields across different parts of the document.

But the real advantage for field service isn't the technology. It's what happens to the end-of-day routine. That five-step calculation chain — hours × rate, materials × markup, sum, tax, total — collapses into a single action: upload the job sheet photo, name your columns, and download the result.

Setting Up Your First Job Sheet Calculation

Let's work through a real example. A technician hands you a paper job sheet from a residential AC repair. The sheet has handwritten entries for:

• Date: 6/23/2026
• Technician: Mike
• Customer: Johnson Residence
• Work performed: Condenser fan motor replacement
• Labor: 1.75 hours
• Labor rate: $85/hr
• Materials: Fan motor — $142.00
• Material markup: 30%
• Service call fee: $79

You want the output to contain the billable amounts — not just the raw numbers from the sheet, but the calculated line items that go directly onto the customer's invoice. Here's how you'd set up the columns:

Upload the photo of the job sheet, enter those column names, and the output is a row in your spreadsheet where every number is already a billable amount — not a raw input waiting for a formula. The "Subtotal" column doesn't reference cells B2×C2 from this specific document the way an Excel formula would. It references the semantic meaning of "Labor Cost", "Material Cost", and "Service Call Fee" — concepts the AI can locate on any job sheet regardless of where the tech wrote them.

This is the difference between position-based formulas (which break when the layout changes) and semantic calculations (which survive layout changes because they reference meaning, not coordinates). If Mike writes the labor hours in the top-left corner on one sheet and the bottom-right on the next, it doesn't matter. The AI finds "1.75" and "85" by understanding what they represent, not where they sit.

The Five Calculations Every Job Sheet Needs

Across HVAC, plumbing, electrical, and general field service, most job sheets boil down to the same handful of mathematical operations. Here are the five that cover the vast majority of billing scenarios, with the column names you'd type to make each one work:

1. Labor Cost = Hours × Rate

The foundation of T&M (Time and Materials) billing. If every tech has the same rate, it's straightforward. If rates vary by tech or job type, you can encode that:

2. Material Cost = Unit Cost × Quantity × Markup

Materials need to be billed at a marked-up price, not your wholesale cost. The markup percentage depends on your business — 15-35% is typical according to NetSuite's T&M contract guidelines.

3. Subtotal = Labor + Materials + Fees

4. Tax = Subtotal × Tax Rate

5. Total = Subtotal + Tax

Five calculations. One extraction pass. The AI finds the raw numbers on the job sheet, performs the arithmetic, and delivers a row where every cell is a finished billing value. The column names are the specification — you define what you want, and the AI figures out how to compute it from whatever the tech wrote down.

What makes this fundamentally different from creating formula columns in Excel is that the computation definition is portable. Once you've defined Labor Cost (Hours × Rate) as a column, it works on every job sheet in the batch — whether the tech's handwriting is neat or messy, whether the hours field is in the top-left or buried in a comment box. In Excel, your =B2*C2 formula is anchored to the specific cell positions of this document's layout. Change the layout and the formula silently breaks.

From One Job Sheet to Fifty — What Batch Processing Changes

The power of computed columns becomes visible at scale. Consider a typical week for a small HVAC shop with four technicians, each running five calls a day. That's 20 job sheets per day, 100 per week. If each sheet requires the five-step manual calculation chain described earlier, the office is doing 500 separate arithmetic operations per week — and that's assuming no errors, no corrections, no callbacks to techs asking "what does this number mean?"

With batch processing and computed columns, the workflow compresses to:

A week's worth of job sheets — 100 rows, seven columns, 700 cells — and every one of them contains a finished number. Not "hours: 1.75, rate: 85" in two separate cells waiting for a formula. Not a column of raw material costs that need to be multiplied by 1.30. Finished numbers. The spreadsheet is the invoice-ready output, not the input to another round of manual work.

For a business currently spending 15 minutes per job sheet on manual calculation (the benchmark for manual HVAC invoicing is 15 minutes per invoice), that's 25 hours of office time per week reclaimed. At an office staff rate of $25/hour, that's $625/week saved on calculation labor alone — before accounting for the errors you're no longer making or the dispute calls you're no longer fielding.

Why the Pen-and-Paper Habit Doesn't Need to Change

A common assumption in field service digitization is that you need to get technicians off paper entirely — replace paper job sheets with mobile apps, digital forms, tablet-based checklists. That's a fine long-term goal, but it's also a heavy lift. It requires buying devices, training techs who've been writing on paper for 20 years, dealing with broken screens and dead batteries on job sites, and managing an IT procurement and rollout that has nothing to do with fixing air conditioners.

The computed column approach doesn't ask technicians to change their workflow at all. They keep the clipboard. They keep the pen. They keep writing down hours, parts used, customer name, work description — exactly as they've always done. The change happens after the paper leaves their hands:

The paper stays. The clipboards stay. The math — the 500 arithmetic operations per week, the 10 calculation errors per month, the 15 minutes per invoice — that part goes away.

This is worth underlining because it's the opposite of what most field service software asks of a business. ServiceTitan, Jobber, Housecall Pro — these are powerful platforms, but they require every technician to use a mobile app. For a five-tech shop where two of the techs still use flip phones, that's a non-starter. Computed column extraction from paper job sheets gives you the billing automation without the device rollout. The techs keep doing what they're good at. The office stops doing math by hand.

FAQ

What if different technicians have different hourly rates?

Write the rate on the job sheet itself — each tech notes their rate alongside their hours. Use the column name Labor Cost (Hours × Rate) and the AI reads both values from each sheet, applying the correct rate per technician per job. If rates are standardized and you want to embed them in the column definition instead, use a fixed multiplier like Labor Cost (Hours × 85).

Can this handle handwritten job sheets?

Yes. The AI reads handwriting — printed and cursive — and understands the semantic meaning of fields even when penmanship varies between technicians. The key is that the AI isn't doing character-by-character OCR and then hoping the letters spell a number. It's interpreting the document holistically — it sees a block of scribbled text next to a dollar amount next to the word "capacitor" and understands this is a material line item with a cost, even if the handwriting is rough.

What if the markup percentage changes between job types — 30% for residential, 20% for commercial?

If the markup is written on each sheet, use Material Cost (Cost × Markup) and have the tech note the applicable percentage. If markups are standardized per job type, process residential and commercial batches separately with different column definitions, or use Inferred Columns — define a column like Job Type (options: Residential / Commercial) and another like Markup Rate (If Job Type = "Residential" then 1.30, else 1.20). The AI reads the job sheet, classifies the job type, and applies the correct markup in a single pass.

Does this work with photos taken on a phone?

Yes. Phone photos of paper job sheets work as input. The AI handles uneven lighting, slight angles, and shadows. For best results, flatten the sheet on a desk and hold the phone directly above it — but even a quick snap on the truck hood works in most cases.

How many job sheets can I process at once?

Batch uploads handle dozens or hundreds of files in a single queue. Free users can test with a limited number; paid plans scale up with monthly processing quotas. The $9/month Basic plan covers light weekly use; the $19/month Pro plan handles daily batch processing for a multi-tech operation.

What if a technician forgets to write down a field — like the service call fee?

If you use a fixed service call fee across all jobs, embed it in the column definition: Subtotal (Labor Cost + Material Cost + 79). The $79 becomes part of the calculation rule and doesn't need to appear on the sheet at all. The AI adds it to every job automatically. This is one of computed columns' underrated strengths — fixed parameter references. Numbers that live in your business rules (tax rates, standard fees, flat trip charges) don't need to be written on every sheet. They're encoded in the column definition once and applied consistently across the entire batch.