Construction issues resolution in Sydney

Construction issues resolution in Sydney - Part 4

On 09/02/2013 the builder came to inspect the exact same defects they have been aware of since September 2012.

During the inspection the builder verbally agreed to fix majority of those defects, rejected some of them as they believed those were maintenance problems and not the building problem and rejected their liability on some of the defects.
The owners corporation requested a report, which should include a list a of defects and exact dates when those defects would be rectified. The builder verbally agreed with that.

After 10 days - 19/02/2013 - the builder sent an email to the owners corporation and Fair Trading that included the unit numbers and the defects that will be fixed/not fixed.
Some defects were missing from the list and as usual there were no firm dates.

Owners Corporation have responded to that email (including Fair Trading) that the report is not complete.

After three days - 21/02/2013 - the builder sent an email providing the contact details of the person who was going to look after the defects rectification and forwarded a correspondence from that person that someone was possibly coming in the following week to fix some of the defects.
They also requested the evidence that some owners notified them about some of the defects! After four times they have been inspecting those!
No certain dates, no list of defects in the email.
As usual nobody appeared or contacted on the following week.

Owners corporation called Fair Trading on 01/03/2013 and the case has been submitted to the Fair Trading inspectors.

UPDATE:
19/03/2013 Fair Trading inspector called and schedule an on site inspection for 17/04/2013.

To be continued.

Other posts from this story.

Comments

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

Travels etc.

Search This Blog