Scope, Revisions & File Retention

Last updated: 19 September 2026

This page states how we define what we agreed to do, what happens when that changes, and what we do with your files afterwards. It is written to be read before a project starts, not argued over after one.

How scope is set

Scope is agreed in writing before any build starts — that is stage three of our process. The written scope names the deliverables, the exclusions, the assumptions we are working under, the revision allowance and the timeline. Nothing starts until you have accepted it.

We quote after seeing a representative sample. An estimate given without one is a guess, and guesses on data work are wrong in a predictable direction.

Revisions versus change requests

A revision is a correction against the scope we agreed — something that does not match what was specified, a figure that fails reconciliation, a formatting error. Every package states how many rounds are included, and that allowance is on the package card rather than buried here.

A change request is a new or altered requirement: an extra KPI, another data source, a different output format, a report page that was not in the scope. Change requests are quoted separately.

When something arrives that we think is a change request, we will say so before doing the work rather than after — you then decide whether to add it, defer it or drop it. We do not absorb changes silently, because a project that quietly grows is a project that quietly slips.

What pauses a project

• Source data that arrives in a different shape from the sample we scoped against.
• Source data that is broken or internally inconsistent. We flag it; we do not guess.
• An unanswered exception that changes the output materially.
• Access we were told would be available and is not.

In each case we stop and tell you, with the options. A paused project has its timeline re-agreed rather than silently extended.

Files you send us

There is no upload on this website. We ask you to share a link you control — Google Drive, OneDrive, WeTransfer or similar — or to ask us for an address to send to. A link you own is a link you can revoke, and you can see who opened it.

Send the minimum needed to scope or deliver the work. Where the work does not need identifying fields — customer names, contact numbers, patient or employee identifiers — remove them before sending. We will tell you what is actually needed before any full-file transfer.

Your enquiry itself

Separately from any files: what you type into the quote form is emailed to the founders and written to a private Google Sheet that only the founders can open. We use it to track which enquiries have been answered. It is not shared, published or linked from anywhere.

Enquiries that do not turn into work are removed from both within twelve months, or sooner on request. If you would rather not be in that sheet at all, email us directly instead of using the form.

Who can see your files

Only the two founders named on the About page. We do not use subcontractors. If that ever changes, we will tell you before it applies to your project, not afterwards.

Retention and deletion

• Working copies of your data are deleted within 30 days of a project closing.
• We will delete them sooner if you ask, at any point.
• Deliverables we built for you are kept only as long as you may reasonably need us to re-send them; ask and we will delete those too.
• Enquiry emails are kept while the enquiry is live or a working relationship is ongoing.

We cannot delete copies held in your own systems, in a shared link you control, or in email you have received from us.

Confidentiality and NDAs

We will sign your NDA. We do not push a template of our own, so yours governs. Raise it before sending anything sensitive and it gets handled before any data moves.

We do not publish client data, screenshots or names without written permission. Where permission is given, we say so on the page.

We do not claim encryption at rest, ISO certification, SOC 2, HIPAA compliance or secure managed file transfer, because we have not implemented them. If your organisation requires any of those, tell us early — we would rather say we are not a fit than imply a control we do not have.

Ownership

You own the deliverable. You receive the working file — the workbook, the queries, the measures, the editable deck — not a locked export. If you stop working with us, nothing stops functioning and nothing needs our permission to change.

Your data remains yours throughout. We claim no right to reuse it, and nothing of yours becomes a sample or a case study without your written permission.

Questions

Anything here that does not fit how your organisation works is worth raising before we start rather than after. Email makemymisreport@gmail.com.