PIN-Only Access
Enter your assigned PIN on the sign-in screen. If your role is allowed into the console, the page opens directly to your visible tools and account workspaces.
LaneAward Console
This guide explains how to use the LaneAward Operations Console as it works today. It focuses on the features that are visible and usable for the signed-in role, without exposing internal permission logic or hidden fields.
Accounts tab.Order Profitability report as a PDF for a selected date range.
The Operations Console is not the place where contributors assign live work to themselves. At this stage,
only manufacturing contributors add their own live tasks in Time On Tasks. The console can help
prepare reusable task descriptions for contributors, but it does not replace the contributor workflow.
Enter your assigned PIN on the sign-in screen. If your role is allowed into the console, the page opens directly to your visible tools and account workspaces.
The console now centers around the Accounts tab and a second workspace tab that is used for
Add User or the selected account.
The console automatically limits what each signed-in person can see. Some roles will only see a smaller subset of users or a read-only view.
The console uses the same shared database as the contributor app. User changes here affect real sign-in and account availability in the connected environment.
Accounts tab to review the current account list.Add User to move tab 2 into create-user mode, or click an account row to open that account in tab 2.Edit, Reset PIN, Deactivate, or Save as needed for that account.Reports tab for a read-only contributor activity summary with drill-down details. For the Order Profitability report, use the printer icon in the toolbar to print or save the current data as a PDF.User Guide, Topology, Runbook, and Reference when those documents are visible for your role.
The console uses PIN-only sign-in. There is no username selection screen. Enter a valid console PIN and use
Enter Console to continue.
If the PIN belongs to a role that is not allowed into the console, sign-in will fail and the page will stay on the sign-in screen.
After sign-in, the header shows the current signed-in name and role. This helps confirm exactly which account is in use before anyone creates, resets, or deactivates users.
Use Sign Out in the header when you want to leave the console or hand the workstation to
another authorized person.
The Accounts tab is now the main review surface. It shows the visible account list in a
spreadsheet-style format with sortable columns such as:
Display NameRoleEmailPay Type and Amount for contributor-tracked rolesTasks with a View button for team leads and manufacturing contributorsClicking a row opens that account in tab 2, where the account can be reviewed or edited.
Selecting Add User opens tab 2 in create-user mode. Required fields are:
Display NameRolePINOptional fields are:
Email AddressNotes (currently held for future use)If required information is missing, the form highlights the field and shows a clear error message instead of saving an incomplete account.
When the selected role is Manufacturing Contributor or Foreman, the console reveals the
Add Contributor Tasks panel. This allows the console operator to add reusable task descriptions for
that new contributor during account setup.
These task templates help the contributor later in Time On Tasks, where task descriptions can
be found more quickly through fuzzy search inside Workload Setup.
This is different from assigning live work. Contributors still add their own live tasks for themselves in the contributor app.
When an account row is selected from Accounts, tab 2 changes to that user’s name and opens a
dedicated account workspace. In the current draft, that workspace can show:
When no account is selected and Add User is not active, that second tab stays hidden so the
visible tab rail collapses left without empty placeholders.
Identity detailsCompensation only when the selected account uses those fields and the signed-in console role is allowed to view compensation dataTeams for visible team memberships plus team-manager and team-lead assignments where the signed-in role is allowed to manage themView Tasks as a header action that opens the reusable task list modal for contributor-style accountsTime Corrections for recent contributor or team-lead work sessions
Use Edit to switch this workspace into editable mode. Use Save to keep the
changes, or Cancel to abandon them. When the signed-in role allows it, this same workspace
also provides Reset PIN and Deactivate for the selected account.
The Time Corrections area is the approved way to fix a forgotten start, pause, or stop. Each
correction requires a reason and preserves an audit row so the original recorded session can still be
reconstructed later.
The View button in the Accounts sheet, and the View Tasks button in
the selected-account header, both open the reusable task list for that contributor-style role.
This task-list editor is only active for Team Lead, Foreman, and Manufacturing Contributor
accounts.
The Teams feature is currently turned off in the Operations Console (2026-06-03). The Teams tab and the Teams card in the Account Editor are both hidden, and team membership has no effect on any report, filter, or management tool. Existing team memberships in the database are preserved but inactive — they can be restored at any time by re-enabling the feature.
Conceptually, a team is a crew assignment — a management decision about who works well together on a given type of order. That decision belongs entirely to management and has nothing to do with the labor tracking system. Teams do not own orders, drive task assignment, or affect how labor is recorded. All time tracking and task work happens at the individual contributor level regardless of any past or present team association.
Profitability reports, contributor activity reviews, Time Corrections, and Order Number Corrections all show data based on what individual contributors actually did, with no team filter applied.
The Teams tab is not visible in the Operations Console at this time. With the Teams
feature disabled (see section 8), no role sees the tab in the top navigation, and the Teams card
in the selected-account workspace is also hidden for all roles.
If the Teams feature is re-enabled in the future, the tab and its associated controls — Create Team, Rename Team, Delete Team, and the team membership and leadership assignment widgets in the Account Editor — will reappear for the roles previously permitted to use them.
All contributors are required to leave their workstation in one of these states before the end of every shift:
Tasks must never be left actively running overnight. A session that runs unattended through midnight accumulates time under the wrong calendar day and requires a manager time correction to fix. If a contributor reports a task was left running, use the Time Corrections workflow immediately.
Paused tasks that will never be continued should not sit indefinitely. Managers should review open paused tasks periodically and follow up with contributors to close out anything that is no longer active work.
Use this workflow when a contributor or team lead forgot to start on time, forgot to pause, or forgot to stop a task at the correct time — including when a task was left running overnight.
Accounts tab.Time Corrections section.Correct Time on the affected entry.Start and Stop time.Save.If the session was still active because the contributor forgot to stop it, saving the correction will close that session as a paused entry at the corrected stop time.
When a contributor completes a repeat task, the session card in Time Corrections shows a
Repeat Multiplier section below the start and stop time fields. This section is only
visible for sessions that were completed as repeat tasks.
Use this section when the contributor timed the iteration incorrectly or entered the wrong quantity.
Accounts tab.Time Corrections section, find the repeat task session and click Correct Time.Action?, Qty?, and Iteration time in min.Save.The session card in the account view updates immediately after saving to reflect the corrected repeat summary.
Pay Type and the compensation amount field are intentionally limited to
Manufacturing Contributor, Foreman, and Team Lead accounts, but those fields are not
visible to every signed-in console role. When Pay Type is set to Salary, the
amount field is labeled Annual Salary and accepts the worker's full annual salary (e.g. 52000).
When set to Hourly, the field is labeled Hourly Rate.
In the current draft, Team Lead and Foreman users do not see compensation columns in the
Accounts tab and do not see the compensation card in the selected-account workspace. Higher
management roles and technical admin roles keep that visibility.
This keeps the console focused on contributor-cost estimation rather than broader payroll processing.
Some signed-in roles can open the console and review what is visible to them, but they will not see the full user-management form. When that happens, the console shows a read-only notice instead of management controls.
The Reports tab now includes a Report selector so leadership and technical roles
can switch between the read-only Contributor Task Activity view and the new read-only
Order Profitability view without leaving the same workspace.
Report to switch between the contributor-focused operational view and the order-level profitability view.Period to switch between Daily, Weekly, and Monthly. The default is Daily.Date Range with the side-by-side From and To calendars to set the exact task timeline you want in the report.Totals for the Period once the selected window loads.Contributor Task Activity keeps the clean summary cards for Active Workers, Queued Tasks, Paused Tasks, Running Tasks, Total Time, and Total Cost.Order Profitability summarizes invoice-backed orders and labor-backed orders in the selected period, then shows invoice number, taxes collected, shipping collected, total cost, retail price, and margin percentage.Time On Tasks contributor app.Open Task Mix dropdown instead of a full row of colored state bubbles.Pauses line to jump directly into pause reasons for that contributor.Retail Price, keeps Admin Costs as a placeholder column for later, and calculates margin from the currently known cost data only.billed_total field on the ProfitMaker order record, which reflects the order value from the time the order is created — before an AR invoice is formally posted in the accounting system. Margin is calculated from that order-level value: (Retail Price − Labor Cost) ÷ Retail Price. If the billed amount is revised before final invoicing, the margin will update automatically on the next ProfitMaker reference refresh.Period or either Date Range calendar now refreshes both reports automatically. The Refresh button remains available as a manual retry and verification control.Windows / Edge users: The date fields show a small calendar icon on the right side of each input. Click that icon to open the date picker. If you click the date text itself and nothing happens, move your cursor to the right edge of the field where the icon is visible and click there.
The Order Profitability report can be printed or saved as a PDF directly from the console. The print icon sits between the To date field and the Refresh button in the report toolbar.
Print flow:
From and To fields, then click Refresh to load the data.Print Preview to see a paginated mockup of the printed pages before committing. Use the arrow buttons to step through pages.Print from either the info screen or the preview screen. Your browser's standard print dialog opens.Go Back to step back, or click outside the panel to close it entirely.What the printed output includes:
Format and orientation:
The print icon is only active when the Order Profitability report is loaded with data. Clicking it before selecting a date range will show a brief message prompting you to select a date range first.
Documentation tabs now follow role permissions and always collapse left in the same order when they are available.
In the current draft:
User Guide.Reports is available to Owner, Developer, Senior Management, and Manager.Topology is limited to Owner and Developer.Runbook is limited to Owner and Developer.Reference is available to Owner, Developer, Senior Management, and Manager.Team Lead sees only User Guide.Foreman also sees only User Guide.Hidden tabs do not leave empty slots in the tab rail.
The About tab is the last tab in the console and is visible to all roles. It shows the app name,
current version number, and update status.
In Time On Tasks, the About section is at the bottom of the hamburger menu (the three-line icon in the top-left corner). It shows the app name, current version, update status, and copyright notice.
Developer: full console access, full user-management access, can see all document tabs.Owner: can manage users, has a cleaner view that hides inactive users and the deactivate button, and can see all document tabs plus Reports.Senior Management: can enter the console, manage the visible user levels available to that role, correct tracked time on eligible accounts, and see User Guide, Reports, and Reference.Manager: can enter the console, manage the visible user levels available to that role, correct tracked time on eligible accounts, and see User Guide, Reports, and Reference.Team Lead: can enter the console, manage manufacturing contributors where allowed, correct tracked time on eligible contributor-style accounts within that scope, and see only the User Guide tab.Foreman: inherits Team Lead-level console permissions, can manage manufacturing contributors where allowed, correct tracked time on eligible contributor-style accounts within that scope, and see only the User Guide tab.Manufacturing Contributor: does not use this console for live work creation; contributors work in Time On Tasks.Operations Console updates do not appear automatically. The codebase is maintained by the development team and is tracked locally with Git, a tool that takes named snapshots of the project at meaningful save points so changes can be reviewed, rolled back, or moved between environments cleanly. Git lives entirely on the development Mac — nothing about the source code leaves the machine, and there is no third-party service in the loop.
Most changes are validated in the staging environment first
(staging.console.laneaward.com) before being promoted to
production (console.laneaward.com). If you see a
behavior in staging that has not yet appeared in production, that is expected — it
is sitting on a development branch that has not yet been approved for production
deploy. The reverse — a production behavior that staging no longer has — usually
means staging is one step ahead of production while a change is under review.
For the technical details of how source changes are tracked and how branches keep work-in-progress separate from the deployed production code, see the Version Control And Source Management section of the Project Reference document.
Make sure you are entering the active PIN exactly as assigned. If the account is inactive, or if the role does not have console access, sign-in will fail even if the PIN used to work before.
That means the current role has console access but not user-management access. Check the identity card in the header to confirm which account and role are currently signed in.
Select the account row itself, not the sort header or a button inside the row. The selected account should move focus to tab 2 and place the user name in the tab title. A small ▾ indicator appears after the name to show that the tab has a dropdown menu with additional sections.
That is expected unless the selected account uses compensation fields and the signed-in console role is
allowed to view them. For example, Team Lead and Foreman users do not see compensation data in the current
draft.
The contributor can still add live work for themselves in Time On Tasks. The reusable task
template list is helpful, but it does not block contributor sign-in or live task creation.
Make sure a date range is selected and the Order Profitability report has been loaded first by clicking Refresh. The print icon only opens the print panel when there is data loaded. If no data is present, a message will appear prompting you to select a date range.
The console requests landscape orientation automatically, but some browsers give the user final control in the print dialog. If the output appears in portrait, open the print dialog's page setup options and switch the orientation to Landscape before printing. This is especially common in Safari.
On Windows using Microsoft Edge, clicking the displayed date text may not open the calendar. Look for the small calendar icon on the right side of the date field and click it directly. The icon highlights when you hover over it.
The default PDF filename is set to Order Profitability Report when printing from the Order Profitability report. If you see a different name such as LaneAward Operations Console, your browser may have cached the page title. Try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) and print again.
Refresh the console page and open the guide again. During staging work, browsers can briefly hold an older copy of a static HTML file.
Open the affected account in Time Corrections, locate the session, and use Correct Time
to set the stop time to when the contributor actually stopped working. Enter a reason such as
Task left running at end of shift — corrected to actual stop time. The recalculated duration
will reflect the correct hours for that day.
Follow up with the contributor directly. Tasks that are genuinely finished should be stopped. Tasks that were added in error should be canceled. The console does not automatically close stale paused tasks — a manager or team lead must work with the contributor to resolve them through the contributor app.
That section only appears for sessions that were completed as repeat tasks. If the contributor did not configure a repeat before stopping the task, the section will not be present and the correction cannot add one retroactively. Contact a Manager or Owner if a repeat configuration needs to be applied after the fact.
The Total min field recalculates automatically whenever Qty? or Iteration time changes. If you do not see it update, confirm both fields contain valid numbers — quantity must be 2 or more and iteration time must be greater than zero.
The browser may be serving a cached copy. On Android or Samsung tablet, open the browser menu, go to
Settings → Privacy → Clear browsing data, clear cached files, and reload the page.
On desktop, use Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows) for a hard refresh.
If a standard refresh did not clear the update notice, a full reinstall may be needed. Tap Install Update in the About section and follow the on-screen steps. You will need to remove the app icon from your home screen and re-add it from the browser after the reinstall completes.
A correction reason is only required when the start or stop time is also being changed. If the start and stop times are unchanged, leave the reason field empty and save. The repeat correction will still be applied.
No. As of 2026-04-30, all user PINs are protected using Argon2id cryptographic hashing. Once a user signs in for the first time after this update, their PIN is permanently converted to a secure hash and can no longer be displayed in plaintext — this is intentional and correct security behavior. To assign a new PIN to a user, use the Reset PIN function in User Accounts. The system will generate a new secure PIN that the manager can then communicate to the user directly.
PINs are protected by two layers of security on the server. First, each PIN is stored using Argon2id — a memory-intensive cryptographic hash that makes bulk offline attacks impractical even if the database were ever accessed directly. Second, a fast-lookup token is stored alongside the hash so the server can identify the correct user account in under one millisecond, then run exactly one Argon2id verification (~230 ms total) rather than checking every user in sequence. Both layers are transparent to users — sign-in is fast and secure with no change to the normal PIN workflow. Failed PIN attempts trigger progressive lockouts (60 seconds, then 5 minutes, then 15 minutes, then 1 hour) per device to block brute-force attempts.
Yes. When resetting a single user's PIN, the console allows you to enter a custom 6-digit PIN or leave the field blank to have the system generate one automatically. In both cases the PIN is stored as a secure hash immediately — it will not be visible after saving. Write it down before confirming if you need to hand it to the user.