How it works
One request, five stages, one clock.
Every job runs the same path, whether it is a nightly janitorial contract or a supply line that let go at 6am. The path is short on purpose, and each stage leaves a record you can hand to an owner without rewriting it.
The trades we cover- Stages a job passes through
- 5
- Emergency response targetWe call back to say if we can cover it
- None yet
- Statements to reconcileper month, per organization
- 1
The path
From a phone at 06:12 to a statement line on October 1.
A real plumbing call, with the times it actually ran. The clock on each stage is elapsed from the moment the request was submitted.
Water pooling at the base of a water heater in unit B12. Submitted 06:12, assigned 06:16, on site 07:41, closed with photographs 09:03. The times illustrate the targets we dispatch against. They are not an average of completed work, because there is none yet.
Stage by stage
What happens, and what gets written down.
The right-hand column is the part that matters later. A job with no record is a job you cannot bill with confidence or defend to an owner.
| Stage | What happens | What is recorded |
|---|---|---|
| 1.0Request | A manager submits from a phone: the property, the unit, what is happening, a photo, the gate or lock-box code, and how fast it needs to move. Under six steps, one screen. |
|
| 2.0Dispatch | The HQ board ranks vendors who cover that trade in that city, have capacity in the window, and whose insurance is current today. A dispatcher assigns from the ranked list. Emergencies pin to the top of the queue. |
|
| 3.0On site | The vendor starts the job in the app. The clock runs, the location is stamped, and photographs go in before anything is touched. If the phone loses signal in a stairwell the start queues locally and syncs when it comes back. |
|
| 4.0Proof | The vendor ends the job, photographs the finished work, and writes what was found and what was done. The manager has the record the same day, in a form you can forward to an owner without editing. |
|
| 5.0Invoice | The job becomes one line on one monthly statement, alongside every other job across every property in the portfolio. Each line drills back to its work order, its photographs and its timestamps. |
|
The mechanisms
Five things that hold the path together.
Any coordinator can promise a fast response. These are the parts of the system that make the promise survive a Sunday night.
An expired certificate blocks the assignment, not the invoice.
Compliance is checked before a vendor is offered the job, not discovered in an audit six months later. 1Stop holds the certificate of insurance, the W-9 and the trade licence, tracks the expiry dates and warns at 30 days. An expired file drops that vendor off the ranked list on its own, so nobody has to remember.
The clock starts at submit, not at assign.
Response time is measured from the moment the request lands, the only measurement a property manager cares about. Measuring from assignment would let us look fast by taking a long time to start, so we do not measure it that way.
A job cannot be closed without photographs.
Before and after photos are part of ending a job, not an optional attachment. That is what makes a completed job forwardable to an owner, and what turns a disputed invoice into a two-minute conversation instead of a two-week one.
The job clock survives a dead zone.
Start and end actions queue on the phone and sync when connectivity returns. A crew in a concrete stairwell or a mechanical room does not lose a job clock, and does not have to guess at the times afterwards.
One counterparty, and no question about whose problem it is.
1Stop is the contracted party on every job. We pay the vendor, we invoice you once a month, and when work has to be put right we send someone back under the same contract. That is a commitment we make to you rather than an insurance policy, and our terms set out its scope and limits.
The exception
A turn is not one job. It is five, in order.
Everything else on this page describes a single dispatch. A unit turnover is a sequence with a critical path, so we schedule it as one thing with one finish date rather than five phone calls that each cost a day.
| Step | The work | What it holds up |
|---|---|---|
| 1Trash-out | Everything the resident left, plus whatever the move-out inspection flagged. | Blocks every other trade. Nothing starts in a full unit. |
| 2Clean | Kitchen, bathrooms, appliances, windows, blinds, and the balcony everybody forgets. | Blocks paint. Painters will not cut in over grease. |
| 3Paint | Walls, ceilings, trim, and the two doors nobody notices until the walk. | Blocks carpet. Paint on new carpet is a second turn. |
| 4Carpet | Cleaned, or replaced on a schedule set by the unit's own history. | Blocks the punch walk. |
| 5Punch and inspect | The list of small things, then the walk that closes the turn. | Releases the unit to be listed. |
The order matters
Scheduled as five separate calls, every handoff is a day. The cleaner finishes Tuesday, the painter has Thursday open, and nobody told the carpet installer. Scheduled as one sequence, the finish date is set before the first crew arrives and the days between trades stop existing.
In Orlando those days cost $58.90 each. Average asking rent is $1,767 a month (Yardi Matrix, May 2026), and rent divided by thirty is what an empty unit gives away every day it waits on a trade. A 250-unit community runs about 107.5 turns a year at the 43% turnover rate in Zego's 2026 survey of 630 property managers, so five days off the cycle is $31,659 of rent recaptured.
Published benchmarks, not results of ours. RealPage puts the average vacant stretch at 34.4 days, which is the number the sequence is trying to cut into.
The arithmetic on one propertyRun one job through it.
One property, one request, and you can read the whole path yourself before deciding anything.
Request a service