How to use Check Lib

Overview

Check Lib is a web-based assessment and reporting tool. It guides the user from setup, through questions or risk-assessment hazards, to final sign-off, report export, and action close-out.

Start a checklist

1. Open the app. No checklist is active by default.
2. Choose the assessment from Select Checklist.
3. Enter the site name, Division, date, assessor, and site representative.
4. Select Start Checklist.

The stage timeline then moves from Setup to Sections. If the checklist includes an introduction, use View introduction from the loaded-checksheet banner.

Saved work

The dashboard includes a Saved locally area for in-progress assessments. It starts collapsed so the current run stays clear, but it can be opened when you need to continue or delete a draft.

• Use Continue to reopen a saved draft.
• Use Delete Draft only when the draft is no longer needed.
• Use the Division filter to narrow the draft list.
• Starting a different assessment keeps other saved drafts unless you delete them.

Drafts are saved in the browser being used. They are not shared between devices or browsers.

Complete questions

Each question has Yes, No, and N/A answer controls. The correct answer is defined by the checklist, so either Yes or No can be the passing answer depending on how the checklist was built.

• Answer each question in the current section.
• If the answer creates an issue, add a clear comment.
• Use Standard comment when the comment is informational rather than severity-based.
• Add evidence or attachments where useful.
• Use Sections to jump between sections.
• Use Show unanswered to focus on gaps.
• Use Save or the mobile Save control to keep a draft.

Review issues

The Issues stage shows failed questions that need review before sign-off. Each issue should have enough context for follow-up.

• Confirm the issue comment.
• Choose the comment type or severity.
• Mark whether action is required.
• If action is required, add a responsible person and due date.
• Use the issue jump controls to return to the question if the answer or comment needs changing.

Missing issue comments or missing action details block the move to final review.

Final review and signature

The Final stage checks whether the run is ready to sign. The app blocks signature until required metadata, answers, comments, and action details are complete.

• Review readiness and section status.
• Use Save Draft if the run is not ready to sign.
• Select Proceed To Signature when validation is clear.
• Sign in the signature pad and confirm.
• The signed run is added to the report queue.

Signed reports are treated as completed snapshots. If a signed report needs to be updated later, create a revision rather than changing the signed original.

Reports and charts

The Reports and History areas show queued and archived signed reports. Dashboard tiles and charts summarise report state, Division, open issues, action requirements, close-out status, and export state.

Use search, Division filters, report filters, and dashboard tiles to narrow the list.

Close-out actions

Open issues remain visible as open actions until they are closed out. Completed or not-required actions are kept as history, but no longer count as open issues.

1. Open Close Out from a queue or archive card.
2. Only unresolved close-out items are shown in close-out mode.
3. Choose Completed, Not required, or leave as Open.
4. Add completed by, completed date, and a close-out note where relevant.
5. Add optional close-out evidence images.
6. Select Save close-out.

Resolved actions disappear from the close-out list, but they remain visible in report history and PDF output.

PDF and CSV export

Export works from the queue, history, or individual report cards. Standard checklist reports export to PDF. SERA reports export to PDF and editable DOCX.

PDF content modes

• Full Inspection Report: summary, issues, close-out history, evidence, and full checklist details.
• Management Summary Report: overview, issue detail, close-out state, and charts without the full checklist table.
• Action and Close-Out Report: issue and action detail for follow-up use.

After export

• Keep in queue: leaves the report active in the queue.
• Move to archive: moves the report into history after export.

CSV summaries

Queue CSV and Archive CSV exports list tracking data, including Division, open issue count, issue history count, action state, close-out state, and export timestamps.

Evidence and attachments

Use evidence when it helps explain what was found, what control is in place, or what action is needed.

Revisions

Use Create Revision when a signed report needs to be updated. The signed original remains unchanged, and a new editable draft is created from it.

• Create Revision is available from queue and history report cards.
• The revision opens as a new in-progress draft.
• When the revision is signed, it becomes a new signed report.
• The original signed report remains available for audit history.

Builder guide

Builder is used to create custom checklists for the Runner. It is best used carefully: set up the checklist details first, then build sections and tasks in a clear order.

Create a checklist

1. Open Builder from the side navigation.
2. Select New Checklist.
3. Enter a clear title and checklist ID.
4. Add a short title, version, type, introduction, and completion guidance if needed.
5. Add sections that match how the assessor should work through the inspection.
6. Add tasks inside each section.
7. Set the correct answer for every task.
8. Save the checklist locally.

Import and export

• Import CSV can create a checklist from section, task, and pass-answer columns.
• Export CSV creates a reusable checklist file.
• Export Metadata JSON creates a structured file for checklist details and guidance text.
• After saving a custom checklist, reload the Runner if it does not appear in the checklist selector.

Good practice

• Preview the checklist in the Runner before using it live.
• Check that every task has the correct passing answer.
• Keep wording consistent across sections.
• Duplicate an existing checklist when making a similar version.
• Export a CSV backup before making major edits.

Admin notes

Most users only need to know that their work is saved in the browser they are using. The notes below are for users responsible for backups or moving records between browsers.

• Standard Backup exports records, drafts, preferences, custom checklists, and attachment metadata.
• Full Backup With Attachments also includes available attachment files.
• Validation Only checks an import and creates diagnostics without changing local data.
• Merge is the normal restore option. It preserves local records where possible.
• Replace overwrites local Check Lib data and should only be used deliberately.
• Clearing browser site data can remove drafts, reports, archive history, custom checklists, and attachments.

Troubleshooting