From request to resolution: architectural and maintenance workflows

1. Use one intake route, then classify the work

Collect a description, location, contact, useful photos or documents, and the requested outcome. Assign a reference so the resident and board can discuss the same issue. Avoid collecting unnecessary personal information. A shared intake does not mean every request follows the same decision process.

Classify the request early: association maintenance, owner responsibility question, architectural change, possible emergency, or a sensitive accommodation issue. An emergency should reach the appropriate emergency or professional response route immediately; it should not wait in an ordinary board queue. This guide is not an emergency-response or engineering manual.

2. Make authority and responsibility visible

Identify who may investigate, request more information, approve spending, authorize a change, or issue a decision. A committee may review a submission without having final approval authority. Record the relevant document or policy and have counsel resolve unclear responsibility or process requirements.

For an architectural request, use a completeness checklist drawn from the applicable standards and verified rules. For maintenance, identify the asset, symptoms, prior work, warranty, and access needs. Fair-housing accommodation requests can require a separate legal analysis; do not automatically treat them as an ordinary aesthetic exception or demand public discussion of medical information.

3. Keep reserve planning and maintenance connected

The Foundation’s maintenance report distinguishes preventive maintenance, inspections, and reserve studies. A reserve estimate does not replace a maintenance schedule or a professional investigation of a new condition. Record recurring inspections and service tasks separately from capital replacement assumptions.

When work is assigned to a vendor, define the scope and what evidence will demonstrate completion. Record approval, quote, scheduling, access arrangements, change orders, and warranty information. Protect residents’ private details when sharing a work order. A vendor marked “scheduled” is not the same as work verified complete.

4. Close with evidence and a usable history

Before closing, confirm the authorized work or decision, record the outcome, and tell the resident what happened or what remains unresolved. If the issue belongs to the owner, explain the responsibility finding and appropriate next route without making an unsupported legal determination. Preserve denial or approval reasons where required.

Link repeat reports to the asset history rather than losing them in a new inbox thread. Review requests that are waiting for information, awaiting a board decision, with a vendor, or overdue for follow-up. Status categories should describe real next actions, not create the appearance that work is progressing when no person owns it.

The working process

1. Capture the issue, location, contact, evidence, and a stable reference.
2. Classify the request and route emergencies or sensitive matters appropriately.
3. Verify responsibility and decision authority before promising approval or work.
4. Assign the next action, owner, supporting scope, and follow-up date.
5. Verify the outcome, communicate it, and preserve the asset or request history.

A worksheet to use with your board

Copy these prompts into your working plan, or use the writing space in the PDF. Keep private owner information and account secrets out of a broadly shared worksheet.

• Request reference / classification / received date
• Responsibility source / decision authority / open question
• Next action / assigned person / follow-up
• Vendor scope / approval / completion evidence
• Resident update / outcome / record location

Before you call it complete

• Request classification recorded
• Urgent issues have a separate response route
• Responsibility and authority checked
• Sensitive requests handled privately
• Scope and approval retained
• Follow-up dates visible
• Completion evidence reviewed
• Repeat issues linked to asset history