Requests live in e-mail and nobody has the full list
A shutdown is asked for in one thread, moved in another and confirmed by phone. When the owner asks which areas were offline last month, the answer is a search through inboxes.
Phased renovation
Healthcare construction phasing coordination: requests, confirmations and the daily record
Work in an occupied hospital moves one area at a time, and every shutdown, access change and finish task has to be asked for, scheduled, confirmed and written down for the owner and the people who use the space. Fidrel does not replace the owner’s own process. It gives the contractor and the owner’s facilities team one place where those requests, confirmations and daily reports are kept in order.
30 days free · No long-term contract.
What goes wrong in a phased renovation
Phases overlap in ways the plan did not show
The ceiling work in one wing and the finish work in the next share a corridor. If the two crews do not see each other’s dates, one of them arrives to find the area still closed to them.
Finish tasks are tracked on paper
Small closing tasks per area, such as patching, painting and cleaning before the area is handed back, sit on a clipboard. Nobody can show later who owned a task or when it was done.
The loop as a log of calendar items and tasks
Think of each shutdown as one calendar entry with three states of knowledge. First it is requested, which means the entry exists with its dates and notes. Then it is confirmed, which is the status the person doing the work sets after the owner’s staff have accepted. Finally it is done, or blocked with a reason in the notes. The calendar shows the entries by day, week or month and lists the next fourteen days as an agenda, so the superintendent and the owner’s facilities team read the same plan. Each state change is a change to one record, not a message in a thread.
Site & daily log
Who sees what
Shared calendar entries are visible to everyone in the project, so invite the owner’s facilities staff and the user departments as participants, or as guests who only read and download. The To-do board is narrower: administrators see the whole board and everyone else sees only the tasks that are theirs. The daily report cannot be deleted, and every change to it is logged field by field with the name and the time, which gives the owner a record that cannot quietly change afterward.
How to run the request loop in Fidrel
Step 1
Put each phase and shutdown in the shared calendar
A project administrator adds an entry of the type Work for the area, with the dates and a notes field that names the system and the people affected. Shared entries are visible to everyone in the project.
Step 2
Ask the people involved to accept
Add the participants to the entry. Each of them accepts or declines, and the one doing the work marks it Planned, Confirmed, Done or Blocked as the day approaches and passes.
Step 3
Give the closing tasks an owner
On the To-do board an administrator creates a task for each closing item, with one owner, a due date, a priority, a checklist and a label for the area. The owner is notified in Fidrel when it is assigned.
Step 4
Write the daily report for the area
Each day the daily report records the work in progress, people on site, equipment, deliveries, delays and safety observations, the work area or location, and photos. Filter the log by location to see one area’s days together.
From a daily report to a corrective item
When a daily report points to a problem, Create NCR fills in the title, text, location and responsible person from the report and links the two in both directions. The NCR has a category, a priority and a corrective action, and it is tracked from open to closed. A change order can then be created from the NCR if scope or cost moves. That chain is the closest Fidrel comes to a phase closeout: each area ends with its tasks done, its NCRs closed and its reports on file.
What this does not do
A shutdown request in Fidrel is a calendar entry with people and a status, not a request form with an approval step. Fidrel does not manage infection control or life-safety measures, and nothing in it states that a requirement of any kind is met. The calendar does not connect to the hospital’s own systems; the only way out is an .ics file. Shared entries are created by project administrators, and the plan for each phase stays as detailed as the people entering it make it.
Related solutions
One project. One subscription. The entire platform included.
Your trial applies to your first own project and starts when that project is created. No card required. Afterwards, choose card or invoice to continue.
- 30 days free
- Unlimited participants
- No minimum term
Insights
View all
Project coordination just got simpler
The project system of the future connects people, documents and decisions. Discover the thinking behind Fidrel.
Read more
Your drawing, on site. Open DWG on your phone.
On site, answers need to be close at hand. Fidrel displays DWG drawings in your mobile browser, within the project’s document structure.
Read more
A clearer schedule. From the first activity to the final milestone.
When everyone can see the next step, moving the project forward becomes easier. Fidrel brings activities, dates and reported progress together in a shared Gantt view.
Read more
Phased renovation
Frequently asked questions
Anything else on your mind? We are happy to help.
Talk to usAs calendar entries with dates, participants and a status, and as tasks with an owner and a due date. There is no request form with an approval workflow, so the approval itself still happens in the way your owner requires.
Shared entries in the project calendar are created by project administrators. People assigned to an entry accept or decline it and set its status to Confirmed, Done or Blocked.
Yes, if they are invited to the project. A shared entry is visible to everyone in the project, and a guest can read and download but not change anything.
In the daily report, which has a work area or location field, fields for work, people, equipment, deliveries, delays and photos, and a change log. Filter the log by location to read one area’s reports together.
No. Fidrel does not manage those measures and makes no claim that any health-facility requirement is met. It records the requests, confirmations and reports your team enters.
Only through an .ics export. There is no integration with the owner’s systems, so anything beyond the calendar file stays manual.