A register can be set so that one log is sent for verification once, or many times. Each round of sending is called a submission. You also choose whether your verification levels sign one after another, or all at the same time. Everything is set on the register's Assign Verifiers screen.
Open the register → Assign Verifiers.
Turn on Verification required.
Under How many submissions can one log have?, choose One time or Multiple. Multiple is only offered if digiQC has enabled it for your organisation; choosing it reveals a box starting at 2 — type a higher number if you need one, up to the maximum shown beside the box.
If a log may have more than one submission, answer Can the next submission be sent before the previous one is verified? — Yes, any time, or No, one after another.
Answer Are all verifier levels asked at once? — Yes, all at once, or No, one level after another.
Add your verifiers to Level 1, Level 2 and Level 3 as usual, then click Save.
A submission is one round of sending a log for verification. It holds everything the filler added since the last time that log was sent. One log can have many submissions — for example, one for the 7-day cube results, one for the 14-day and one for the 28-day.
No. The levels you set on the register are used for every submission of every log under it. There is no separate verifier setup per submission.
Submission order decides when the filler can start the next round of entries. Verifier level order decides how your levels sign one round. They are separate settings and can be different.
Every level is emailed at the same moment. The submission is verified only when all levels have verified. Nobody waits in a queue.
No. Every enabled level must verify. One verification only records that level's decision.
Up to three, the same as before.
Two is the smallest number that makes sense for "Multiple", so the box starts there. Type any higher whole number over it, up to 20 — the fixed maximum for every organisation.
They are all set to One time submission with levels asked one after another, so they keep working exactly as they did. You can change them whenever you like.
A submission that has already been sent finishes under the rules it was sent with. The next submission sent uses your new setting.
No. Logs that have already gone past the new number keep everything and finish their current submissions. They just cannot start a new one.
It stays exactly as it was — its verified submission is still locked and cannot be edited. But it becomes eligible for a new submission, since the register now allows more than one. You will see a confirmation naming this before you save the change.
Yes. If that level already has submissions waiting, the new verifier is emailed straight away with the number waiting and a button that opens their To Do. If nothing is waiting, no email is sent — they are emailed when the first submission reaches them.
Yes. Every save records what changed, the old and new value, who changed it and when. Ask digiQC support if you need it.
Only a System Admin can change them. Everyone else sees the same screen with the controls greyed and the message "To change verification settings, ask your System Admin for Register setup access."
It must be a whole number from 2 up to 20 — the fixed maximum for every organisation. Below 2 you will see "Enter a number of 2 or more."; above 20 you will see "Enter a number of 20 or less."
Verification required is off. Turn it on and the settings appear.
Yes. It applies whenever verification is on, whether the register allows one submission or many.
Existing registers are not changed by this release — they stay on one submission, levels one after another, until you change them.
Multiple's maximum is a fixed 20 for every organisation — there is nothing to configure and nobody to ask for a higher number.
Verifiers are set once per register and used by every submission — there is no per-submission verifier list.
Any one verifier of a level can act for that level, in both orders.
Register sends email only. There are no in-app or WhatsApp messages.
2.4.3 Fill a register — logs, entries and submissions — how the filler sends each round.
2.4.6 Verify or send back register submissions — what the verifier sees and does.
2.4.7 Check a register log's verification status and detail — reading the state from the log list.
