Activity and reporting
A survey field report is only worth the time it saves. PLN records the work against the task it belongs to, so the crew fills in what they know and the office reads it in context instead of reassembling it from a chat thread.
An activity entry carries the work date, the user, the task, time spent, distance, expenses, and notes. Because the task is part of the record rather than a label typed into a cell, every later view of that work already knows the client, the location, and the price.
Reports filter by date range, user, task, or status. Preparing a monthly summary or checking a payout is a filter over records that already exist, which is a different job from chasing six people for their week.
Because activity stays connected to the task, invoice preparation starts from captured facts rather than reconstructed memory. Nothing is retyped between the report and the invoice, so nothing drifts between them.
On this page
Field reporting software is a crowded category, and most of it is built for inspection rounds or construction checklists. This page is about the survey case specifically: what a report has to carry, how it gets filled in on site, what the office does with it, and where it differs from a generic field form.
The record
Generic field reporting tools model an inspection: a form, a checklist, a signature. Survey work is not an inspection. It is a job with a location, a price, a crew, instruments, and a client waiting for a deliverable, and a report that drops any of those creates office work rather than removing it.
The unit of survey work is the task: a client, a survey type, a location, a due date, and a price. A report filed against a site or a date has to be matched back to the job by a human. A report filed against the task never needs matching.
Time spent is recorded per activity entry, against the user who did the work. That makes the same number usable for a payout check, a profitability question, and an invoice line, instead of being re-derived three times from three places.
Survey crews travel between marks, and the driving is a real cost that generic field forms rarely capture. Distance sits alongside hours in the same entry, so a monthly total includes the travel that actually happened.
Parking, materials, fuel, an unexpected permit. Recorded on the job they belong to, they reach the invoice. Recorded on a receipt in a jacket pocket, they reach the invoice sometimes.
The free-text note is where a surveyor says the mark was disturbed, the access road was closed, or the client changed the boundary on site. It is the part no form field anticipates and the part the next crew most needs.
On site
The field app is built for the crew standing on site rather than for reporting from a desk. Assigned work, task geometry, control points, photos, and chat are in the pocket, and the office sees the result immediately. The app is available on Google Play and the App Store.
The crew opens the task they are standing on and adds the entry there. Choosing the job from a list at the end of the day is where mis-filed reports come from, and it is the step this removes.
Work submitted without a connection is queued on the device and sent automatically when the connection returns. Settings shows when the last sync happened and whether anything is still waiting, so a crew can see the queue has cleared before leaving a valley.
There is no end-of-day upload step and no export. Once an entry syncs it is in the same activity log the office reads, which is what makes a same-day question answerable the same day.
In the office
A field report that is only ever read once has not earned the time it cost to file. These are the two things the same record does afterwards without anyone re-entering it.
Activity and reports
The activity log, time tracking, and potential payout are computed from the entries the crews filed. Choose a total price or an hourly rate per task and the summary updates itself, so a payout conversation starts from the same numbers the surveyor entered.
Billing
Task pricing, the contact record, activity history, and billing actions are visible where the work was managed. The invoice is prepared from what was recorded rather than from someone's reconstruction of the month, which is the difference between checking an invoice and rebuilding one.
The month-end problem
Very few survey companies fail to record their work. What they lack is a place where the record is already in the shape the next question needs, so the cost lands weeks later, in the office, on the person preparing the invoices.
When hours live in a messaging thread, distances in a notebook, and expenses on receipts, nothing is missing — it is just distributed. The work is gathering it, and that work scales with the number of crews rather than the number of jobs.
A month rebuilt from memory produces numbers that a surveyor can dispute, because they were derived rather than recorded. A month filtered from entries the surveyor filed themselves produces numbers nobody has to defend.
The expense that never made it to an invoice, the extra hour nobody logged, the second trip because the mark had moved. These are not accounting errors; they are the predictable result of recording work somewhere the invoice does not read.
Comparing activity against planned work shows the gaps during the month rather than at the end of it, when the crew still remembers the day well enough to fill one in.
Category fit
Most field reporting software is built for inspection rounds, utility maintenance, or construction sign-off. Those tools are good at what they do. The mismatch is structural rather than a question of quality, and it shows up in the same five places every time.
Who files what
Field reporting fails when it is one person's chore. It works when each role puts in what only they know and takes out what only they need.
Files the entry on the task while standing on it: hours, distance, expenses, and the note about what was actually found. This is the only step that has to happen on site, and it is the only step the app is optimised for.
Checks that the day's assigned work has entries against it before the crew stands down, using the same task list the surveyors filed against. Missing logs are visible against planned work rather than discovered a month later.
Reads activity by date range, user, or status to answer where the month went, which tasks ran long, and what needs following up. No collection step, because there was never anything to collect.
Prepares invoices from tasks whose price, contact, and activity history are already attached, and can see the work behind each line without asking who did it.
Questions
An activity entry records the work date, the user, the task it belongs to, time spent, distance travelled, expenses, and a free-text note. Because the task is part of the record, the client, survey type, location, and price come with it rather than being retyped.
Yes. Work submitted without a connection is queued on the device and sent automatically when the connection returns. Settings shows when the last sync happened and whether anything is still waiting.
The field flow is opening the assigned task and adding an entry to it. QuickTask exists for one-handed work on site, with find nearby, FastPicture, and FastDraft. Crews who already send updates by message are not learning a new habit, only a different place to put it.
It does not have to travel. Activity is recorded against the task, and the task carries the price, the contact, and the history, so invoice preparation reads the same record rather than importing from it.
For survey work it usually does, because time spent is recorded per entry against the user and the task. That makes the same figure usable for payout checks and for asking whether a task type is priced correctly.
PLN System Mobile is available now on Google Play and the App Store.
Next step
Start a three-month free trial or contact the team with questions about rollout, pricing, trust, and workflow fit.