Code of conduct

Why this is published

Most codes of conduct exist to satisfy a procurement checklist and are written so broadly that nothing could ever breach them. This one is published because a client should be able to point at a specific sentence and say that VenSoc did not do that.

What a client can hold VenSoc to

We do not report work as complete when it is not

A completion report names the command that was run and shows its output, and lists explicitly what is unfinished. If something was not verified, the report says so rather than implying otherwise.

We tell you bad news early

A slipping estimate, a wrong architectural assumption or a defect we introduced is raised as soon as it is known, not at the next scheduled review. Late disclosure of a problem is worse than the problem.

We say when we are the wrong firm

Where a requirement is outside what VenSoc can deliver well, or where a certified supplier is genuinely needed, we say so at the first meeting rather than after the contract.

We do not oversell what AI can do

AI is used heavily in delivery and its limitations are stated as plainly as its capabilities. Where a problem does not need AI, we will say that, including when saying it costs us the work.

Your confidential information stays yours

Client names, systems, data and methodology are not disclosed without written permission, and confidentiality obligations survive the end of an engagement. Where permission has not been given, published case material describes the client rather than naming them.

We do not use your data for our benefit

Client data is not used to train models, build benchmarks, or enrich marketing lists. It is processed for the purpose it was given for and nothing else.

How we work with people

VenSoc does not tolerate harassment, discrimination or intimidation of anyone — colleagues, client staff, candidates or contributors — on any basis. This applies in meetings, in writing, in code review and in every channel where VenSoc work happens.

Technical disagreement is expected and welcome; it is how the work gets better. Disagreement is about the decision, never about the person who made it. Reviewing someone’s work is not licence to be unkind about it.

Candidates who apply receive an answer. Where a role does not exist, the careers page says so rather than collecting applications for a vacancy that is not open.

Reporting a breach

If anyone at VenSoc falls short of this, email info@vensoc.com. Reports are read by the founder. You will receive an acknowledgement, and you will be told what was done — including where the answer is that VenSoc disagreed with the complaint and why.

No client has ever been penalised commercially for raising a concern about conduct, and none will be.