Creating a Job — Complete Guide
The three-step creation form, the five workflow types, and the faster route: upload the policy and let Estimatics fill the form for you.
7 min read
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.
Who can create a job
| Where | Who |
|---|---|
| Web | Super Admin, Admin, Coordinator |
| iPhone | Field Inspector, Super Admin |
Estimators can't create jobs. Two account conditions apply too: your email must be verified, and the account must be able to create jobs, meaning an active trial or plan. On the free trial you can have up to 3 jobs. If something blocks you, the app tells you why, for example "Please verify your email before creating a job." or "Trial limit reached (3 Jobs). Upgrade to continue." If the Create button is missing, your role can't create jobs. If the page opens blank, the account can't create jobs right now, for example because billing needs attention.
→ Roles and permissions · The free trial
The fast way — create from the policy
From Jobs, open the Create menu and choose Upload document to capture job details.
- Upload the policy as a PDF, up to 15 MB. Photos and Word files aren't accepted.
- Estimatics reads it. Stay on the page while it processes — don't close or refresh it.
- When it finishes, the creation form opens already filled in with what the policy said: carrier, policy number, insured, address, dates, deductible, coverage limits.
- 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.
ℹ Note
Creating from a document needs AI available on your account. If it isn't, for example because billing needs attention, the option is disabled.
→ What extraction pulls out of a policy
The manual way — three steps
Jobs → Create → Create new job manually. The form has three steps. Nothing is saved until you finish, so if you leave halfway, you start over.
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 ("What kind of job is this?"). 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. The one pre-selected depends on the company type you set up for your account.
Start date.
Billable job. A switch that starts from the workflow type (on for Quick Quote and Work Order, off for the claim workflows). Turn it on to track invoicing and payment for the job.
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.
ℹ Note
Workflow type and customer type are fixed at creation. They can't be changed afterward. Most of the rest can be edited by a Super Admin or Admin from the job's Overview tab while the job is in New, Inspection Assigned, or Inspection Scheduled, but some fields lock once the job has evidence: job type, damage type, and the property address.
Step 3 — Damage and insurance
Which sections you see depends on the workflow. Insurance claims ask for damage, insurance, and coverage details. A Work Order asks for damage but not insurance. A Quick Quote asks for neither, and its description is called "Work description".
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 Damage, Wind Damage, Hail Damage, Flood Damage, Fire Damage, Smoke Damage, Mold Damage, Asbestos, Weight of Ice/Snow, Vandalism Damage, Impact Damage, Lightning Damage, 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.
When you finish, you see "Job created successfully" and the job opens.
The five workflow types
| Workflow | What it's for |
|---|---|
| Insurance Claim — Inspection & Estimate | The full claim lifecycle: field inspection, estimate, delivery |
| Insurance Claim — Inspection Only | Field inspection and documentation. No estimate |
| Insurance Claim — Estimate Only | Scope and estimate from what's already on file. No field inspection |
| Quick Quote | Contractor workflow: capture, estimate, send to the client |
| Work Order | Full contractor workflow with scope, execution, and billing |
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 to a Field Inspector and it moves to Inspection Assigned; the inspector sees it on their iPhone. From there it follows its workflow's sequence. A job in an Estimate Only workflow doesn't need an inspector.
The job's Overview tab shows a Next step card that tells you what to do now and whether it happens on the web or on the iPhone.
No drafts
Estimatics doesn't save partial jobs. There is no Drafts tab and no way to save a job halfway. Gather the owner's name, the full address, the property type, and the start date before you begin. The policy-upload route is the quickest way to start with most of it filled in.
Creating a job from the iPhone
Tap Create Job, then choose to create it manually or to upload a policy document. You need a signal. The required fields are the owner's name, address, state, city, ZIP, and property type. Insurance companies are added on the web as organizations of type Insurance Company; until one exists, it can't be picked on the phone.
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.
- Set a damage type. The AI-built estimate needs one, so a job without it can't build a scope.
Workflow types and statuses
The five workflows and the status sequence each one follows.
Document Intelligence
What extraction pulls out of a policy, and how values reach the job.
Navigating the workspace
The nine tabs, and why you may not see all of them.
Your first job, end to end
From creation to delivered report.
Last updated: October 2026 · Questions? Email support@aiestimatics.com
Last updated: October 2026 · Feedback on this article