Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Trello for Construction/Maintenance Company

Gareth Ricketts
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 19, 2021

As above? We have up to 50 jobs on at any one time with various levels of work for each one.

Are we better off creating a board per job, or one board called operations and then 50 cards for the jobs. Each job will then have it's own lists or 'sub cards generated'

We will be using Planyway to assign the jobs to our staff

Thanks in advance


Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 19, 2021

@Gareth Ricketts 

I don’t think there is a single right answer for you.

For example, I have client with a fleet of 20 vehicles that go through services to turnover the vehicles so that they can be ready for rental. They do repairs and maintenance of none rental vehicles. In that situation, they assign task and subtask using a customisable work order boards to their specialist in their own personal boards. Each task and subtask sits on a list and all work and reporting happens on the list rather that across a board. 

Yet another client has 2400 work orders per year and everything happens on one board. None-maintence work progression is triggered from Work iS triggered from an external management system.

Another client conducts business on separate boards eg Quotation and customer approvals, job tracking, completion and delivery, rework, purchase orders...etc

Flavien Gache
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 19, 2021

In my opinion, it could be useful to use one per job if jobs are independants from one another and if each job needs to work on its board. It could allow you to separate each job and detail everything without giving irrelevant information to other jobs.

If boards are going to be used by the same person, or same set of persons, you could be better off with only one board. It would mean less clicks and less back and forth for the person that will schedule plannings.

However, I think going with Planyway is the right move : its features are really interesting for those who don't want to deal with the complexity of Jira. Butler would be a great addition to automate repeating tasks.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events