A correction is more than rendering the same design again. FotoFit managed credentials keep a durable recipient record and support authorised editing and regeneration. Temporary jobs produce disposable batches and do not provide the same correction history.
Classify the change before editing
| Change | Recommended handling | Reason |
|---|---|---|
| Spelling or date correction | Edit the managed record and regenerate | The replacement remains connected to the issuance |
| Template-wide design update | Review scope before regenerating affected records | Not every historic certificate should change automatically |
| Different recipient or award | Create a separate approved issuance | It is a different business record, not a correction |
| Temporary batch error | Fix the source and run a new job | Temporary output has no durable managed record |
A controlled correction workflow
- 1Confirm authorityVerify that the requester or workspace member is allowed to change the issued data.
- 2Correct the source of truthUpdate the approved recipient or event data, not only a downloaded file.
- 3Edit the managed recordChange only the fields required for the correction and review the preview.
- 4RegenerateCreate the replacement output through the managed-record action.
- 5Reconcile deliverySend or export the replacement only after checking the current file and verification page.
History is a safety control, not an editing shortcut
Managed records retain the current file and limited regeneration history while the record exists. Where history controls are available, authorised users can inspect earlier versions and restore a suitable version. That history does not prove the issuer's authority or replace an external audit trail required by law or accreditation rules.
Verification should resolve to current state
A QR code should open the managed verification record rather than encode a static claim that cannot change. After correction, review the public information and the current generated file. FotoFit confirms the record held by the issuing workspace; it does not independently certify the issuer or programme.
Common questions
Can I correct a temporary certificate?
You can fix the source and generate a new temporary batch, but there is no managed recipient record to edit or preserve.
Does regeneration consume output capacity?
Yes. Generated replacements use the workspace's applicable output allowance; check the current plan before a large correction run.
Does deleting the current file erase every related record?
Deletion controls differ for records, jobs, forms and stored versions. Review the confirmation shown by the dashboard or request verified account-level help when broader deletion is required.