Compare Property-Manager Purchasing Mandates
Compare two building mandates behind one manager and invoice portal, with a bounded proposal request accepted and an unsupported expansion rejected.
10/24/20263 min read
The same property manager and invoice portal can serve two buildings under different purchasing instructions. Treating the portal as the buyer identity can send a proposal to the wrong contracting party or silently extend approval beyond one building. Compare the actual authorized scope before combining locations into a single opportunity.
The fictional example below uses two explicit owner-approved instruction sheets supplied for the exercise. They are invented operational mandates, not interpretations of unseen leases or real contracts. All organizations and outcomes are hypothetical. Actual contracting authority belongs with the responsible commercial and legal owners.
Compare two mandates, not two logos
Harbor Management coordinates both Alder House and Briar House. Alder Assets owns Alder House; Briar Estates owns Briar House. Both sites use Harbor's P3 invoice-processing portal. The proposed service is a visual inspection and written condition report for common-reception information panels, with no repair, replacement or tenant-space work.
The supplied instruction MA4 applies to Alder House. Harbor may coordinate access arrangements and request a proposal for that defined inspection. Alder Assets' designated reviewer must approve the scope and price, and Alder Assets is the named contracting party. No work is authorized merely by requesting a proposal.
The supplied instruction MB2 applies to Briar House. For the same listed common-reception inspection, Harbor may contract in its own name after approval by Harbor's operations lead. Tenant equipment is excluded. Replacement work requires a fresh decision from Briar Estates through the documented owner route. The two sheets deliberately establish different boundaries.
Decision field: Proposal coordinator
Alder House: MA4: Harbor Management
Briar House: MB2: Harbor Management
Decision field: Inspection approval
Alder House: MA4: Alder Assets' designated reviewer
Briar House: MB2: Harbor's operations lead
Decision field: Inspection contracting party
Alder House: MA4: Alder Assets
Briar House: MB2: Harbor Management, within MB2
Decision field: Invoice-processing route
Alder House: MA4: P3 portal
Briar House: MB2: P3 portal
Decision field: Excluded expansion
Alder House: MA4: Tenant equipment and replacement work
Briar House: MB2: Tenant equipment; replacement needs a new owner decision
The shared coordinator and administrative route are real similarities within the example. They do not erase the different principal, approver or mandate version. Store those fields separately so a copied portal address cannot overwrite the contracting-party field.
Complete the accepted-request test
Request R21 comes from Harbor coordinator Hana: prepare a proposal for the defined inspection at Alder House under MA4. The researcher compares the building, task and requested next action against MA4. All three fit: Alder House, inspection only, proposal preparation only.
The completed decision is “accepted for bounded proposal preparation.” The draft names Alder Assets as the prospective contracting party, lists the common-reception panels, excludes tenant equipment and replacement, and identifies the designated owner's scope-and-price approval as pending. Hana is the coordination contact, not automatically the person accepting the purchase.
No work order is created and no site visit is booked. An accepted request to prepare a proposal is not an accepted contract. The P3 portal is recorded as a later administrative route if the required approvals occur, not evidence that a purchasing commitment already exists.
Reject the expansion without losing the original
A second fictional request, R22, says to add replacement of a tenant's badge reader at Briar House “under the Alder proposal approval” and use the same P3 portal. The reviewer records three failed comparisons. The building changes from Alder to Briar; the task changes from inspection to replacement; and the item lies in excluded tenant scope.
There is also no Alder proposal approval in the completed record: R21 only authorized preparation. Even a later Alder approval would not establish Briar authority. MB2's permission for a common-reception inspection does not cover this replacement request.
R22 is therefore rejected as an expansion of R21. The existing Alder draft remains bounded and unchanged. Any Briar replacement proposal would need a separate scope and the appropriate fresh owner decision, including resolution of the tenant-equipment boundary. The researcher does not contact the tenant or seek site access on the strength of the portal message.
Preserve the reconciliation in the account record
The final ledger has two requests: one accepted for proposal preparation and one rejected expansion. Neither is a completed sale or permission to perform work. For each, retain request reference, site, mandate version, task, prospective contracting party, required approver, administrative route, disposition and reason.
Companies House's company-information service provides specified filed information such as registered addresses and officers. That can help distinguish legal entities. It does not establish these fictional mandates, current building responsibility or authority for a particular purchase.
The useful research outcome is not merely knowing that Harbor manages both buildings. It is being able to explain why the same coordinator's first request fits one documented boundary while the second does not. Recheck the relevant instruction when the site, task, principal or approval changes; do not let a familiar invoice route become an all-purpose authorization.