Skip to main content

Construction issues resolution in Sydney - Part 14

It's 37 days (1.25 months) past since the builder refused to finish the defective work on 28/10. Fair Trading inspector spent three weeks calling to the builder trying to get them back to fix the issue. All that time the bathroom/shower couldn't be used midst 30+ degree heat.

The builder started blaming the owner that it's the owner's fault that the work is unfinished.
However all the evidence was against the builder. They also said they are not coming back and that other company should fix it.

In the meantime the owner and strata decided to organise for other company to finish the work and reported that to the Fair Trading inspector. In a couple of days the builder called to strata manager and said they can come and finish the job!

Long story short the builder came out on 21/11 and 22/11 and almost completed the work, but left some sealing unfinished and the floorboards removed.
They also left the site without letting the owner know. The owner needed to take a day off work to monitor the work being done. Otherwise it would have been worse.

The owner notified the strata and Fair Trading (with photos) that the work wasn't completed. On the 26th the builder sent and email that this is all nonsense and that the owner swore at the tradesmen and "gave them hard time" when they were on site.
So instead of doing the proper job they send emails that the owner is bad. :)

Yesterday 04/12 Megasealed specialist came to finish the sealing and did a great job. The account will be forwarded to the builder to settle. Will see how that goes. At least the bathroom/shower can be used now! It took almost 3 years to fix the issue:

- December 2011 reported
- April 2013 Fair Trading rectification order
- April 2014 tribunal order
- 09/10 - 04/12 (two months) during the complete bathroom demolishing and repair plus around a week in summary during the "testing" period the bathroom/shower couldn't be used.

However one problem seems like sorted out.

Other outstanding issues are on the way - waterproofing issues at the balcony. The builder said they will send somebody to test again. They did it in May 2012 and April 2013 also. Get more popcorn ready?

Stay tuned.

Read the whole story here

Comments

Popular posts from this blog

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi