Skip to main content

Construction issues resolution in Sydney - Part 10

Got some positive results - one of the major defects was fixed!

The issue was scratches on all glass panels - sliding doors to the balcony, windows etc. All of them were scratched during construction phase.
As per contract of sale it has been responsibility of vendor to rectify. They first denied it and tried to impose it on the builder. The builder insisted that it's not their problem.

In January 2014 the owner took a right approach and contacted the vendor every week until finally 24/06/2014 the glass has been replaced!

It took 2.5 years to fix the issue!

Some people say that it might have been easier to replace it at the owners's expense than to wait for so long.
I disagree with this, because the owner paid money already for a quality product. The vendor signed a contract where obligations and responsibilities are outlined.
What surprise me is that how easy it is for people to not comply with their duties in a hope that the other party will just give up.

Other defects rectification is still underway. The builder keeps delaying the works even though the Tribunal ordered to finish the rectification within 2 weeks. It's already 10 weeks past!

Stay tuned for more news on this one.

Other posts from this story.

Also have a look at my post regarding strata living and what to look at before and when you buy a strata unit.
 


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