Source: [FileTRX](https://treenodes.com/case-studies/filetrx/)

This Markdown version is generated from the public page. Visit the source for interactive examples and full-size visuals.

[Projects](https://treenodes.com/case-studies/)

TREENODES · Client file collection

# FileTRX

A product for collecting client files through a structured request, with requirements, outstanding items and progress visible in one place.

**Browse all projects**

## TreeNodes’ contribution

Analysis, architecture, software implementation and ongoing technical support.

**Project history**

Current project

FileTRX project views

![FileTRX request builder listing required and optional files and questions](https://treenodes.com/assets/case-studies/filetrx-request-builder.webp?v=b44b4260f7cc)

**Request builder**

 Product screenshot: define the files and answers needed for a client request.

![FileTRX owner view showing the status and progress of a sample client request](https://treenodes.com/assets/case-studies/filetrx-owner-progress.webp?v=73804b1b7192)

**Owner progress**

 Product screenshot: the owner can review required-item progress and share the client request.

THE PROJECT

## Purpose and scope

File collection is a repeated business process: define what is needed, ask the client, receive a response and follow up on what is missing. FileTRX gives that process a structured request that remains useful while a client responds in stages.

**Sector**

Client file collection

### Requirements and analysis

We analysed the handoff from both sides: what an owner needs to request and what a client needs to supply. The distinction between uploaded files and fulfilled requirements shaped the product, including required and optional items, instructions and visible partial progress.

### Software architecture

We designed the application around the request and its individual requirements. Files, answers, instructions and completion state belong to that structure, connecting the client’s response with the owner’s view of the work still outstanding.

### Implementation

We implemented the request workflow, from defining files and questions to sharing a browser link and reviewing submissions. The client can respond without a FileTRX account, while the owner can manage the request and see which requirements still need attention.

### Ongoing technical support

FileTRX remains a current project. We continue to provide technical support across the system and carry new requirements through analysis, architecture and implementation, keeping changes connected to the file-collection workflow.

[Read the FileTRX case study](https://treenodes.com/products/filetrx/)

RELATED SERVICES

## Explore the services behind this work.

-   [Business & systems analysis](https://treenodes.com/services/business-systems-analysis/)
-   [Software architecture](https://treenodes.com/services/software-architecture/)
-   [Web, mobile & business software](https://treenodes.com/services/software-development/)
-   [Workflow automation](https://treenodes.com/services/workflow-automation/)
-   [Database & technical support](https://treenodes.com/services/technical-support/)

LET’S TALK

## What would you like to build or improve?

Tell us about the business process, the software you need or the system already in use. We can discuss analysis, architecture, implementation and ongoing technical support.

[Discuss a project](https://treenodes.com/contact/) [Explore our services](https://treenodes.com/services/)