Instructions

The instruction is the center of property operation work. It records when the request was made, a record number and subject, the requested amount, an optional instrument, an owner, a counterparty and an organization. Its revision separates the current scope from earlier attempts. A reviewer decides against that exact scope; a provider submission later retains an external instruction identity and reference.

An Operations Analyst starts in draft, checks the counterparty eligibility note and collects the mandate evidence. The request moves into review only when the amount, instrument and counterparty can be checked together. The Independent Reviewer records a decision for the current revision. After authorization, the Provider Coordinator submits the stable instruction identity. The resulting status tells the team whether the request is awaiting provider response, confirmed, rejected or cancelled.

• Preparation. The owner records the requested amount and identifies the organization and counterparty before asking for review.
• Revision-bound review. Every decision names the source revision, so an earlier approval cannot silently cover a changed amount or instrument.
• Outcome tracking. The external identity and provider reference remain on the instruction while execution evidence and operation receipts carry the details of what happened.

Agree what qualifies as a complete instruction for each kind of property operation. Define who may prepare one, who may independently review it and which provider connection is authorized to receive it. Decide how the record number maps to an existing operating reference. If an external system owns the mandate or settled transaction, keep that source authority explicit in the handoff.

Also agree how to handle an uncertain transport outcome. The team should search for the original operation receipt and provider reference before taking another action. The stable operation key makes a repeated equivalent request return its first result; a changed request under the same key should be rejected. This prevents a double submission when a network response is lost.

An Operations Analyst prepares an instruction for a property manager with a requested amount of $2,400. The owner attaches the supporting mandate and moves the request to review. The Independent Reviewer checks that amount, the instrument and eligibility note, and records approval for the current revision. The Provider Coordinator submits the authorized identity and keeps the provider reference. If the provider acknowledgment is delayed, the request remains pending while the team reconciles the receipt and provider evidence.

Change the amount after that approval in a rehearsal. The prior decision must not authorize the revised request. Send an identical submission request twice under the same operation key as another rehearsal: the second attempt should return the original outcome, not create another provider action.

• Instructions by status — Requests grouped by their current operating state, owner and amount.
• Authorized for submission — Approved scope ready for the provider handoff.
• Pending provider response — Requests whose external result still needs to be established.

Review an instruction and verify its provider outcome.