Skip to main content

Setting up your Pre-start template

Learn how to set up and manage Pre-Start Test Templates in FieldInsight to ensure internal assets are safe, compliant, and ready before each job.

H
Written by Harsh D
Updated this week

What is a Pre-Start Test Template?

A Pre-Start Test Template in FieldInsight is a predefined checklist used to verify that internal assets are in proper working condition before a job starts.
It ensures that critical equipment: for example, fire extinguishers, pumps, or tools - meets safety and performance standards prior to being deployed.

Think of it as a safety and readiness gate: technicians complete these checks at the start of the job so that any issues can be flagged early, reducing risks and avoiding last-minute delays.

Key benefits:

  • Provides consistency across technicians and jobs.

  • Improves safety compliance and prevents unexpected asset failures.

  • Helps track maintenance history for internal assets.


📝 Step-by-Step Guide to Creating a Pre-Start Test Template

Step 1: Access Assets

  • From the left-hand navigation panel, go to Assets → Assets.


Step 2: Open Test Templates

  • Click on Test Templates in the Assets section.

  • Set the Test Type to Pre-Start Tests and click Search.


Step 3: Add a New Test

  • Click on + Add Test.

  • Enter a clear and descriptive name, e.g. “Pre-Start Internal Extinguishers”.

  • Click Next.


Step 4: Configure Asset Standards

  • In the Asset Standard field, search and select the relevant standard (e.g. AS1851 2012 – Portable and Wheeled Fire Extinguishers).

  • Below that, in the Description section - provide a description for clarity.


Step 5: Select Asset Types

  • Search for and select the Asset Types applicable to this test.

  • Example: select Fire Extinguisher and Extinguishers.

  • If this template applies to all assets, you can choose For all asset types.


Step 6: Assign Job Types

  • Either select specific Job Types where this test applies, or tick For all job types if it’s generic.


Step 7: Enable Technician Signature (Optional)

  • Check Technician signature required if you want technicians to sign off on the test for compliance.


Step 8: Define Runtime Threshold

  • Service Due at: Enter the runtime value (e.g. 100).

  • UoM (Unit of Measure): Choose the unit (e.g. HR, m, ltr, kg).

  • This defines when a service alert will be triggered.

Runtime Job Creation Rule:

  • Manual: A job will be created only when a user manually initiates it after reaching the threshold.

  • Automatic: A job will be automatically generated by the system as soon as the runtime threshold is reached.

👉 Choose Manual if you want more control; choose Automatic to ensure nothing is missed due to oversight.


Step 9: Set Preventative Maintenance Frequency

  • Define how often the test should recur by default, e.g. every 3 months.

  • Add a Short Name (e.g. 3M) for easy reference.

Check the boxes:

  • Pass or fail (if you want the test to have an option stating the above at the end of the test.

  • Repeatable (if you think this is going to be repeated)


Step 10: Define Default Time & Report Template

  • Default Time to Complete:
    Specify the estimated time a technician usually needs to perform this test (e.g. 1 minute).


    (This is used for scheduling, resource planning, and reporting.)

  • Report Template Type:
    Choose Default to use the standard FieldInsight reporting layout, or choose a Custom Template if your organization has a tailored reporting format.


Step 11: Apply Relevant Flags

  • Check Pre-Start Test (important since we’re creating a pre-start template).

  • Check Is Internal for internal asset tracking. Note: Pre-starts work with your internal assets so it's necessary for this to be ticked.

  • Enable other flags (like Request Work Order Number) if required by your workflow.


Step 12: Add Test Questions

  • Click + Add Question to create specific checks.

  • Enter a Field Name, e.g. “Generic Check: Is the asset working fine?”


  • Select an appropriate Field Type (Text field, Checkbox, Dropdown, etc.).

  • Configure options such as:

    • Mandatory Field

    • View/Edit by Worker

    • Show Label

👉 Repeat this step to add as many questions as needed.


Step 13: Save the Template

  • Once all configurations and questions are added, click Save to store the template.


✅ Best Practices

  • Use clear, concise names for templates and questions so technicians instantly understand what’s required.

  • Periodically review and update templates to reflect evolving safety standards.

  • Leverage Automatic runtime job creation for critical equipment to avoid missed servicing.


🌟 Closing Note

By setting up Pre-Start Test Templates, you ensure that your internal assets are checked, documented, and maintained proactively before they are deployed in the field.
This not only improves safety and compliance but also keeps your operations running smoothly without unexpected equipment-related delays.

NEXT UP

Did this answer your question?