Sequencing failures
Painters arrive before flooring is done. Cleaners show up before trash is out. Every trade out of order creates another chance to lose a day.
Turns360 | A Field & Key operating initiative
Turn intelligence for property operations.
The property management industry still runs too many turns through spreadsheets, text threads, vendor memory, and somebody who knows how to keep the whole thing moving. Turns360 was designed around a different idea: own the full path from inspection to ready.
The operator reality
Everyone can finish their task and the unit can still be late.
Inspection gaps
The problem found after dispatch is almost always more expensive than the problem caught before scope.
Tribal knowledge
The process lives in the head of the person who knows which vendor to call, what order the work should happen in, and what usually goes wrong.
Visibility too late
Leadership finds out the turn is in trouble when a move in date is at risk instead of when the first dependency slipped.
What Turns360 is
Service led. Intelligence backed. Built around the operator.
Turns360 is a coordination and intelligence service that sits above existing vendors and staff. The goal is not to replace the PMS or force the property team into another system all day. The goal is to keep the turn moving, catch issues early, and close the unit against the work that was actually approved.
01
Service led
Coordination, sequencing, vendor follow up, materials, approvals, and exception handling stay with the service instead of being pushed back onto the property team.
02
Intelligence backed
Inspection findings become structured scope, approval decisions, dependency logic, and quality control instead of another set of notes somebody still has to interpret.
03
Operator ready
The workflow is built around the way property teams actually make decisions, including thresholds, exceptions, field verification, and portfolio learning.
The intelligence layer
This is where the model becomes different.
Inspection to scope
Field findings convert into structured scope before dispatch so the turn starts with a clearer understanding of what is actually there.
Approval logic
Items inside agreed thresholds can move. Items outside them surface with enough context for someone to make a decision without freezing the whole turn.
Exception routing
When something changes mid turn, the issue is identified and routed while there is still time to recover.
Quality control
Closeout is measured against the approved scope for that unit, not a generic checklist and not vendor self report alone.
Portfolio learning
Each completed turn should improve cost signals, exception patterns, vendor understanding, and the next operating decision.
Connected economics
Turn time, cost, readiness, leasing deadlines, and vacancy belong in the same operating conversation because the property experiences them as one result.
How it works
Five steps. One connected workflow.
01
Inspect
Start with what is actually there. Capture condition in a format that can move directly into the work.
02
Scope
Translate findings into a structured scope with trade categories, dependencies, materials, cost expectations, and approval needs.
03
Sequence
Run the work in dependency aware order and adjust quickly when a blocker changes the plan.
04
Verify
Move forward on evidence. At closeout, verify the unit against the work that was approved.
05
Learn
Use time, cost, exception, rework, and vendor data to make the next turn cleaner and more predictable.
Why it belongs inside Field & Key
Turns are an operating problem before they are a software problem.
The same question that shaped the leasing work shows up here too. If the organization keeps rescuing the outcome after the process breaks, eventually the process itself has to change.