Local tool

Response workbook

Record how many fixes each business line needs, how many are done, and whether the result has actually been verified. The counts are yours. This page does not scan anything.

Saved in this browser only. Other devices will not see it. Do not enter passwords, keys, customer data or personal information. Use aliases for systems and people. The tool makes no network requests.

User-entered record — not a scan report. Example rows are labelled. Verify the figures before circulating this printout.

Scroll the table sideways to edit owner, target date and verification.

Business lines, required and completed fixes, open test bugs, owner, target date and verification state
Business / systemAlias, not a secret	RequiredFix items	CompletedNot > required	Open test bugsSeparate count	OwnerAlias	Target dateOptional	VerificationYour judgement	Actions

No business lines yet.

Add a row to start. If nothing responds, JavaScript is disabled — use the static checklist below and print this page.

What the export contains

UTF-8 CSV with a header row, quoted text, and escaped quotes and line breaks.
Text beginning with =, +, - or @ is prefixed with an apostrophe to stop spreadsheet formula execution.
Every record carries the note “User-entered data - not a scan report”. The filename is not a security attestation.
Printing hides navigation, buttons and the summary sidebar; table headers repeat if the table breaks across pages.
There is no import, no account, no sync, no email and no remote save in this release.

JavaScript is off

The editable workbook needs JavaScript. The static checklist below still prints and can be completed by hand. Nothing on this page is sent anywhere either way.

Assess
- The actual web PHP runtime is identified for every public service.
- Every service, node, container and worker copy is listed, including staging and scheduled jobs.
- The package source is recorded: distribution package, upstream build or container image.
- A named maintainer is accountable for each entry.
Patch
- The matching update is applied from the correct package source.
- Required interim measures are applied where patching is not yet complete.
- Old workers, replicas and containers have exited.
- A rollback path and business window are recorded.
Verify
- Running package version or image digest is evidenced per node.
- Key business regression checks are completed.
- Exceptions and failing checks are tracked with an owner.
- Traffic is served by the patched runtime, not an old worker.
Handover
- The accountable owner accepts the result.
- Known residual items, next actions and dates are recorded.
- Evidence is stored where the next maintainer can find it.

Open the handover template to record the result in a document.

Response workbook

Four-stage checks

01 Assess 0 / 4

02 Patch 0 / 4

03 Verify 0 / 4

04 Handover 0 / 3

What the export contains

Confirm