Current features
Describe the workflow, inputs, outputs, platform, and available features in concrete terms.
Corporate responsibility / Ethics & integrity
Integrity starts with clear expectations.
People need a fair account of what software can do, what remains uncertain, and what a custom project will deliver. These principles guide how we describe AI and how we run projects.
Our approach
Describe what is available
A service description should let someone understand its present scope without mistaking planned work for a delivered feature.
Assumptions and limits
Explain important requirements and where technical review is needed before using an output.
Planned work
Identify future or proposed capabilities as plans. A roadmap is not a reason to assume a feature exists today.
Our approach
Keep technical judgment in the loop
Software can organize and calculate, but a qualified person must review the inputs and result for the actual project.
Estimates, reports, and calculations depend on the data entered and the conditions in which they will be used. Users should check assumptions, applicable standards, and project requirements before relying on an output. The website terms explain this responsibility in more detail.
Make a concern specific
If a claim seems too broad, send us the page, the statement, and the context in which it could be misunderstood. Specific feedback gives us a clear point to review.
Our approach
Set a workable custom scope
A custom software proposal should describe the problem, the expected result, and the decisions needed before delivery.
Understand the workflow
Discuss the people, inputs, existing tools, constraints, and result the software should support.
Define the work
Agree on the proposed functions, integrations, review points, responsibilities, and price before work begins.
Review changes
When a requirement changes, discuss the effect on scope, delivery, and support instead of assuming it was included.
Confirm handover
Discuss documentation, support, and who will review the software in its real operating context.
Our approach
Raise a question or concern
Use the contact channel that fits the issue. We do not present this general contact route as an anonymous reporting line.
What to include
Share the page or project, the statement or decision you are concerned about, and the correction or clarification you are seeking. Do not email passwords, payment-card numbers, or confidential project files.
Corporate responsibility
Continue the conversation
Ask us about a specific project requirement or information on this page.