Skip to content

Owner Relations research

Measuring owner approval aging without overclaiming

A research brief on timing owner approvals in property management, separating the request, the review, and the decision from the outcome.

| 3 sources sources

Measuring owner approval aging without overclaiming
Table of contents

A repair estimate goes to the owner for approval. The owner is traveling, the email is buried, and the vendor is waiting. Three days later the approval arrives, and the repair is scheduled. The property manager remembers the delay but cannot say whether it was the owner, the request, or the follow-up.

Owner approval aging is the time an item waits for an owner decision. It is a useful measure because delays affect repairs, vendor relationships, and resident satisfaction. It is also easy to misread. A fast approval may be a rubber stamp, and a slow approval may reflect a complex decision.

What the measure can show

The measure can show when the request was sent, when the owner opened it, and when the decision arrived. It can show the distribution by owner, property, and request type. It can show the requests that are still open.

Those facts support a review of the approval process. A cluster of delays with one owner may need a different communication channel. A cluster of delays on one request type may need a clearer template.

What the measure cannot show

The measure cannot show whether the owner had enough information to decide. It cannot show whether the approval was good or whether the repair was necessary.

The measure also cannot show cause without the stage breakdown. A slow decision may be a missing document, a busy owner, or a request that was never sent.

Methodology

This brief reviews public guidance on records, internal control, and privacy, and maps it to a private owner approval process. The sources support documentation and review discipline. They do not prescribe an approval target or measure owner satisfaction. The proposed stages are an operating design.

Define the request and the decision

Record the request type, the amount, the property, the vendor, and the decision needed. A request that says "approve repair" is not enough. The owner needs the scope, the cost, and the alternatives.

The decision should be recorded in the owner's words or a clear status. "Approved as submitted" is a decision. "Sounds good" may need a follow-up.

Separate the stages

Record when the request was sent, when the owner first viewed it, and when the decision arrived. Sent-to-view measures the owner's attention. View-to-decision measures the owner's review. The total is the owner's experience.

If the request was sent to the wrong address or bounced, that is a routing problem, not an owner delay. Record it separately.

Check the completeness before sending

A request that is missing the scope, the cost, or the photos will come back with questions. Check the packet before it goes out. A complete request is more likely to get a timely decision.

The template should include the decision options and the deadline. An owner who knows the repair is urgent can prioritize it.

Use the channel the owner prefers

Some owners prefer email, some prefer a call, and some prefer the portal. Record the preference and use it. A request sent to a channel the owner ignores is not a fair test of their responsiveness.

If the owner does not respond, try one alternative channel before escalating. Record the attempt and the time.

Review the aging by owner and type

Look at the requests that remain open and the owners with the longest delays. A pattern may indicate a communication gap or a request that is too complex.

Do not use the measure to rank owners. Use it to improve the request and the follow-up. A short conversation about the preferred channel is often more effective than another reminder.

Protect the owner's information

Approval records can include financial and personal details. Keep them in the approved system and limit access to the people who need them. Do not share an owner's decision in a broad channel.

Set a retention period with the property's records policy. An approval archive kept indefinitely creates risk without adding insight.

Keep the template short

A request that takes ten minutes to read will not get a fast decision. Use a one-page template: scope, cost, photos, options, and the deadline. The owner should be able to decide without opening another document.

A short template also makes the request easier to review. A long narrative hides the decision.

Record the follow-up

If the owner does not respond, record the reminder and the channel. A single reminder is reasonable; a daily stream is not. The record should show what was tried and when.

If the item is urgent, escalate it through the approved path rather than sending another reminder to the same inbox.

Decide what the review will change

Before the review, name two changes the team would make depending on the result. If the send stage is slow, the team might change the template. If the decision stage is slow, the team might change the channel.

Share the summary with the property manager and the owner coordinator. Both see different parts of the process and can suggest a fix that fits the owner relationship.

Use the log in the owner review

Bring the open approvals and the aging pattern to the owner review. The conversation can cover the request format, the preferred channel, and the decision timeline. That is more useful than another reminder.

The review should produce one or two changes. A new template or a channel change is enough. Record the change and the date.

Keep the sample honest

A review of one month and one portfolio is a check, not a benchmark. Say so. Report the count and the request types so the reader can judge the evidence.

A small sample can show a pattern but cannot support a percentage for every owner. The review should be repeated before a conclusion is treated as stable.

Keep the request visible

A request that disappears into an owner's inbox is not a decision. Use a shared tracker that shows the open requests and the next follow-up. The property manager should be able to see the queue without asking the coordinator.

Visibility also helps the owner. A short list of pending approvals is easier to act on than a search through email.

Record the outcome

Close the loop with the decision and the next action. An approval that is recorded but not acted on is only half the process. The property manager should be able to see what was approved and what happened next.

A short outcome note is enough. It keeps the next review from reopening the same request.

Bounded pilot

Review one month of owner approvals. Record the request, the send, the view, the decision, and the outcome. Report the open items and the time by stage. Ask a reviewer who did not send the requests to explain where the delay sits. If they cannot separate a routing problem from an owner delay, the fields need work.

Limitations

This brief describes an operating measurement model. It does not establish an approval benchmark, a legal standard, or a measure of owner satisfaction. The cited sources support general records and control principles. Results depend on the completeness of the requests and the accuracy of the timestamps.

Sources

  1. The Green Book; U.S. Government Accountability Office; checked November 10, 2026.
  2. Records Management; U.S. National Archives and Records Administration; checked November 10, 2026.
  3. Privacy Framework; National Institute of Standards and Technology; checked November 10, 2026.

Conclusion

Owner approval aging is useful when it is split into send, view, and decision stages and paired with the request quality. The measure cannot prove that an approval was good. It can show where the process waits and which request or channel change would help.

For related workflows, see the inspection closeout brief and the property management VA services overview.