Documentation
Tutorials
Workflows
Kebab actions
Daily Work
Dashboard & Reports
Quality Control
ISO 17025
Reagents & Storage
Logs
Contacts
Billing
Analysis Setup
Settings
Initial Setup
Help & Reference
Standards
Architecture decisions
Positioning
Outage continuity · Part 1/3
1·Introduction0:000:00

Prepare for an outage

This guide describes how the laboratory prepares to keep working on paper when it cannot reach the app — in a power cut, an internet cut, or when the app itself is unavailable. Working during the outage is covered in Work during an outage, and entering the paper afterwards in After an outage.

Found under: Daily Work → Working during an outage.


The paper filled in during the outage is the original record (§7.5.1, §8.4.2), and it has to exist before the outage: in a power cut nothing can be printed.


Step 1 — Print the forms pack

Open the Working during an outage page. The Forms section lists each form with its number of pages. The forms are built from the laboratory's own setup (methods, elements, sampling plans, storage locations, instruments, acceptance criteria, staff). A form whose setup is missing is not offered, and the page says why — for example "No lab method has elements".

Every available form is ticked; untick any you do not need and press Print pack. All the forms print in one document. The pack starts with a one-page instructions sheet, "Instructions: working during an outage", which sums up what to do during the outage and after it; it is ticked first in the list. If the pack is over the size limit, the worksheets print as a second document, opened with the Open the worksheets button.

After printing, the Status section shows when and by whom the pack was last printed. If methods, elements, acceptance criteria, sampling plans, storage locations, instruments, User Competencies or Competency Requirements are added or edited later, the page points this out and asks for a new print. A deletion, or an authorisation that lapses on its end date, is not pointed out; the reference sheets read "Valid at the time of printing" with their date, so print them again after such a change.

Step 2 — Reserve sample numbers and print labels

In the Reserved sample numbers section, fill in How many (from 1 to 200) and press Reserve and print labels. One barcode label prints for each number.

Reserved numbers carry their own visible prefix (default X{YY}-{NNNN}, for example X26-0001) and the system never issues them itself. A sample received on paper therefore gets its final number at the door and keeps it up to the report, without colliding with a number the system issues (§7.4.2), as long as their format keeps a prefix that no other numbering uses. The laboratory can change the format in the numbering settings (Settings → Numbering & Calendar → Document Numbering, field "Contingency Sample Code Format"; see Document Numbering).

The Status section shows how many remain ("Unused reserved numbers"), and the numbers themselves are listed below the button. If labels are lost, the Reprint labels button prints the labels of the unused numbers again.

Step 3 — Storage

Keep the pack, the labels and pens in a place every member of staff knows and can reach without power — not only as a file on a computer.

Step 4 — Daily snapshot of open work

The Daily snapshot of open work card emails a PDF of the laboratory's open work every day, so it is known even when the app is unavailable. The PDF contains:

  • Samples in progress — those not yet completed — those at the laboratory first, by due date (those without one after them, oldest received first), then those still with the collector: code, customer, phone, status, received date and due date, with the word "overdue" once it has passed. Up to 400 samples are listed, and the end says how many more there are.
  • Open worklists — those that hold aliquots, with date, method and number of aliquots. An open worklist with no aliquots is left out.
  • Sampling planned for today — the day's scheduled visits. Repeats of recurring visits are not included, and the document says so.

The snapshot is configured by those with the "Set up and send the daily snapshot" permission — by default the Lab Director; a laboratory can grant it to other roles, such as the Receptionist, in Settings → Role Permissions (see Roles): Send daily by email, Send time and Recipients (email addresses separated by commas), then Save. It is sent every day, weekends included, after the set time, even when there is no open work (the document then says so). It goes out through the laboratory's own SMTP settings (Settings → Communication & Notifications → Email Settings (SMTP)); without them it is not sent, and the card says so with a link to the settings.

The card shows when it was last sent. If a send did not happen, the card gives the reason and the send is tried again later. If it reached only some recipients, the card says how many; the day counts as sent. The Send now button sends the snapshot at once, only to the stored addresses, after showing them for confirmation; it counts as today's send, so that day's scheduled send does not happen. Print now prints the same document and is available to anyone who can open the page.

Readiness

The page's Readiness card, and the dashboard's Outage readiness card (Compliance tab, shown by default to the Lab Director and the Quality Manager), show four points, each with its state: "In order", "Needs attention" or "Not set up".

  • Form pack — needs attention when it was never printed, or when the laboratory's setup changed after the last print.
  • Reserved number labels — need attention when fewer than 10 unused reserved numbers remain.
  • Daily snapshot — needs attention when sending is enabled and the SMTP settings are missing, or the last send did not happen or reached only some recipients, or the send time has passed and it has not been sent today. Before the send time a send that has simply not happened yet is not an issue; a reason from an earlier failed or partial send stays shown until the next successful send. When sending is not enabled it shows "Not set up", which does not count as an issue.
  • Readiness drill — needs attention when no drill has been completed in the last 12 months (see "Yearly readiness drill" in After an outage).

Above the points, the card says how many need attention.

Continuity procedure

The Continuity procedure button prints, with the laboratory's name, a two-page procedure for the quality system: purpose, scope, responsibilities, preparation, what to do during and after an outage, the yearly drill and the records kept. Its header has spaces for the code, issue, date and approval, filled in by hand. Register it in the laboratory's quality system (ISO 17025 → Quality System → Document Control); the app does not register it itself.


See also