Every brief goes
somewhere you can read it.
The most important claim we make is that a person approves the work before it happens. That is worth more when you can see where the approving happens. It happens in Bladbase — a collaborative documentation workspace — or right inside your MarketPilot portal. Either way it is a document you can read, argue with, and sign off.
What actually happens
Five steps, and a person owns two of them.
A finding becomes a brief
An audit surfaces one specific issue — a thin service page, a blocked AI crawler, eight pages competing with each other. Each becomes a single scoped brief: what to change, why it matters, and how we will know it worked.
The brief lands in your workspace
It is published as a document in your own Bladbase workspace — not a PDF in an email, and not somewhere only we can see. It arrives marked awaiting review, which is exactly what it is.
You read it, and you can change it
Comment on it, edit it, ask a question. The moment a person touches a brief, MarketPilot stops rewriting it — the document becomes yours, and a later re-run will not quietly replace your words.
Nothing starts until you approve
Approval is the gate, and it is bound to the words you actually read. If the plan changes afterwards, the approval is withdrawn and we ask again rather than proceeding on a version you never saw.
The work is done, then verified
Once the change is live, MarketPilot re-checks the page against the same measurement that raised the finding. It closes because the signal moved — not because someone ticked a box.
Why a separate workspace
The document outlives the tool
A brief that lives only inside our dashboard is only as durable as your subscription. In Bladbase it is a document in a workspace you own, with its own history — who wrote what, when, and what changed between versions. If you stop working with us, the record of what was proposed and what you agreed to stays with you.
Editing is the point, not an exception
Most review tools give you approve and reject. Real review is neither — it is “yes, but change this paragraph.” Because a brief is an ordinary document, you can rewrite it before you approve it, and what you approve is what you wrote.
An approval covers words, not a checkbox
When you approve, we record exactly which version you approved. If the brief is edited afterwards — by us or by you — that approval stops counting and we ask again. It is not possible for work to proceed on a plan you did not read, because the system compares the two rather than trusting that they match.
You do not have to use it
Bladbase is where the document lives when you want one. If you would rather just decide, every brief also appears in your MarketPilot portal in plain language — why, what changes, what we need from you — with one button. The gate is the same; only the surface differs.
What this rules out
The point of a gate is the things that cannot happen while it is closed.
- An AI cannot decide to change your site. There is no path from a finding to your live pages that does not pass through a person approving a specific, written change.
- A brief you edited cannot be overwritten by a re-run. The moment a person writes to a brief, our publishing stops touching its body. That is one-way and deliberate.
- Work cannot start on a stale approval. Change the plan and the approval is withdrawn — starting and shipping are both blocked until it is approved again.
- Nothing closes on an assertion. A change is verified by re-measuring the signal that raised it. If it did not move, the finding stays open and says so.