How we declare what we built

Declared in writing, every time

We build systems for a living, and some of those systems sit alongside work that will be assessed. This page is how we keep that honest: every academic engagement declares what we built, in writing, to your department. Stated plainly so there is no ambiguity before you engage us.

Talk to an engineer

CH 01 ACQUIRE
Back

The principle

Work submitted for assessment must be the work of the person submitting it. Our engineering does not stop at that line — it is declared at it. Every academic engagement names which components we built and which you built, and that statement goes to your department before anything is delivered.

This is not a limitation we work around; it is what makes the arrangement usable. An undeclared contribution is the single thing that can void a degree, and no system we could build is worth that. A declared one is just engineering, of the kind industry-sponsored projects have run on for decades.

If your requirement is that someone else completes the work, we are not the right provider. We would rather establish that on a short conversation than halfway through a semester.

Departments and supervisors are welcome to contact us directly about how we work with their students.

Coverage

What we will not do

01
Build the parts you are assessed on

We build infrastructure, tooling and the components named in the declared scope. The work your marks depend on stays yours, and our commits stay in our own repository.

02
Write your manuscript

We build the apparatus and prepare technical material. We do not draft the chapters you are assessed on, and where we contribute to a paper we are named on it.

03
Sit assessments

No examinations, no assessed work completed on anyone’s behalf.

04
Guarantee outcomes

No grade, no acceptance, no publication is ever promised — and we avoid venues that promise them.

05
Hide a contribution

There is no version of this where we build something and it goes unstated. If a department would object to the declaration, that is the answer about the engagement.

06
Tune results to a target

We will not rerun tests until one returns significance. A null result honestly reported is the better paper.

Outcome

What this means for you

  • You will be asked to produce work between sessions
  • You will be reviewed on what you produced
  • We tell you the architecture is wrong, and rebuild it where the declared scope says it is ours
  • You finish able to answer questions about every decision
  • The work survives a viva, because it is genuinely yours

Ask first. The answer might be no.

The first conversation is free and its only purpose is to work out whether we are the right people for what you are doing. If we are not, we say so and tell you what would suit it better.

FAQs

Questions we usually get.

Answered already, to save you the email.

All 15 questions in the Help Centre