Why the Developer’s App Becomes Your Main Record After Key Collection
Collecting keys is a milestone, not the finish line. For most new BTO, HDB, condominium and EC homes, the first serious task is to inspect the unit and report workmanship defects while the Defects Liability Period (DLP) is running. The developer’s app—whether a common platform such as Novade or CityNexus, or a custom portal used by the main contractor—is often the formal channel for that first defect list. It timestamps entries, creates a case trail and routes items to the parties handling follow-up. Treat it as a record, not a complaint box.
The quality of each app entry matters more than the number of entries. A contractor needs to find the exact spot quickly, so separate unrelated issues and describe each one clearly: room, location, defect and evidence. “Common bathroom – floor tile outside shower kerb: hollow sound at the centre and slight lippage along the joint” is far more useful than “tiles bad”. If the app has a category field, choose the closest match; if not, put the category in the title. Attach a wide shot for context and a close-up for detail. One photo rarely proves both the location and the defect.
Before opening the app, do a systematic walkthrough with a floor plan and labels for each room. Check walls and ceilings for cracks, stains and seepage near windows and wet areas; floors and tiles for hollow spots, uneven joints and scratches; doors and windows for alignment, smooth operation and loose hinges; built-in carpentry for alignment and finishing; electrical sockets, data points and lighting points; and plumbing and sanitary fittings for leaks, chokage and water flow. Common defects include hollow tiles, uneven flooring, water seepage, misaligned doors and windows, loose sockets or switches, poor paintwork, plumbing leaks and damaged surfaces. Write down what you can see and photograph; the app is not the place for verbal promises.
The DLP context matters. Published guidance notes that the DLP is generally 12 months from key collection, and defects can be reported within that period provided renovation has not started and the home is not occupied. Sequence therefore matters: inspect early, submit early and keep a copy of every entry. The app may record a defect, but it does not automatically mean every item will be accepted for rectification. A clear, dated record gives you something concrete to follow up on when the contractor responds.
Building a Defect List That Survives the App Workflow
A defect list that works inside a developer’s app is evidence-led. For each item, capture the room or area, exact location, defect type, observation and at least one photo. Use a consistent naming style so the contractor can match the entry to the unit: “02 – Kitchen – Floor trap – slow drainage; water pools around the grate after 10 seconds” is easier to act on than a long paragraph with no reference point. If the app accepts video, use a short clip for doors, windows, sliding panels or water ponding. For plumbing, show the tap running and the water flow; for a hollow tile, photograph the marked tile and the surrounding joint.
Review the list before you submit. Look for duplicates, vague descriptions and items that are really cosmetic preferences rather than defects. The DLP is not a maintenance warranty for normal wear and tear or accidental damage, so keep the list focused on workmanship, installation and visible damage. Use neutral wording such as “for contractor to verify” rather than “must replace” when unsure. If the app has a character limit, put the short description in the field and let the photo carry the detail. Save a PDF export or screenshots, including any submission reference.
For homeowners who want a documented second opinion, an independent inspection can help before or after the app submission. Defect Check Singapore prepares defect reports in the developer’s format and can lodge items through the app used by the developer on the homeowner’s behalf. The firm is an independent inspection company and does not carry out rectification works, so the report supports your submission and follow-up rather than replacing the developer’s rectification process.
Keep the list practical for the people who will fix it. Group items by room if the app is room-based; if it is trade-based, group by trade. Add a short summary if the app allows one: number of items, rooms affected and any urgent issue such as water seepage or a leaking joint. Do not pad the list with repeated entries for the same tile or door. A tight, well-photographed list is more likely to be processed than a long one that forces the contractor to guess what you mean.
After You Hit Submit: Tracking, Follow-Up and Re-Inspection
Submitting the list is the start of the process, not the end. Save the confirmation screen, the submission ID and a copy of the list. Check the app’s status labels carefully: “open”, “in progress” and “rectified” may mean different things to different developers. Do not treat a status change as proof that the work is done. Wait for the contractor’s notification, then inspect the item physically. If a defect is marked closed but the hollow sound, stain or misalignment is still there, reopen it or add a comment with a new photo. Keep the tone factual and specific: “Item 14, master bedroom window, still stiff when opening; video attached on 12 May.”
Re-inspection is where many lists succeed or fail. Use the same room-by-room checklist and compare the before and after photos. Check that the repair itself has not created a new defect—patchy paint, damaged grout, a scratched frame or a misaligned cover. If the app allows comments, keep the thread on the platform so the record stays together. If it does not, send a short email referencing the app case number and attach the photos. Keep an eye on the DLP timeline; the published 12-month period from key collection is the window in which defects can generally be reported, provided renovation has not started and the home is not occupied. Rushing into renovation before the major defects are resolved can make the conversation harder.
A simple real-world pattern is common. A BTO owner collects keys, walks through the flat with the app open and logs 38 items. The contractor closes 20 quickly, but on re-inspection the owner finds six still outstanding and reopens them with close-up photos. A condominium owner submits a shorter list but uses dark photos; two items are rejected, then resubmitted with clearer images and a location sketch. In both cases, the app did its job because the owner kept evidence and followed up. The lesson is not to submit more items; it is to make each item easy to verify.
Finally, keep the record in one place: app screenshots, export files, before-and-after photos and a simple spreadsheet of what was submitted, what was closed and what you still need to check. The developer’s app is only as strong as the record you build around it. When the contractor says an item is done, verify it yourself, document it and keep the thread alive until the rectification is genuinely complete.
Osaka quantum-physics postdoc now freelancing from Lisbon’s azulejo-lined alleys. Kaito unpacks quantum sensing gadgets, fado lyric meanings, and Japanese streetwear economics. He breakdances at sunrise on Praça do Comércio and road-tests productivity apps without mercy.
