Skip to main content

Construction issues resolution in Sydney - Part 13

The builder started demolishing the bathroom and shower 07/10/2014 (three weeks ago) and then proceeded to do waterproofing, bedding, tiling etc.

As appeared, from the words of tradesmen who worked on the site there was barely any waterproofing originally.
This is a question to original sub-contractors and certifiers who did the original work - how that might have happened?

Anyway until last week everything went well when I went to check the shower drain and found that the water stays there on one side and doesn't flow out completely.


The builders closed it with the grate and were about to finish the whole job, but I pointed that problem to them and said it should be rectified before they finish everything.
They started saying that "it's normal and the water will evaporate". Then they started saying that they couldn't do another drain and this is the only possible solution. The whole floor and shower walls were ripped off - why the hell didn't they find the right solution when it wasn't tiled yet?
The plumber let the word out that he already said to the builder that the original drain won't work properly, but they insisted on using the old drain to save money. In my opinion it's retarded to save a couple of dollars on a job where you have already spent about $10000 or more and running into a risk of re-doing the work again!

Nevertheless the builder's sub-contractor kept saying that it's normal and that I should go to manufacturer of the drain or the builder or strata or somewhere else. I requested to fix the problem before completion of the whole work. They have gone mad at me and provided two options:

- Finish the work apart from the drain problem and accept it
- Stop all the work right now

In response I requested them to fix the problem. Anyway they stopped doing everything and left. Also saying that I shouldn't contact them directly.

The Fair Trading inspector has confirmed that they shouldn't leave the place like this and have to fix the problem. The next step is to renew the proceedings in the NCAT (tribunal).

More adventures to come - stay tuned!

Read the whole story here
Labels:

Comments

Post a Comment

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 .
Post a Comment
Read more

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...
Post a Comment
Read more

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...
1 comment
Read more