AI-Assisted Consulting

The question behind this article is a practical one I suspect more consultants and enterprises will have to confront: when an external consultant uses AI to work on a client’s problem, is the client taking a materially different risk from the one it already accepts when its own employees use enterprise AI tools?

Until recently, this was rarely part of a consulting engagement. A consultant might receive confidential information, work on it using conventional software, and return the result. AI changes that picture because some of the work may now be processed through an external AI provider.

That can sound more alarming than it actually is if the technical process, the safeguards and the differences between individual and enterprise AI accounts are not clearly understood. The aim of this article is to separate those issues, explain where the real risks lie, and show what practical controls can be used to manage them.

The intended audience is not only consultants. It is also the managers, legal teams and security teams who increasingly have to decide whether AI-assisted consulting can be used responsibly within an enterprise engagement.

1. What happens when AI is used

Q1. Where are the client’s source files and project outputs stored?

The consultant’s working practice is to keep the authoritative source files and project outputs under the consultant’s control on dedicated local computer or server storage, unless another arrangement has been agreed with the client. The use of a cloud AI assistant does not require the consultant to move the client’s primary file repository into cloud storage.

Q2. What happens to client information when the consultant asks AI to work with it?

The AI provider processes the information needed to complete the requested task. This is the same core processing step that occurs when a client employee uses a cloud-based enterprise AI assistant. The original source file can remain on the consultant’s local computer or server; only the content needed for the task is transmitted for processing. That processing does not, by itself, mean the information is used to train the provider’s models or kept as a permanent copy of the original file.

Q3. Does the consultant need to send all of the client’s information to the AI provider?

No. The consultant’s approach is to provide only the information reasonably required for the task. Where a task can be completed with a smaller data set, a limited extract or information with unnecessary identifiers removed, that narrower input can be used instead.

Q4. Does a local-file workflow create a permanent cloud copy of the original client file?

Not simply because the file is used in an AI-assisted workflow. The original file can remain on local computer or server storage while relevant content is transmitted for processing. Depending on the AI service and features used, prompts, responses, task context, uploaded files or technical service data may be retained for a period under that provider’s applicable settings and terms.

2. Processing, model training and confidentiality

Q5. Does AI processing mean the client’s information is used to train or improve the AI model?

No - not merely because the information is processed. Processing a request, often referred to as inference, is separate from using data for model training or model improvement. For client engagements, the consultant’s policy is to disable optional model-training or model-improvement use wherever the provider offers that control. The relevant settings and terms should be verified for each AI service used in the engagement.

Q6. Why does the AI provider need to process readable client information at all?

A cloud AI system must be able to process the information it is being asked to analyse, summarise, transform or use in a task. This is true whether the user is the consultant or an employee of the client. Enterprise controls can govern how that processing is managed, but they do not remove the need for the AI service to process the information required for the task.

Q7. Can personnel of the AI provider ever access client content?

This depends on the provider, product and applicable terms. Providers may allow tightly controlled access for defined purposes such as security, abuse investigation, technical support, incident response or legal obligations. The same provider-side considerations can apply when the client’s own employees use that provider’s cloud AI service. Any specific restriction required by the client should therefore be checked against the selected service’s current terms.

3. Consultant use compared with the client’s enterprise AI use

Q8. Is the client taking a fundamentally different technical risk when the consultant uses a cloud AI assistant?

Not in the core act of cloud inference. In both cases, the information needed for a task is transmitted to and processed within the AI provider’s computing environment. The main differences arise from the surrounding contractual, administrative and governance controls available under the particular account or service used.

Q9. What is the same when the consultant and the client’s employee perform the same AI-assisted task?

The core technical consequence is the same: the AI provider processes the information needed for the task and returns an output. Keeping the original source file on local storage does not change that processing step, and using an enterprise account does not eliminate it. The relevant question is therefore how the processing is governed, what optional uses of the data are disabled, and what retention and access controls apply.

Q10. What additional controls may an enterprise AI service provide?

Depending on the provider and service level, enterprise offerings may include organisation-wide retention policies, administrator-controlled access, audit and compliance tools, data or inference residency options, managed encryption controls, single sign-on, connector restrictions, and business contractual terms or a data-processing agreement. These controls manage and document the use of AI across an organisation; they do not change the basic requirement for the provider to process information during inference.

Q11. Which of those safeguards can a sole consultant apply directly?

A sole consultant can apply a number of the same operational safeguards directly, including limiting the information provided to the AI service, disabling optional training, controlling which connectors are used, keeping source files in the agreed storage environment, retaining project context only while it is required, and deleting client-specific provider-side material when it is no longer needed. Enterprise-only contractual rights, organisation-wide audit controls or provider-side residency commitments remain distinct where the client requires them.

Q12. What should the client focus on when deciding whether this working method is acceptable?

The practical question is whether the consultant’s documented controls and the selected AI service meet the requirements of the engagement. If the client requires its own managed AI environment, a particular data-processing agreement, specified residency, audit capability or another enterprise-only control, that requirement can be identified before confidential information is processed.

4. Retention, deletion and project continuity

Q13. Why may AI conversations be retained during an active project?

Long-running consulting work can depend on decisions, assumptions and design choices made earlier in the engagement. Retaining relevant project context while the work remains active can support continuity, reduce repeated disclosure of the same information and preserve the reasoning behind earlier decisions.

Q14. How is provider-side project context handled when it is no longer needed?

The consultant should retain provider-side project context only while it has a legitimate purpose for the active engagement and remains consistent with the client’s requirements. When that context is no longer required, the consultant should use the provider’s available deletion controls for client-specific conversations, uploaded files and project spaces. The provider’s applicable retention and deletion process then determines when removal is completed from its systems.

Q15. Can useful general learning be retained after client-specific material is removed?

Yes, where the engagement terms permit. General methods, templates and lessons can be retained after client-identifying, confidential and proprietary information has been removed. The retained material should be separated from the client-specific information from which it was derived.

5. Connectors, external services and access

Q16. How are connectors to email, cloud drives, databases or other systems handled?

Each connector creates an additional route through which information may be accessed or transferred. The consultant should use only those connectors that are required for the engagement and appropriate for the relevant data and purpose. The client can identify any connector or external system that should not be used with its information.

Q17. Are connected third-party services covered automatically by the AI provider’s controls?

Not necessarily. Information sent to or retrieved from a connected service may also be subject to that service provider’s own privacy, security and retention terms. Where a connector is proposed for client work, the relevant third-party service should therefore be considered separately.

6. Local storage, backup and resilience

Q18. How is locally stored client work protected against loss?

Client work should have an appropriate backup arrangement so that a failure of the working computer or server does not result in the loss of the only copy. Where cloud backup is not permitted, the backup can be maintained on encrypted local media under the consultant’s control. The arrangement may include an automatic encrypted local backup and a separate encrypted copy that is normally disconnected, subject to the client’s agreed requirements.

Q19. What is the purpose of a separate disconnected backup?

A separate disconnected copy reduces the likelihood that the same event, such as accidental deletion, corruption, malware or an automated process, affects both the working copy and every backup at the same time. Its location, retention period and handling should remain consistent with the client’s confidentiality requirements.

7. Agreement with the client before processing

Q20. What should be agreed before confidential information is processed with AI?

The client and the consultant should be clear on which AI provider or service may be used, what categories of information may be processed, whether any information must be excluded, which connectors or external services are permitted, how provider-side project context will be retained, and whether the client requires use of its own managed enterprise environment.

Q21. What if an NDA or client policy states that confidential information must not be uploaded to the cloud?

That wording should be clarified before confidential information is processed by a cloud AI service. The original file can remain on local computer or server storage, but content required for the AI task must still be transmitted to the AI provider for processing. The client and consultant should therefore document whether the restriction is intended to prohibit cloud storage, cloud processing, or both.

Q22. What is the consultant’s overall operating principle?

The consultant’s approach is to use AI only within the scope agreed with the client, provide the minimum information required for the task, keep authoritative files in the agreed storage environment, disable optional training or sharing where applicable, control connectors and external services, retain provider-side project context only while it serves an active project purpose, and remove client-specific context when it is no longer required.

8. Engagement-specific confirmation

The following items can be confirmed at the start of an engagement so that the client and the consultant share the same understanding of the proposed AI-assisted working arrangement.

• ☐ Approved AI provider(s) and account or service type are identified.
• ☐ The categories of client information that may and may not be processed by AI are identified.
• ☐ Optional model-training or model-improvement settings are disabled where applicable.
• ☐ Any provider-specific data-sharing settings for coding agents or full working environments are reviewed.
• ☐ Permitted connectors and external services are identified.
• ☐ The agreed storage location for primary client files and outputs is identified.
• ☐ The backup arrangement is consistent with the client’s requirements for cloud storage and confidentiality.
• ☐ Retention and deletion expectations for AI conversations, uploaded files and provider-side project spaces are agreed.
• ☐ Any requirement for enterprise-only controls, data residency, audit capability, managed encryption or a data-processing agreement is identified before processing begins.

AI-Assisted Consulting

The question behind this article is a practical one I suspect more consultants and enterprises will have to confront: when an external consultant uses AI to work on a client’s problem, is the client taking a materially different risk from the one it already accepts when its own employees use enterprise AI tools?

Until recently, this was rarely part of a consulting engagement. A consultant might receive confidential information, work on it using conventional software, and return the result. AI changes that picture because some of the work may now be processed through an external AI provider.

That can sound more alarming than it actually is if the technical process, the safeguards and the differences between individual and enterprise AI accounts are not clearly understood. The aim of this article is to separate those issues, explain where the real risks lie, and show what practical controls can be used to manage them.

The intended audience is not only consultants. It is also the managers, legal teams and security teams who increasingly have to decide whether AI-assisted consulting can be used responsibly within an enterprise engagement.

1. What happens when AI is used

Q1. Where are the client’s source files and project outputs stored?

The consultant’s working practice is to keep the authoritative source files and project outputs under the consultant’s control on dedicated local computer or server storage, unless another arrangement has been agreed with the client. The use of a cloud AI assistant does not require the consultant to move the client’s primary file repository into cloud storage.

Q2. What happens to client information when the consultant asks AI to work with it?

The AI provider processes the information needed to complete the requested task. This is the same core processing step that occurs when a client employee uses a cloud-based enterprise AI assistant. The original source file can remain on the consultant’s local computer or server; only the content needed for the task is transmitted for processing. That processing does not, by itself, mean the information is used to train the provider’s models or kept as a permanent copy of the original file.

Q3. Does the consultant need to send all of the client’s information to the AI provider?

No. The consultant’s approach is to provide only the information reasonably required for the task. Where a task can be completed with a smaller data set, a limited extract or information with unnecessary identifiers removed, that narrower input can be used instead.

Q4. Does a local-file workflow create a permanent cloud copy of the original client file?

Not simply because the file is used in an AI-assisted workflow. The original file can remain on local computer or server storage while relevant content is transmitted for processing. Depending on the AI service and features used, prompts, responses, task context, uploaded files or technical service data may be retained for a period under that provider’s applicable settings and terms.

2. Processing, model training and confidentiality

Q5. Does AI processing mean the client’s information is used to train or improve the AI model?

No - not merely because the information is processed. Processing a request, often referred to as inference, is separate from using data for model training or model improvement. For client engagements, the consultant’s policy is to disable optional model-training or model-improvement use wherever the provider offers that control. The relevant settings and terms should be verified for each AI service used in the engagement.

Q6. Why does the AI provider need to process readable client information at all?

A cloud AI system must be able to process the information it is being asked to analyse, summarise, transform or use in a task. This is true whether the user is the consultant or an employee of the client. Enterprise controls can govern how that processing is managed, but they do not remove the need for the AI service to process the information required for the task.

Q7. Can personnel of the AI provider ever access client content?

This depends on the provider, product and applicable terms. Providers may allow tightly controlled access for defined purposes such as security, abuse investigation, technical support, incident response or legal obligations. The same provider-side considerations can apply when the client’s own employees use that provider’s cloud AI service. Any specific restriction required by the client should therefore be checked against the selected service’s current terms.

3. Consultant use compared with the client’s enterprise AI use

Q8. Is the client taking a fundamentally different technical risk when the consultant uses a cloud AI assistant?

Not in the core act of cloud inference. In both cases, the information needed for a task is transmitted to and processed within the AI provider’s computing environment. The main differences arise from the surrounding contractual, administrative and governance controls available under the particular account or service used.

Q9. What is the same when the consultant and the client’s employee perform the same AI-assisted task?

The core technical consequence is the same: the AI provider processes the information needed for the task and returns an output. Keeping the original source file on local storage does not change that processing step, and using an enterprise account does not eliminate it. The relevant question is therefore how the processing is governed, what optional uses of the data are disabled, and what retention and access controls apply.

Q10. What additional controls may an enterprise AI service provide?

Depending on the provider and service level, enterprise offerings may include organisation-wide retention policies, administrator-controlled access, audit and compliance tools, data or inference residency options, managed encryption controls, single sign-on, connector restrictions, and business contractual terms or a data-processing agreement. These controls manage and document the use of AI across an organisation; they do not change the basic requirement for the provider to process information during inference.

Q11. Which of those safeguards can a sole consultant apply directly?

A sole consultant can apply a number of the same operational safeguards directly, including limiting the information provided to the AI service, disabling optional training, controlling which connectors are used, keeping source files in the agreed storage environment, retaining project context only while it is required, and deleting client-specific provider-side material when it is no longer needed. Enterprise-only contractual rights, organisation-wide audit controls or provider-side residency commitments remain distinct where the client requires them.

Q12. What should the client focus on when deciding whether this working method is acceptable?

The practical question is whether the consultant’s documented controls and the selected AI service meet the requirements of the engagement. If the client requires its own managed AI environment, a particular data-processing agreement, specified residency, audit capability or another enterprise-only control, that requirement can be identified before confidential information is processed.

4. Retention, deletion and project continuity

Q13. Why may AI conversations be retained during an active project?

Long-running consulting work can depend on decisions, assumptions and design choices made earlier in the engagement. Retaining relevant project context while the work remains active can support continuity, reduce repeated disclosure of the same information and preserve the reasoning behind earlier decisions.

Q14. How is provider-side project context handled when it is no longer needed?

The consultant should retain provider-side project context only while it has a legitimate purpose for the active engagement and remains consistent with the client’s requirements. When that context is no longer required, the consultant should use the provider’s available deletion controls for client-specific conversations, uploaded files and project spaces. The provider’s applicable retention and deletion process then determines when removal is completed from its systems.

Q15. Can useful general learning be retained after client-specific material is removed?

Yes, where the engagement terms permit. General methods, templates and lessons can be retained after client-identifying, confidential and proprietary information has been removed. The retained material should be separated from the client-specific information from which it was derived.

5. Connectors, external services and access

Q16. How are connectors to email, cloud drives, databases or other systems handled?

Each connector creates an additional route through which information may be accessed or transferred. The consultant should use only those connectors that are required for the engagement and appropriate for the relevant data and purpose. The client can identify any connector or external system that should not be used with its information.

Q17. Are connected third-party services covered automatically by the AI provider’s controls?

Not necessarily. Information sent to or retrieved from a connected service may also be subject to that service provider’s own privacy, security and retention terms. Where a connector is proposed for client work, the relevant third-party service should therefore be considered separately.

6. Local storage, backup and resilience

Q18. How is locally stored client work protected against loss?

Client work should have an appropriate backup arrangement so that a failure of the working computer or server does not result in the loss of the only copy. Where cloud backup is not permitted, the backup can be maintained on encrypted local media under the consultant’s control. The arrangement may include an automatic encrypted local backup and a separate encrypted copy that is normally disconnected, subject to the client’s agreed requirements.

Q19. What is the purpose of a separate disconnected backup?

A separate disconnected copy reduces the likelihood that the same event, such as accidental deletion, corruption, malware or an automated process, affects both the working copy and every backup at the same time. Its location, retention period and handling should remain consistent with the client’s confidentiality requirements.

7. Agreement with the client before processing

Q20. What should be agreed before confidential information is processed with AI?

The client and the consultant should be clear on which AI provider or service may be used, what categories of information may be processed, whether any information must be excluded, which connectors or external services are permitted, how provider-side project context will be retained, and whether the client requires use of its own managed enterprise environment.

Q21. What if an NDA or client policy states that confidential information must not be uploaded to the cloud?

That wording should be clarified before confidential information is processed by a cloud AI service. The original file can remain on local computer or server storage, but content required for the AI task must still be transmitted to the AI provider for processing. The client and consultant should therefore document whether the restriction is intended to prohibit cloud storage, cloud processing, or both.

Q22. What is the consultant’s overall operating principle?

The consultant’s approach is to use AI only within the scope agreed with the client, provide the minimum information required for the task, keep authoritative files in the agreed storage environment, disable optional training or sharing where applicable, control connectors and external services, retain provider-side project context only while it serves an active project purpose, and remove client-specific context when it is no longer required.

8. Engagement-specific confirmation

The following items can be confirmed at the start of an engagement so that the client and the consultant share the same understanding of the proposed AI-assisted working arrangement.

• ☐ Approved AI provider(s) and account or service type are identified.
• ☐ The categories of client information that may and may not be processed by AI are identified.
• ☐ Optional model-training or model-improvement settings are disabled where applicable.
• ☐ Any provider-specific data-sharing settings for coding agents or full working environments are reviewed.
• ☐ Permitted connectors and external services are identified.
• ☐ The agreed storage location for primary client files and outputs is identified.
• ☐ The backup arrangement is consistent with the client’s requirements for cloud storage and confidentiality.
• ☐ Retention and deletion expectations for AI conversations, uploaded files and provider-side project spaces are agreed.
• ☐ Any requirement for enterprise-only controls, data residency, audit capability, managed encryption or a data-processing agreement is identified before processing begins.