Service Report Compiler

One activity becomes a branded PDF — and goes back onto the record as an attachment.

What it needs

• An FSA tenant where you have admin access to Extensions.
• One install link, pasted once. No deployment on your side.
• No engine — it reads and writes FSA only.
• A font file if you want your own typeface; otherwise it ships with sensible defaults.

Installing

Paste this into Foundational Services → Extensions in FSA, together with your licence key. The full flow is on the install page.

https://studio.altiwerk.com/ext/servicereports/appconfig.json

It also runs on mobile — see mobile setup for configuring the Web Container, including pinning it so technicians see only this one.

Getting a first result

1. 1

   Start from a preset

   Four starter layouts ship with it. Duplicate the closest one rather than starting from an empty page.

2. 2

   Arrange the blocks

   Fifteen block kinds, dragged into order, full or half width. Add your letterhead, footer columns and page setup once — it is per template, not per report.

3. 3

   Generate one against a real activity

   Check what appears: checklist answers, effort, bookings, materials, expenses, mileage, photos and signatures all come from the job.

4. 4

   Attach it back

   The finished PDF goes onto the record in FSA as an attachment, which is usually the point of the exercise.

Worth knowing

What it does in full, and the questions buyers ask, are on the product page.