What should block a unit-turn task from being marked complete?
Format: Article.
Block completion when the agreed work is unfinished, the evidence points to the wrong unit, a required review is missing, or a dispute remains open. A vendor saying “done” is a report to check. It is not the same as a manager accepting the task or authorizing the unit for its next use.
A unit turn is the work done between occupants. One crew may need another crew to finish first. The office needs to know which task must wait, why, and who can clear the hold. One green badge for the whole unit hides those details.
Set completion rules before the visit
When you assign a task, write what will count as done. Name the unit, agreed work, proof needed, and person who will check it. Ask what that person needs to see. A choice of file format is not a test of the work.
Buildium's maintenance guidance recommends documenting what was done, when, by whom, and at what cost, with a completion check before closing a request. Its guidance does not certify the result of a unit turn. [S01] Your team still needs task-specific rules and qualified people for technical or safety questions.
Keep three fields separate: work reported finished, evidence reviewed, and task accepted. A photo upload may satisfy the first evidence request while leaving acceptance open.
Copy this readiness and completion matrix
The sample rows below are proposed controls, not inspection standards. Replace them with your approved work scope.
| Turn task | Ready to start when | Evidence for review | Completion blocker | Decision owner |
|---|---|---|---|---|
| Repair wall area | Agreed repair and required earlier work checked | Vendor note identifying the area and work performed | Different area repaired or scope unclear | Maintenance lead |
| Paint repaired area | Required prior work accepted | Dated task record and agreed photos | Evidence predates the repair or finish is disputed | Turn supervisor |
| Clean the unit | Work area released under site procedure | Area checklist and supervisor findings | Locked room omitted without a recorded exception | Cleaning supervisor |
| Replace listed fixture | Exact fixture and approved scope confirmed | Qualified worker's completion record | Wrong fixture or required technical review missing | Authorized maintenance reviewer |
| Assemble turn packet | Individual task records available | Accepted-task list and open holds | A required task is still unreviewed | Property manager |
A dependency means one task must wait for another. Do not guess this from row order in a sheet. State it: task P cannot start until task R passes its required check. If work may start in another room, name that room. Do not clear the whole unit.
Handle partial work without false closure
Give part-done work its own state. Note what is done, what is left, why, and who owns the next visit. A manager may approve less work than first planned. Record that as a change. It does not prove the full original task was done.
Also separate a missing attachment from a disputed result. For missing evidence, request the specific record. For disputed work, keep both accounts and assign a reviewer. Asking the vendor to upload the same photo again will not settle a disagreement about what the photo shows.
Use a dispute card. Include the task ID, agreed test, vendor's account, and the report that conflicts with it. Name any tasks that must wait, the reviewer, and the next check. Leave the close date blank until the person with authority decides. If a task reopens, keep the earlier decision and add the new event.
Hypothetical example: paint marked done too soon
In a fictional unit turn, a painter reports that the bedroom wall is finished. The attached image was taken before the wall repair was accepted. The turn coordinator does not reject the workmanship from the photo alone. Instead, the task moves to “evidence needs review.”
The supervisor checks the location and visits the room. The repaired section still needs finishing, while the rest of the room matches the agreed scope. The supervisor records partial acceptance, assigns the remaining section, and holds the final cleaning task for that area.
The office may plan work in another room if that room has passed its own checks. That does not make the whole unit ready for leasing. A vendor bill or planned move-in date must not mark the work done.
Review what the blocked queue tells you
At the turn meeting, sort holds by cause. Is earlier work still open? Is proof missing or tied to the wrong unit? Is review due, or is the result in dispute? Give each hold an owner and next check. Do not score a vendor from the hold count alone. Check the facts first.
Test the system with an old photo, a missing room, and a task reopened after acceptance. Confirm that each dependency returns to the right state and that a due date cannot override a hold.
Core Agentic can discuss a custom design to review turn tasks with these records. It is not a finished unit-turn product. Software cannot certify that a unit is fit to live in, safe, or ready to lease. People with the right authority and professional guidance make those decisions.
Book a Demo to discuss task evidence and dependency checks for your turn process.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.