← All resources

Maintenance workflows

From Maintenance Request to Paid Invoice: A Workflow Checklist

Map a maintenance request through assignment, approval, completion, invoice review, and payment. Use this checklist to identify missing information and unclear handoffs.

By Angelo Rosso5 min readUpdated October 5, 2026

A maintenance request can be repaired before its paperwork is finished. The resident may have an update while the bookkeeper still needs an invoice. The vendor may submit a bill while the coordinator is waiting for completion details.

Those are separate parts of the same workflow. Making the handoffs visible helps the team understand what is finished, what is waiting, and who should act next.

This checklist is a starting point for mapping your company's process. Adapt it to your management agreements, approval policies, and existing emergency procedures. It describes coordination and recordkeeping; it does not prescribe repair methods or approval amounts.

Start inside your existing maintenance system

Buildium documents task ownership, vendor work orders, estimates, and creating a bill from a work order. AppFolio documents maintenance requests, work orders, and billing and purchase-order approval workflows. Check those native options before introducing a parallel tracker. Feature availability and configuration should be confirmed in your account. Buildium maintenance features, AppFolio maintenance features.

Choose one recent, ordinary request and trace it from arrival to payment. Use the following stages to identify gaps rather than assuming every company needs a new system.

1. Receive the request and identify the next action

Suggested owner: the maintenance coordinator or designated intake person.

Capture enough information to identify the property, understand the reported issue, and contact the right person.

  • Record the property and unit with a consistent identifier.
  • Preserve the resident's description and relevant attachments.
  • Record when and how the request arrived.
  • Identify the person responsible for the next action.
  • Record access or scheduling information in the approved location.

Acknowledge receipt without promising a repair time that has not been confirmed. Requests requiring urgent attention should follow your established emergency route, rather than wait in an ordinary administrative queue.

If requests arrive by phone, email, and portal, decide how each becomes a record in the same operational system. Avoid leaving a request solely in an individual's inbox.

2. Assess the request and obtain required approval

Suggested owner: the coordinator, with approval from the authorized person.

Record what is known, what still needs investigation, and whether approval is required under your company's rules.

  • Define the initial scope clearly enough to assign the work.
  • Check whether an estimate or additional information is needed.
  • Identify the approver when authorization is required.
  • Record the decision, scope, and any agreed limits.
  • Set a next-review date for items awaiting a response.

An unresolved approval should have a visible owner and next step. A status of “waiting” alone tells the next employee very little.

If the scope changes later, route the change through the appropriate approval process. Preserve the updated decision alongside the original work record.

3. Assign the work and confirm the handoff

Suggested owner: the coordinator; next action belongs to the assigned technician or vendor.

An assignment sent is different from an assignment accepted.

  • Give the work order a reference that can follow it through invoicing.
  • Provide the agreed scope and necessary access instructions.
  • Confirm who has accepted the work.
  • Record the appointment or next scheduling action.
  • Tell the resident what has actually been confirmed.
  • Set a follow-up trigger if acceptance or scheduling remains unresolved.

Share only the information needed to perform the work. Keep access details in the appropriate secured system rather than broadly copied messages or general reports.

4. Track progress and handle changes

Suggested owner: the person coordinating the repair.

Use status labels that tell someone what is happening: awaiting approval, scheduling, assigned, in progress, awaiting parts, or ready for completion review. Choose labels your team will maintain consistently.

Each open item should make three things clear: what is blocking progress, who owns the next action, and when it will be checked again.

Record changes in scope and estimated timing. Update the resident when there is meaningful new information, including delays. If the work must be reassigned, preserve the history so the next person can continue without reconstructing the conversation.

5. Verify completion and close the communication loop

Suggested owner: the coordinator or another designated reviewer.

A vendor's “done” message is an input to your completion process. Define what evidence your company needs for this type of work.

  • Record the completion date and work performed.
  • Attach relevant notes or photos where appropriate.
  • Identify remaining work, callbacks, or unresolved concerns.
  • Send the resident an accurate completion update.
  • Make the completion record available to the person reviewing the invoice.

Keep “repair complete” separate from “invoice received” and “paid.” Those events can occur on different dates.

6. Match and review the invoice

Suggested owner: the bookkeeper or accounts-payable reviewer, with approval as required.

Connect the invoice to the work order before moving it toward payment.

  • Confirm the vendor, property, invoice number, and amount.
  • Check the invoice against the agreed scope and approval.
  • Look for a duplicate invoice or prior payment.
  • Obtain missing descriptions or supporting documents.
  • Route discrepancies to a named person.
  • Record the authorized approval and accounting information.

Use the accounting team's established rules for coding and payment. A workflow tool can identify missing fields; the designated reviewer decides how to resolve them.

7. Record payment and preserve the trail

Suggested owner: the authorized payment role.

Follow your normal payment controls. Record the payment reference and status in the accounting system, and handle rejected or unsuccessful payments explicitly.

A payment initiated is not necessarily a payment completed. The record should let the appropriate person distinguish those states.

Link the final invoice and payment information to the maintenance history so a later question can be answered without searching multiple inboxes.

A short review checklist

For a handful of recent requests, ask:

  • Can we follow one reference from request to invoice?
  • Can we see the next action on every open item?
  • Do repair and payment statuses stay distinct?
  • Are approvals and scope changes easy to find?
  • Can another employee continue the work from the record?
  • Where did someone have to ask for information twice?

Choose one repeated gap to improve. For example, make work-order references mandatory in your vendor invoice instructions, then review whether fewer invoices require clarification. Measure the result before expanding the change.

Sources & further reading