Creating and Using Inspection Templates to Build SOPs in Pete

Go to Settings in Pete.

Open Templates.

Select Inspections.

Use this area to manage all inspection templates alongside other template types such as appointments, e-signatures, newsletters, notes, SMS, and tasks.

This is the central location for creating and maintaining inspection workflows.

Click the blue button to create a new inspection template.

Enter a clear template name, such as Property Inspection.

Add a description if needed so users understand the purpose of the inspection.

Decide whether to build the template manually or import it from an existing checklist.

Choose Import from checklist if you already have a checklist document or list of inspection steps.

Paste the checklist into Pete as plain text if needed.

Alternatively, create each section manually.

Add the items in the order they should be completed.

Use this step to convert your existing process into a structured inspection template.

Set the field type for each item based on what the inspector must provide.

Common field options include:

Decide whether each field is required or optional.

Enable or disable notes, instructions/helper text, and photo/video attachments as needed.

Use instructions to guide the user without allowing them to edit the guidance text.

Once the checklist is built, use it to generate a playbook/SOP in Pete.

Treat the inspection template as the checklist version and the playbook as the written standard operating procedure.

Review the generated SOP to ensure the steps match your business process.

Use the SOP to explain why the inspection exists and how it should be completed.

Keep the SOP aligned with the inspection template so both stay consistent.

Create or open a task template for the work that requires the inspection.

Attach the inspection template to that task template.

Use this when the inspection must be completed as part of a workflow or status change.

This ensures the inspection is not just a checklist, but a required part of task completion.

Save the task template after linking the inspection.

Open the relevant property record.

Locate the inspection section in the property details.

Add the inspection template manually or through the linked task.

Confirm the correct template is attached to the correct property.

This allows the inspection to be tracked directly from the property record.

Identify whether the inspection will be completed by an internal user or an external user.

Internal users are Pete team members who can create, edit, review, and submit inspections.

External users are vendors, contractors, or gig workers who only need the public-facing inspection link.

Decide access level before sharing the inspection.

Open the inspection and choose how to distribute it.

Options may include:

Set an expiration date if the inspection must be completed within a specific time.

Send the link to the person responsible for completing the inspection.

The recipient does not need a Pete login if using the public link.

The assigned user opens the inspection link and begins filling it out.

Complete each checklist item in order.

Add required photos, videos, or notes where prompted.

Mark items as complete as you go.

Use the inspection to capture proof of work, property condition, or appointment details.

Save progress before submitting if the inspection is not finished.

Once complete, submit the inspection.

The inspection will move into a status such as submitted or in progress, depending on the workflow.

A manager or reviewer can then mark it as reviewed.

Use the review step to confirm the inspection was completed correctly.

Go to the dashboard and open the property resources and inspections area.

Review counts for inspections that are in draft, in progress, submitted, or reviewed.

Open any inspection to see the template, submitter details, and current status.

Reassign, share, or jump to specific sections if needed.

Use this dashboard view to manage multiple inspections at once.

Do not skip the template review step before publishing; incorrect fields or instructions can cause confusion later.

Make sure the inspection is assigned to the correct user and property before sharing.

If using an expiration date for external users, confirm the deadline is realistic and clearly communicated.

Review whether photos, videos, notes, and required fields are enabled correctly before sending.

If your process changes, update the template and SOP together so they stay aligned.

Confirm who is responsible for marking the inspection as reviewed so statuses do not stall.

Start with an existing checklist and import it instead of building from scratch.

Use the SOP/playbook generation feature to save time documenting the process.

Standardize field types across inspections so users know what to expect.

Use single-use links for external users to reduce login friction.

Add clear helper text and instructions to reduce back-and-forth questions.

Keep inspection templates versioned and updated as your process evolves.

Use the dashboard to quickly identify drafts, submitted items, and items awaiting review.

For field teams, use the mobile app or offline capability when inspections happen on-site or without reliable internet.