Organize conflicting commercial HVAC buyer instructions for review

Keep the competing requests as separate evidence

A facility contact, procurement person and property manager may give different instructions about the same opportunity. Capture each actual statement with sender role as verified, date, source reference, affected scope/version and requested decision. Ask AI to group conflicts without choosing whose instruction governs.

This is not another account map or change-order intake list. Its output is a decision register for incompatible instructions before the team proceeds. Keep technical interpretation, commercial authority and agreement meaning with their responsible reviewers. A senior-sounding title or a later timestamp should not substitute for actual authorization.

Use a fictional schedule conflict

A fictional approved proposal includes weekday work. A facility contact later requests a weekend window, while a procurement message says no price increase is authorized. The register should show the timing request, the commercial constraint and the current approved baseline as three distinct facts. It must not promise the weekend at the old price or reject the request as impossible without operational review.

Add an owner for the specific question: operations reviews feasibility, estimating reviews the approved commercial implications and the account owner clarifies the customer’s authorized decision route. If the records do not establish who can approve the combined outcome, leave authority unresolved and prepare a focused question through the existing channel.

Record the actual resolution before handoff

Use columns for conflict ID, statements/sources, baseline affected, possible consequence requiring review, decision owner and status. Preserve the difference between a proposed resolution, internal approval and the customer’s verified decision. AI can draft a concise meeting agenda but should not send messages or change the opportunity.

When a resolution is authorized, record its source and update the appropriate controlled document through the responsible person. Do not merely replace the old note with a smoother summary. Test the register on fictional competing instructions, an explicit correction from a verified approver and a message with uncertain authority. Measure unsupported overrides and missing conflicts. A register is useful when it makes the next decision clear, not when it makes every disagreement appear resolved.

Review checklist

• Preserve every statement and source date.
• Identify the approved baseline affected.
• Separate authority, feasibility and price review.
• Record verified resolution before operational handoff.

Source context and limits

NIST supplies general context on unreliable generated conclusions. This administrative decision register is our proposed method, not a determination of legal authority or a technical interpretation of customer requirements.