ModulesWorkforce Log

Workforce Log

A spreadsheet of every sign-on on one project in a date range: one row per sign-on, 25 columns in Lacroo Core’s order and header text, in shift-day order. The file is named Workforce Log.csv, as in Core. In your report history it is titled after the project and the dates, for example Riverside Road Upgrade - Workforce Log (Sep 1, 2026 to Sep 26, 2026).

Every sign-on is included: sign-ons to a prestart, Start Shift sign-ons (a QR scan with no prestart), and sign-ons brought over from Lacroo Core, whatever the person’s role. A sign-on whose prestart was later deleted stays in the file.

Where it is

  • Reports › Field reporting › Workforce Log.
  • The Workforce Log button on the Sign On Workbench, next to Export CSV. It opens the report with From and To set to the workbench’s day and Supervisors set to the workbench’s supervisor. It never starts a report by itself.

Who can run it

Anyone with Sign On Workbench › View sign-on workbench on the project. By default that is the master admin, organisational manager, project admin, engineer, senior supervisor and supervisor roles. Labour, plant operators, hire roles and clients do not see it.

PersonSign-ons they get
AdminEvery sign-on on the project.
Supervisor and senior supervisorThe sign-ons they supervise (the supervisor on the sign-on, else the prestart’s) or are an associated supervisor on, in the chosen project only.
Engineer, Export whole project onEvery sign-on on the project, Start Shift sign-ons with no supervisor included. This is the default.
Engineer, Export whole project offThe sign-ons of the supervisors they are assigned to (as supervisor or associated supervisor). With no supervisors assigned, every sign-on on the project.

The Supervisors list shows only the supervisors on the sign-ons you can see.

How to run it

FilterWhat it does
From, ToWhole days in the project’s calendar, both included. They start at this month so far. Up to 2 years.
SupervisorsOnly the sign-ons these people supervise. Empty means everyone, including Start Shift sign-ons with no supervisor.

A line under the filters says how many sign-ons the file will hold. When there are none it says “No sign-ons found for these dates.” and you cannot run it.

The file downloads by itself when it is ready; no email is sent. Files are kept for 90 days. A run that fails always emails you.

A sign-on’s day (the Prestart Date column, and the day From and To match) is the day recorded on the sign-on; if none, the prestart’s date; if none, the day it was signed.

The columns

#ColumnWhat it shows
1ProjectThe project’s name.
2Project CodeThe contract number of each live stage, in stage order, joined with , (for example 6139, 6140).
3Project Company IDThe company ID (CID) of the same stages, each value once. Blank when no stage has one.
4Prestart DateThe sign-on’s day, as dd/mm/yyyy.
5Prestart TimeThe prestart’s start time, for example 6:30 am. Blank for a Start Shift sign-on.
6Prestart LocationThe prestart location saved at sign-on; else the prestart’s location; else where the QR code was scanned.
7Shift TypeDay, Afternoon or Night. Blank when not recorded.
8SupervisorThe supervisor on the sign-on, else the prestart’s supervisor. The same person the Supervisors filter matches.
9Sign On NameThe person’s name.
10Unique IDThe person’s ID. For a worker brought over from Core, Core’s own user ID, so Power BI keeps its join.
11Sign On RoleThe person’s role on this project (their project role, else their company role).
12SupplierThe supplier on the docket made from this sign-on; else the supplier the worker is engaged through on this project; else the supplier on their profile. Never the head contractor itself.
13Phone NumberAs stored, with its leading 0 or +.
14Beakon IDThe Beakon ID on the person’s profile, else their answer to a sign-up question named Beakon ID.
15Sign On DateThe day the person actually signed on, as dd/mm/yyyy. It can differ from Prestart Date, for example after midnight on a night shift.
16Sign On TimeThe moment the person signed on, for example Aug 3, 2026 6:30 am.
17Aboriginal or Torres Strait IslanderThe worker’s answer: Yes, No or Prefer Not to Say.
18Language GroupThe worker’s answer.
19ApprenticeYes or No.
20TraineeYes or No.
21Year Of CommencementAs stored, for example 1996.
22GenderThe worker’s answer.
23Date Of BirthAs dd/mm/yyyy.
24Post CodeAs stored, including whole suburb lines some workers typed.
25EmailThe person’s email. Blank for people with no real email address.

Dates and times are in the project’s time zone. Every cell is quoted text, Phone Number and Year Of Commencement included, as in Core. An empty value is an empty cell.

The demographic columns

Columns 17 to 24 come from the project’s sign-up questions, matched by the question’s name. Case, spaces and punctuation are ignored, and a few other names are accepted:

ColumnQuestion names it reads
Aboriginal or Torres Strait IslanderAboriginal or Torres Strait Islander, Aboriginal/Torres Strait Islander, Aboriginal and/or Torres Strait Islander, ATSI
Language GroupLanguage Group, Language
ApprenticeApprentice
TraineeTrainee
Year Of CommencementYear of Commencement
GenderGender
Date Of BirthDate of Birth, DOB, Birth Date
Post CodePost Code, Postcode, Postal Code

Beakon ID (column 14) also reads a question named Beakon ID when the person’s profile has none.

  • When a project has two questions with the same name, the first one the worker answered is used.
  • A column is blank when the project does not ask the question or the worker did not answer it. Language Group and Date Of Birth stay blank unless the project asks them.
  • A worker who is not a member of the project gets blank answers.

Sign-ons brought over from Lacroo Core

A sign-on migrated from Core prints what Core printed: the role Core recorded at sign-on, the typed name of a name-only sign-on (its Unique ID is CUSTOM_SIGN_ON_<name>, as in Core), Core’s prestart time, and Core’s user ID for the worker.

Differences from Lacroo Core

  • A supervisor’s file holds only the chosen project. Core’s supervisor download mixed in every project they had ever run.
  • From and To are the project’s calendar days, so the same file comes out on any computer.
  • The day that selects a row is the day printed in Prestart Date, so a row never shows a date outside the range.
  • Sign On Time is the real sign-on moment in the project’s time zone.
  • Phone numbers keep their leading 0 or +.
  • Commas, quotes and line breaks stay inside their cell, and accented names show correctly in Excel.
  • A cell that starts with =, +, - or @ gets a leading ', so Excel shows it as text and never runs it as a formula. Numbers, such as a phone number starting with +, are left as they are.
  • Rows come in a fixed order: shift day, then sign-on time.
  • From and To start at this month so far.
  • An unanswered Apprentice or Trainee is blank. Core printed No.
  • Date Of Birth is the stored date, never moved by a time zone.
  • Shift Type is one word: Day, Afternoon or Night.
  • Aboriginal or Torres Strait Islander reads the right answer.
  • Sign-ons Core stored with no prestart date appear on their sign-on day.
  • A sign-on with a blank saved prestart location or supervisor shows its prestart’s.
  • A Core prestart time stored as a raw timestamp prints as h:mm am.

The Sign On Workbench table has a Role column: the worker’s current role on this project (the role set for them on the project, otherwise their company-wide role). It is today’s role, not the role they held at sign-on. Export CSV carries it as role_name, right after user_name.

A field worker’s name is a link. It opens their profile on Field Users (/admin/field-users?worker=<user id>). Office staff have no profile there, so their names are plain text, and so are all names for anyone who cannot open Field Users. Someone who has since left the project is plain text too, because they are no longer on its Field Users list. The link needs Field Users › Manage (the same access the profile dialog needs), so viewers without it see plain text. Whether someone is a field user is the same rule the project Members tab uses (project_member_role).

Sign On Workbench: Export CSV

Export CSV on the Sign On Workbench downloads the sign-ons the workbench shows for its filters, up to 20,000 rows. Above that it says “Too many sign-ons for one file. Choose fewer dates.”

signed_at is the project’s time with its offset, for example 2026-04-07T08:10:00+10:00, and the file is named for the project’s today. See Dates & Times.

The workbench follows your normal sign-on access. The Workforce Log follows Export whole project for engineers, so for an engineer with it on, the Workforce Log can hold more sign-ons than the workbench shows.

See also