Community Site Change Requests: Track the Proposal Without Updating Records Too Soon
Capture proposed changes affecting a community site with source documents, required reviews and a clear distinction between a request and an authorized completed change.
By PortfolioRental Editorial Team · · Updated 2026-10-19
In this article
A request affecting a community site may involve several records and reviewers. The administrative danger is treating the first message as a completed change, updating the directory or map before the authorized process has resolved what should happen. A change register preserves the proposal and makes its actual stage visible.
This workflow does not decide whether a proposed physical, occupancy or agreement change is permitted. Those decisions belong with the authorized community team and appropriate professionals under the applicable process.
Capture what is being proposed
Record the site reference, sender and specific requested change. Preserve attached documents and distinguish a question about possibilities from a formal request for action. Do not broaden the scope based on a casual conversation.
If the request contains several independent changes, separate their review questions while linking them to the same source. Approval of one part should not silently authorize the others.
Identify the required review route
Use the community's approved procedure to determine who reviews the request and what records they need. The assistant should not create a checklist of legal or technical requirements from memory. Ask the responsible owner to resolve any uncertainty in the process.
| Change stage | Administrative record | What should not happen yet |
|---|---|---|
| Inquiry received | Original question and site reference | Treating the question as an approved action |
| Information collected | Requested sources and remaining gaps | Declaring the packet sufficient without required review |
| Decision pending | Exact question and responsible reviewer | Updating active records as if approved |
| Decision recorded | Authorized outcome and conditions | Assuming the physical or operational change occurred |
Keep the status labels meaningful. An approved proposal and a confirmed completed change are different events.
Maintain the current record during review
Preserve the existing approved information while noting the pending proposal in the appropriate place. Do not overwrite a current contact, site description or document reference merely because a replacement has been suggested.
If an open task depends on the proposed change, flag that dependency. The receiving coordinator should know whether to use the current record or seek an authorized instruction before proceeding.
Record the decision with its conditions
Link the answer to the exact proposal and documents reviewed. Preserve limitations, requested follow-up and any outstanding professional confirmation. If the response is ambiguous, clarify it before communicating an instruction externally.
Do not interpret silence or a general acknowledgment as approval. Keep the case pending under the approved follow-up process until the necessary answer is established.
Reconcile records after the authorized event
When the responsible person confirms that the appropriate change has occurred, update affected records through the approved process. Identify directories, maps, tasks and communication templates that may need revision. Retain relevant history so earlier work remains understandable.
Property management support can maintain the register and coordinate those updates. The objective is an accurate account of proposed, approved and completed changes, with each decision remaining under the community team's control.