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 3/3
3·Introduction0:000:00

After an outage

This guide describes how an outage is recorded and how its handwritten records reach the system once access is restored, and the yearly readiness drill. Preparing and working on paper are covered in Prepare for an outage and Work during an outage.

Found under: Daily Work → Outage records.


The outage, the records entered from paper and their check are kept on the Outage records page. The Working during an outage page links to it.

Step 1 — Record the outage

Open Outage records and press New Outage Record. Fill in:

  • Outage start — the current moment is suggested; change it to the real start time.
  • Outage end — it can be filled in later, but it is needed to close the record. An end before the start is not accepted.
  • Cause — "Power cut", "Internet connection loss", "Application unavailable", "Planned maintenance" or "Other". The cause "Readiness drill" is for the yearly drill (see "Yearly readiness drill" below).
  • What was affected and Actions taken (§7.11.3).

The record gets its number automatically (default OUT-{YYYY}-{NNNN}) and stays "Open" until it is closed. Record the outage before you start entering the samples from paper: samples with a reserved number are then linked to it by themselves (Step 3).

Failures of the platform itself are also recorded by the provider and shown, read-only, under System Incidents.

Step 2 — Enter the records from the paper

  • Samples: on the Samples page, for each New Sample choose the label's reserved number in the Sample Code field — the field suggests the unused reserved numbers. The suggestions appear only when creating; on an existing sample the code does not change. The app does not accept a second sample with the same code. Paper samples are entered one by one, with New Sample and the number from the label; Batch intake issues system numbers and does not link the samples to the outage record.
  • The real time: in every record that has an event date, enter the date and time written on the paper, not the moment of typing — for a sample, in the Received Date. The app keeps when something happened apart from when it was entered (see Why every sample carries two timestamps).
  • Reason: some records — among them samples, calibrations, reagent lots and customer complaints — ask for a Reason for the late entry when the event date is more than 7 days old (see Why a late entry asks for a reason). Write there that the record was entered from an emergency form, with the outage date and the page — for example "From emergency form, outage 03-11-2026, p. 2". The reason is not filled in automatically.

Step 3 — List the entries in the outage record

Open the outage's record (Edit). Below its fields is the Entries from paper section: one line for each record entered from a form, with the form and the page it came from. The section appears once the record has been saved. An entry refers to the record; it does not create or change it.

Added automatically: samples. When a new sample is saved with a reserved number and there is exactly one open outage record, an entry is added to it with type "Sample", the sample's code, form "Sample Receipt (SRF)" and, as its time, the sample's Received Date. The app does not know the form's page; fill it in with Update on the entry. When no outage record is open, or more than one is, no sample is linked; in the second case the section says so. Open records with the cause "Readiness drill" do not count, and no sample is ever linked to them automatically.

Added by hand: every other record, and any sample that was not linked automatically. Press New entry and fill in:

  • Record type — "Sample", "Analysis", "Worklist", "Environmental Reading", "Deviation", "Customer Complaint", "Shipment", "Reagent Lot" or "Other".
  • Number or description — the record's own number (e.g. sample code) or, if it has none, a description.
  • Paper form and Page — the pack's form and the page written on the "Emergency form" line.
  • When it happened — the time written on the paper.
  • Note, if needed.

An entry is changed with Update and removed with Delete; deleting it also removes its attached file, while the record itself is not affected.

Step 4 — Attach the filled form

On each entry, Form file in the entry's actions menu (⋮) opens the "Photo or Scan of the Form" window. Attach the photo or scan with the File button or by capturing it with the device's Camera. PDF, PNG or JPEG files up to 5 MB are accepted. Each entry holds one file; a new file replaces the previous one. View file and Remove file are in the same window.

The file is a copy. The paper remains the original and is kept (Step 7).

Step 5 — Check by a second person

Typing from paper is a data transfer and is checked (§7.11.6). A second person, other than the one who entered it, compares the record with the form and presses Checked on the entry, optionally with a Check note. From then on the entry says who checked it and when; entries not yet checked read "Not checked", and the Unchecked column of the list shows how many there are in each outage.

When the entry is for a sample or an analysis that the app found by its number, the sample and the analysis say so on their own screens until the check is made: "Entered from a paper form (OUT-2026-0001). Not yet checked by a second person." — with the outage record's number in the brackets. After the check the note reads "Entered from a paper form (OUT-2026-0001). Checked.". The note is for information: approving the analysis does not depend on it.

The second check is recommended; the app does not enforce it:

  • The person who made the entry can also mark the check. The entry then carries the mark "checked by the same person", on screen and in print, so that it is clear no second person made it.
  • A check is undone with Undo check.
  • A check is also undone by itself when what was checked changes: the entry's type, number, form, page or time, or when its file is replaced or removed. The app warns before the change. Changing only the note, or attaching a file to an entry that had none, does not undo the check.

Step 6 — Close, print, reopen

Once the entries have been listed and checked, the record is closed from its row menu, with Close.

  • Closing needs the "Close / Delete Outage Records" permission, held by default by the Lab Director and the Quality Manager (see Roles). Recording an outage and its entries does not need it.
  • Outage end is needed; without it the action shows as inactive.
  • A record can be closed with entries that have not been checked; the closing window states how many there are ("Entries not yet checked"). A Closure note is optional. Closing is completed with Close record, and who closed the record and when is recorded.

The same permission is needed to Delete a record. Only an open record with no entries from paper can be deleted; if it has entries, delete them first.

A closed record accepts no change, to itself or to its entries; it opens read-only. To change it, Reopen it, with the same permission; reopening clears the closure (who, when, note).

Preview, in the same menu, creates the record's document for printing: the outage's fields, the table of entries with each one's form, page and second check, and signature lines. It is available before closing too.

Step 7 — Keep the paper

The paper is not thrown away after it has been entered, nor once its photo has been attached. It is kept with the laboratory's other records, for as long as its records retention policy sets, so that every entered value can be compared with the original (§8.4.2).

Finally, check whether enough unused reserved numbers and forms remain for next time, and print whatever is missing (see Prepare for an outage).


Yearly readiness drill

At least once a year, try out working on paper before you need it:

  1. In Outage records, press New Outage Record and choose the Cause "Readiness drill".
  2. Do one real routine task of the day on a form of the pack — for example an environmental reading or the use of an instrument. Do not invent a sample or a record for the drill.
  3. Enter the record from the paper, list it in the record's Entries from paper and attach the photo of the form, as in a real outage.
  4. A second person checks the entry (Checked), and the record is closed with Close.

The drill counts as done once its record is closed with at least one checked entry; Readiness then shows its date as "Last drill". An open drill does not count. While it is open, it does not stop samples being linked automatically to a real open outage.


See also