














































DoorCheck is a fire door inspection and record keeping system from DoorCheck Limited, a UK fire door inspection company based in Ilford, Essex. Its current app, DoorDoc, earlier sold as the DoorCheck App, runs on iPhone and is built for inspectors who survey doorsets for building owners and facility managers. Inspectors add buildings, locations and doors, record defects and compliance issues with photos and comments, summarise corrective and preventive actions, and issue branded PDF reports. Earlier reports carry forward, so each door keeps an inspection history. Through Makini's Unified API, a CMMS or facilities management product reads doors as assets with their buildings and locations, where the connection exposes them, so each doorset maps to the record its maintenance team already uses. When an inspection logs a defect, such as a damaged seal, the product can open a remedial work order for the door contractor. A compliance dashboard tracks which sites have inspections due, and a door hardware manufacturer reviews defects by component to plan replacement parts. A DoorCheck user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. What a connection exposes depends on the subscription and account used, so connect the account that holds the client's buildings, not one inspector's login. DoorDoc works offline, so findings reach the connection only after the inspector's iPhone syncs.
Have any questions? We’re here to help You
Yes, DoorDoc is the current fire door inspection app from DoorCheck Limited and replaces the earlier DoorCheck App. Version 2.0.0 was rebuilt from the ground up as a native iPhone app, needs iOS 15.1 or later, and asks users to sign in again after updating. Inspection companies use it to issue reports branded with their own details and logo.
Each door in DoorCheck's DoorDoc app carries a door ID and barcode, position in the building, fire rating with its evidence, door and frame materials, wall construction, vision panels and glazing, ironmongery and photos. Inspectors mark gaps, hinges, seals, signage, glass, door leaf, closer, locks and frame as Passed, Failed or N/A, pick faults from a standard list, and the app works out the overall result.
DoorCheck Limited's website does not describe a public API for DoorDoc; records from the app feed the customer's DoorDoc portal for reporting and certification. A vendor that needs fire door data in its own product can read it through Makini's Unified API, where Makini maintains the connector. Makini's page lists no data objects, so confirm which records the connection exposes.
Connect DoorCheck through Makini Link with an account manager's login, or a dedicated account with the same reach. In DoorDoc, account managers see every location for their company, while inspectors see only the locations assigned to them, and accounts are set up by the account manager rather than inside the app. An inspector's login would expose only part of the buildings and doors.
DoorCheck data reaches a vendor's product after two delays. Inspectors download a location before a visit and can work without signal, so edits, faults and photos stay on the iPhone until a connection returns. Makini then syncs on an interval set by its plan, not in real time. Use the data for compliance tracking and remedial planning, not as a live feed from site.
A CMMS can match each DoorCheck door on its door ID or barcode, using the building location and position as a check, since identical doorsets repeat across floors. A Failed result can then open a remedial work order against the right asset, where the connection exposes doors and results. Leave the inspection outcome unchanged in DoorCheck, since it is the evidence used for certification.
