Shared hosting requires the server to remain authoritative for attempt timing, grading, and pass/fail state — using database timestamps and request-response flows instead of background jobs.
Who this guide is for
Article content
Server Authority Under Constraints
Shared hosting changes the design assumptions. The server must remain authoritative for attempt start times, expiry, grading, and pass/fail state, but the implementation should stay within normal request-response flows.
Practical Implementation Model
That means database timestamps, periodic autosave, and server-side submission logic rather than background job dependence.
Schema and Backend Foundation
The current schema and backend foundation now support that model without changing the shared-hosting deployment strategy.
For compliance training, assessment design should protect completion integrity, result accuracy, and certificate reliability without creating unnecessary operational complexity.
Assessment completion supports training evidence, but it should not be presented as proof of complete POSH compliance by itself.
Topics