Hosted reporting workflow · UI40

Fault Reports

Report → assign → progress → request review → decide

Report, assign, record progress, review

Open Fault Reports to manage equipment faults. The browser now uses the same simple reporting and follow-up layout in both workspaces. Start with Report a fault, record what was observed, then select Save report. This creates a Reported record, not a completed Task, an equipment release or a closed investigation. No routine confirmation checkbox is required.

The report remains private to its reporter, current owner, authorised heads of its selected active department and project administrators with the relevant module access. Who can see this report? expands the complete scope. This is not anonymous or HSE-team-only reporting. Avoid unnecessary personal or medical details and use your company emergency and escalation procedures separately.

Capture the facts without guessing causes

A title and observed description are required. Record any known impact/restrictions and immediate actions. The observed date is optional; no date is invented. Choose the responsible department or leave Project administration, and select the reported priority. Link equipment is optional and uses one exact accessible record/version. Filtering or searching does not remove the chosen link; a failed lookup requires a retry or deliberately removing the optional link before saving.

A fault report is distinct from its linked equipment. It does not quarantine or release that item, change stock, complete maintenance or renew certificates.

These report forms do not support photo/file uploads yet. Handover attachments and document-invitation signing are separate features, not automatically available to every record type.

Update your own initial report

Your own first-cycle report can be corrected without a generic reason while it is still Reported, unassigned and has not entered triage or work. The hub requires its complete local create/amend history. The account, server time, version and before/after values are still retained automatically; no explanation is fabricated.

Correcting another author, a previously assigned/worked report, a reopened cycle or a report with incomplete history requires a genuine explanation and review. Unassigning a report does not erase earlier work. Saving identical report fields or identical assignment values keeps the saved version and audit unchanged; an obsolete version is still refused.

Assign and follow up

An authorised department head or project administrator uses Assign & follow up. Find the owner by name, login or account ID. Filtering keeps the selected owner, even outside the results. An unavailable saved owner or department is retained visibly rather than silently replaced; the server checks current eligibility before saving.

Same-department assignment/reassignment, target-date changes and unchanged or raised priorities save directly with Save assignment. There is no generic reason or extra checkbox for those normal actions. A change of responsible department or a priority reduction needs a short explanation and explicit confirmation. Changing a field clears that confirmation.

The selected owner gains report access and a former owner may lose access unless they remain its reporter or an authorised manager. Assignment does not reassign a linked Task. Current authority is checked again at save; a normal member with a Manage capability is not automatically a designated department head.

Find your work and record progress

The Responsibility filter offers All accessible reports, Assigned to me, Reported by me and Unassigned. These filters apply to the complete permitted catalogue before counts and 100-record pagination, not just the visible page. Combine them with status, search and, in HSE / QSHE, report type. They do not expand access or represent unread messages.

The assigned owner opens the record and chooses Save progress note. Enter the actual progress/findings and save directly. The note itself is the useful information; no second generic reason is required. Notes may be added in In progress or On hold, without automatically resuming held work. Prior cycles remain retained.

Request closure and make the decision separately

The owner uses Request closure, records the corrective work/proposed resolution and the verification performed with remaining limitations, then selects Send for closure review. No extra routine checkbox is required, but both substantive descriptions remain mandatory. This changes the report to Awaiting review, not Closed.

An authorised manager uses Review proposed closure, reads the saved resolution and verification, deliberately chooses Close after review or Return for further work, provides review findings and confirms the decision. No decision is preselected. Returning the report requires fresh corrective verification before a later review. Same-person review is recorded as such, never described as independent review.

Closing a report does not close its Task, approve maintenance, release equipment or authorise work. For emergencies, regulatory reporting, medical handling, permits and equipment release, follow separate approved procedures.

Keep linked corrective work separate

Create corrective Task keeps the existing separate source-sharing review. It prepares a private draft of the task fields, not an automatic copy or save. Confirm its selected content and audience deliberately. An existing Task can instead be linked using its exact permitted identity and version.

Task links never give another account source access and never synchronise closure or completion. Inaccessible sources are redacted. Changed source versions are labelled; a stale selected version is not silently substituted. Changing an established Task link retains its existing reason/confirmation.

Exceptional actions and retained history

Hold, cancel, reopen and archive are under More report actions, keeping everyday work prominent. Resume remains available for a held report. These actions retain a genuine reason and confirmation. A hold review date is a recorded date, not an automatic reminder or resumption. Closed/cancelled records may be archived, not erased; reopening starts a fresh review cycle.

History / amendments retains actor/time/version and earlier values under current report access. Ordinary report PDFs remain available where permitted. The native Windows reporting dialogs and master PDF guides were not rebuilt by this browser update.

Protect unsent wording and retry the same request

Report forms are online, in-tab work, not autosaved offline drafts. Closing an untouched form is direct. Closing changed wording or an uncertain request warns before discarding. Navigation and account-scoped recovery do not submit unfinished work for another person. Reloading/closing the page may lose unsaved text; do not clear browser storage.

A lost response retains the exact original request and operation ID for Retry unchanged request, preventing duplicate reports or progress notes. Current permissions, audience and versions are rechecked. A conflict retains your wording and refuses to overwrite newer saved information. Copy that wording before closing to inspect the saved record.

Opening a form rechecks the selected saved report without silently switching revisions. A later lookup cannot cover another account, editor or dialog. Interrupted source searches have an explicit retry/remove-link path. These protections do not turn the form into durable offline storage.