Set the boundaries before connecting data

Define the files and systems the workflow needs, who may access them and which actions it may take. Reading a document, preparing a draft and sending a customer message are different permissions.

We check provider storage and processing arrangements, available settings and retention requirements with you. Project-specific data handling is agreed separately from the privacy notice for this website.

Build checks into the work

  • Limit access to the records and actions required for the agreed task.
  • Put review points before actions that need someone’s decision.
  • Make missing information and failed connections visible.
  • Keep useful records of important changes and define who reviews them.
  • Plan how to pause the workflow, continue work manually and recover safely.

Support is an agreed scope

An ongoing plan can cover maintenance, resolving issues and reviewing worthwhile improvements for the systems in scope. It identifies the responsible people, how staff ask for help and which parts are handled by software providers.

Before you agree to the plan, we explain the recurring fee, any usage or provider charges, coverage hours, response expectations and included work. Exclusions, optional improvements and any additional charges are made clear. The plan should fit the tool and its importance to your business.

Support the people using it

We include practical guidance and training in the agreed launch scope, so staff understand what the tool does, where to check its work and how to continue if it is unavailable. Feedback from the people doing the work helps shape worthwhile improvements.

A new feature or bigger system is not automatically an upgrade. We assess the benefit, cost and effort with you before recommending a change. Keeping a simple, reliable setup may be the better choice.

Test changes before everyday use

Models, software connections and business processes change. An update that improves one task can introduce a problem elsewhere. Agreed changes should be checked against the workflow’s ordinary cases and its important exceptions before rollout.

Keep the working version and a recovery plan available where the tools allow it. Your team should know which changes are ready for use and which still need review.

Match the controls to the task

Access controls and testing reduce risk; they do not eliminate it. The level of review should reflect the consequences of an error. Regulated, confidential or safety-critical work needs a specific assessment before the solution is used.

For an initial conversation, describe the workflow, systems and concerns without sending passwords or sensitive project material.

Questions you may have

Will our information be used to train a model?

That depends on the provider, product, agreement and settings selected for the project. Those terms need to be checked and agreed before connecting information; the website does not make a blanket promise.

Can CTHY support a tool another provider built?

That requires an assessment of the tool, documentation, access and provider responsibilities. Support should only be agreed after the scope and dependencies are understood.