Scope and AI suggestions

Engineer notes hold the internal source wording, including findings and completed work. They do not appear on the customer PDF. The customer-facing scope is the reviewed wording that does.

You can write the customer scope manually, copy engineer notes into it or use an AI suggestion when the company has connected an OpenAI project.

Choose More scope actions → Copy engineer notes, then Copy to scope to copy the whole field. This includes findings and completed work and replaces any existing customer scope. Review the copied wording before customer use. Cancel keeps the current scope; the engineer notes stay unchanged.

Create or tidy a scope

• If the customer scope is empty, Create customer scope uses the engineer notes as the source.
• If a customer scope already exists, Tidy current scope improves that wording without replacing the engineer notes.
• The result aims for concise UK English, corrected grammar and punctuation, and a clear separation between findings, proposed remedial work and customer requirements when the source supports that structure.

The suggestion never applies itself. The estimator compares it with the source and chooses whether to apply it, retry or keep the current wording.

Review before applying

The review sheet places the source and suggestion side by side. Expand the exact wording changes when you need a word-level comparison. Quote Control also reports editorial changes, possible omissions and questions that remain internal.

Deterministic checks protect identifiers, quantities, measurements, amounts, dates, times, URLs and links. If one changes, the suggestion cannot be applied. The estimator must correct or retry it.

Editorial help, not technical approval

Check every technical detail before applying a suggestion. The AI service can improve wording; it cannot confirm the proposed repair, design or compliance of the work.

Privacy and records

The source text is sent by the Quote Control server to the company’s configured OpenAI project. Quote Control records privacy-safe run metadata and whether the user applied, kept, retried or restored the result. The trace does not store a second copy of the source or generated wording.

Manual editing remains available when the integration is absent, unavailable or at its monthly pilot limit.

Add prepared assets to the scope

Each asset-preparation task keeps its internal costing checks separate from the customer wording. When a task’s recommendation is ready, choose Add to customer scope. Quote Control appends the asset and recommendation once; it does not maintain a hidden live link or overwrite later customer edits.

Edit the required part quantity and unit cost on the asset task, then use Save draft. A unit change opens a separate quantity and cost review. Editing or applying a review does not mark a supplier cost as received. When Part cost received creates a linked pricing line, Scope of works remains the owner of that quantity and unit. Pricing displays the resulting value as Managed in Scope of works.

When Access cost received is selected, enter the confirmed access amount. Quote Control creates a separate quantity-one Access linked item. The access value is reported under Other costs and can be cleared without removing a received part cost. Access never becomes a supplier purchasing item.

Where enabled, the engineer-report workflow can create an editable draft before review. Creating it does not accept the proposed scope or pricing. Follow that guide to review and explicitly accept the proposal before submission. Included work already represented in the customer scope is marked as prepared so it is not appended again.