Blind cord safety audit app
Looped blind and curtain cords are a known strangulation risk for young children, and Australia has a mandatory safety standard for corded internal window coverings. Property managers audit their rentals to find non-compliant installations before a tenant with a toddler moves in. The audit is window-by-window: what covering, where the cord ends, and whether a tie-down or cleat holds it out of reach.
Built for property managers running teams of roughly 3–50 inspectors.
Sample Cord safety report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Cord safety report
Window covering audit — 8 Mockingbird Court (fictional)
- Purpose
- Pre-tenancy safety audit
- Date
- 3 March 2026
- Windows audited
- 11
| Window | Covering and cord | Finding |
|---|---|---|
| W1 · Lounge | Vertical blind, looped chain, tensioned to sill | Finding: Secured |
| W4 · Bedroom 2 | Roman blind, loose looped cord hanging to 900 mm | Finding: Not secured |
| W5 · Bedroom 2 | Holland blind, cordless spring roller | Finding: No cord |
| W8 · Bedroom 3 | Venetian, cleat fitted at 1.2 m, cord wrapped | Finding: Cleat too low |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the cord safety report where your template puts it.
Per window
- Window ID and room
- Covering type
- Cord type (looped / single / chain / none)
- Lowest cord point above floor (mm)
- Securing device fitted
Assessment
- Secured / not secured / no cord
- Furniture near the window a child could climb
- Photo
Follow-up
- Rectification needed
- Trade or handyman required
- Re-check date
Standards the report works to
- Competition and Consumer (Corded Internal Window Coverings) Safety Standard 2014Mandatory safety standard (ACCC)
- The mandatory requirements for securing cords on internal window coverings supplied and installed in Australia.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the cord safety report gets built
Capture it once, offline
Your firm builds the blind cord safety audit form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your rooms and external areas
Enter rooms and external areas once, as a register. Every one of your defects, photos and timber pest findings then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The cord safety report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a cord safety report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The summary says no major defects were found; the form carries a major structural defect on the rear wall.
Checks a residential property framework usually carries
- The standard’s required wording, limitations and exclusions are all present
- Every area is either reported on or listed as not accessed, with a reason
- Each defect in the summary appears in the body at the same severity
- Timber pest findings carry the risk statement the standard requires
Questions
- Can the form flag a cord that hangs too low?
- You set the threshold, and a visibility rule can raise a follow-up question whenever a measured cord height is recorded below it.
- Can we audit a whole rental portfolio this way?
- Each property is a job using the same form, so audits across a portfolio share one structure and one report template.
- Does the report record that we fixed the problem?
- A follow-up job can reuse the window list and record each item as rectified, producing a second report that closes the first.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other residential property work we cover
- Apartment defect surveysDefect evidence report
- Boundary tree dispute reportsArborist boundary report
- Building and pest inspectionsCombined building pest report
- Dividing fence condition reportsFence condition report
- Granny flat approval inspectionsSecondary dwelling report
- Meth residue testingContamination test report
- Mould inspectionsMould assessment report
- New-build handover inspectionsPCI defect report
Other disciplines
Rebuild your cord safety report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.