Every job, every visit, in one record.
Intake to invoice lives in one place. Statuses, visits, notes, photos, and the full activity timeline — no notebook sprawl, no lost context.
Try jobs on a live workspace.
No credit card, no setup call. Three jobs and a full invoice on the house.
Visits on the calendar, not in your head.
Drop a visit on a day, assign a worker, and the job status updates automatically when they check in on site.
- Drag-and-drop scheduling on the calendar
- Per-worker view for dispatchers
- Auto-status transitions on check-in / check-out
A timeline that never lies.
Every change — status, line item, photo, visit — appends to an append-only activity log. You always know what happened, when, and who did it.
- Append-only audit trail
- Actor attribution for every event
- Stream notes from the crew into the feed
A pipeline that matches the day.
Draft → scheduled → in progress → completed → invoiced → paid. Transitions are enforced so your pipeline is always honest about where the work really is.
- Enforced status transitions (no orphaned jobs)
- Per-status filters on the jobs list
- Workspace-wide dashboard tile for today's visits
A front door that collects the right details.
New-job intake captures client, property, scope, and a first photo in under a minute — from a phone call, a web form, or a walk-in at the shop.
- Quick-add from the dashboard
- Public intake form with a shareable URL
- Auto-create client and property on submit
What a well-run jobs pipeline looks like.
- 12
- Average fields to open a new job
- 1
- Tap to schedule a visit
- 0
- Duplicate records between job and invoice
- 100%
- Of changes captured in the activity feed
Spin up a test invoice and see the flow.
Every action below runs on the real app, no demo, no sandbox.
“I stopped losing jobs to 'wait, did we already schedule that?' Everything is on one screen, and the timeline tells me who did what.”
Why jobs are Falcon Bill's center of gravity.
One source of truth
Client, property, visits, estimate, invoice, and activity all hang off the job. Nothing lives in three apps.
Honest pipeline
The status of a job reflects reality. No pipeline theater, no stale 'in progress' jobs that finished last quarter.
Auditable
Every significant mutation is recorded. When a client asks 'when did you do this?', you have the answer.
Crew-friendly
Workers see only their assigned visits and update status from the field. Owners keep the wider view without drowning in detail.
Schedule-aware
The calendar is the jobs list, not a separate tool. Drag a visit to Tuesday; the job knows.
Billing-ready
When the last visit closes out, the job is pre-built for an invoice. The crew finished; the paperwork can finish on its own.
Jobs, cleanly modeled:
- Client + property association
- Scheduled visits with assignees
- Status lifecycle (draft → paid)
- Voice memo or chat note logs straight to the job timeline via the AI assistant
- Line items attached to visits
- Photos on the job and per-visit
- Activity feed for the whole job
- Direct links to estimates and invoices
- Per-worker 'my visits' view
- Quick-add from the dashboard
- Public intake form for new-client capture
- Progress billing across multiple invoices
- Signature capture on visit completion
Jobs, reframed.
A container, not a checklist
Jobs hold every artifact — estimates, invoices, photos, signatures, messages. They're a folder, not a stage in a pipeline.
Ownership you can trust
Role-based access keeps the financial layer owner-only while giving workers the field view they need.
Momentum the crew can feel
A visit checked in on site nudges the job status forward on the dashboard. Everyone sees the day moving.
Safety at the edges
Enforced transitions prevent 'accidentally marked paid' mistakes. The pipeline stays trustworthy without extra policing.
Reporting you didn't have to build
Every job carries status and timestamps, so simple queries (open vs. completed vs. paid) are always one filter away.
An exit that still makes sense
If you leave Falcon Bill, your jobs export as CSV with every visit, line item, and payment. The story stays legible.
Open a workspace and send something.
Draft, send, get paid, end-to-end in under two minutes.
How pros use Falcon Bill jobs.
- Tracking a three-visit service call from intake to paid invoice
- Logging a visit by voice memo from the truck — the assistant adds it to the job timeline
- Running a week of lawn-care visits across four crews on one calendar
- Handling progress billing on a kitchen remodel across three invoices
- Capturing visit-by-visit photos for insurance-claim backup
- Giving workers a 'my visits' view they can open from a truck cab
- Keeping a multi-property client's jobs neatly separated
- Routing new-lead intake through a public form on your marketing site
- Converting an accepted estimate into a job with one tap
- Using the activity feed as evidence in a dispute months later
- Closing out a job when the last visit wraps and the invoice clears
“The job is the thing that ties the crew, the client, and the paperwork together. I used to have three screens open; now I have one.”
Jobs, by the numbers.
- < 60s
- To open a new job from the dashboard
- ∞
- Visits per job
- 5
- Crew members per workspace on Team
- 100%
- Of statuses enforced through transitions
Your first three jobs are on the house.
No card required. Your data carries into any paid plan the day you upgrade.
Common questions about jobs.
Do I need to use jobs to send an invoice?+
No — you can send a standalone invoice. Jobs add value when a piece of work has multiple visits or a lifecycle longer than a single appointment.
Can workers create their own jobs?+
Depends on their role. Owners and admins can; workers see jobs assigned to them and update visit status from their phone.
What happens to the job when the invoice is paid?+
The job moves to 'paid' automatically. The timeline records the payment and the balance update.
Can a job have multiple invoices?+
Yes, for progress billing or split jobs. Each invoice is tied back to the parent job.
Is there a crew calendar?+
Yes — the schedule view shows all visits across workers. Per-worker filters let dispatchers zoom in.
How does a job get created?+
From the dashboard's quick-add, from a converted estimate, from a client record, or from a public intake form you can link on your own site.
Can visits have their own photos and notes?+
Yes. Photos and notes can live on the job or the visit. Both roll up into the activity feed so nothing gets lost.
What about recurring jobs?+
Recurring jobs are on the roadmap. For route-based work today, duplicate a completed job weekly or use a template saved to the price book.
Try Falcon Bill free. Your first three jobs are on the house, no card required.
Start free