Trades · Software category
Subcontractor management software,
and the constraint most of it ignores.
The category covers six stages, scoping a package, levelling quotes, committing to a trade, holding compliance, coordinating on site and paying. What decides whether a product works is not how good its subcontractor portal is. It is what happens for the trades who will never open it, which is most of them. This page covers the stages, the adoption constraint, what to look for, the questions worth asking, the honest limits, and how VIABUILD approaches it.
01 / The direct answer
What subcontractor management software does
Subcontractor management software handles the relationship between a builder and the trades who do the work, from scoping a package through quoting, engagement, compliance and site coordination to payment. On a residential job that relationship is most of the business, because almost all of the work and almost all of the cost sits with subcontractors rather than with your own labour.
Products in the category cover different subsets of those stages and describe themselves similarly. The stage most often missing is the commitment, the purchase order or subcontract that moves committed cost the day a trade is engaged. A product that coordinates trades beautifully and has no view on committed cost will leave your job cost position behind by the length of every trade’s billing cycle, which is exactly the window in which a decision would have helped.
The discipline itself, independent of software, is in subcontractor management and trade packages and scoping. The induction and site access part of compliance has its own buying guide on contractor induction software. This page is about the software category as a whole.
02 / The lifecycle
Six stages of a trade relationship, and where each one leaks
Almost every builder is strong at some of these and improvising at others. Working out which two are costing you most is a better basis for buying than comparing feature lists.
Scoping the package
Deciding exactly what the carpenter is responsible for, and what he is not. Most disputes with trades are not about price, they are about a boundary nobody wrote down. A package with a clear scope, an inclusions list and a set of exclusions is the cheapest risk control available to a builder.
Requesting and levelling quotes
Three quotes against the same scope, compared line for line rather than on the bottom figure. Levelling is the step most builders do in their head, and it is where the apparently cheapest quote turns out to have excluded the thing the other two included.
Engaging and committing
The purchase order or subcontract that turns an accepted quote into a commitment, coded to the job and the cost line, with the scope attached. This is the moment committed cost should move, weeks before an invoice exists, and it is the single most valuable behaviour in the category.
Compliance before anyone starts
Licence, insurances, safe work method statements and an induction, current on the day they walk on. The failure is almost never that a builder does not care. It is that a certificate of currency expired in March and nobody noticed until an incident made it matter.
Coordinating on site
Dates, changes, confirmations, questions and the answer to what is happening on Thursday. This is the highest-volume interaction and the one most often conducted across four personal phones with no record attached to the job.
Paying, and knowing what is left
The invoice against the order, what remains on the package, retention if it applies, and payment terms. A trade who is paid predictably prioritises your job over a builder who is not, which is a commercial advantage with no software feature attached.
03 / The constraint
Your subcontractor is not going to use your software
This is the fact the category is built to avoid, and it decides more about whether a product works than any feature in it.
A bricklayer works for six builders. If every one of them asks him to install an app, create an account, remember a password and check a portal, he will use the one belonging to the builder who gives him the most work, and ignore the rest. That is not resistance to technology. It is a rational allocation of unpaid administrative effort by another business that has its own quoting, invoicing and scheduling to do. The same trade who will not open your portal answers a text message within the hour, because a text costs him nothing and arrives where he already is.
The consequence is that most subcontractor portals succeed with the two or three trades who do most of their work for you and fail silently with everyone else. The failure is silent because the builder still gets the work done, by text and by phone, and the record simply does not exist. You have then paid for a coordination system and are still coordinating in your pocket.
The question worth asking of any product in this category is therefore not how good the trade experience is. It is what happens for the trade who never signs in. If the answer is that they receive their dates as a message and can confirm without an account, and that their reply is captured against the job, the product has been designed for reality. If the answer is a description of how easy the portal is to use, the product has been designed for a demonstration.
04 / Before you buy
Six things to look for
The first two follow directly from the adoption constraint. The fifth is the one that decides whether your cost position is current or historical.
Nothing that requires a trade to log in
The strongest predictor of whether this category works for you. Ask what a subcontractor does with no app, no account and no password, and what happens on a phone with poor reception. Anything requiring adoption by another business will be adopted by the two trades who like you and nobody else.
Replies that land on the job, not in a phone
Text messages are how trades actually answer, so the question is whether a reply is captured against the task and the job or lost in a personal thread. This is the difference between coordination that survives a supervisor leaving and coordination that lives in someone’s pocket.
Compliance with expiry dates that chase themselves
Licences, public liability, workers compensation or personal accident cover for sole traders, and SWMS. The useful behaviour is not storage, it is the reminder before expiry and the visibility of who is currently non-compliant across every active job.
Scope attached to the commitment
The purchase order or subcontract should carry the scope it was priced against, so the argument three months later is settled by the document rather than by memory. Ask whether the accepted quote and its scope travel with the order or live in a different system.
Committed cost the day the order is raised
Engaging a trade is a financial event. If the system only records the money when the invoice arrives, your cost position is behind by the length of that trade’s billing cycle, which on a nine month build is where all the useful decisions were.
One record of the trade across every job
Their details, insurances, rates, the packages they have run for you, what they invoiced and how they performed, in one place rather than per job. That accumulated record is what lets you price the next job from experience rather than from the last quote you happened to receive.
05 / The conversation
Questions worth asking a provider
Six questions with specific answers. The first is about the other business in the relationship, which is the perspective most software evaluations leave out entirely.
- 01
What does my bricklayer receive, and what does he have to install
Ask to see the trade’s side on a phone. Then ask how many of the vendor’s existing customers have their trades using it, and what proportion of trades adopt it. A product that answers this precisely has measured it. A product that answers with enthusiasm has not.
- 02
Show me a text reply land on the task
Live, with a real phone. Then ask what happens when the reply is ambiguous, or when the same trade has three open conversations. The handling of the ambiguous case is where products differ, and a system that guesses silently is worse than one that asks.
- 03
How do I know today who is not compliant
Ask for one screen showing every trade with an expired or expiring insurance, licence or SWMS, across all active jobs. If that answer can only be assembled by opening each subcontractor record, it will be assembled after an incident rather than before one.
- 04
Walk a package from scope to payment
Scope, quote request, comparison, acceptance, purchase order, committed cost, invoice, remaining balance. Ask to see it end to end with the scope document attached throughout. Every point where the demonstrator switches to a spreadsheet or an email client is a seam you will maintain.
- 05
What happens when the dates move
A date change is the most common event in the relationship. Ask what a trade is told, how they confirm, what you see if they do not, and whether the schedule and the notification are the same system or two products that were introduced to each other.
- 06
What is the total cost, and are trades charged as users
Per-user pricing that counts subcontractors changes the economics of this category completely, because a residential builder deals with dozens of trades and only employs a handful of people. Ask specifically, and ask what happens to the record of a trade you stop using.
06 / Honest limits
What subcontractor management software cannot do
Three limits, and the last one is the one that actually determines whether your jobs run well.
It cannot make a trade adopt it. Evaluate on what happens when they do not, because that is the normal case rather than the exception, and a product whose value depends on subcontractor adoption is asking you to solve a problem it has handed back to you.
It cannot fix a badly scoped package. A system that sends the wrong scope to three trades does so very efficiently, and you receive three quotes for work you did not intend to buy. Scoping is knowledge about building and about this job, and the reference for doing it well is trade packages and scoping.
And it cannot manage the relationship. The reason a good tiler prioritises one builder over another is that they get paid on time, the site is ready when they arrive, and decisions get made rather than deferred. Software genuinely helps with all three, by shortening the gap between an invoice arriving and being approved, by keeping the programme honest so a trade is not called in a week early, and by making a question answerable quickly. That is real value, and it is not a substitute for being the builder trades want to work for. On the commercial side, the same point holds about payment terms, which are a relationship decision rather than a setting.
07 / How VIABUILD does it
Designed for the trade who will never log in
VIABUILD starts from the constraint rather than working around it. A subcontractor is sent their dates and confirms with one tap, with no app, no account and no password. When they reply by text the message lands against the task on the job rather than in somebody’s personal phone, threaded through your own number, so the coordination record survives a supervisor changing.
Where a reply is unambiguous it is filed for free by rule. Where several conversations are open and it is genuinely unclear which task a message belongs to, Oryn™ ranks the most likely task from the actual open set and only files it when confident, tagged as filed by Oryn and always movable. It never invents a task, and an uncertain case is shown to you rather than guessed into your records.
On the money side, purchase orders are generated from the locked budget grouped by cost code, so engaging a trade moves committed cost on the day the order is raised rather than when the invoice turns up, and each supplier invoice corrects the order’s remaining balance from the source data rather than a running total. Inductions, SWMS, toolbox talks and QR site sign-in run in site safety.
What we do not claim. There is no subcontractor portal, because we do not believe trades will use one, and that is a deliberate design position rather than a missing feature. Oryn does not negotiate, does not level quotes for you, and never commits money on its own. Full detail is on subcontractor management.
08 / FAQ
Common questions.
Subcontractor management software handles the whole relationship between a builder and the trades who do the work. That covers six stages. Scoping the trade package so responsibility is defined before anyone prices it. Requesting quotes and levelling them against the same scope. Engaging the trade through a purchase order or subcontract that records the commitment against the job and its cost code. Verifying compliance, licence, insurances, safe work method statements and induction, before they start. Coordinating on site, which is dates, changes, confirmations and questions. And paying, tracking the invoice against the order and what remains on the package. Products in this category cover different subsets of those six, and the one they most often omit is the commitment, which is the one that matters most to your cost position.
Because a subcontractor is not your employee, and adopting your software is unpaid work for another business. A bricklayer works for six builders. If each of them asks him to install an app, create an account and check a portal, he will use the one belonging to the builder who gives him the most work and ignore the rest, and he will do that reasonably. This is the single most important constraint in the category and most products are designed as though it does not exist. The arrangements that survive contact with reality are the ones that meet trades where they already are, which in Australian residential building means a text message and a phone call. The useful question when evaluating a product is not how good the trade portal is. It is what happens for the trade who never opens it, because that is most of them.
Four things at minimum, and the detail varies by state and by trade. A current licence for the licensed trades, which is checkable against the relevant state authority. Insurance, typically public liability, and workers compensation where they employ or an equivalent personal accident cover where they are a sole trader. Safe work method statements for high risk construction work, prepared by the trade for the work they are doing on your site rather than a generic document. And a site induction before they start, with a record that it happened. The practical failure is almost never refusal, it is expiry. A certificate of currency lapses quietly and nobody notices until an incident makes it matter, which is why the valuable software behaviour here is the reminder rather than the storage. The safety context is in the WHS reference and the induction workflow has its own page.
Procurement is the money and the commitment. Subcontractor management is the relationship around it. In practice they overlap almost entirely for a residential builder, because the trade packages are the procurement, and separating them is usually an artefact of how products are sold rather than how a builder works. The distinction that does matter is which end a product came from. A procurement-lineage product will handle scoping, quote levelling, purchase orders and committed cost well and be thin on site communication and compliance. A field-lineage product will handle communication, inductions and safety well and have no view on committed cost. Neither is wrong. What is expensive is buying one and assuming it covers the other, then discovering in month three that your committed cost figure does not include the trades you engaged by text.
Against the same scope, line by line, with the exclusions read first. The bottom figure is the least informative number on a trade quote, because the cheapest price is very often the one that excluded something the others included, and that gap becomes a variation or an argument once the work is under way. Levelling means normalising the quotes so you are comparing like with like, adding back what one trade excluded, checking the quantities they priced against your own, and noting who has and has not allowed for access, height, waste, or working around another trade. It also means treating an unusually low quote as a question rather than a win, since a trade who has misread the scope will discover it on site and the conversation that follows is worse than paying the second cheapest price. The mechanics are in the quote levelling and trade package references.
Three limits. It cannot make a trade adopt it, as above, so evaluate on what works when they do not. It cannot fix a badly scoped package, and a system that sends the wrong scope to three trades very efficiently produces three quotes for the wrong work. Scoping is knowledge about building and about this specific job, and no product supplies it. And it cannot manage the relationship. The reason a good bricklayer prioritises one builder over another is that they get paid on time, the site is ready when they arrive, and the decisions get made. Software helps with all three by removing the delays that cause them, which is genuinely valuable, and it is not a substitute for being a builder people want to work for.
The design starts from the constraint that trades will not adopt your software. In VIABUILD a subcontractor gets sent their dates and confirms with one tap, no app and no login, and when they reply by text the message lands against the task on the job rather than in somebody’s personal phone, threaded through your own number. Where a reply is unambiguous it is filed automatically. Where several conversations are open and it is genuinely unclear, Oryn ranks the most likely task from the actual open set and only files it when confident, tagged as filed by Oryn and always movable, which means an uncertain case is visible rather than guessed into your records. On the money side, purchase orders are generated from the locked budget grouped by cost code, so engaging a trade moves committed cost the day the order is raised, and each supplier invoice corrects the order’s remaining balance from the source data. Site safety, inductions and SWMS run in the safety module. What we do not claim is a subcontractor portal, because we do not think trades will use one.
09 / Keep reading
Keep reading on trades and procurement
The references behind scoping, quote levelling and procurement, the purchase order workflow, and the other category guides.
Send the dates. Get the reply on the job.
VIABUILD sends trades their dates for one-tap confirmation with no app or login, files their text replies against the task, and moves committed cost the day the purchase order is raised.