A project needs an ICRA, an ILSM, and a hot work permit, each signed off by a different department. Ruya puts all of it on one permit package, on the building, and shows you exactly where it is stuck.
Nobody has to remember which permit the finding requires. The package already has it.
Not a separate form on a separate timeline for each one. One record per project, on the building it belongs to.
A project opens one package. Every assessment and every work permit it needs lives inside it, each with its own status, all on one lifecycle from drafting through closed.
Infection control, environmental safety, interim life safety, life safety, and water infection control. ICRA gets classified and WICRA gets scored, and the package does not move until they are done.
Score the assessments and the permits their findings require get added for you. Welding on the job adds the hot work permit, and the hot work adds the fire watch. Nobody has to know the rule to be covered by it.
Attach the floor plan to the package and draw the containment boundary on it, so the reviewer approving the work and the inspector walking it are looking at the same barrier.
A pipe fails above an OR ceiling at 2am. Declare it, name the approver who deemed it approved, and the crew starts. The permit runs on a clock, and whether the documentation was filed inside the window is reported rather than assumed.
Eight stages from drafting to closed. This is where the time actually goes.
The package opens against the project and the building. The assessments get filled in and scored, and what they find decides what else the job needs.
Each permit goes to the parties who have to approve it. The chain shows how many have decided, who has not, and how long it has been sitting. Returned for changes starts a new round instead of a new email.
Pre-work, mid-work and final, each assigned to a named inspector. A failed inspection books a re-inspection, and the defect stays open until somebody clears it.
The package closes with every sign-off, inspection and timeline entry intact, each one carrying who did it and when. The audit pack prints the whole thing, per building.
Nobody assembles this for a survey. It is what is left over from running the job properly.
None of these are unusual. They are the ordinary month of a facilities team, before and after the package lives on the building.
The same package on every building, from the assessment that starts it to the pack a surveyor reads.
Ruya measures approval cycle time, how long each party sits on a decision, and the first-time inspection pass rate for every building, so the bottleneck is a number instead of an opinion. Emergency declarations are reported the same way, including whether the documentation was filed inside the window.
How many permits are in flight, which ones are waiting on a signature, and whose signature it is.
Every stop-work event with its reason, who called it, and how long it took to clear.
Permits coming up on their expiry date, grouped by how soon, before somebody works under a dead one.
ICRA classified and WICRA scored while the package is still drafting, not after the barrier goes up.
What the assessment finds adds the permits it requires, so the control is on the job whether or not somebody remembered it.
The containment boundary drawn on the current floor plan, so the reviewer and the inspector see the same line.
Every status change carries who did it and when, from initiation through closure, on the package itself.
Findings from an inspection carry a severity and stay open until they are cleared, with the time it took recorded.
Emergency declarations name the approver and are reported on how quickly the documentation followed.
Which is why the package sits on the building, next to everything else that describes it.
The containment boundary is drawn on the current floor plan, not on a printout from last year. The room the work is happening in carries its own department and ICRA level in the room record, so the assessment starts with something already known. The trade doing the work is in the vendor directory, tied to the buildings they are contracted for. A defect an inspector raises becomes a work order on the same building. And when a surveyor asks what was open and when, the binder reads the packages your team already closed.
Hospital permitting software is a system that creates, routes, and archives the safety permits hospital construction and maintenance work requires, including Infection Control Risk Assessments (ICRA), water ICRAs (WICRA), Interim Life Safety Measures (ILSM), and hot work permits. Facilities teams use it to keep a complete per-building permit trail that stands up to Joint Commission (JC), DNV, and CMS review instead of paper forms and email threads. Ruya Permits is a software and service solution: every permit is tied to its building and floor plan location, with one trail across every campus.
One project gets one package. Every risk assessment and every work permit that project needs sits inside it, each with its own sign-off and its own status, all on one lifecycle that runs from drafting through submitted, approval, issuance, active construction, final inspection and closed.
The required risk assessments are infection control, environmental safety, interim life safety measures, life safety, and water infection control. The work permits are above ceiling and penetrations, hot work, fire watch, ground penetration, and hazardous surveillance inspection. Emergency declarations run on their own fast path.
No, and that is the point. Score the assessments and the permits their findings require get added to the package for you. Welding on the job brings the hot work permit, and hot work brings the fire watch. You can still add one by hand when you want to.
Each permit routes to the parties that have to approve it, infection control, facilities, fire, compliance, and the chain shows how many have decided and how long it has been sitting with the ones who have not. Returned for changes opens a new round rather than restarting the paperwork.
A declaration skips the standard approval and is deemed approved on the spot, with the approver named, so the crew can start. The permit runs on a clock, and whether the documentation was filed inside the window afterwards is reported rather than assumed.
The audit pack: every permit on that building with its status, its sign-offs, its inspections and its activity log, print-friendly. It is a summary of what your team already did, not a document somebody wrote for the survey.
Pick the one where you already know a signature is sitting somewhere. We’ll build the package in Ruya and run it with you on screen. Twenty minutes, with the founder, not a sales rep.
Rashad Mujeebuddin, Founder, Ruya
On your schedule — no prep needed.