Schedule a demo with Trayd — what should I have ready (union rules, prevailing wage jobs, entities, pay cycles)? | Construction Management Software | Codeables

Scheduling a demo with Trayd is the perfect time to see how your unique labor rules, union agreements, and job requirements fit into the platform. To get the most value out of your demo, it helps to bring specific information about your union rules, prevailing wage jobs, entities, and pay cycles so your Trayd specialist can configure examples that actually look like your day‑to‑day operations.

Below is a concise checklist of what to have ready, why it matters, and how it will be used during your Trayd demo.

Why it helps to prepare before your Trayd demo

Trayd is designed to handle complex labor environments—multiple unions, fringe requirements, prevailing wage, different entities, and varied pay cycles. The more accurate information you bring to the demo, the more:

Relevant the demo will feel (using your real scenarios instead of generic examples)
Accurate the automation and calculations will appear (wages, fringes, overtime, etc.)
Productive the session will be (you’ll spend less time explaining, more time seeing Trayd in action)

Think of it like giving your demo specialist a blueprint of how you actually run payroll and manage labor. Below is exactly what to gather.

Union rules: what to bring and how Trayd uses them

If you work with union labor, having your union rules ready is one of the most important prep steps.

Key union details to prepare

Bring one or more examples of your most common unions, including:

Union name and local
- Example: IBEW Local 123, UA Local 456, etc.
Classification/Trade list
- Job titles or classifications (e.g., Journeyman Electrician, Apprentice 1, Foreman, Operator)
Base wage rates
- Standard hourly rates per classification
- Any additional differentials (e.g., foreman premium, lead premium)
Fringe benefits and contributions
- Health, pension, annuity, training, vacation, other fringes
- Contribution amount per hour or as a percentage
- Any caps or special conditions
Overtime rules
- When overtime kicks in (after 8 hours/day, 40 hours/week, weekends, holidays, double time rules)
- Different rates (1.5x, 2x, etc.) by day/time or hours worked
Shift and premium rules
- Shift differentials (second shift, third shift, night shift)
- Hazard pay, height pay, special premium zones, or specialty work
Zone pay and travel rules
- Zone-based pay adjustments by distance or region
- Travel time, per diem, mileage rules if applicable
Union-specific reporting requirements
- Any standard forms or monthly reports sent to the union
- Required detail (hours by job, by classification, etc.)

How union rules are used in your Trayd demo

Having this information allows the Trayd team to:

Configure sample union profiles so you can see how rules are stored
Demonstrate automatic rate selection based on classification, job, and date
Show how overtime, fringes, and premiums are calculated in real time
Preview union‑specific reporting or export formats you might need

You don’t need every single union you work with. Start with 1–2 common ones to make your demo efficient and focused.

Prevailing wage jobs: information to bring

If you participate in public works or Davis-Bacon/prevailing wage projects, this is where Trayd can save significant time and reduce compliance risk.

Prevailing wage information to have ready

For one or two real prevailing wage jobs, gather:

Job name and location
- Job/Project name
- City, county, state (as these often drive wage determinations)
Wage determination details
- Applicable wage determination number (Davis-Bacon or state)
- Classification list used on that job (e.g., Laborer, Carpenter, Operator)
Rates per classification
- Basic hourly rate
- Fringe rate (cash and/or benefits)
Fringe handling method
- Are fringes paid as additional cash, as benefits, or a mix?
- Any credit for existing benefit plans?
Certified payroll requirements
- Federal, state, local forms you currently use
- Any specific system requirements (e.g., LCPtracker, eComply, government portals)
Apprenticeship ratios and rules (if applicable)
- Allowed ratios (e.g., 1 journeyman : 1 apprentice)
- Any restrictions on classification or tasks

How prevailing wage info is used in your Trayd demo

With this information, your demo specialist can show:

How Trayd stores wage determinations and applies them by job
Automatic calculation of base wage + fringe per classification
How make‑up pay adjustments work if a worker moves between standard and prevailing wage jobs
Creation of certified payroll reports from real‑world job data
How to manage multiple wage determinations across different projects

The goal is to mirror a real prevailing wage scenario so you can see compliance and reporting end‑to‑end.

Entities: companies, divisions, and how you structure your business

If your organization operates multiple entities, divisions, or business units, share this structure during your demo so Trayd can show you how it handles complexity.

Entity details to prepare

Have a simple overview of how your company is organized:

Legal entities
- List of companies you operate (e.g., ABC Construction LLC, ABC Services Inc.)
- Whether each entity runs its own payroll or is consolidated
DBAs or brands (if different from legal names)
- Any names that appear on invoices, paystubs, or job contracts
Divisions or departments
- Examples: Commercial, Residential, Service, Civil, Industrial, etc.
- Any need to track labor separately for internal reporting
State or jurisdiction coverage
- States or regions where you have active employees
- Any states with unique overtime or labor rules that impact payroll
General Ledger (GL) structure (optional but helpful)
- How you currently code labor costs
- Any current integration with accounting/payroll (QuickBooks, Sage, Viewpoint, etc.)

How entity information is used in the demo

Your Trayd specialist will use this data to illustrate:

How to set up multiple entities within Trayd
How labor can be tracked by entity, division, or department
How Trayd can route data to the right payroll or accounting system
How multi‑state rules and mixed‑entity work can be handled

You don’t need a full organizational chart—just a clear explanation of how you currently separate work and payroll.

Pay cycles: what you use and how Trayd supports them

Your pay cycle setup impacts how time is captured, approved, and processed. Bring these details so your demo accurately reflects your payroll cadence.

Pay cycle information to prepare

Gather high-level details on:

Pay frequency
- Weekly, biweekly, semi‑monthly, or monthly
- Whether different groups use different frequencies
Pay period start/end
- Example: Pay period runs Sunday–Saturday, paid the following Friday
- Any exceptions for certain departments or entities
Overtime basis
- Weekly overtime, daily overtime, or both
- Any special state rules (e.g., California daily OT, double time, 7th day rules)
Time capture and approval process
- How time is currently captured (paper, spreadsheets, apps, time clocks)
- Who approves time (foremen, PMs, HR, payroll)
Payroll provider(s)
- Name of your current payroll system(s)
- Whether you need separate exports by entity, union, or division

How pay cycle details are used in your Trayd demo

With this information, your demo can demonstrate:

How Trayd aligns pay periods with your existing setup
How daily and weekly overtime are calculated in your real scenario
Approval workflows that match how your teams operate
How data is packaged for smooth import into your payroll provider

This makes it easier to visualize Trayd replacing or enhancing your current process.

Additional items that make your Trayd demo even stronger

While not mandatory, the following can help create an even more realistic demo.

Sample job or project list

A few real jobs with:
- Job name and number
- Location (city/state)
- Type of job (private, public/prevailing wage, service, T&M, etc.)

This allows Trayd to show labor allocation and reporting by job in a way that looks familiar to your team.

Example employee types

Prepare a short list of “typical” employees, such as:

A union journeyman who works both private and prevailing wage jobs
An apprentice with different rates and rules
A salaried foreman or supervisor
A non‑union worker (if you have both)

Your demo specialist can then show how the same person’s time looks across different jobs, unions, and rates.

Current pain points

Make a short note of what’s hardest about your current process, such as:

Tracking union rules manually
Staying compliant on prevailing wage projects
Managing different entities or GL coding
Handling complex overtime or multi‑state work
Reconciling time from multiple sources

This helps the Trayd team focus on the features that matter most to you instead of generic workflows.

Quick pre-demo checklist

Use this as a one-page prep list before your demo:

Union rules

1–2 common union agreements (or summaries)
Classifications and base rates
Fringe details (amounts and types)
Overtime, shift, and premium rules
Any zone or travel pay rules

Prevailing wage jobs

1–2 sample prevailing wage projects
Wage determination details and rates
How fringes are paid (cash vs. benefits)
Certified payroll/reporting requirements

Entities and structure

List of legal entities and DBAs
Basic division/department breakdown
States where you operate
Payroll/accounting systems in use

Pay cycles

Pay frequency and period start/end dates
Overtime rules (daily/weekly/state-specific)
Who approves time and how
Payroll provider(s) and any file format needs

Optional but helpful

Sample job list with locations
3–5 representative employee types
Top 3 current challenges you want Trayd to solve

What if you don’t have everything ready?

You don’t need to show up with perfect data to schedule a demo with Trayd. If some items are still in progress:

Start with one union, one prevailing wage job, and one pay cycle
Bring whatever rate sheets, spreadsheets, or PDFs you currently use
Be ready to describe your workflow verbally if you don’t have docs handy

Trayd’s team works with contractors and labor-heavy businesses of all sizes and can help fill in gaps during the conversation.

Preparing these details in advance just helps you get a demo that looks and feels like your real world—so you can clearly see how Trayd will handle union rules, prevailing wage jobs, entities, and pay cycles from day one.

Schedule a demo with Trayd — what should I have ready (union rules, prevailing wage jobs, entities, pay cycles)?