When information is tied to the correct asset, site and source, it is easier to separate confirmed facts from items that need review. Share what is genuinely known and leave uncertain fields clear instead of adding estimates that could affect the quotation scope.
Use one reference and clear revisions
Start with a clear enquiry reference and use it in message subjects, attachment names and every related quotation or order. When a quantity, specification or destination changes, create a new revision with a date and change summary instead of silently editing the previous file. Maintain a question and response register showing owner, status and the document supporting each decision. For a project with several sites or packages, use sub-codes beneath the master reference. This structure prevents old and new versions from being mixed and lets every participant see which scope is under review and which document is waiting for a decision.
Review the quotation against the enquiry
Compare the quotation line by line with the latest enquiry revision: equipment, quantities, services, destination, currency, programme, documents, assumptions and exclusions. Keep questions in one list and do not treat a verbal explanation as a change unless it is recorded in a formal clarification or revision. Where the proposal offers options, separate the selected option from those still under review and make sure the effect of each is visible. Check seller, beneficiary and quotation reference details in the approved document rather than copying them from an old message. Clear approval begins with one version recognised by both parties, not a set of conflicting attachments.
Connect approval and payment to the correct status
After scope approval, keep the order or contract, revision, amount, currency and reference together in one record. Payment details are shared only through the authorised method expressly named in the formal offer, and the beneficiary name and reference should be matched to that offer before any action is taken. Website payment and customer-portal routes are not currently enabled, so payment instructions or status should not be expected to appear on the website. When a notice or receipt is sent by the method stated in the offer, it remains under review until confirmed by the authorised party; sending the file alone does not confirm receipt of funds. Do not apply one project's payment to another reference or publish payment details or documents on a public page.
Track execution and handover under the same reference
Link programme updates, approvals, changes and handover records to the relevant reference and revision. When a change arises, record its description, reason, effect, status and authorised approver before treating it as part of the scope. At handover, use a list of equipment or lines, documents, training and warranties actually included in the contract; do not add an unagreed output or mark it received without a record. Until the customer portal is enabled, project updates and handover documents are exchanged through the formal method identified in the offer or by the project team. This preserves a traceable journey from the first enquiry through completion of the agreed package.