In this article
“Done” can mean the technician finished, the coordinator reviewed the result, or an invoice moved forward. A good maintenance map never asks one word to stand for all three.
Define the finish line for each role
AppFolio’s Vendor Portal guide distinguishes work-order stages from invoice and payment stages. That separation is useful context: a completed service visit does not by itself establish that every administrative or communication step is finished. This article proposes an editorial closure method, not new product status definitions.
Start by listing the evidence each role needs. The service provider reports what work was performed and any follow-up limitation. The coordinator checks the report against the original scope. The accounting role follows the organization’s invoice-review controls. The resident-facing role closes the communication loop. Some teams combine these roles, but the separate responsibilities still exist.
Keep factual evidence close to the work
A work summary should distinguish observed conditions, work actually performed and recommendations for later. Do not treat a recommendation as an approved additional job. Where photos or documents are appropriate, keep them in the authorized record and avoid exposing unrelated resident information.
If the report says the symptom could not be reproduced, preserve that uncertainty. Rewriting it as “issue fixed” makes the record cleaner but less accurate. An unresolved condition may need another operational decision even when the original visit has concluded.
Fictional crossing: a repair with a second step
A vendor completes the temporary work described in the assignment and notes that a separate component needs assessment. The coordinator confirms the completed scope, opens the appropriate follow-up through the company’s process and tells the resident what is known. The team does not imply that the recommendation has already been authorized.
Use a closure receipt, not a victory message
A practical closure receipt answers four questions: what scope was completed, which evidence was reviewed, what remains open, and who owns the remaining work. It is an internal method for clarity, not a legal acceptance document or guarantee of workmanship.
- Completed scope is tied to the original assignment.
- Exceptions remain visible with a responsible role.
- The resident update matches confirmed facts.
- Invoice handling stays with authorized reviewers.
Do not let payment status rewrite the story
An invoice question can remain open after an operational issue is resolved, and operational follow-up can remain open after an invoice moves forward. Keep these tracks linked but distinct. This site cannot approve invoices, assess contract obligations or determine when anyone must be paid.
Review a sample of closed work periodically for missing receivers rather than rewarding a low open-item count alone. If a task was closed while its next step moved to an untracked inbox, the visible metric improved without the handoff improving. Compare this with reading reports as workflow questions and keeping a change trail.
Source notes and boundaries
Public sources checked October 21, 2026. The process methods and fictional examples are original editorial guidance, not AppFolio instructions or a test of a private account. Features, labels and permissions can vary.
- AppFolio Vendor Portal overview — Vendor work-order stages and coordination; completion, invoice review and payment are distinct states.