FieldproxyAI-native field service softwareForms and checklists
How do I turn a Word or PDF checklist into a mobile form for technicians?
Go through the paper checklist line by line and give each line a field type (pass, fail or N/A, a number with a range, a photo, a signature), mark which ones are required, and add logic so questions that only apply to some equipment appear only when they do. Anything the paper repeats, such as 100 anchors or 30 sprinkler heads, becomes one repeating row the technician adds as many times as needed, not 100 separate questions. Then test it on a real job and check that the PDF it produces still reads like the report your customers already accept.
- Map every line of the paper form to a field type before you build anything.
- Repeated items (anchors, heads, units) become one repeating row, not hundreds of questions.
- Use logic so electrical, manual or site-specific questions show only when they apply.
- Require the fields that matter (fail photo, reading, signature) so a job cannot close without them.
- Test on one real job and compare the PDF output with the report your customer signs off today.
AI converters and vendor setup teams get you a first draft fast, but someone who does the inspections still has to check every field, every rule and the final report before technicians use it.
Facts checked as of November 2026. Sources at the end of the page.
Step by step
How it works, step by step
This works the same for inspection sheets, service reports, PM checklists and site audits. The order matters: decide the structure before you open any form builder.
1. Collect the real versions
Get the Word or PDF checklist, two or three filled-in copies with handwriting on them, and the report the customer receives. The filled-in copies show what technicians actually write in the margins, which is usually the field the form is missing.
2. Give every line a field type
Pass, fail or N/A becomes a choice field. Measurements become number fields with a unit and an allowed range. Free text stays text. "Take a photo" becomes a photo field, and the sign-off box becomes a signature. Jobber's checklists, for example, offer short and long answer, dropdown, checkbox, numerical answer, image upload, date picker and signature fields, which covers most paper forms.
3. Turn repeated items into a repeating row
If the paper lists "Anchor 1, Anchor 2... Anchor 100", build one row (anchor ID, location, load applied, pass or fail, photo) that the technician repeats. Device Magic calls this a repeat group, a set of questions answered multiple times; Fulcrum calls it a repeatable section, where each child record has its own location and timestamp.
4. Add logic for branches
Questions that apply only to electrical hoists, or only to one service type, should appear only when that answer is picked. A fail should open a follow-up: what is wrong, a photo, a note. SafetyCulture (help now at mitti.com) describes logic that can show a follow-up question, require a note or media, prompt an action, notify people or complete the inspection, with up to 40 nested logic fields per condition.
5. Decide what is required
Mark the fields a job cannot be closed without: the signature, the fail photo, the reading. ServiceM8, for example, says its forms can be made mandatory at the start or end of a job. Keep required fields to what the customer or regulator actually needs, or technicians will type filler to get past them.
6. Map the answers into the report
The form collects the data; the PDF template decides how it looks. ServiceM8's Forms add-on, for example, uses a Microsoft Word template to turn answers into a document. Fields marked internal (estimator notes, time spent) stay off the customer copy.
7. Test on a real job, then switch
Have one senior technician fill the new form and the old paper side by side on a live job. Fix what slowed them down, then retire the paper version on a set date so nobody runs both.
Where it breaks
Why it goes wrong
These are the problems buyers described on our sales calls, by trade and size.
Hundreds of near-identical questions
A fall protection engineering and load testing firm said it could not put a hundred questions in for the same item, one per anchor, each with pass or fail. Their technicians were back on paper and pen, signing the sheet and uploading a scan. When a builder has no repeating row, the digital form is worse than paper.
Logic that does not carry over
An overhead crane and hoist inspection company with about 20 technicians wanted different questions for electrical and manual equipment, the way their SafetyCulture templates worked, and some fields kept internal so the client report shows only deficiencies. A converter that copies the text but drops the branches gives technicians every question on every crane.
Every change needs someone else
A warehouse racking inspection business had to ask its software vendor to build forms. An oil and gas operations technology team said changing one custom form through its enterprise IT team could take months. If the people who run the inspections cannot edit the form, it falls out of date with the standard.
Forms that let people skip
A pump sales and service company asked for a form that blocks submission until required fields are filled, while keeping the look of its existing service report. A bicycle and scooter leasing company said its mechanics simply did not fill the forms in properly. Optional fields get skipped on a busy day.
Typing on site is slow
The fall protection firm asked for speech to text so technicians on a roof could talk instead of type. Long notes typed with gloves on get shortened to "ok".
One form, many service types
A residential high-rise landscape maintenance team needed different checklists for watering, mulching and pruning, plus a record of when each was last done. One long form for every visit hides the questions that matter for today's task.
The options
Ways to do it
How teams turn a paper checklist into something technicians fill on a phone, as each tool's own pages describe it.
| Approach | Getting the paper form in | Logic and repeated items | Watch for |
|---|---|---|---|
| Fillable PDF (Adobe Acrobat) | Turn a scanned form or a Word, Excel or InDesign file into a fillable PDF | Fixed layout; no repeating rows on a phone; no link to a job | Still a document, not data you can report on |
| Inspection app (SafetyCulture, help now at mitti.com) | Upload 1 PDF up to 10 MB, 1 Excel file up to 5 MB or up to 6 images; Word must be converted first or sent to their team | Logic shows follow-ups, requires notes or media, notifies people; up to 40 nested logic fields per condition | Jobs, scheduling and invoicing usually sit in a second tool |
| AI form converter (GoCanvas AI Forms) | Drag and drop a PDF; fields, checkboxes and sections are mapped to a mobile draft | Logic, required fields, photos, GPS and signatures set during review | Review every field; complex forms need hand fixes |
| Checklists inside a general FSM (Jobber, ServiceM8) | Rebuild by hand. Jobber allows up to 100 checklists; ServiceM8 starts from a Word template for the report | ServiceM8 forms can skip questions not needed; Jobber checklists apply to every visit of a recurring job | Check repeating rows and per-field visibility before you commit |
| FSM configured to your forms (Fieldproxy) | Send the Word or PDF; the checklist is built with you as part of setup | Conditional logic, required photos and sign-offs on the job; repeated items set up as e.g. one row per anchor | You still check the draft and the PDF on a real job |
As of November 2026, from each vendor's own pages (sources below). Test with your hardest form, not your simplest.
Worked example
A worked example: a 100-anchor load test
Say a fall protection company tests and certifies roof anchors on a 20-storey building with 100 anchors, plus 2 davits and 1 monorail. Made-up numbers, to show the build.
The paper version is a 6-page Word document: building details, 100 printed anchor lines, a davit page, a monorail page and a sign-off. Built as is, that is more than 400 questions on a phone. Built properly, it is about 25 fields.
The header section holds the site, the building owner contact, the test equipment ID and its calibration date. The anchor row holds anchor ID, roof zone, anchor type, load applied, result and a photo, with the photo required only on a fail. The technician adds 100 rows, or scans each anchor's tag to start a row. A davit section and a monorail section appear only if the job type says they are on site, which is the logic step.
Required fields are the test load on each row, a photo on every fail and the technician's signature. Notes are dictated with the phone keyboard's microphone; Gboard on Android, for example, lets you talk to write in most places you can type.
The PDF prints the anchor rows as a table, 25 to a page, with fails first and photos in an appendix, which is the grid layout the customer was used to. In the US, that table is the evidence a building owner relies on when it tells the window cleaning contractor in writing that each anchorage has been identified, tested, certified and maintained, as OSHA 1910.27(b)(1)(i) requires before anyone uses a rope descent system on it.
Before you buy
What to check before you buy
Good signs
- A repeating row or section for items like anchors, heads or units, with a photo per row
- Logic that shows or hides questions and sections based on earlier answers
- Per-field required rules, including a photo required only on a fail
- Number fields with units and allowed ranges that flag readings outside them
- Fields that can be marked internal so they never print on the customer report
- The PDF layout can match the report your customers already accept
- The people who run inspections can edit the form without a developer or a vendor ticket
- Works offline on the phone and syncs when signal returns
Red flags
- Repeated items must be built as separate questions
- The vendor must build or change every form for you
- Converted forms drop the logic from your original templates
- Answers live only in the PDF, so you cannot list fails across sites
- No way to block closing a job until required fields are done
- Each form change goes through a long IT queue
In Fieldproxy
Setting it up in Fieldproxy
Fieldproxy is set up around your process, so your checklists are built from your own paper forms during setup. Field names and rules below are examples.
Send the paper form
Share the Word or PDF checklist, a filled-in copy and the customer report. The checklist is built as part of your setup, with your field types, logic and required fields (/solutions/job-checklists). You can also ask Command Center (/agents/command-center) to change a form later, and it shows a confirm card with Undo before anything changes.
Logic, required fields and repeated rows
Questions appear by equipment type or service type, e.g. electrical hoist questions only when Power = Electrical. Fails require e.g. a photo and a note. Repeated items are set up as e.g. one anchor row the technician adds per anchor, so 100 anchors is one row used 100 times.
Faster entry on site
The Android or iOS technician app (/solutions/mobile-app) works offline with photos, signatures and GPS check-in. The Voice agent (/agents/voice-agent) turns a technician's voice notes into structured job data, and the Video agent (/agents/video-agent) fills the form from one clip of what was shown and said. The Vision agent (/agents/vision-agent) reads a nameplate photo into the asset fields.
Your report, not a template
Answers print into a PDF built from your own template, so the customer gets the layout they know. Internal fields stay off the customer copy.
One price per company
Fieldproxy is one price per company with unlimited users, so every technician and office editor is included; see /pricing.
How switching works
How switching to Fieldproxy works
We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.
Send your hardest form
The Word or PDF checklist with the most branches or repeated items, two filled-in copies and the report the customer receives.We build it with you
Field types, logic, required fields, repeated rows and the PDF layout, reviewed with the person who does the inspections.Test on a live job
One technician fills the new form beside the paper one, and we fix what slowed them down.Retire the paper
The rest of your checklists follow the same pattern, and paper stops on a set date.
FAQ
Questions people ask
- Can an existing Word or PDF checklist be turned into a digital form automatically?
- Partly. Tools like SafetyCulture's PDF upload and GoCanvas AI Forms produce a draft with fields and sections mapped, but logic, required rules and repeated rows usually need a person to set them. Treat the converted form as a first draft.
- How do I handle a load test grid with 100 anchors?
- Use a repeating row: one set of fields (anchor ID, location, load, result, photo) that the technician adds once per anchor. Print it in the report as a table so it still looks like the grid your customer expects.
- Can technicians use speech to text to fill in checklists?
- Yes. The microphone on the iPhone and Android keyboards works in any text field, and some field service apps also turn voice notes or a video clip into structured answers. Check dictation works offline if your sites have no signal.
- Can the form block a technician from submitting until required fields are filled?
- It should. Mark the fields that matter as required, including a photo only when an item fails, and the job cannot close until they are done.
- Can different service types use different checklists on the same site?
- Yes. Either attach a different checklist per job type, or use logic in one form so only the questions for today's service type appear.
- Will the PDF report look like my current paper form?
- Only if the tool lets you control the report template. Ask to see your own form's report before you buy, not a sample.
- Can I keep some fields internal so the customer report shows only the findings?
- Look for per-field visibility. Internal notes, time spent and estimator comments should stay in the record and off the customer PDF.
Sources
Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.
- SafetyCulture (Mitti) Help: convert Excel, images or PDF into a template: https://help.mitti.com/004066
- SafetyCulture (Mitti) Help: logic fields: https://help.mitti.com/002285
- GoCanvas: from PDF to mobile form with AI Forms: https://www.gocanvas.com/blog/ai-forms-convert-pdf-to-mobile-form
- Device Magic Help: repeat groups: https://intercom.help/device-magic/en/articles/392976-repeat-groups
- Fulcrum Help: what are repeatable sections: https://help.fulcrumapp.com/field-types/what-are-repeatable-sections
- Jobber Help Center: checklists: https://help.getjobber.com/en/articles/checklists/
- ServiceM8 Support: Forms add-on overview: https://support.servicem8.com/help-center/servicem8-add-ons/forms/forms-overview.md
- ServiceM8: Forms: https://www.servicem8.com/forms
- Adobe Experience League: create fillable forms in Acrobat: https://experienceleague.adobe.com/en/docs/document-cloud-learn/acrobat-learning/getting-started/create-fillable-forms
- Gboard Help: type with your voice: https://support.google.com/gboard/answer/2781851
- OSHA 29 CFR 1910.27: scaffolds and rope descent systems (anchorage certification): https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.27
Related
Keep reading
- How do I produce field inspection reports in my own format, with an engineer review before they go to the client?
- How do I require before and after photos before a technician can complete a job?
- How do I turn inspection deficiencies into quotes and repair jobs automatically?
- Pallet racking inspection software
- What is the best field service software for a 5-10 person HVAC team?
- Cheaper ServiceTitan alternatives for small plumbing and HVAC companies, without payment processor lock-in