Use case
Level 2 / ContextProof before the client asks
Clients notice problems late, and remember who did not tell them. A report that shows the state of every file, with the evidence behind it, turns governance into work you can bill for.
Without a check
What goes wrong
- The first sign of a problem is an email from the client.
- Screenshots and one-off checks are hard to repeat and easy to dispute.
- Nobody can say with confidence what the site served last month.
With Flowpane
What changes
- PDF governance reports with an executive summary, per-file state, cross-file conflicts and recommendations.
- Every report states its evidence boundaries, so it never claims more than it can show.
- On Agency, reports carry your logo instead of Flowpane's.
What it looks like in Flowpane
Illustrative- InfoReportExecutive summary, 8 artefacts, 3 cross-file conflicts.
- AdviceReportEvidence boundaries: what this report can and cannot prove.
Level 3 / Method
How each check works.
Each file, how it fails in public, what true looks like, and exactly how it is checked.
ScoringHow the score worksFlowpane scores each of eight artefacts from 0 to 100, then weights them into one site score. Only the next public check moves it. Drafts and errors never do.ReadCookies and consentCookies and consentAnyone can see which trackers and consent tools a homepage loads before a visitor clicks. Flowpane records that evidence. It is not a legal assessment.ReadCoherenceCross-file coherenceEach governance file can pass validation alone and still contradict another. Flowpane's coherence engine compares them and reports where your files disagree.Read
See what your sites are claiming.
Add an origin and get a score, the gaps, and the evidence behind each one. Then Flowpane keeps checking, so the answer stays current.
Free during the beta. Flowpane only reads your origin.