Frontline Manual

Asset library links appear only when the library is available. A saved link explains when it is not available yet; contact the asset team for manuals and training. If availability cannot be checked, reconnect and sign in, then select Check availability. When available, open Asset library from Home or Manuals & training from the selected prestart asset. Search by asset label, registration, make or model and select the correct machine. Only current published resources with a verified relationship to that machine appear. Check the title and revision, then open the document or video while online. SharePoint permission is checked again when opening. If no verified material is available, contact the asset team; a similar model is not a substitute. Withdrawn resources disappear and changes to machine identity require managers to recheck applicability. There are no automatic offline manual packs. Reading a manual or watching a video does not record training completion.

Frontline and Hub support field work, project administration and the records needed to manage that work. Information handled: Work identity and contact details, such as your name, work email and access role. When you use model-backed manual help, the current question and approved manual excerpts may be processed to draft the answer. Work-directory matches are returned deterministically by Frontline and are not sent to the model. Project and work records, including forms, safety and quality records, maintenance and logistics details, documents, photos and comments. Some records may identify workers or other people involved in the work. Activity records created when the apps are used, such as submission, status, review and audit details. Operational diagnostic events such as a generated correlation ID, API route type, outcome, status, duration and minimised write-audit metadata. These events do not include form contents, photos, AI conversations or raw user identifiers. Why it is handled: To sign users in, control access and show the right work and project information. To complete and manage operational, safety, quality, maintenance, logistics and administration processes. To keep a traceable record of submissions, reviews, decisions and system operation. Where it comes from: Information you enter or upload. Information supplied by your organisation or its authorised users and connected business services. Information created through app use, such as timestamps, status history and audit records. Services and recipients: Information is available to authorised people in your organisation and to service providers used to operate the apps, including Microsoft identity and Microsoft 365 services, hosting providers and approved AI services. These providers may handle information outside Australia depending on your organisation's service configuration and contracts. See your organisation's privacy policy for its current arrangements. Retention and deletion: Operational records are retained in the organisation's approved systems under its retention and legal requirements. Frontline may temporarily keep pending submissions and recent activity on the device so work can continue or sync. Privacy-minimised diagnostic logs follow the hosting retention period approved by the organisation and are not a replacement for the operational record. The apps do not set one deletion period for every record; use the client policy and contact below for access, correction or deletion requests. AI and automation: Frontline can send the current question and approved manual excerpts to an approved AI service to draft a manual answer. Work-directory matches and personal, work, site-living and safety guidance are produced deterministically before any model request. Frontline does not save a chat history after the assistant page is closed. Provider processing and retention depend on the organisation's approved service configuration and contracts. Frontline is not a counselling or crisis service. Hub contains an optional media-enrichment process that can analyse approved images and context for a human reviewer; it is disabled in the current non-mock containment state. AI output is assistance only and does not make final approvals or other decisions about people. Access, correction and concerns: Use the client details below to request access or correction, ask about deletion, or raise a privacy concern. The client organisation owns its privacy policy, terms, contacts and complaint process. Open Privacy & Terms before sign-in or from your profile for the client policy, terms, privacy contact and complaint instructions.

Frontline is a mobile field-work app for project, safety, quality, maintenance, logistics and evidence tasks. Select the current project from Profile. In normal production use, the selector shows the active projects returned by Frontline. The selection is remembered for the signed-in account on this browser or device and restored after restart or sign-in; another account on the device receives its own selection. Frontline checks a remembered project against the next successful project-list refresh and asks for a new selection if it is no longer available. While the list is unavailable, a valid last selection may remain as device-saved context until Frontline reconnects. After one successful online sign-in, the current installed Frontline build can keep a privacy-safe app shell and a seven-day token-free account locator on that device. If all internet connections then fail, a prepared device can reopen Frontline, Take 5 and Sync for that account without treating the local locator as live authentication. The app displays Offline access and the prepared account. First use, Microsoft sign-in, live reference information and server acknowledgement still require connectivity. When the connection returns, sign in with the same Microsoft account before queued work can sync. Explicit Frontline sign-out removes offline access preparation without deleting that account's queued work. If Microsoft sign-in startup cannot finish promptly while online, Frontline shows a recovery message instead of leaving an indefinite loading screen; protected app content remains unavailable until sign-in succeeds. When a supported form cannot be sent, Frontline holds it in the signed-in account's Awaiting sync queue until Sync can submit it. Receipts distinguish queued, server-acknowledged, exact read-back verified, retryable failure and rejected failure without claiming verification from a successful POST alone. Receipt details separate occurrence, queue and server-received instants. Open the header bell for Notifications & activity: it combines pending Sync Queue work with the existing seven-day receipt history for the current account on this device. It is not a complete organisational or cross-device audit history. Use IT support request at the bottom to open Notify with IT Support selected. Profile lets the signed-in user choose a supported IANA display timezone; the underlying instant remains UTC. Copy the reference when following up. Online, Offline and Service unavailable describe distinct connectivity states. Frontline confirms a health-check failure before reporting Service unavailable, and a successful Frontline API response clears stale outage state. Browser-offline detection remains immediate. The cached app shell contains no authenticated API response or worker-specific server page. Privacy & Terms is available from Profile and before sign-in. Photo-enabled forms prepare supported images to a maximum 1600-pixel edge and progressively reduce JPEG quality only when needed. Frontline measures the complete workflow request before sending it; if it remains too large, the form and photos stay open so one or more photos can be removed. A size rejection is not described as offline and is not added to repeated automatic retries. In Sync, wait until the displayed retry time after a temporary failure, then tap Sync now. Use Sign in to retry when requested. Access denials and evidence conflicts need IT Support; keep the reference. Delete asks you to confirm the form, time and reference before removing the unsent device copy; Cancel keeps it and server records are not deleted. If saved submissions cannot be read, keep app data and use Try reading again or IT Support. Keep the app open if work is only held in memory. Take 5 retries resume matching saved answers and stop on conflicting evidence. An unfinished Take 5 is saved on the device for up to 24 hours and restored only for the same account and project. It remains working data, not a completed safety record, and is cleared only after confirmed submission, durable offline queueing or explicit discard. Use the in-form JHA library to check a project JHA while online without leaving Take 5. Take 5 saves its device copy before returning home even when online. Saved on this device means pending sync; use Notifications & activity or Sync to check for server acknowledgement. Recently used asset lists and checklist questions are held only in temporary session memory for the current account and project. Profile refresh clears these temporary copies; the next visit reloads the list or questions.

Open Apex Award from the shortcut beside SharePoint and Teams on the Frontline home page. Select the correct project before starting, enter the location where you work and the full name of the person you are nominating. Select every value they demonstrated: Positive Impact, Leadership, Accountability or Growth. For each selected value, describe what they did and give specific examples. The form requires a connection and does not use the offline Sync queue. Submit once and keep the displayed nomination reference. If submission fails, your answers remain on screen so you can retry the same attempt. A successful response means the nomination was recorded with Submitted status; it does not mean the person has been shortlisted or won. Award decisions are made through the authorised management process. Include only work-related information needed to explain the nomination.

Eligible queued work retries automatically when Frontline opens, reconnects, returns to the page or becomes visible in the foreground; the original form does not need to be reopened. If Frontline was opened through a prepared offline account, reconnection does not grant server access: sign in with the same Microsoft account before retrying. A different account cannot see or sync the original account's queue. Matching Take 5 retries tolerate SharePoint whole-second timestamp storage, but genuinely different or duplicate evidence still stops safely for review. Automatic retries remain silent if Microsoft requires interaction, and the item stays queued with Sign in to retry. A phone may suspend a minimized or closed web app, especially on iPhone, so Frontline does not promise scheduled or closed-app delivery. An older queued photo request becomes retryable when it now fits the bounded request policy. If it is still oversized, Sync marks it Rejected and preserves the device copy; submit a smaller replacement from the original workflow and delete the rejected copy only after the replacement is acknowledged. A saved prestart with an unfinished immediate-repair task stays in Sync. If access is denied, automatic retries pause; contact IT Support, then use the Retry button on that item when access is resolved. Keep the same reference. A saved action with a pending photo also stays in Sync. If access is denied, contact IT Support and use that item's Retry button once access is resolved; automatic retries pause. Legacy maintenance requests already queued on this device use the same follow-up recovery rules. Retry deadlines, rejected items, account isolation and acknowledgement-before-removal safeguards still apply. A valid Take 5 is first saved in the account-owned device queue, then sent automatically while the app is open and the same Microsoft account has live access. Home navigation does not mean SharePoint has confirmed the write. If a selected JHA sign-on was requested, that instruction stays with the Take 5 until both writes are acknowledged. If device storage cannot commit the queue item, the form stays open and does not claim success. Keep the device copy and use Sync to check pending or failed work. Do not clear browser data before acknowledgement.

Open Notify from the Frontline home page and choose the applicable HTS routing type: Incident or Injury, Contact Your Site Manager, Monthly Excellence Award, Unable to attend work, Materials-Used, Check In, IT Support, Complaint / Grievance, Contact HTS HR, Contact HTS Payroll, Contact HTS HSE, Contact HTS MGMT, or Other. The exact notification type is recorded for the configured HTS automation to use for downstream routing. Select the intended active colleague from the approved work directory. That value is email context; the automation selects the delivery group from the current project number and Key Personnel register. For IT Support, contact Ki Bullock at KiBullock@proxistack.com.au directly when needed. The displayed contact does not change or prove downstream Power Automate delivery; its project and Key Personnel routing is maintained separately. Choose the urgency, enter only the information needed and add an optional location or up to three photos when useful. A successful Frontline acknowledgement says Notification recorded and provides a reference. It proves the SharePoint workflow input was created; it does not prove the downstream automation completed, a message was delivered, a recipient received it, or action was taken. Notify uses at-least-once recording: an ambiguous retry retains the same reference and may create a duplicate rather than risk dropping the notification. Standard notifications may enter the signed-in account's Awaiting sync queue. Managers and administrators may record a confidential notification directly to the HTS Confidential site while online. New confidential messages and photos are never stored in the browser offline queue; keep the form open after an error and retry with the same reference. Frontline reports when the confidential record was created but attachments were not confirmed. Use the required direct-call, leave, payroll, grievance, safety or emergency procedure as well; Notify never replaces immediate verbal escalation or emergency contact.

Frontline provides Take 5, hazard observation, site inspection and safety interaction workflows. Select the correct project before starting. On a device prepared by a successful online sign-in, Take 5 can reopen and use its core questions when the internet is unavailable; live project risks, variations and JHA library information may be unavailable. Complete the questions from the conditions you observe, add actions where required and review the declaration before submitting. Stop and Think checks, task confidence and the declaration must be Yes. The server checks the completed checklist before confirming it; missing answers or failed safety gates leave the item unacknowledged in Sync. Keep that device copy and contact your supervisor or IT Support to resolve it. Confirmation records the accepted checklist version and the answers that can vary. A Take 5 saved offline remains on that account's device until connectivity returns and the same Microsoft account signs in to sync. Inspection photos and the complete request are checked before submission. If the request is too large, remove one or more photos and retry; the form stays open and the error is not presented as an offline failure. If Frontline cannot safely keep an offline inspection on this device, the form stays open so you can reconnect and retry without assuming it was saved. Use the inspection Add action control to record an action. Retry the saved attempt using its original reference. If the action is recorded but its photo is pending, keep the item in Sync. Access denial pauses automatic retries: contact IT Support, then use the item's Retry button after access is resolved. Conflicting evidence needs review; do not create a replacement to bypass it. Retrying preserves an action already closed by management. Frontline guidance does not replace the approved site procedure, SWMS, JHA, supervisor direction or emergency process. On submission, Take 5 first saves the completed form on this device and returns home. This is pending sync, not a server-confirmed safety record. Check Activity or Sync for acknowledgement. An explicitly selected JHA sign-on travels with that saved attempt and is confirmed only after the Take 5 and sign-on are written. Storage failure leaves the entered form open for retry. Continue to follow the approved site safety and JHA procedures.

Use the Safety area to find active JHA documents and record a JHA sign-on. In the MSDS / SDS Register, On Site shows products recorded for the selected project and may apply the current-project filter. All Products searches the organisation-wide SDS catalogue and does not apply project filtering. Always follow the current approved document shown by HTS and escalate a missing, expired or unclear document to the responsible supervisor.

The Quality section is visible and clearly marked Coming Soon. Quality checksheets and inspection test plan workflows remain unavailable until their dedicated validation and release gate is complete. Punchlists remain separate and record items that need attention and their status. Use the selected project, describe observed conditions accurately, attach relevant evidence and only change a status when authorised.

Use Prestarts to select the asset type, identify the asset and complete every required check before submission. The asset selector shows only records explicitly marked Active; blank, inactive and unknown statuses are excluded. Use manual entry only after checking the asset identity through the approved site process. Record faults, safety hazards and comments accurately. On the vehicle question Does the machine require immediate repair?, selecting Yes opens the repair comment field and saves the comment with that checklist answer. New prestarts retain their reference in the consolidated prestart register. When a fault requires immediate repair, Frontline also records a linked repair task. If the prestart is saved but that task cannot be confirmed, keep the same submission in Sync and retry it rather than submitting another prestart. Temporary failures retry after the displayed wait. Access denial pauses automatic retries: contact IT Support about access, then use the Retry button on that item when resolved. Conflicting links need IT Support review. Retrying preserves existing maintenance work and does not reopen completed tasks or overwrite notes. For electrical Test & Tag, photograph the tag clearly, add the item photo when available, choose Open or Closed and enter an accurate description. A successful submission confirms the files were recorded for the existing automation; extraction and the final register update happen afterward. If the maintenance form reports Maintenance saved; follow-up pending, keep it open and retry the same attempt. Frontline retains the reference and completion time so missing photos or follow-up work can finish. Contact IT Support about access denial or conflicting evidence; do not recreate the entry. Use Maintenance Plan for future work and Maintenance Activity for the consolidated record of completed work. One Activity can close no plan item, one item or several selected items for the same asset, and can add several Future Maintenance Items. Use Inspection for an ordinary maintenance follow-up check; formal compliance inspection still requires its governed checklist. Linked Activity submission is online-only and keeps the form open on failure so the same attempt can be retried. Do not create a replacement activity. Any signed-in Frontline user can use Already completed — link activity to select an existing same-project, same-asset Activity without changing its original evidence. Frontline preserves who originally recorded the work and separately records the authenticated user who performed the later link. These relationship controls remain unavailable until the verified register migration is enabled.

The Materials area supports available order, RFQ and delivery workflows for the selected project. Check project and reference details before submitting. If a commercial value, supplier instruction or approval is unclear, use the responsible commercial process rather than relying on the assistant.

Where a form accepts photos, choose Take photo to open the device camera or Choose from library to select existing images. Frontline scales a supported image to a maximum 1600-pixel edge and starts at JPEG quality 0.72, reducing quality and then dimensions only when needed to keep the encoded photo within 512 KiB (about 384 KiB decoded). A source image over 20 MiB is rejected before preparation. Frontline also measures the complete workflow request against its route-specific limit. If it is still too large, the form and photos remain available: remove one or more photos and try again. Review the preview and remove the wrong image before submitting. The standalone Photo Upload page requires a network connection and confirmation that HTS has permission to use the image.

The assistant may help find one active, visible HTS colleague at a time using approved work-directory fields: name, work email, job role and current project. Frontline returns that result deterministically without sending the directory projection to the AI model. It does not provide private employment information, inactive or hidden records, bulk employee lists or authority to contact someone outside the normal work purpose.

Harry can direct a worker to approved support but is not a counselling, medical or crisis service. For confidential support with personal, family or wellbeing concerns, use the HTS Employee Assistance Program (EAP) details approved for the deployment, or contact a trusted person, manager or People & Culture. If someone is in immediate danger, follow the site emergency process and contact local emergency services.

A worker who is sick or not fit for work should tell their direct supervisor or manager as soon as possible, indicate the expected absence if known, follow the applicable HTS or client leave-notification process and provide reasonable evidence if requested. For pay, timesheet, roster, leave or work-hours questions, contact Payroll or the approved responsible team and identify the specific record, period, shift or discrepancy. Raise a workplace concern with a supervisor or manager, or with People & Culture or another appropriate authorised recipient when the concern involves that person or direct discussion is not comfortable. Frontline Notify records the selected HTS notification type as an exact routing key for downstream automation. A Frontline receipt confirms recording only; continue to follow any required direct contact, leave, payroll, grievance, safety or emergency process. Harry cannot diagnose illness, decide fitness for work, lodge a complaint or determine an outcome.

Questions or concerns about site accommodation, rooms, meals, transport, noise, amenities, privacy, security or another resident should be raised with the accommodation or site manager, or the worker's supervisor, with the issue, location and urgency stated clearly. If the concern involves that person or the worker is not comfortable raising it with them, contact People & Culture. Personal wellbeing support is available through the deployment-approved EAP. Harry cannot allocate a room or resolve an accommodation complaint.

A worker should not start or continue a task that feels unsafe or where required controls, PPE or the current approved SWMS, JHA or SDS are missing or unclear. Move to a safe place if needed, warn affected people, tell the supervisor, site manager or health and safety representative, and follow the current site and emergency procedures. Only make an area safe within your training and when it is safe to do so. Use the applicable Take 5, hazard-observation, near-miss or incident process to record the concern. Harry cannot inspect a site, select controls or PPE, or override approved documents and supervisor direction.

The assistant must answer only from approved user manual articles, cite the source reference used, and say clearly when the approved sources do not contain the answer. Restricted engineering, security, identity and deployment material is not an ordinary-user source.