Send for approval

When you have prepared a certificate but you cannot sign it yourself, you send it for approval. This moves the certificate from Draft to Awaiting approval and hands it to a Quality Person (QP) or Admin, who is the only person who can sign and submit it. Sending for approval is typically done by a Technician after data entry.

Before you start

• The certificate must be in Draft status. Only a draft can be sent for approval.
• You need the Certificates: Update permission. Technicians, Submission Coordinators and Admins can prepare certificates; only QP and Admin can sign. See Roles & permissions.

1. Finish reviewing the draft

Before you hand it off, make sure the mapped data is correct and any presentational edits are done — see Review & edit mapped data. Once the certificate is signed it can no longer be edited, so the approver relies on your review being complete.

2. Send to approver

1. Open the draft certificate from the Certificates list. It opens in the wizard.
2. Move to the final step. Because you do not have sign permission, this step is labelled Send to Approver.
3. Select Send to Approver.

The Send to Approver step for a user without sign permission

The certificate moves to Awaiting approval and the step shows a Sent to Approver confirmation. A QP or Admin can now pick it up and sign it.

Tip

If you are a QP or Admin, you will not see a Send to Approver button — the final step is Sign and submit instead, because you can complete the whole flow yourself. See Sign a certificate.

What happens next

• A QP or Admin reviews and signs the certificate, moving it to Approved for submission — see Sign a certificate.
• While it is awaiting approval the certificate can still be edited if a correction is needed, but it cannot be edited once signed.

Related

• Sign a certificate
• Review & edit mapped data
• Certificates overview
• Roles & permissions