Lucknow, India

Service Planning

Manage sensitive information during service discovery

Share enough context to assess a workflow while keeping unnecessary personal and confidential data out of early discussions.

IGS Editorial · 3 min read · Updated 17 November 2026

Manage sensitive information during service discovery — editorial artwork
Illustrative service planning image

Discovery helps a provider understand a process, but it does not require unrestricted access to production information. Early conversations often need examples of structure and complexity rather than real customer identities or complete transaction histories.

Begin by deciding what question each piece of information will answer. If a process description is enough, do not send a live dataset. Sharing less at the outset can make the discussion easier to manage without reducing its usefulness.

Start with process descriptions

Explain the workflow, systems, volumes and exception types. Use field names and representative shapes rather than full records where practical. A screen layout may be described without exposing actual accounts.

Avoid including credentials, authentication codes or unrestricted system links in a brief. Access should follow an approved process, not arrive as an incidental attachment to a meeting invitation.

Prepare safe examples

Use synthetic examples when they can demonstrate the issue accurately. If real material is necessary, apply an appropriate review and protection method. Removing a name alone may not make a record anonymous if other details identify the person or organisation.

Check document properties, hidden spreadsheet tabs, comments and image backgrounds. Information can remain outside the visible part of a sample. Have a responsible person verify the material before transfer.

Agree the exchange route

Confirm who may receive the information, where it will be stored and how long it is needed. Use approved transfer tools and access controls. A public enquiry form is not an appropriate default for sensitive operational files.

Confidentiality terms may be relevant, but they do not replace practical access and handling controls. Obtain suitable specialist advice for the information and obligations involved.

Keep access purpose-limited

If a system demonstration is needed, consider a supervised session or test environment. Define permitted actions and avoid granting broad export rights merely for convenience. Record temporary access and the removal point.

Ask the provider what information is genuinely required and why. A clear explanation helps the business choose a proportionate method. Uncertainty should prompt clarification rather than an unrestricted transfer.

Close the discovery stage

Review what was shared, which access remains and what must be returned or removed. If the engagement proceeds, carry relevant handling requirements into the service agreement. If it does not, ensure information is managed according to the agreed terms and applicable requirements.

Discovery is a stage of the information lifecycle, not an exception to it. Thoughtful preparation allows useful evaluation while reducing unnecessary exposure and establishing clearer expectations for any later service relationship.

Review a sample attachment before sharing

A spreadsheet prepared for discovery contains anonymised visible rows but also a hidden tab with real customer details. A document may contain tracked changes or comments naming an internal project. Inspect the whole file, not only the section intended for discussion.

Where possible, create a synthetic example from the required structure instead of editing a live file. Verify that it still demonstrates the workflow question accurately. An example that is safe but unrealistic may lead to an unsuitable proposal.

Record who approved the material and the intended recipients. Use the agreed transfer route and close temporary access after discovery. If new information is requested, assess the purpose and handling requirements again rather than treating the initial approval as unlimited. This makes discovery an accountable exchange of necessary context and establishes habits that can carry into a later service relationship.