DAS 140 vs. DAS 142: track notice, dispatch and proof separately

The Buildalytic workflow

Buildalytic offers apprenticeship compliance workflows. Its workflow offering organizes project notices, dispatch requests, responses and missing-evidence follow-up without merging the distinct form histories. The steps, contacts, approvals and record destinations are agreed with your team during setup.

The California DAS public-works FAQ explains the distinction, recipients, timing and exceptions. Use that official guidance to determine the obligations for the project. The register below organizes evidence after the responsible reviewer has established which requirements apply.

Sources: workflow offering; discuss the setup

Begin with the project and craft

Create a project record with the contract or subcontract reference, location, relevant crafts, expected work dates and the person responsible for apprenticeship compliance. A generic company-level folder is not enough to show which notice belongs to which job.

Identify the applicable committees using the official program resources. Recipient selection depends on facts such as the craft, project location and contractor’s training status. Do not assume that the committee used on a previous project is the only recipient for the next one.

Record who reviewed the recipient list and when. Save the relevant source or lookup result. A mailing list can become stale, and a later reviewer should be able to understand why the team used particular contacts at the time.

Keep the two purposes visible

The official FAQ states that contract-award information is due within ten days of the prime or subcontract date, and no later than the first day workers are employed on the project. It also explicitly says that this notice is not automatically a dispatch request. Verify the current guidance and applicability before setting deadlines.

Use separate register rows for award notification and apprentice dispatch. A form upload attached to the project should not complete both rows. Each has its own recipient, timing, evidence and status.

The table is an operating model, not a statement that these five rows exhaust every apprenticeship obligation.

Design status names that describe evidence

Use “draft,” “reviewed,” “sent,” “delivery evidence saved,” “response received” and “follow-up required.” Avoid one undifferentiated “apprenticeship complete” status.

A sent email can establish that a message was sent through your process. It does not prove that the request was sufficient, reached every required recipient or resulted in dispatch. A response can acknowledge receipt without confirming availability. Preserve the actual wording and let the responsible reviewer determine its significance.

Likewise, “no response” should not be converted into “exempt.” An exemption is a separate determination with its own source and review. A workflow that silently makes that conversion creates false certainty at the exact point where a person needs to investigate.

A fictional project register

Assume a fictional electrical subcontract on Project H-24. The compliance reviewer identifies the applicable notification and dispatch requirements. The coordinator prepares award information and saves the reviewed recipient list with the project.

The award record gets its own ID, N-004. The dispatch request gets R-007. Each points to its version, recipients and transmission evidence. When one recipient responds that it needs more job information, R-007 remains open for follow-up. The award notification does not need to be recreated merely because the dispatch conversation continues.

Later, the field team confirms the actual start and the worker’s recorded hours. Those facts are linked to the project’s apprenticeship review. They are not inferred from the fact that R-007 was sent. A new reviewer can follow the chain from the project to each request, response and field record.

Build a calendar around the actual start

A planned start can move. Keep the original plan, revised dates and the event that triggered the change. Ask the responsible reviewer whether the change affects any notification or request action. Do not assume that moving a calendar appointment updates an already transmitted document.

Set internal review targets early enough to collect missing craft, contact or project information. Label those dates as company operating targets. They help the team prepare without being confused with official deadlines.

Make the next action specific. “Check apprenticeship” is too broad. “Confirm the revised work date with the compliance reviewer and determine whether request R-007 needs follow-up” gives one person a task that can be completed and verified.

Preserve delivery and response evidence

Store the exact version transmitted, recipient details, transmission date and available delivery evidence. Keep incoming responses attached to the same request ID. If a phone call resolves a question, record the date, participants and factual outcome, then seek written confirmation when the process calls for it.

Do not replace the recipient’s response with a summary that overstates it. “Can supply apprentices subject to confirmation” should not become “crew confirmed.” Keep the source message available so the reviewer can check the interpretation.

Limit access to personal information. A general project status view can show the request owner and next action without displaying apprentice identity documents. The restricted compliance record can hold the evidence needed by authorized staff.

Connect forms to hours without inventing a compliance verdict

A document register and an hours review complement each other. One shows communications and evidence. The other supports the applicable ratio and payroll review. A completed form does not automatically demonstrate that every later work-period requirement was met.

Keep projected and actual hours separate. Projected hours explain a planning assumption; actual approved records explain what happened. If the scope or crew changes, identify who reviews the effect rather than letting the old projection persist indefinitely.

For exceptions, record the question and source. Was a recipient unresolved? Was a response incomplete? Is the actual work record missing? These conditions require different actions and should not be collapsed into an alarming but unhelpful red badge.

Review recurring problems at the process level

At the weekly compliance meeting, review open requests by age and the next required decision. Repeated missing project details suggest a preparation problem. Repeated unresolved recipients suggest that the official lookup and reviewer handoff need improvement.

Do not measure success only by forms sent. Useful measures include requests with complete delivery evidence, open response questions and time from an identified issue to an authorized decision. Those are internal workflow measures, not claims that a project is legally compliant.

Keep a short correction record when a form version changes. Record what changed, why, who approved it and which recipients received the revision. That history is more valuable than a folder containing several undated copies of the same form.

How Buildalytic handles this workflow

Buildalytic’s apprenticeship workflow connects the project’s notice, dispatch, response and evidence tasks. Bring one fictional project with a moved start date and an incomplete response to the demo. Ask to see how the system keeps the two forms and their statuses distinct.

The useful result is a reviewer who can find the missing decision quickly. Generating a form is only one step; following the request through a real change is the better acceptance test.

To put this Buildalytic workflow to work, discuss the setup with your project’s source records, responsible people and expected outcome. Use the checks in this guide to verify the agreed process before rollout.

Sources: workflow offering; discuss the setup