Your work first.
The detail when you need it.

Use Sitepack in your phone or computer browser. The signed-in workspace is for authorised company members; shared worker links only provide the access granted by that link.

1. Open app.sitepack.com.au and sign in or create an account. Complete any account, company or consent steps shown. A company join request may need owner/admin approval.
2. Open More > Settings. Check your name and mobile. An owner/admin should check company details, state, primary trade and how the business mostly gets work.
3. Choose Projects & jobs, Service & callouts or Mix of both where appropriate. This affects the existing job and callout tools, not the safety review rules.
4. Owners/admins manage team access and billing. Check current terms and pricing in the account rather than relying on an old guide or promotion.

Today is the starting screen. It brings personal actions and urgent attention forward without replacing the full registers.

1. Use Report a hazard for a new field report.
2. Open My work for actions assigned to you. Read the required work, priority and deadline before taking a step.
3. Owners/admins can open Review for reports and completed work needing a decision. Leads do not receive the same review controls.
4. Open More for the original tools, jobs, settings, full safety register, assignment and delivery controls available to your role.
5. Use Refresh when you need a fresh view. Open the full register for filters, history and records beyond a summary list.

See the Today screen

From Today, choose Report a hazard. Capture the facts you know, including what you saw and where, without filling gaps with guesses.

1. Record: tap Record and allow microphone access. Choose Type instead if recording is unavailable or not suitable.
2. Speak: describe the situation and location. Tap Stop when finished. Stopping sends the recording to OpenAI for transcription.
3. Check and save: correct the transcript, use Job details if relevant and flag immediate danger when applicable. Choose Save report and wait for the saved confirmation.
4. To retain the original audio, download it before leaving the tab. The capture recording is not automatically stored with the hazard; upload it separately as evidence if required.
5. Open the saved report to register supporting photos or audio. Evidence upload has its own confirmation and may reopen review.

Treat the original account and the AI draft as different things. An authorised person must assess the report and the actual conditions.

1. Open the urgent report or review queue. Read the original account, registered evidence, current urgency and decision history.
2. If facts are missing, request clarification using the available decision. Do not treat a confident AI draft as evidence of conditions that were never reported.
3. Record a human assessment or implemented controls only when the decision is supported by what has actually been done.
4. Assign linked follow-up actions where work needs an owner and due date. Creating an action does not itself control the hazard.
5. Urgent clearance is a separate authorised owner/admin decision. An action being verified does not automatically remove outstanding urgent review.

The focused task page shows the required work, responsible person, due date and next step. Expand the secondary sections for evidence, history and advanced controls.

1. To assign work, use Assign an action from the hazard or More. Record a clear title, required work, responsible person, due date and priority.
2. As the assignee, read the task. Choose Start action only when your authority and site procedures allow it. If the work is already done, use the completion option.
3. Describe what was completed and select registered supporting evidence where required. Submit completion and check the saved state.
4. Awaiting verification means completion was reported, not independently confirmed. A permitted reviewer checks the result and verifies it or returns it with a reason.
5. High-priority actions cannot be verified by their assignee or completion submitter. Lower-priority self-verification, where permitted, requires a reason.
6. If someone else changed the record, load the latest version, review the differences and deliberately reapply your decision. Do not blindly repeat a stale submission.

See an example task

Safety-action SMS, reminders and escalation are in a limited rollout. They require company activation, eligible recipients and delivery gates. Ask the account owner or Sitepack to confirm your company is enabled.

1. Open More > Notifications & escalation, or expand Notification history on a task or report.
2. Read the actual delivery state. Queued is not sent. Sent is not delivered. Delivered is not read or acknowledged.
3. Check recipient and escalation settings with an authorised administrator. Do not assume every worker or supervisor receives every notice.
4. For failed, suppressed or uncertain outcomes, inspect the reason and use a direct contact method when safety requires it. Only use supervised recovery controls after reviewing what happened.
5. Treat worker links as access-bearing links. Share only with the intended recipient; they are not equivalent to an authenticated company-review session.

The tools have not disappeared. Open More or Tools dashboard for the existing workflows. Keep your competent-person review and on-site procedures in place.

1. Projects: open Jobs, create or select the job and maintain its crew roster. Generate and review the required SWMS, then share the permitted sign-on link or QR.
2. Service/callouts: open Take 5 or SWMS and select the one-off callout/no-job option where available. Record the location and review the record before using it.
3. Mixed work: use the job for planned work and the callout path for site-less records. The callout register lists compliance records, not dispatch bookings or invoices.
4. Toolbox talks: prepare or review the talk, deliver the discussion and retain sign-on records. Check the job's actual scheduling and delivery settings rather than assuming automation is enabled.
5. Incidents/near misses: open Near miss or the incident register from the tools dashboard. Record the account and evidence; review AI suggestions and make any required external notifications separately.
6. Tools dashboard also provides company documents, SWMS register/library, handover and other enabled modules. Module availability and account gates still apply.

A success message is the evidence that a save completed. A recording, draft or queued request is not a saved safety record.

1. Microphone blocked: allow browser microphone access or choose Type instead. Retry transcription only when connected; check every recovered transcript.
2. Offline or failed save: keep the tab open and retain a separate copy where safe. Reconnect and confirm the save. There is no promised durable offline outbox or automatic background sync.
3. Session expired: retain the unsaved account before signing in again. Draft-retention protections do not guarantee recovery after closing a tab, clearing browser data or restarting the device.
4. Missing action or review option: check the company, account role and current record state. Ask an owner/admin; do not use someone else's account or link to bypass access limits.
5. Evidence: hazard attachments support up to 10 MiB per file, with six photos and one audio file per hazard. Check the upload confirmation; this limit is different from voice-transcription capture.
6. For account or product help, contact hello@sitepack.com.au with the page, approximate time and error text. Avoid sending unnecessary personal or sensitive incident details.