Creating a Job — Complete Guide

Every inspection starts with a job. The job record holds who owns the property, what happened, which carrier is involved, and what the policy covers. What you put in here is what the AI has to work with later — a thin job record produces thin findings.

There are two ways to create one.

---

The fast way — create from the policy

From Jobs, open the Create menu and choose to create from a document.

1. Upload the policy PDF.
2. Estimatics reads it. The drawer stays open while it processes — usually under a minute.
3. When it finishes, the creation form opens already filled in with what the policy said: carrier, policy number, insured, address, dates, deductible, coverage limits.
4. You review every field, correct what's wrong, complete what the policy didn't say, and save.

This is the route worth defaulting to. Typing a declarations page by hand is where transcription errors enter a claim file.

→ What extraction pulls out of a policy

---

The manual way — three steps

Jobs → Create → Create manually. The form has three steps.

Step 1 — Property owner and address

Property owners. One or more. For each: name, email, primary and secondary contact numbers, and notes. Pick an existing contact from your CRM or create one inline.

Property address. Street, second line, city, state, ZIP, and property type. This address is the anchor for regional pricing and the property's location context — get it right.

Step 2 — Job details and customer

Workflow type. The single most consequential field on the form. It decides which statuses the job moves through and which modules it uses. Five to choose from — see below.

Start date.

Customer type — Organization, Individual Contact, or Property Owner. This sets who the customer block collects: an organization (name, type, email, phone, full address) or a contact.

Step 3 — Damage and insurance

Damage — claim number, date of loss, damage type, cause, year built, roof age, and a free-text description.

Damage type is one of thirteen: Water, Wind, Hail, Flood, Fire, Smoke, Mold, Asbestos, Weight of Ice/Snow, Vandalism, Impact, Lightning, or Remodel/Repairs/Renovation. Cause is a dependent list — pick Wind and you get Hurricane, Tornado, Windstorm, Wind Gusts; pick Fire and you get fourteen ignition sources.

Insurance — carrier, policy number, deductible, effective and expiration dates, assigned adjuster, independent adjuster.

Coverages and policy limits — Dwelling (A), Other Structures (B), Contents (C), Loss of Use (D), water damage, fungi/mold, and the EMS limit.

Don't have the declarations page in front of you? Leave the limits empty and upload the policy to the job later. Extraction fills them in on your confirmation.

---

The five workflow types

Each one carries its own status sequence — a Quick Quote never passes through Inspection Assigned, and an Estimate Only job never has an inspection stage at all. Quick Quote also hides the Geometry and Analyze tabs, because that workflow doesn't use them.

→ Workflow types and job statuses in full

---

What happens when you save

A job created on the web starts at New. Assign it and it moves to Inspection Assigned. From there it follows its workflow's sequence.

---

Draft jobs

You don't have to finish in one sitting. Save as a Draft at any point — drafts carry their own status, appear in your job list with a draft badge, and keep everything you'd entered. Open one and pick up where you stopped.

---

Tips

• Fill in the insurance block. Coverage context is what lets the AI say something useful about coverage rather than "no policy on file".
• Be specific in the damage description. Name the affected areas, the materials, and the event. "Tree fell on the northwest corner of the roof during the April 2 storm" is worth more than "wind damage".
• Pick the workflow deliberately. It's the one field you can't take back.
• Upload the policy. Whether as the entry point or afterward, extraction beats typing.

---

---

Last updated: September 2026 · Questions? Email support@aiestimatics.com