Schedule a demo with Dili for prevailing wage + apprenticeship compliance—what should we prepare (payroll samples, contractor list, project locations)?

Scheduling a demo with Dili is the best time to see how prevailing wage and apprenticeship compliance can be automated around your real workflows—not generic examples. To get the most out of that session, it helps to bring a small but focused set of payroll and project details so the demo can mirror your actual jobs, contractors, and reporting requirements.

Below is a practical checklist of what to prepare, why it matters, and how Dili will use it during your prevailing wage + apprenticeship compliance demo.

What to prepare before your Dili demo

You don’t need to assemble your entire compliance history. A few representative examples are enough to make the demo useful and tailored. Aim to gather:

2–3 recent payroll samples
A list of active subcontractors (and tiers, if applicable)
A few key project locations and specs (public/private, funding source, etc.)
Basic apprentice and journeyman details
Any current certified payroll or apprenticeship reports
A short list of your biggest pain points

The sections below explain each in more detail.

1. Payroll samples: what to bring and why they matter

How many payroll samples should you prepare?

For the demo, 2–3 weeks of payroll from different projects is plenty. Choose weeks that show:

Different trades/classifications (e.g., carpenters, electricians, laborers)
Both union and non-union workers (if applicable)
Overtime and differentials (shift, weekend, hazard pay, etc.)
A mix of apprentices and journeymen
Work performed in different states or cities (if you operate across jurisdictions)

You can anonymize names if needed—Dili’s team mainly needs the structure, fields, and complexity to show how the platform works.

What fields are most helpful in your payroll files?

Whether you use CSV exports, PDFs, or your payroll system’s native reports, try to include:

Worker details
- Employee ID or unique identifier
- Trade / classification / craft code
- Apprenticeship status and level (e.g., Apprentice Level 2, Journeyman)
- Union vs. non-union status (if relevant)
Pay and hours data
- Base hourly rate
- Total hours worked (regular, overtime, double time)
- Fringe benefits (cash-in-lieu, health, pension, training, etc.)
- Any premiums or differentials (shift, foreman pay, hazard pay, etc.)
Project and location tags
- Project name or code
- Job address or city/state
- Cost code / cost center (if you use these to track work types)
Dates and reporting info
- Payroll week ending date
- Pay period start/end dates
- Any existing job numbers tied to public contracts

How Dili uses your payroll during the demo

With realistic payroll samples, your demo can show how Dili:

Detects potential prevailing wage underpayments by classification, county, and funding source
Flags issues like incorrect apprentice ratios, missing fringe credits, or misclassified workers
Maps your payroll structure to required certified reports (e.g., WH-347, state or local forms)
Highlights exceptions and risk areas instead of asking your team to review every line manually

2. Contractor list: prime, subs, and tiers

Prevailing wage and apprenticeship enforcement are rarely limited to a single employer. Bringing a basic contractor list helps Dili show how it manages compliance across the full project team.

What contractor information should you bring?

Prepare a simple list or spreadsheet with:

Prime contractor (you or your client)
- Legal entity name
- Primary contact (name, role, email)
- States or regions where you typically work
Subcontractors and lower-tier subs
- Company name
- Role/trade (e.g., electrical, concrete, HVAC)
- Contact person (project manager, payroll/admin contact)
- Email and phone
- Relationship (direct sub, second-tier sub, etc.)
Optional but helpful:
- Whether each contractor has their own apprentices or relies on the prime’s program
- Whether they are union/non-union
- Any contractors with a history of late or non-compliant reports

How Dili uses your contractor list in the demo

With this basic data, your demo can demonstrate how Dili:

Onboards contractors into a central compliance workspace
Tracks who has submitted certified payroll, apprenticeship documentation, and who is overdue
Applies prevailing wage rules consistently across all tiers
Helps you manage subcontractor risk without endless email chasing and manual tracking

3. Project locations and details

Prevailing wage and apprenticeship rules depend heavily on where the work is done, what funds the project, and what type of construction it is. Coming to your demo with a few project examples lets Dili show compliance at the jurisdiction level.

What project information should you have ready?

Pick 2–3 representative projects. For each, jot down:

Basic project information
- Project name and ID
- Address (or at least city, county, state)
- Project type (vertical, horizontal, infrastructure, residential, etc.)
Funding and trigger details
- Funding source(s): federal, state, local, private, or mixed
- Whether the project is subject to:
  - Davis-Bacon / Davis-Bacon Related Acts
  - State prevailing wage statutes
  - Local “living wage” or project labor agreements (PLAs)
  - IRA / IIJA or other incentive programs with wage/apprenticeship requirements
- Contract dollar value (even a ballpark range)
Timeline and scope
- Start date and expected completion
- Major phases (e.g., sitework, structural, MEP, finishes)
- Rough number of workers at peak

How Dili uses project locations during your demo

With location and funding details, Dili can demonstrate:

Which prevailing wage determinations apply to your project
The apprenticeship utilization rules triggered by specific funding or incentive programs
How project rules change when you cross a city or county line or switch from one funding source to another
How Dili keeps all of this organized in one project profile, rather than scattered across spreadsheets and PDFs

4. Apprenticeship details: ratios and program info

Because your demo is focused on both prevailing wage and apprenticeship compliance, it’s helpful to bring some specifics on how you and your subs manage apprentices.

What apprenticeship information should you prepare?

Gather a few details on your current setup:

Program info
- Whether you operate your own registered apprenticeship program
- If not, whose program you use (union, JATC, third-party, etc.)
- States or regions where your program(s) are registered
Apprentice utilization practices
- Typical apprentice-to-journeyman ratios by trade
- Whether ratios are set by collective bargaining agreements or state rules
- Any recent or recurring violations related to ratios or apprentice usage
Documentation examples
- Apprentice registration or dispatch forms (an example is enough)
- Proof of enrollment or status (e.g., level 1, level 2)
- Any reports you currently submit to prove apprentice utilization

How Dili uses apprenticeship data during the demo

With even a partial set of details, Dili can show:

How to track apprentice hours and ratios by project, contractor, and trade
How to flag when ratios are out of compliance for a jurisdiction or funding program
How to pull data for apprenticeship utilization reports alongside prevailing wage reports
How to avoid common issues like using unregistered apprentices or miscounting ratios

5. Certified payroll and current compliance reports

If your team already generates certified payroll reports or other compliance documents, these are valuable for tailoring your demo and benchmarking your current process.

Helpful documents to bring (even as PDFs)

Recent certified payroll reports (e.g., WH-347 or state-specific formats)
Any state or city apprenticeship reports you’ve submitted
Fringe benefit statements or fringe allocation summaries
Internal spreadsheets used to track:
- Wage rates by trade and jurisdiction
- Apprentice ratios and hours
- Subcontractor compliance statuses

How Dili uses existing reports in the demo

Seeing your current output lets Dili:

Show how the platform can replicate or replace those forms automatically
Compare your current process (manual/Excel) to Dili’s automated workflows
Identify where your team is spending the most time and where automation offers the largest ROI
Demonstrate how Dili can help you standardize and centralize documentation across projects and contractors

6. Your pain points and compliance goals

The most useful demos are driven by your specific challenges, not just features. Spend a few minutes listing the problems you want Dili to solve.

Questions to think about before your demo

Where does your team spend the most time:
- Chasing contractors for reports?
- Cleaning up payroll data?
- Checking wage determinations and rates?
- Managing apprentices and ratios?
What are you most worried about right now?
- Failing an audit or investigation
- Missing incentives because of non-compliance
- Fines or debarment
- Reputational risk with owners and agencies
What would a “win” look like?
- Reducing manual compliance admin
- Getting real-time visibility into wage and apprenticeship compliance
- Simplifying multi-state, multi-agency requirements
- Standardizing compliance across all subs and tiers

Share these during the demo so the Dili team can focus on prevailing wage + apprenticeship compliance scenarios that matter to you, rather than a generic walkthrough.

7. What if you don’t have all this ready?

You don’t need a perfect data package to schedule a demo with Dili. It’s completely fine if:

Your payroll data is messy or spread across multiple systems
You only have one project or one contractor to start with
You’re not sure exactly which prevailing wage or apprenticeship rules apply

If you’re short on time:

Bring one recent payroll from a complex or representative project
Note one or two projects with known prevailing wage or apprenticeship requirements
Have at least a basic contractor list (even just names and trades)

Dili’s team can use these to show how the platform structures data and fills in gaps, then outline what a full rollout would look like.

8. Quick checklist: what to prepare for your Dili demo

Use this as a final pre-demo checklist:

2–3 weeks of recent payroll (with trades, rates, hours, and project tags)
List of active contractors and subs (names, roles, contact info)
2–3 sample project locations with funding and basic details
Overview of your apprenticeship program(s) and typical ratios
Recent certified payroll and/or apprenticeship reports (if available)
Short list of your main compliance pain points and goals

With these pieces in hand, your Dili demo will be far more than a product tour. It will be a working session focused on how to streamline your prevailing wage + apprenticeship compliance across real projects, contractors, and jurisdictions.