Customer-supplied materials need their own workflow
Jobs where the customer supplies some or all materials often look simple at quote stage. In practice, they create a different operating model.
The confusion usually shows up later:
- the quote says "labour only" but the team still ends up supplying bits and pieces
- site staff arrive and key materials are missing
- nobody knows who approved substitutions
- purchased extras are not separated properly from customer-supplied items
- invoicing turns into an argument about what was included
- job costing looks better or worse than reality because material assumptions were never recorded clearly
The underlying problem is not just materials. It is that the business is treating an exception workflow as if it were a standard supplied-materials job.
If the customer is providing materials, the job needs explicit rules around scope, responsibility, site readiness, stock handling and cost reporting. Without that, the quote, the schedule, the field team and the accounts team will all make different assumptions.
Why these jobs break normal workflows
A standard workflow usually assumes the business controls procurement. That means the business can decide:
- what is being ordered
- how much is being ordered
- when it will arrive
- what standard or specification is acceptable
- who carries the cost if something is wrong
Customer-supplied material jobs break that control model.
Now the business may be responsible for labour, installation quality and sometimes supplementary items, while the customer controls part of the inputs. That creates shared responsibility, which is exactly where many systems become unclear.
A few common examples:
- A customer supplies all fixtures, but the installer still needs consumables, brackets or fasteners.
- A builder supplies major materials, but expects the subcontractor to identify shortages on site.
- A client supplies specialised equipment, but it arrives damaged or incomplete.
- A job is quoted as labour only, but the team buys urgent replacement parts to keep the work moving.
None of those situations are unusual. The problem is when the workflow has no structured way to record them.
Start by separating job types properly
The first fix is simple but important: do not treat all jobs as one class of work.
At a minimum, there should be a clear distinction between:
- business-supplied jobs
- customer-supplied jobs
- mixed-supply jobs
That distinction should be visible from the quote stage onwards, not buried in notes.
A labour-only or customer-supplied job has different operational risks from a fully supplied job. A mixed-supply job is different again, because both parties are contributing materials and the boundary needs to be explicit.
If these job types are not separated early, several problems follow:
- procurement teams may order materials that were never meant to be supplied
- field teams may assume site materials are complete when they are not
- invoicing teams may not understand what can be charged
- reporting may merge labour-only and supplied-material jobs into one margin picture, which distorts profitability
This is not just an admin label. It changes how the workflow should behave.
Scope clarity matters more than the quote total
When customers supply materials, the most important part of the quote is not only the price. It is the assumptions.
The quote should make clear:
- which materials are supplied by the customer
- which materials are supplied by your business
- whether quantities have been verified or are based on customer information
- who is responsible for shortages
- who is responsible for defective or non-compliant materials
- what happens if substitutions are required
- whether additional site visits, delays or waiting time are chargeable
- whether disposal, unloading, handling or storage is included
If this is vague, the dispute does not wait until the end. It starts the moment something goes wrong on site.
For example, if a customer says they will supply all cable, that can mean very different things operationally. Does it include excess allowance? Delivery to site? Correct specification? Segregation by area? Protection from weather? If none of that is clarified, the site team inherits the ambiguity.
A quote that says "labour only" without supporting assumptions is often not enough.
The key responsibility rules to define up front
Customer-supplied material jobs need explicit responsibility boundaries. Otherwise staff end up making judgement calls in the middle of a live job.
The workflow should define who is responsible for each of these:
Quantities
Has the business verified quantities, or is it working from customer-provided counts?
That matters because "install 40 supplied units" is different from "install supplied units as available". If the quantity is wrong, the job plan, labour allocation and completion expectations change.
Quality and specification
If supplied materials are the wrong size, wrong rating, incomplete or unsuitable, who makes the decision on whether work proceeds?
The site team should not be left informally deciding whether to install something questionable just to avoid delay.
Delivery timing
Who confirms materials are on site before labour is dispatched?
This should not rely on someone assuming the customer has arranged it. Site readiness needs a clear owner.
Shortages and damage
If items are missing, broken or arrive late, what happens next?
Possible pathways might include:
- job proceeds with partial scope
- job is paused pending customer action
- your business supplies the missing items as a variation
- a return visit is raised and approved
The important part is that the response is defined, not improvised.
Substitutions
If a substitute material is required, who approves it and how is that approval recorded?
This protects both delivery quality and invoicing.
Build the workflow around visibility, not memory
The visible failure on these jobs is often "the team turned up and the materials were not right". The real failure is usually that the system had no reliable checkpoint before dispatch.
A better workflow makes the exception visible before it affects labour, scheduling and costing.
A practical structure might look like this.
1. Quote classification
At quote stage, flag the job as:
- customer-supplied
- mixed-supply
- labour only
This should trigger the right template, assumptions and approval requirements.
2. Material responsibility capture
Record, in a structured way:
- customer-supplied items
- business-supplied items
- items not yet confirmed
- whether quantities are verified or assumed
Do not rely on free-text notes alone if the information needs to drive scheduling, procurement or invoicing.
3. Pre-start confirmation
Before scheduling labour, confirm:
- required customer-supplied materials are on site or booked for delivery
- any required documentation, specifications or product details are available
- responsibility for handling equipment, unloading or storage is understood
If that confirmation has not happened, the job should not appear "ready" in the same way as a standard job.
4. Site exception handling
If the team identifies shortages, damage or unsuitable materials on site, the workflow should tell them what to do:
- record the issue
- attach photos if relevant
- nominate whether work can proceed partially
- trigger a decision from the office, supervisor or customer
- log any additional business-supplied items separately
This avoids ad hoc phone calls becoming the only record.
5. Cost and invoice separation
Any materials purchased by the business for a customer-supplied job should be recorded distinctly from normal project supply.
That is important for two reasons:
- the customer may need to approve those additions
- internal reporting needs to distinguish planned labour-only work from unplanned supply costs
The data fields that keep these jobs under control
If customer-supplied materials are handled through vague notes, visibility disappears quickly. A few structured fields usually matter more than a long job description.
Useful fields include:
- supply model: business-supplied, customer-supplied, mixed-supply
- customer-supplied material scope
- business-supplied material scope
- quantity status: verified, customer-advised, estimated, unknown
- site readiness status
- material delivery status
- responsibility for shortages
- responsibility for defective materials
- substitution approval required: yes or no
- approved by
- additional purchased materials on behalf of customer
- chargeable delay or return visit flag
- variation required: yes or no
- invoice treatment for supplementary items
Not every business needs all of these as separate fields, but the workflow needs the information somewhere structured enough to drive action.
If a scheduler, supervisor and accounts person all need the same answer, it should not live only in somebody's inbox or memory.
Statuses should reflect operational reality
One reason these jobs create mess is that they move through normal job statuses even when they are not genuinely ready.
A job should not go from "quoted" straight to "scheduled" if customer-supplied materials are still unconfirmed.
Useful statuses might include:
- Quoted
- Awaiting customer material confirmation
- Ready to schedule
- Scheduled
- On site - material issue
- Awaiting customer resolution
- Proceeding with partial scope
- Variation awaiting approval
- Completed
- Completed pending additional charges
- Ready to invoice
The exact names matter less than the logic behind them.
The purpose of the statuses is to make the exception visible. A manager should be able to see, without digging through notes, which jobs are delayed because of supplied-material issues, which ones are partially complete, and which ones have extra costs waiting for approval.
That visibility is what protects both operations and profitability.
Labour-only and mixed-supply jobs should not be reported the same way
If reporting treats all jobs as if the business supplied materials normally, margin visibility becomes unreliable.
For example:
- a labour-only job may look highly profitable because there is no material cost, even though the price was set accordingly
- a mixed-supply job may look poor if emergency purchased items are buried in job costs without context
- a return visit caused by missing customer materials may be absorbed into labour cost with no visibility of why it happened
The answer is not to exclude these jobs from reporting. It is to classify them properly.
At a minimum, reporting should let you distinguish:
- labour-only revenue
- business-supplied material revenue
- customer-supplied jobs with supplementary purchased items
- delay costs or return visits linked to supplied-material issues
- approved versus unapproved variations
That makes job costing more honest.
It also helps management answer better questions, such as:
- Are these jobs actually profitable at the pricing model being used?
- How often are supplied-material shortages causing return visits?
- Which customers or job types create repeated ambiguity?
- Are office and field teams spending too much time managing exceptions that were not allowed for in the quote?
Without that separation, the business can end up making pricing or staffing decisions based on distorted margin data.
Handle shortages, substitutions and damage as defined exception paths
The most expensive part of these jobs is often not the missing item itself. It is the disruption.
When there is a shortage, damaged item or unsuitable supplied material, the workflow should push the job into a defined exception path rather than letting staff work it out informally each time.
A practical exception structure might include three possible outcomes.
Proceed with available scope
If the team can complete a meaningful portion of the work safely and sensibly, the system should allow partial completion with clear records of what remains.
That means:
- completed scope is recorded
- incomplete scope is identified
- return visit need is visible
- invoice rules are clear
Pause pending customer action
If the missing or unsuitable materials prevent sensible progress, the job should move into a paused status with clear ownership.
That should answer:
- who has been notified
- what is required to restart
- whether rescheduling is needed
- whether additional charges may apply
Business supplies missing items as a variation
Sometimes the fastest option is for your business to supply the missing materials and keep the job moving.
If that happens, it should not be hidden inside normal job completion. It should create:
- a record of what was supplied
- a customer approval if required
- a clear cost entry
- a corresponding invoice treatment
This is where many margin errors happen. Staff do the practical thing on site, but the system never catches up.
Prevent invoicing disputes by documenting assumptions early
Most invoicing disputes on customer-supplied jobs are not invoicing problems. They are quoting and workflow problems that only surface at invoice stage.
If the original assumptions are vague, accounts staff are left trying to justify:
- extra materials supplied by the business
- additional attendance
- waiting time
- rework caused by unsuitable supplied materials
- partial completion or staged invoicing
Those are hard conversations if the system does not show what was agreed.
A better process documents the assumptions at the start and carries them through the job. The invoice then reflects a visible operational history, not a reconstruction after the fact.
In practice, that means the job record should show:
- what the customer agreed to supply
- what condition or completeness was assumed
- what changed
- who approved any change
- what extra labour or material was created as a result
That does not eliminate every disagreement, but it removes a lot of ambiguity.
A simple example of what good looks like
Consider a mixed-supply installation job.
The customer is supplying the main fixtures. Your business is supplying mounting hardware, cabling accessories and labour.
A workable process might look like this:
- The quote is marked as mixed-supply.
- The fixture list is recorded as customer-supplied and flagged as customer-advised quantities pending confirmation.
- The quote notes that incorrect quantities, damaged fixtures or missing components may cause delays, variations or return visits.
- Before scheduling, the office confirms the fixtures have been delivered to site.
- The job moves to Ready to schedule only once that confirmation is complete.
- On site, the installer finds that six fixtures are missing mounting components.
- The installer records the issue and flags whether work can proceed partially.
- The supervisor approves a partial completion and raises a variation for the missing components if your business will supply them.
- The job costing record separates original labour, additional purchased items and return-visit labour if needed.
- The invoice reflects the agreed scope plus approved additions.
That is not a complicated system. It is just explicit.
The benefit is that nobody has to guess whether the missing components were part of the original price, whether the team should continue, or why the margin changed.
Keep the workflow practical
Not every business needs a heavily customised platform to manage this properly. Often the real improvement comes from agreeing on:
- the job classifications
- the required data fields
- the pre-start checks
- the status logic
- the exception paths
- the approval rules
Once those are clear, software can support the process. Without that clarity, even good software will still produce confusion because the workflow itself is unresolved.
A lot of operational pain comes from trying to force exceptions into a standard process. Customer-supplied materials are one of those exceptions that deserve their own rules.
If these jobs are common in your business, it is worth mapping the workflow from quote to scheduling to site completion to invoicing. That usually makes it easier to see where responsibility becomes unclear, where costs disappear into the wrong category, and where the job should pause instead of quietly drifting into dispute. If that process spans multiple teams or systems, 5M Consulting can help design a workflow that keeps the exception visible without making the operation harder to run.