Policy · applies to every FYP engagement

Academic integrity policy.

This policy is part of every FYP mentorship agreement. It exists to protect three things: your degree, your university’s assessment standards, and the honest value of the work you will defend.

Our mentorship promise — read this first

We do not sell ready-made final-year projects and we do not hide external authorship. We mentor your team through problem selection, architecture, implementation reviews, testing, deployment and presentation — so the final work remains yours. This boundary aligns with university assessment requirements and the Higher Education Commission’s plagiarism expectations. If you want someone to secretly build your project, we are the wrong service — deliberately. Full details: academic integrity policy.

The boundary

Permitted and prohibited assistance.

✓ What mentors will do✗ What we will never do
Explain concepts and architecturesSecretly build the full assessed project
Review student-written codeGive you a purchased or recycled project to submit
Demonstrate a technique on a separate exampleFabricate research, testing or users
Identify bugs and coach debuggingWrite a false contribution history
Review drafts and provide commentsWrite the final report for submission under your name
Help configure deploymentHide mentor or third-party contribution where disclosure is required
Run mock defence questionsGuarantee grades or examiner outcomes

This boundary aligns the service with university assessment requirements and the Higher Education Commission’s published plagiarism policy (hec.gov.pk) and undergraduate education policy (UGEP).

Your commitments

What every mentored team agrees to.

  • A student ownership declaration, signed at Stage 1 and reaffirmed at closure
  • An accurate mentor contribution record, kept in the project workspace
  • No fabricated research, data, testing or users — ever
  • No recycled or purchased project material submitted as new work
  • No impersonation of team members in meetings, repositories or submissions
  • A truthful Git and contribution history — no backdated or transferred commits
  • Correct citation and licence handling for every external source, library and asset
  • Disclosure of mentorship to the academic supervisor whenever the university requires it — and our encouragement to disclose even when it does not
Enforcement

What happens if the boundary is pushed.

We will decline or end engagements that ask us to

  • Complete assessed work for submission
  • Conceal contribution where disclosure is required
  • Fabricate evidence of any kind
  • Meet a deadline only fraud could meet

And we put it in writing

The integrity declaration, the approved scope, the mentor contribution record and the closure record all live in the project workspace. If your university or supervisor asks what help you received, the honest answer is documented and shareable — which is exactly how mentorship should work.

Thrive FYP Accelerator

Comfortable with these rules? Then we will get along.

Teams who want structure, feedback and a defensible project thrive here. Book the free fit assessment and bring your questions.

Chat with us