Tuesday 20 October: Complaint form offline

The supplier of our case management system has confirmed that they are experiencing a significant technical issue.

At present, we have no access to the case management system and we are currently unable to provide updates on existing cases.

We are planning on the basis that this could continue for a period of time including for the remainder of this week.

If you would like to check if your complaint is ready for the SPSO or enquire about making a new complaint, please complete our Complaint Checker.  

Please be assured we are doing all we can and will provide updates on our website. 

For an all service update: Service update | SPSO

Decision Report 201202395

  • Case ref:
    201202395
  • Date:
    December 2013
  • Body:
    Glasgow City Council
  • Sector:
    Local Government
  • Outcome:
    Not upheld, no recommendations
  • Subject:
    repairs and maintenance

Summary

Ms C complained that the council failed to follow the appropriate tendering and procurement process for communal repairs to her close. She said that they had ignored a report requiring them to re-tender due to a lack of competitive quotes, as only two of the four companies approached had responded. She also said that the council costs were far higher than her privately obtained quotes, and that they had misled her by asking her to submit quotes that could not in fact be used as the suppliers were not on the council's approved list of contractors.

Our investigation found that the council had already apologised for the confusion about which contractors could form part of the tendering process, and had produced a new information leaflet, setting out the statutory repair process clearly for private residents. We also found that although the report on the tendering process recommended re-tendering, there was no requirement for the council to accept this, and that re-tendering could have resulted in higher costs. We did, however, criticise the council for poor record-keeping, as the decision-making audit trail was unclear.

Updated: March 13, 2018