Skip to content
Practice & rollout

Digitisation in the trades: jobs and site reports, paperless

Job intake, measuring, site reports, hours and invoicing: how trade businesses capture work on site without the paper note winning, and what fitters adopt.

15 min read HandwerkMobile ErfassungRapportStundenerfassungAuftragsabwicklung

A trade business handles every job several times over: when the call comes in, when it is scheduled, when the work is measured on site, when the report is written up after hours, when hours are collated at month end and finally when the invoice goes out. Along the way the same piece of information changes carrier repeatedly, from a spoken request to a notepad, from the pad to the planning board, from the timesheet to the job folder, from the folder to the billing run. In this setting digitisation rarely means one new piece of software for everything. It means capturing information in structured form exactly where it first arises, and deriving everything else from that. This article walks through the job route station by station, names the points where time and evidence are typically lost, and describes the conditions under which fitters genuinely use mobile capture. The decisive hurdle is not the technology but the direct comparison with a paper note: anything that takes more effort on site than a sheet of paper will not be adopted, however convincing it looks in the office.

Key takeaways

  • The job route in the trades consists of six stations — intake, scheduling, work on site, site report, materials and billing; what matters is not their number but how often the same information is rewritten along the way.
  • Mobile capture only takes hold if it costs less effort on site than a paper note: pick lists instead of free text, presets drawn from the job, capture without a signal, and an entry finished in roughly ninety seconds (project experience).
  • As long as paper and app are both permitted, paper wins; the switch therefore needs a defined cut-off date per crew rather than an open-ended transition period with two parallel routes.
  • The largest measurable effect lies not in typing time but in the lead time from work performed to invoice issued, because queries about quantities, extra work and hours disappear once everything hangs on the job.
  • The side benefit is a sound evidence base for handover and warranty: defect claims on work performed on a building are subject to a five-year limitation period (German Civil Code, section 634a), so photos, quantities and signatures must remain findable for that long.

The job route in the trades: six stations, one case

Whatever the trade, a job passes through the same stations. It comes in, gets scheduled, is carried out and measured on site, is reported back, consumes material and is invoiced. Every station produces information the next one needs: no site address, no schedule; no quantities, no invoice; no hours, no job costing. The difference between a well organised and a poorly organised business does not lie in the number of these stations, which is the same everywhere, but in how often the same information is rewritten from one carrier to the next along the way, and how long it stays invisible in transit.

Paper is not a sign of backwardness here; it is a remarkably good tool. A note needs no battery, no login and no network, it works with work gloves on, in the rain and in a basement with no reception, and it folds into a trouser pocket. Anyone introducing mobile capture is competing with that tool, and not in a meeting room but on a ladder, in a boiler room or on a roof. Paper disappears only when the digital route is faster in that exact place, not when it looks better in the office.

For an assessment it pays to trace a single typical job from intake to payment and to note at every point who copies which piece of information from which source. How that plays out across trades and job types is set out in our overview of work in the trades sector. The sections below take the stations one at a time.

  1. Job intake. Customer, site, contact on site, job type, urgency, agreed scope. Anything missing here gets chased by phone later on.
  2. Scheduling. Who travels where and when, with which vehicle, which qualification and which material already loaded.
  3. Work and measurement on site. Positions carried out, quantities, extra work, obstacles, photos before and after.
  4. Site report. The feedback that turns work into a billable case: times, quantities, material, signature.
  5. Material call-off. What came from the store, the van or straight from the wholesaler, and which job it belongs to.
  6. Billing. Check, approval, invoice, handover to accounting and the job costing that shows whether the work carried itself.

Job intake: what is missing here is missing all the way to the invoice

Most jobs in the trades start verbally, over the phone, in passing on a site or as a callback to voicemail. What gets recorded is what the caller happens to mention, and that is rarely complete. Regularly missing: the exact site address including entrance and floor, a contact with a phone number who will actually open the door, the type of installation or component involved, the agreed cost framework, and whether this is time-and-material work, a fixed price, a maintenance contract or a warranty case. Every gap generates a call later, and every call costs time twice: for the fitter waiting and for the office searching.

The most effective change at this station is not a new system but an intake form with mandatory fields per job type. Whoever records a fault has to state the installation, the access and how to reach someone; whoever records a maintenance visit has to select the contract and the interval. Free text fields remain available, but they do not replace structured entries, because neither scheduling nor billing can be derived from prose. The effort for the person on the phone rises by a few seconds, while queries later in the process drop noticeably (project experience).

The second lever is the site record. Trade businesses return to the same buildings for years. If access details, installed components, earlier jobs and contacts hang on the site rather than on an individual job, intake only requires finding the site; everything else is prefilled. That shortens the call noticeably and improves the quality of the data at the same time, because it is not re-elicited from scratch each time.

Decide the job type early

Whether a job runs on a time-and-material basis, at a fixed price, under a maintenance contract or as warranty work determines what has to be captured on site. Time and material demands detailed hours and material quantities, a fixed price mainly evidence of completion, warranty work above all sound documentation of the cause. If the job type is only clarified at invoicing, precisely those details are missing that nobody can gather after the fact.

Scheduling: one view instead of three lists

In many businesses the schedule exists three times over: as a magnetic board in the office, as individual calendars, and as knowledge in the head of the supervisor who knows which crew is familiar with which site. As long as all three versions agree, this works. They agree as long as nobody falls ill, no material is missing and no customer cancels. Precisely when replanning is needed, they diverge, and the crew in the van learns about the change by phone while already driving towards the old destination.

A digital schedule does not need to run an optimisation model for that. It needs to do four things: make the current state visible to everyone, allow changes without re-entry, take in feedback from site and show which jobs are being left behind. The most common mistake here is too fine a grid. Scheduling trade work in quarter hours schedules past reality; half days or whole days are more robust and therefore actually maintained.

One leading schedule

There is exactly one version of the schedule, and it lives where the job lives. Side lists are fine as long as they are produced from the schedule rather than maintained alongside it.

Assignment instead of shouting

Every job has a responsible crew and a date. Jobs without an assignment are visible immediately and no longer surface only when the customer calls to ask.

Changes actually arrive

If the office moves an appointment, the crew sees the new state on the device. A phone call remains possible but is no longer the only channel carrying a change.

Coarse grid, honest buffers

Plan in half days, with travel time included and a fixed allowance for callouts. A schedule that only works on days without incidents stops being maintained after two weeks.

Measuring and site reports: the core of the job route

The site report is the point where work performed becomes a billable case. It ties together four things that otherwise stay apart: the work carried out with quantities, the time spent, the material consumed and the evidence that it happened this way. If one of them is missing, rework follows, usually in the office, usually days later, usually as a query to somebody who is now on the next site and no longer remembers the details.

The classic sequence looks like this: the fitter notes times and material on a printed form, the sheet stays in the van, reaches the office on Friday or at month end and is typed up there. In such businesses several days often pass between the work and the recorded report (project experience). During that time the job is invisible to everyone else: the customer cannot be informed, the invoice cannot be written, the job costing cannot be calculated. And if the sheet is illegible or missing, reconstruction begins.

Mobile capture reverses that order. The details are created where they arise anyway, at the moment they are reliably known. A photo of the situation before the work, the quantities against positions prefilled from the quotation, a photo afterwards, the contact signing on the device. As soon as the van has a signal again, the report is in the office. Technically this is not demanding; the difficulty lies entirely in the handling.

A site report that takes longer on site than the paper form does not get captured, it gets written up in the evening. At which point it is what it was before: a recollection.

Principle from rollout projects in the trades (project experience)

For measuring there is an additional rule: quantities have to be captured as structured values, not as text. A length, an area, a count belong in a numeric field with a unit and a reference to a position from the quotation. Only then can the invoice be produced from it, and only then can somebody later retrace how a total came about. Where measurement sheets are in use, prefilling from the quotation helps most: the positions are already there, and only the actual quantity and any deviation need to be entered.

What fitters actually adopt

Adoption of mobile capture is not a question of attitude and rarely a question of age. It is a question of ergonomics on site. A device gets used when it can be operated with one hand, when it does not reload after every step, when it does not demand a login with a long password, and when the entry is finished quickly. Around ninety seconds per report has proved a workable threshold (project experience); anything longer gets bundled, written up later or skipped.

It matters just as much that capture gives something back. If the fitter can see on the device what was done at this site last time, which component is installed and how access works, the app is not merely a reporting duty but a tool. In our experience this return decides usage more strongly than any instruction. The reverse also holds: introduce a capture system whose only visible purpose is monitoring how fast people work, and you will get formally completed fields and no substance.

ConditionWhere it fails in daily workWhat carries instead
Fast entryFree text fields that have to be filled in on site using an on-screen keyboardPick lists, presets from the job, quantity fields with units
AvailabilityBasement, new build or rural area with no mobile coverage, capture breaks offFull capture offline, automatic sync at the next connection
A single routePaper and app both permitted, everyone decides for themselvesOne cut-off date per crew, after which the paper form is no longer accepted for billing
Device and handlingPrivate phone, small buttons, operation only possible with both handsCompany device with enough screen area, large targets, usable with gloves
Visible purposeCapture feels like monitoring, nothing ever comes backSite history, material status and job documents can be viewed on the device
SupportOne briefing in the break room, responsibility unclear afterwardsBriefing on a real job, a named contact in the business for the first few weeks

Time capture: obligation, practice and the write-up problem

Recording working time is no longer optional in Germany. The Federal Labour Court has ruled that employers are obliged to introduce a system for recording working time; the requirement is derived from occupational safety legislation, while the precise statutory form remains a matter for the legislator. Sector-specific record-keeping duties and collective agreements apply on top. How these requirements translate into a particular business is a matter for employment law advice; this article covers only the organisational side.

Organisationally, the widespread practice of writing up hours at month end from memory or from a stack of notes is problematic for two reasons. First, written-up times get smoothed: round figures appear, travel time vanishes, short pieces of extra work fall away. Second, the link to the job is missing. A total of hours without a job reference may satisfy payroll, but it is useless for job costing, which means the business does not know which type of work actually carries itself.

The workable route is coupling to the site report: whoever starts and ends the job on the device produces the time as a by-product. It is captured once and used twice, for payroll and for job costing. What matters is separating travel time, set-up time and breaks cleanly, because they are treated differently. And there has to be a defined correction path: subsequent entries must be possible while remaining identifiable as such.

Capture once, use several times

The strongest effect comes not from making a single entry faster but from it happening only once. Time, quantity, material and evidence arise in the same act on site and are then reused for scheduling, payroll, invoicing and job costing. Every additional list maintained alongside cancels that effect out again.

Material call-off: the van is a warehouse too

Material leaves the business by three routes: from the store, from van stock, or straight from the wholesaler to the site. The third is the most convenient and the most expensive to trace, because the delivery note stays in the van and the link to the job is only attempted when the supplier invoice is checked. The second is the most invisible: what sits in the van has usually already been booked out of the inventory system even though it is still there. Both mean material costs do not attach to the job.

Full van stock management with stocktaking is too much effort for most businesses. The minimally invasive route is different: consumption is recorded against the job, not against the store. When writing the report, the fitter picks the installed articles and quantities from a short list tailored to the trade. Two things then follow automatically, the material line on the invoice and a replenishment requirement for the van. Stock is not tracked exactly, but the costs land on the right job, which is the point.

Illustrative sketch: a site report record as it arises on site
Job:        A-2026-04187   Site: apartment building, entrance B
Job type:   time and material
Crew:       crew 3, two people

Time        start 07:45   end 12:10   travel 35 min
Work        position 2.4 from quotation, quantity 18.50 m
Material    pipe DN 20, 12 m       (van stock)
            seal kit, 4 pcs        (van stock)
Evidence    3 photos: before, during, after
Handover    signature of site manager, 12:08
Note        extra work: wall opening, released verbally on site

Transfer to the office: automatic as soon as a signal is available
Status: captured on site, supervisor approval pending

Invoicing: the report becomes the document

The hardest figure in the trades is not entry time but the lead time from work performed to invoice issued. It governs liquidity, and it depends almost entirely on the quality of the site report. If the report is complete, invoicing is an approval. If it is incomplete, a chain of queries, appointments with the supervisor and searches begins that stretches the case by days or weeks.

An approval step still makes sense. Not everything captured on site goes to the customer unchanged: extra work has to be marked as such, goodwill has to be decided, deviations from a fixed price have to be explained. The difference is that the approval now builds on complete information rather than consisting of gathering it. Approval means deciding, not researching.

The handover to accounting should then not be manual again. Whether through an interface to the accounting system or through an agreed data exchange with the tax adviser, invoice data should leave the business exactly once. On top of that comes the change of format for invoices between businesses: the requirements for structured electronic invoices follow from German VAT legislation and apply in stages, and which stage applies to a particular business is best clarified together with the tax adviser.

Are times, quantities, material and evidence present? Missing details are clarified the same day, while the memory still holds, not at month end.

Evidence and warranty: the side benefit that counts later

Mobile capture is usually justified by time savings. The benefit that often turns out to be the greater one is different: a sound evidence base. If photos of the condition before the work, the measurements, the installed components with batch or serial number, the fitter's notes and the signature at handover all sit on the job, you can demonstrate years later what was carried out and in what condition things were found. That is exactly the question that matters in a dispute.

The periods involved are long. For work performed on a building, defect claims are subject to a limitation period of five years (German Civil Code, section 634a); for other contracted work it is regularly two years (German Civil Code, section 634a). Where the German construction contract procedures part B are agreed, a period of four years applies to buildings instead (VOB/B, section 13 paragraph 4). Which rule applies in a given case depends on the contract and should be assessed legally. Organisationally the conclusion is simple: documents must remain findable across those periods, and findable via the job rather than via a folder name.

For that to work, files belong on the case rather than in an image folder sorted by date. Photos without a job reference are worthless after two years because nobody can tell which bathroom is in the picture. How to build such a filing structure without turning it into a large document project is described under document digitisation. Retention periods under tax law follow their own rules, which were changed recently and should be agreed with the tax adviser.

  • Photos of the condition before work starts — the only protection against a later claim that existing damage was caused during the work.
  • Measurements with a position reference — quantities tied to a quotation position rather than a number without context on a sheet.
  • Installed components with type and number — the basis for spare parts, maintenance and checking whether a component is affected.
  • Handover note with signature and timestamp — acceptance starts the clock on several periods and should not be purely verbal.
  • Notes on obstacles and instructions given on site — verbal releases only become traceable if they are recorded the same day.

Rollout: the sequence decides adoption

The most common mistake in digitisation projects in the trades is starting at every station at once. Intake, scheduling, reporting, time, material and invoicing get changed together because everything is connected. Factually that is true; organisationally it overwhelms a business that also has to work through its jobs. The opposite is workable: one process, one crew, a manageable period of roughly four to six weeks (project experience), then review and a decision about the next step.

A sensible starting point is where the information first arises and where the benefit is immediately visible, which is almost always the site report. Briefing happens on a real job, not from a manual and not in the break room; how to set that up is described on our page about training and rollout. It also takes a named contact inside the business for the first few weeks who collects questions and change requests instead of letting them evaporate in break-time conversation.

And it takes a cut-off date. As long as paper and device are both permitted, everyone decides for themselves and paper wins, being faster and more familiar. The cut-off is set crew by crew, announced and explained, and from that day the printed form is no longer accepted for billing. Whether the change has taken hold can then be read from a handful of figures: the share of jobs captured on the device, the share of reports written up more than a day later, and the lead time from work performed to invoice issued. The review below shows what that can look like.

Terminal
$ review reports --month 2026-06 --by crew
Crew 1: 92 of 100 jobs captured on device Crew 2: 88 of 96 jobs captured on device Crew 3: 41 of 99 jobs captured on device -- follow up
$ review late-entries --threshold 24h
Reports recorded later than 24 hours: 17 of 295 of which 12 from one site without mobile coverage
$ review lead-time --from work --to invoice
Average previous month: 11 days Average current month: 4 days Open reports awaiting approval: 6

Effort, sequence and doing your own maths

Before tools are selected, it pays to record how the work actually runs. A process analysis with site visits, counting points and assessed findings starts at EUR 1,900 net; implementing a single automation or interface starts at EUR 4,900 net, ongoing support at EUR 190 net per month. These are entry figures rather than a quotation; they simply indicate the order of magnitude a first step tends to occupy in a mid-size business.

Each business is best placed to calculate the economics with its own numbers: jobs per week, minutes spent chasing and retyping per job, the share of jobs with a query, average days to invoice. Sound statements come from your own volumes, not from somebody else's savings ratios. We deliberately quote no guaranteed percentages, because the spread between trades and company sizes is too wide to turn into a promise.

Where such projects tend to fail in the trades

On too many simultaneous fronts, on a rollout without a cut-off date, on devices that cannot be operated on a roof or in a boiler room, on missing offline capability, and on a capture system that gives nothing back. Technical reasons come last in that list; the decisive part of the work lies in organisation and rollout, not in choosing a tool.
This article is based on data from: the German Civil Code (section 634a), the German construction contract procedures part B (section 13), German occupational safety legislation, German VAT legislation and our own project experience from digitisation projects in trade businesses.

Related Articles

Practice & rollout

Tracking inspection deadlines without paper folders

Managing inspection intervals digitally: due dates in month and year, a two-month grace period, and the record kept on the machine, not in a yearly binder.

18 min read
Process analysis & assessment

Finding bottlenecks: measure waiting time, don't guess

Where do orders pile up, who is waiting for an approval? How to measure waiting time against handling time, find the real bottleneck and respond to it properly.

14 min read
Automation & interfaces

Verification of payee in payment runs: handling mismatches

Since October 2025, banks check name and IBAN before every credit transfer. How supplier master data, payment blocks and call-backs handle the bank's responses.

16 min read