Assessment library

# Saved compliance assessments

Review existing assessment records and generate a refreshed document pack.

Local workspace reminder

Your assessments, drafts, workflow notes, generated packs, and backups are stored on this computer. They are not cloud-synced by this app.

Use Backup data before moving computers or making major restore changes.
Completed packs -
Valid assessments -
Needs attention -

Compliance route

## Compliance route and safe use

Use this screen to understand how the local workspace supports Cyber Essentials and ISO 27001-style preparation without pretending to certify, audit, or legally approve the business.

Purpose Compliance preparation workspace

Creates a practical security and compliance document pack from a local questionnaire, then helps review findings, workflow, evidence, history, backups, and follow-up.

Limitations Not certification

Does not provide legal advice, ISO certification, Cyber Essentials certification, audit assurance, control testing, evidence quality checks, and it is not a compliance decision.

User input Questionnaire driven

The pack reflects the answers entered by the user. If answers are incomplete, optimistic, or wrong, the generated documents and findings must be reviewed before use.

Safe outcome Preparation, not proof

Use the outputs to organise policies, evidence, gaps, owners, and actions before a formal Cyber Essentials submission, ISO 27001 preparation activity, consultant review, or internal approval.

### What this tool is good for

- Creating a first draft policy, evidence, and action pack for a small organisation.
- Turning questionnaire answers into review prompts, implementation actions, evidence links, owners, target dates, and history.
- Keeping a local record of assessments, drafts, generated packs, workflow follow-up, version comparison, activity, and backups.

### What this tool is not

- It is not an independent audit, penetration test, certification body, lawyer, DPO, or managed security service.
- It does not prove that controls are operating, evidence is complete, or the business is compliant.
- It does not cloud-sync or recover customer systems; backup and restore only protect this app's saved assessment library.

### How to use the outputs safely

1. Complete the questionnaire honestly against the organisation's current operating reality.
2. Generate the starter pack and read START_HERE.txt before relying on any generated policy or evidence wording.
3. Review the Document Pack Summary, Implementation Action Plan, and Evidence Register with the business owner.
4. Use Findings, Workflow, Due dates, and Activity to assign owners, dates, notes, and follow-up for gaps.
5. Reassess after improvements, compare versions, and use the pack as preparation material for formal review rather than certification evidence by itself.

Local data & backups

## Local data & backups

Use this screen before moving the app, cleaning folders, downloading copies, testing restore, or explaining the local workspace to someone else. It maps the main records created by this app and the backup discipline needed to protect them.

Main workspace generated_documents

Active assessment packs, generated Word documents, Excel evidence trackers, START_HERE.txt files, questionnaire records, and workflow sidecars live under this folder.

Drafts _drafts

Incomplete browser questionnaires are saved as draft JSON records until resumed, deleted, or completed into a normal assessment pack.

Archived packs _archived

Archived assessment packs move out of the active library but keep their generated files, questionnaire record, and workflow history for later review or restore.

Backups Backup ZIP downloads

Backup data creates a portable ZIP that lands wherever the browser saves downloads. Keep that ZIP somewhere safe before moving computers or changing local data.

### Important app records

questionnaire_answers.json
  The saved assessment answers, company details, generated date, review date, and schema version used to build or review a pack.
assessment_workflow.json
  The local workflow sidecar created after finding follow-up is saved. It stores status, owner, target date, notes, and activity history without rewriting questionnaire answers.
START_HERE.txt and generated Word or Excel files
  The generated review pack. These files are practical working outputs; regenerating creates a new numbered folder rather than overwriting an earlier pack.
Downloads
  Downloaded files are copies for review or sharing. They are not the master assessment record and changing a downloaded copy does not update the saved local pack.

### Safe handling rules

- Use the browser controls for archive, restore, draft deletion, permanent delete, and backup instead of manually moving app records.
- Do not edit JSON records by hand unless you are deliberately repairing test data and have a backup first.
- This app does not cloud-sync or automatically recover another machine's records. Each computer has its own local workspace.

### When to use Backup data

Use Backup data before moving computers, clearing generated_documents, testing restore, deleting archived packs, or making major local-data changes. A backup protects this app's saved assessment library; it is not a customer system recovery backup.

Start here

## Start here: first-time user route

Use this screen as the plain-English route map for a first assessment. It explains the order of work from questionnaire to generated pack, review, workflow follow-up, backup, and reassessment.

Step 1 Answer the questionnaire

Create a new assessment, enter company details, and answer the yes/no readiness questions against the organisation's current reality.

Step 2 Generate the starter pack

The app creates a numbered local pack with START_HERE.txt, Word policies, an action plan, a coverage matrix, and an Excel evidence register.

Step 3 Review and work the gaps

Read the pack in order, then use Findings, Workflow, Due dates, and Activity to assign owners, dates, notes, and follow-up.

Step 4 Back up and reassess

Create a portable backup before major local-data changes, then reassess later and compare versions after improvements have been made.

### Use the app in this order

1. Open the app in your browser on the computer where the assessment library is stored.
2. Click New assessment and enter the company name, document owner, employee count, and questionnaire answers.
3. Save a draft if interrupted, or complete every question to generate the first document pack.
4. Open the new pack's Files tab and start with START_HERE.txt.
5. Review document_pack_summary.docx, implementation_action_plan.docx, and compliance_evidence_register.xlsx before treating the pack as useful.
6. Open Findings to understand which answers create review prompts, actions, and evidence expectations.
7. Use Workflow to assign owners, statuses, target dates, and notes for gap follow-up.
8. Use Due dates and Activity to track planned work and audit what changed.
9. Use Backup data before moving computers, testing restore, deleting archived records, or making major local-data changes.
10. After improvements, review the assessment, generate a new numbered pack, and compare versions.

### Do not promise

- Do not describe the output as ISO 27001 certification, Cyber Essentials certification, legal advice, audit assurance, or independent control testing.
- Do not treat generated policies, evidence rows, management notes, or workflow status as approved business content until a business owner has reviewed them.
- Do not present backup and restore as customer system recovery. It protects this app's saved assessment library only.

### Ready to continue?

Continue when you understand the route: questionnaire, generated pack, START_HERE.txt, summary, action plan, evidence register, findings, workflow, backup, reassessment, and external review if needed. All outputs are draft review aids rather than compliance decisions or proof that controls are operating.

Workflow overview Priority signals
Filter findings Narrow the worklist
Search Pack versions
Status
Review indication
Owner
Priority
Overdue only
Bulk update Update selected findings
Select all shown 0 selected
Owner for selected findings
Status for selected findings
Target date for selected findings
Note to append to selected findings

## Active finding workflow

Loading...
Activity overview History signals
Filter activity Narrow the history
Search Pack scope
Company
Operation
From date To date

## Workflow activity register

Loading...
Comparison overview Response transitions
Choose versions Narrow the comparison
Company
From version
To version
Responses
Assessment area
Transition

## Assessment version comparison

Select two versions from the same company.

Loading...
Planning overview Due windows
Filter dates Narrow the schedule
Search Pack versions
Company
Owner
Item type
Status
Due window
Include complete items

## Due-date planning

Assessment reviews and finding target dates from active packs.

Loading...

## Backup restore preview

Validate a portable backup ZIP, review what it contains, check the restore safety guardrails, choose a controlled restore approach, and only restore after the required pre-flight confirmation is complete.

Select backup ZIP
Local-only backup reminder

This tool protects this app's local saved assessment library. Keep backup ZIPs somewhere safe before moving computers, clearing generated_documents, or testing restore.

### When would I use this?

Use backup and restore when you need to move this app's saved assessments to another computer, recover from a lost or damaged generated_documents folder, or check that a backup ZIP contains usable assessment data.

1. Create a backup Use Backup data on your current computer to download a portable ZIP of active packs, archived packs, drafts, and workflow records.
2. Preview the backup Choose the ZIP here. The app checks the contents, shows conflicts, and lets you choose a controlled restore approach before any files can be written.
3. Restore carefully After preview, the restore action stays disabled until the selected approach is usable, the same ZIP is still available, and the exact RESTORE BACKUP phrase is typed.
Plain English: Readiness means whether the backup is usable. Dry-run plan means what would be restored. Conflict strategy means what happens if the same pack already exists locally. Restore safety checklist means the checks that must pass before restore can write files. Selected restore approach means the conflict strategy that will be submitted with the restore request. Restore confirmation means typing RESTORE BACKUP exactly before the Restore backup button can be enabled.
Preview step. Selecting a ZIP here validates the archive, manifest, checksums, conflicts, record visibility, restore readiness, restore safety checklist, dry-run restore plan, and conflict strategy simulations without writing files. Restore remains a separate gated action below.

### Controlled restore execution

Preview a backup ZIP before restore controls become available. Restore writes are blocked until a usable strategy is selected and the exact confirmation phrase is typed.

Backup ZIP No preview loaded
Selected approach Not selected
Required phrase RESTORE BACKUP
Type RESTORE BACKUP exactly to enable restore

Restore is disabled until preview and confirmation checks pass.

## Assessments

Loading...
Search assessments

Assessment workspace

## Choose an assessment to inspect

Select a saved assessment from the left list to review metadata, findings, version changes, pack files, and generation actions.

Pick a record Use the left assessment list to open Overview, Findings, Changes, Files, and Actions.
Start new work Use New assessment or Drafts when there is no completed pack yet.
Manage follow-up Use Workflow or Due dates when you need owners, statuses, and targets.
Review safely Use Activity, Compare versions, or Backup data before major local-data changes.
1 Create a sample assessment first

Use a test company before entering real business details, then review the generated START_HERE.txt and document pack.

2 Save as draft if interrupted

The browser can save an incomplete questionnaire locally, so the first pack does not need to be finished in one sitting.

3 Use Start here before real use

Start here explains local-only records, backup expectations, and safe wording before any real business output is used.

Selected assessment

##

Pack review route

### Start with the pack, then work the follow-up

Use this selected assessment as the bridge from generated files into findings, actions, evidence, and later reassessment.

Document owner
Employees
Generated
Review due
Schema version
Questionnaire record
  Valid

Overview is a read-only record summary. Answer totals are descriptive and are not a compliance score, certification decision, independent assurance, or proof that controls are operating.

### Recorded questionnaire answers

Yes
No
To confirm

Recorded-answer totals are descriptive and are not a compliance score or certification decision.

### Assessment findings

Loading findings...

Review prompts, not scores Findings are operational review prompts from recorded answers; they are not a compliance score, audit opinion, or certification decision.
Use filters carefully Follow-up means work the item; Confirm response means the saved answer still needs certainty.
Track local workflow Status, owner, target date, notes, and activity are saved to assessment_workflow.json, not questionnaire_answers.json.
Archived is read-only Archived pack workflow remains visible for history, but it cannot be edited until the pack is restored.

### Changes from previous version

Loading comparison...

Immediate predecessor only This tab compares the selected active pack with its previous active version for the same company.
Traceability, not proof Changed answers show what was recorded differently; they do not prove a control improved or was independently verified.
Use the top-level Compare view Use Compare versions when you need to choose any two active or archived packs or export filtered comparison rows.
Source packs stay unchanged Reviewing changes here is read-only and does not rewrite questionnaire records, workflow sidecars, or generated files.

### Pack files

Loading...
First review sequence Use the four highlighted rows below in order: START_HERE.txt, Document Pack Summary, Implementation Action Plan, then Evidence Register.
Work locally Open locally launches the file in its desktop app; Open pack folder shows the full generated pack on this computer.
Download is a copy Download saves a browser copy and does not change the generated pack or its local catalogue record.
Back up before editing Use Backup data before moving, restoring, deleting, or making major local changes to generated pack files.
Questionnaire record ``
Review safely Review/edit and Generate updated pack create a new numbered pack while keeping this source record unchanged.
Resolve only pending Resolve pending answers opens only To confirm responses and then creates a reviewed numbered pack.
Archive, don't delete Archive hides an active pack from the main library without permanent deletion; restore can bring archived packs back later.
Local data caution Copy paths, file open/download actions, restore, and permanent delete use this computer's local assessment library. Use Backup data before major local-data changes.
Create next pack Use these when you want a new numbered assessment pack.

Active record: review/edit or generate creates a new numbered pack. Pending-only resolution appears when answers need confirmation.

Manage local record Copy paths, archive, restore, or delete records in this local library.

Active record: copy the record path or archive this pack; use Backup data before major local changes.

Assessment draft

##

Document owner
Employees
Questions answered

Resume this draft to continue the questionnaire. No document pack has been generated yet.

## Records needing attention

Folders with missing or invalid questionnaire records

New assessment

## Company questionnaire

Complete all questions to generate the first document pack.

48 yes/no questions Save a draft anytime Generates a numbered local pack
Carry forward workflow Keep status, owner, target date, notes, and update time for findings whose questionnaire answer has not changed.

### Company details

Company name Document owner Number of employees