How Construction Companies Can Automate Supplier, Subcontractor and Approval Workflows

Why this matters for Japanese construction companies

Construction is becoming an increasingly important automation target in Japan. MLIT’s i-Construction 2.0 initiative is designed to advance automation across the construction production process. The program identifies three major areas: automation of construction work, automation of data linkage, and automation of construction management. MLIT’s stated goal is to achieve at least 30% labor reduction—or approximately 1.5× productivity—at construction sites by FY2040.

That direction continued in 2026. MLIT’s second-year progress report highlighted greater use of automated and remote construction, expansion of ICT construction, AI use, and a shift from experimentation toward broader operational adoption. Much of the public discussion around construction DX understandably focuses on equipment, BIM/CIM, remote construction and field technology. But there is another layer that deserves equal attention: the administrative and operational workflows surrounding construction. Before work can happen on site, organizations may need to coordinate:

• supplier information,
• subcontractor records,
• commercial approvals,
• safety documentation,
• insurance or qualification documents,
• purchase requests,
• project approvals,
• internal reviews,
• site-readiness decisions,
• invoice and payment processes,
• and multiple internal systems.

These processes may not be as visible as an autonomous construction machine. But they can consume substantial staff time when they depend on email, spreadsheets and repeated follow-up.

Government materials provide industry context. These workflow examples do not imply Axton or Fluyenta participation in i-Construction 2.0 and are not MLIT requirements.

The problem is usually not one bad system

Consider how a subcontractor may enter a project today.

• The subcontractor emails documentation.
• A procurement or administrative employee checks whether everything is present.
• A missing document triggers another email.
• A safety or project team reviews relevant information.
• Someone records the status in Excel.
• A manager approves the company.
• Accounting or procurement creates the supplier record.
• Documents are saved to a shared folder.
• The project team waits for confirmation.
• Someone eventually tells the site team that the subcontractor is ready.

None of these activities is individually unusual. The problem is that the complete process is fragmented.

• The subcontractor cannot easily see what is missing.
• Internal teams may not know which department currently owns the request.
• Managers may have no consolidated view of pending approvals.
• Information may be re-entered into multiple systems.
• Documents may expire without anyone noticing.
• The ERP may contain the final supplier record but have no visibility into the process that happened before it.

This is where workflow orchestration becomes useful.

A better model: one end-to-end subcontractor workflow

An automated construction onboarding process might operate like this:

1. 1Subcontractor invited
2. 2secure portal opened
3. 3company information submitted
4. 4required documents uploaded
5. 5completeness checked
6. 6relevant internal reviews triggered
7. 7exceptions returned for correction
8. 8commercial approval
9. 9project/site approval
10. 10ERP/vendor system updated
11. 11project team notified
12. 12onboarding record retained

The exact steps vary by company. That is important. Automation should reflect the construction company’s actual policies—not impose a generic process simply because software supports it.

Workflow 1: Supplier and subcontractor onboarding

One of the strongest automation candidates is supplier or subcontractor onboarding. Typical information might include:

• company details,
• contact information,
• banking or payment information,
• insurance-related documents,
• licenses or qualifications where applicable,
• commercial documentation,
• project-specific documentation,
• or other company-defined requirements.

Instead of requesting these through email, an external portal can give the supplier one controlled submission point. The process can then check whether required information exists before an employee begins reviewing it.

• If something is missing:the workflow requests the missing information automatically.
• If everything is present:the request moves to the relevant reviewer.
• If additional review is needed:the correct department receives a task.
• If approved:downstream systems can be updated.

Fluyenta’s web-interface capability is designed to connect responsive forms and portals directly to workflows and underlying data, which is relevant to this kind of supplier-facing process.

A real partner-experience example

Fluyenta/RunMyProcess has published an anonymized supplier-onboarding example involving a building-materials retailer. The organization had been managing supplier onboarding through email and telephone communication. Its stated challenges included lengthy approval cycles, poor visibility across branches, and frustration for both staff and suppliers. The resulting solution introduced structured data collection, automated approval routing and visibility into onboarding status. Fluyenta describes the outcomes qualitatively as faster onboarding, improved employee efficiency and a better supplier experience.

This is Fluyenta/RunMyProcess partner experience, not an Axton-completed construction project. The reason it is relevant to construction is the workflow pattern:

1. 1external company submits information
2. 2organization validates it
3. 3multiple people approve it
4. 4status must remain visible.

That pattern appears frequently in supplier and subcontractor management.

Required documents and review criteria must be configured for the organization’s policies and applicable obligations. A workflow does not itself guarantee legal compliance.

Workflow 2: Subcontractor document management

Collecting documents is only part of the problem. Documents change. Certificates expire. Project requirements change. A subcontractor may be approved for one activity but not another. A file may need renewed information before the next project. A workflow can therefore treat a document as part of an ongoing process rather than a static file. For example:

1. 1Document submitted
2. 2document type identified
3. 3required fields checked
4. 4expiration date captured
5. 5responsible team reviews
6. 6accepted/rejected
7. 7expiration monitored
8. 8renewal requested before expiry

This is especially useful where the company must demonstrate that required internal checks actually occurred. The important principle is not simply storing the document. It is knowing:

• who submitted it,
• who reviewed it,
• when it was approved,
• what version was used,
• when it expires,
• and what happens next.

After a person accepts the documents, approved records could be synchronized with project or document systems where suitable integrations are available.

Workflow 3: Internal approvals

Construction projects produce approvals everywhere. Examples may include:

• purchase requests,
• supplier approval,
• subcontractor engagement,
• project expenditure,
• equipment requests,
• change requests,
• document acceptance,
• exception approvals,
• or management sign-off.

Email is convenient for informal communication. It is much weaker as a process-management system. A workflow can formalize rules such as:

• Under a defined value → project manager approval
• Above a defined value → project manager + finance approval
• New supplier → procurement review required
• Exception to policy → senior approval required
• Incomplete documentation → cannot proceed

Fluyenta’s workflow engine is designed around multi-role processes, business rules, decisions, exceptions and human tasks. The key benefit is not simply that an approval button replaces an email. It is that the process knows:

• what stage it is in,
• who is responsible,
• what rule applies,
• what happened previously,
• and what should happen next.

People retain the approvals required by company policy; an approved outcome could then trigger an ERP or project-system update through a configured integration.

Workflow 4: Purchase and procurement approvals

Procurement is another natural candidate. A construction procurement process may cross:

• project operations,
• procurement,
• finance,
• management,
• supplier communication,
• and an ERP or accounting system.

A simplified process could be:

1. 1Purchase request
2. 2budget/project validation
3. 3approval routing
4. 4procurement review
5. 5supplier selection
6. 6PO action
7. 7ERP update
8. 8requester notification

Fluyenta’s current enterprise-operations positioning explicitly includes vendor onboarding, PO approvals and contract-management workflows, along with monitoring of bottlenecks, ownership and audit trails. The important part is that the workflow can sit around existing enterprise systems. The ERP remains responsible for the functions it performs well. The orchestration layer handles the process that crosses departments and systems.

Workflow 5: Site-readiness coordination

Another useful construction scenario is preparing a subcontractor or team to enter a project. Different departments may need to verify different things before work starts. The workflow could coordinate:

• required documentation,
• project assignment,
• internal review,
• safety-related checks,
• commercial status,
• equipment or access requirements,
• final readiness approval,
• and notification to the site team.

A dashboard could then show states such as:

• Not started
• Documents incomplete
• Under review
• Correction required
• Commercial approval pending
• Project approval pending
• Ready

Rather than asking: “Has this subcontractor been cleared yet?” the organization can see the status directly.

Responsible staff retain readiness judgments. Where integrations are available, reviewed status could be shared with project systems to support coordination.

Workflow 6: Expiry and renewal management

Construction operations frequently involve information that has a validity period. Instead of discovering an expired item when somebody happens to open the file, a workflow can monitor the recorded expiration date. For example:

• 60 days before expiry → notification
• 30 days before expiry → supplier reminder
• 7 days before expiry → escalation
• expired → status changed / internal review required

The exact rules should reflect company policy and applicable requirements. This turns document management from passive storage into active process management.

Staff review renewal exceptions and any decision that requires judgment. Reminder and status workflows could connect to document or project records where integrations are available.

Workflow 7: Change and exception approvals

Construction rarely follows only the “happy path.”

• Changes occur.
• A supplier may need an exception.
• Documentation may be incomplete.
• A project may need an urgent purchase.
• An approval may need escalation.
• A contract condition may change.

Enterprise workflow automation is valuable partly because it can explicitly model these exceptions. Instead of employees improvising through email, the process can define:

• what qualifies as an exception,
• who can approve it,
• what justification is required,
• what evidence must be retained,
• and what downstream systems should be updated.

Fluyenta’s process-orchestration model explicitly combines automated actions with human approvals, business rules and exception handling across systems.

Where an external portal changes the experience

For construction companies, an external portal can remove a major source of friction. Without a portal:

• supplier emails procurement,
• procurement emails the project team,
• project team requests another document,
• supplier sends it to the wrong person,
• someone saves the wrong version,
• supplier asks for status,
• employee searches through emails.

With a portal:

• supplier sees requirements,
• submits information once,
• receives structured requests for correction,
• can see status where appropriate,
• and interacts with one controlled process.

Meanwhile, internal employees see only the tasks relevant to their role. That is fundamentally different from adding another generic website. The portal becomes a controlled interface to the business process.

Where AI can actually help

AI can be valuable in construction administration when the problem involves large amounts of unstructured information. Potential uses include:

• document classification,
• information extraction,
• expiry-date extraction,
• summarization,
• identifying missing sections,
• routing documents,
• or preparing information for a reviewer.

For example:

1. 1Subcontractor uploads document
2. 2AI identifies document type
3. 3extracts selected fields
4. 4employee verifies result
5. 5workflow continues

This can reduce repetitive document handling without allowing AI to make decisions that the company believes require human judgment. Fluyenta’s AI capabilities are designed to embed AI steps inside governed workflows rather than treating AI as a separate standalone chatbot. Its broader platform also emphasizes role-based controls, auditability and human approvals.

What AI should not do automatically

Not every construction decision should be delegated to AI. Examples that may warrant human review include:

• accepting a high-risk exception,
• approving major expenditure,
• deciding whether a subcontractor satisfies company-specific requirements,
• interpreting ambiguous documentation,
• or making decisions with significant safety, contractual or regulatory consequences.

The objective should be: AI handles information work. Rules handle predictable policy. People handle judgment. That is more useful than simply trying to maximize automation.

Connecting the workflow to existing systems

A common concern is: “We already have ERP, accounting, project-management and document systems. Are you proposing another system?” Not necessarily. Enterprise automation can be used as a coordination layer. For example:

1. 1External portal
2. 2workflow
3. 3manager approval
4. 4ERP vendor record
5. 5project system
6. 6document repository

Fluyenta’s integration capabilities support cloud and on-premise environments, APIs and system-to-system data transformation, while its SAP positioning specifically describes automating approvals and validation around SAP rather than requiring organizations to customize or replace the ERP core for every workflow. The right architecture depends on the company. But the principle is valuable: Do not make employees perform the integration that systems should perform.

BIM/CIM does not eliminate workflow problems

Japan’s construction DX efforts are also expanding the use of BIM/CIM. MLIT describes BIM/CIM as digitizing information across survey, design, construction and maintenance stages so project participants can use and share data more effectively across the construction lifecycle. That is important. But better project data does not automatically automate:

• supplier onboarding,
• commercial approvals,
• document requests,
• procurement decisions,
• exception handling,
• or external stakeholder communications.

BIM/CIM and workflow automation solve different but complementary problems. One improves shared construction information. The other coordinates how people and systems act on information.

What should not be automated first

Construction companies should resist the temptation to automate everything simultaneously. Poor first candidates include processes where:

• nobody agrees on the current procedure,
• the business owner is unclear,
• rules change constantly,
• important policy questions remain unresolved,
• data does not exist in usable form,
• or the process is so rare that automation provides little benefit.

Automation should also not preserve unnecessary bureaucracy simply because it exists today. If a process requires seven approvals because nobody has challenged it for ten years, the first question should not be: “How do we automate seven approvals?” It should be: “Do we actually need seven approvals?” Process improvement comes before process automation.

A practical construction workflow architecture

A useful construction automation pattern can be represented as:

The value comes from managing the whole process, not from automating one button.

What management gains

Workflow automation can give management something that email and spreadsheets struggle to provide: visibility. Instead of asking individuals for status, managers can potentially see:

• number of open onboarding requests,
• where requests are currently waiting,
• which tasks are overdue,
• which suppliers require corrections,
• which approvals are pending,
• which documents will expire,
• and which process steps create repeated bottlenecks.

Fluyenta’s platform specifically includes workflow monitoring and auditability alongside task ownership and process visibility. That changes automation from a convenience tool into an operational-management capability.

A sensible first project for a construction company

Do not begin with: “Automate our entire supply chain.” Choose something narrower. For example: Digitize the onboarding and approval of new subcontractors for one business unit or project type. Map:

• who starts the request,
• what information is required,
• what documents are required,
• who reviews each part,
• which exceptions occur,
• which system needs the final data,
• and what “approved” actually means.

Then build the first workflow. Once the organization learns from that process, it can extend the same architecture to:

• renewals,
• additional projects,
• supplier onboarding,
• procurement,
• site-readiness,
• purchase approvals,
• change requests,
• or other construction workflows.

How to decide whether a workflow is worth automating

A good automation candidate usually shows several warning signs.

• Employees repeatedly chase people for status.
• The same information is entered more than once.
• External companies send documents by email.
• Approvals are difficult to track.
• Only experienced employees know what happens next.
• Managers cannot see where requests are stuck.
• Files are stored correctly, but nobody knows whether the business process around them is complete.
• A request crosses several departments.
• Expired information is discovered reactively.
• The process creates many “Can you check this?” messages.

If several of these are true, workflow automation may be worth investigating.

How Axton Group × Fluyenta approaches construction automation

Construction and infrastructure are especially relevant areas for Axton Group LTD Japan because they align with Axton’s existing business and engineering context in Japan. Through the partnership with Fluyenta, Axton can bring that local construction understanding into discussions about enterprise process automation. Axton’s role begins with the business process:

• How does the work happen today?
• Who participates?
• Where does it slow down?
• Which systems are involved?
• Which decisions require people?
• What must remain auditable?

Fluyenta contributes the enterprise workflow, integration, portal and governed-AI technology, backed by more than 20 years of enterprise process-automation experience. The objective is not to introduce automation for its own sake. It is to help construction organizations move important work with less manual coordination, better visibility and clearer accountability.

Construction automation should connect the office and the project

Construction DX is often discussed in terms of what happens physically on site. That transformation is important. But the work surrounding the site matters too.

• A digitally advanced construction operation should not have autonomous equipment on site while supplier approval is still trapped in someone's inbox.
• It should not have BIM/CIM project information while subcontractor status is tracked in an isolated spreadsheet.
• It should not use AI for engineering analysis while procurement staff manually re-enter supplier data between systems.

The next stage of construction digitalization is not simply adding more individual technologies. It is connecting them into processes that people can actually operate. And supplier, subcontractor and approval workflows are a practical place to start.

Frequently Asked Questions