What it does
Contractor uploads
The engineer emails the certificate to whoever booked them, and it stays in that person's inbox. A link that files it against the right asset solves most of the problem.
A request goes out as a link tied to a specific asset and certificate type, with an expiry and a use limit. The contractor uploads; the file lands against the right premises and asset, and the expiry is set from the certificate.
Uploads are virus-scanned, and the link is scoped to the one thing it was minted for — it cannot be repointed at another record, and refusals are deliberately indistinguishable so the endpoint gives nothing away.
Nothing about it requires the contractor to create an account, remember a password, or be onboarded.
What it does not do
The boundary, stated plainly, because you will find it eventually and it is better to find it now.
- It records what the contractor uploaded. It does not verify they were registered, competent, or that they did the work.
- A link is a bearer credential for the one action it was minted for. Anybody who has it can use it until it expires or is spent.