Write procedures in the app; see what changed.
In PureField LIMS, document control is the module where controlled documents are written in the app's editor, a draft is compared with the revision in force and signed through its category's approval flow. The controlled PDF is generated from the text and bound to its SHA-256 digest. A revision in force gives each reader a read-and-understood task to e-sign.
Request an accountApprovers see what changed before they sign.
Documents are written in the app with the lab's header and footer, and a draft is compared with the revision in force right away. Each category has its own approval flow.
The video opens draft Rev.03 of the mycotoxin analysis instruction on the writing page with Edit text; the text sits on paper with the laboratory's header and footer, as it will print. From the Headings list it jumps to section 4, changes the dried-fig laboratory sample from 10 kg to 12 kg and adds a raisins row below it; the status line moves from Unsaved changes to Saving… to Saved 10:41. After Finish writing, the Changes section of the document page compares the draft with Rev.02 in force: +10 words, −1 word and the changed section, the deleted 10 struck through in red and the additions underlined in green. The Side by side view then shows both revisions next to each other with block numbers.
- An editor on the page
- Write with headings, tables and images in the page layout you choose; the text saves itself within seconds. On submission the PDF is generated from the text, and the signature is bound to the SHA-256 digests of both.
- Changes marked
- The draft is compared with the revision in force, inline or side by side. Added and deleted words, changed sections and table cells are highlighted.
- Flow, effective date, reading
- Each step of the flow is signed by a different person, and approval comes from someone outside the revision's writers and editors. A revision in force opens a 14-day read-and-understood task.
From draft to in force
Write the text
Edit text opens the editor: headings, tables, images, a note box and a block menu on /. The page layout (A4 upright or sideways, margins, font and size) carries into the controlled PDF.
Autosave
The text is saved a few seconds after you stop typing. Below the editor: Saved and the time, the word count and who edited last; every save goes to the audit trail.
See what changed
The Changes section compares the draft with the revision in force: words added and deleted, changed sections, inline or side by side. Tables are compared cell by cell.
Submit for approval
The PDF is generated from the text with the lab's header and footer on every page. Up to five review steps of the category's flow are e-signed in order, then the approval.
In force, then read
A revision comes into force at once or on a planned date, and the previous one is withdrawn on its own. Reading tasks go to roles, titles or names; each person has 14 days to close theirs with their own e-signature.
Controlled document rules
The rules are enforced in the database for ISO/IEC 17025 §8.3, whichever screen a change comes from.
- Segregation of duties
- Approval comes from someone other than the people who wrote, edited or submitted the revision. Each step of the flow is signed by a different person.
- The PDF is printed from the text
- An in-app revision's PDF is always generated from its text, and the approver signs that PDF's SHA-256 digest. Approval goes through only if the PDF matches the current text.
- Text frozen for approval
- A submitted revision's text opens read-only, as a page. If it needs a fix, the revision goes back to draft and its author corrects and resubmits it.
- Editing at the same time
- If two people edit one draft at once, the later save gets a warning and the first saved text is kept. They reload the page and carry on from the saved text.
Further reading
Frequently asked questions
Can we prepare a document in Word and upload it as a PDF?
How do I see what changed between two revisions?
How do read-and-understood tasks work?
