Plant checks · Defect records · Office review
Pre-Start App for NZ Construction Plant
Record the operator’s checks against the machine. Fieldlink’s plant pre-start workflow brings checklist responses, defect notes, photos, meter readings and a signature into a record the office can review.
Give the office a record of what the operator reported and which defects need follow-up.
01 / Plant pre-starts
Choose the right record for the work.
A plant pre-start records checks on a vehicle or machine. A site pre-start or morning briefing covers the crew’s work, site hazards and controls. They serve different purposes.
Fieldlink’s dedicated Pre-Starts register is machine-based: choose the plant item, complete its checklist and submit the record. Use configured job forms for site checks, or the existing printable site pre-start template for a paper record. Plant records are not automatically the same as job form submissions.
02 / Plant pre-starts
From machine selection to a submitted record.
Operators use the company checklist on their phone. Office and admin users can change checklist items and designate the mechanical items that should create damage reports when marked as failed.
Select the machine
Choose the vehicle or plant record so the inspection is stored in the right equipment history.
Record the checks
Enter checklist responses, defect notes and supporting photos. Add the applicable hours or odometer reading.
Record the operator’s decision
Complete the signature and overall safe/unsafe response according to your company process. The response is the operator’s assessment.
Submit for office visibility
The submitted record carries the machine, operator and timestamp. The office can review pre-starts and inspect recorded defects.
03 / Plant pre-starts
Make the defect visible without overstating the automation.
A failed item designated as mechanical in the company checklist creates a damage report against the machine, with the reported notes and photos. A failure on another item is still recorded in the pre-start but does not necessarily create a separate damage report.
When the operator marks the overall pre-start unsafe, the machine’s status is set to maintenance pending office review. This is a software status change, not a physical lockout, repair or confirmation that the machine can return to service.
A valid new meter reading can advance the recorded machine hours or odometer; it does not move the meter backwards. The office or workshop follows up through the equipment and review workflows.
04 / Plant pre-starts
A completed checklist is a record.
Use checklist items appropriate to the machine and your company process, taking account of manufacturer information and site requirements. A stored response or signature does not independently prove that the machine or site is safe.
Plan for connectivity to upload evidence and submit records. Confirm the saved record in the register; do not rely on a general offline claim for every pre-start action.
Before you start
Common questions
Can we customise the checklist?
Office and admin users can edit the company checklist and designate mechanical items that create damage reports on failure. Review the list against the plant you operate.
Does every failed item create a damage report?
No. Automatic damage reports apply to items designated as mechanical. Other failed responses remain part of the pre-start record.
Does marking a machine unsafe lock it out?
It sets the fleet record to maintenance pending office review. It does not physically isolate the machine or replace your company’s isolation and return-to-service process.
Is this also a site briefing app?
The dedicated workflow is for plant checks. Use the job’s assigned forms for a configured site briefing or daily site check; toolbox talks have a separate session and attendance workflow.
Keep the work connected.
For the full office-to-field workflow, explore Fieldlink job management. Find practical tools and guides in the Civil Hub.
Keep plant checks available to the office.
Explore pre-start records and defect follow-up with your team in Fieldlink.