Review framework
Two separate questions run through every review: what should happen to this issue, and what is the finding actually based on. They are answered by different parts of the system, and neither one is allowed to borrow authority from the other.
A · Action classification
Classification is an action, not a severity score. It tells you whether to correct something, confirm it, decide it, or ask about it — and it is capped by the strength of whatever the finding rests on.
Supported by evidence in the package and not safe to leave to site — a clash, a blocked swing, a fixture that cannot be used, or a verified mandatory requirement that is not met.
Drawn consistently, but outside what works in use, or resting on a published standard rather than a mandatory requirement. Worth confirming before it is fixed.
A decision that will be lived with rather than a defect: places where best practice, comfort or proportion suggest a deliberate choice should be made.
The drawings do not yet say. ROMURE states the question to ask instead of assuming an answer — an unset dimension, an unscheduled item, a detail that is not drawn.
A check that ran and passed — a measured clearance inside range, or a requirement met against a verified clause. What was verified is published alongside what failed, so you can see the whole picture.
A finding never declares itself Critical. The Critical badge is a separate consequence judgement and requires separate verified life-safety evidence with strong confidence. “Mandatory to correct” and “dangerous” stay different sentences, which is why an escalation cannot be produced by the same step that classifies the finding.
B · Basis of finding
Every finding names its basis, and the basis caps how far the finding can be escalated. If no verified source applies, ROMURE says so on the finding itself rather than implying one.
Manufacturer installation requirements are modelled alongside project requirements rather than as a separate basis, because both are mandatory-to-project. Nothing outside this list can be used to support a finding — there is no “general knowledge” category for a model to reach into.
Jurisdiction-aware rule packs
Building requirements are local. ROMURE binds every rule to the jurisdictions, space types and project types it genuinely applies to, and selects packs from the project's own location — city, then country.
ROMURE does not reproduce the text of a code or standard. Rules are encoded as ROMURE's own neutral statements of the requirement — the threshold, the unit and the clause it came from — so that the source is verifiable without copying protected material.
ROMURE does not display the logos or marks of standards bodies or authorities. The publisher is named in the source record so you can go to the original document yourself.
ROMURE does not present a standards result as a legal conclusion unless the project jurisdiction is confirmed for that review.
Standards coverage
Coverage is published as it stands, including what is missing. A region being listed here is not a claim that its requirements are covered in full — read the status on each region.
Read from the published coverage file when the browser can fetch it; otherwise the launch coverage states above remain live and are the current verified position.
Dubai
Dubai kitchen rules are verified. Nothing else in the UAE is covered, and no ROMURE pack covers the Dubai Building Code as a whole.
National packs and state codes
Federal accessibility packs are active only for explicitly declared scope. No state or city code has been adopted, so no IBC or IRC conclusion is produced for any United States project.
England only, not the UK
England has verified Approved Document packs for accessibility, space, stairs and ventilation. This is England only: Wales, Scotland and Northern Ireland are separate jurisdictions.
Nationwide guidance and state by-laws
The Harmonised Accessibility Guidelines are active. No state or city adoption pack exists yet, so no National Building Code provision is presented as mandatory.
Separate from England
Scotland has its own building standards system. No rule is registered, so a Scottish project is explicitly uncovered and England's approved documents are never applied to it.
Each verified on its own sources
Wales and Northern Ireland each have their own building regulations. No rule is registered for either, so both are explicitly uncovered and England's approved documents are never applied to them.
Anywhere not listed is uncovered. A review there still runs on the drawings — spatial evidence, coordination, dimension and usability — and simply carries no local code conclusions.
Source and provenance
An example record, from the one verified pack that is active today. This is the shape of the metadata behind every rule — not the text of the requirement itself.
A rule is only as good as the last time it was checked. Each record carries the date it was last verified and the amendments it has been tested against since, so a review can be reproduced and audited rather than taken on trust.
ROMURE reviews interior drawings for coordination, dimension and usability issues. It does not replace your architect, engineer or local authority approval. A standards result is not a legal-project conclusion unless the project jurisdiction is confirmed.
Keep going
Start here
Coverage is honest, the classifications are capped by evidence, and the first review costs nothing to judge.
Coverage states on this page are ROMURE's launch position and are updated as packs are verified. No payment is taken on this page.