Your to-do list
The To do tile on Start, first in the row of tiles.
The To do tile is always first in the row on Start: how many tasks are yours, with how many are overdue, paused or with others beneath. Press it and your list opens beneath the row, in place of any other window; press it again, or Close, to put it away. Its top line has the counts, a box to search your tasks, which also finds a payment request by its payee, reference, expense number or amount, typed as 502.84 or £1,234.50 (a word led by a minus leaves out tasks with that word) and Filter, which opens the rest: urgency, who it is from or assigned to, the label, the order (most urgent first, oldest due first, newest due first, or oldest surgery first, which puts payment requests in the order of the operations they pay for, with any that pay for no operation after them; undated tasks go last, a payment request going by its expense's due date; the payment run's list takes the same order; this browser remembers it), and Show, which ticks any of overdue, unlabelled, paused, with others and completed and names what is ticked. Every task has a tick box at the left, which only picks it. Tick one or more and a bar appears at the foot of the screen, stays there as you scroll without moving the list, and says how many are selected. Its Label, Postpone and Reassign each open a small list above them, and choosing from it does the job at once for the ticked tasks: there is no Apply. Label lists your labels, lets you type a new one, and has No label to take one off. Postpone offers 1 day, 3 days, 1 week, 2 weeks or 1 month, or a date, then Postpone; an amount moves each task on by that much, counting from the day it was already put off until where it is postponed already, and a date puts them all off to that day; each is put off for you the way a single Postpone is. Reassign lists the current staff of every organisation you work at: choosing a person gives them every ticked task, and Several people lets you tick more than one, then Reassign, so the tasks are dealt out between them in turn, fifty-two tasks given to four people being thirteen each; a task that is not yours, or whose person is at none of your organisations, or who is already on it, is left where it is and named. Done in the bar finishes every ticked task at once, and Undo reopens them; a task that is already done, or an application call that must say how it ended, is left and named. When the ticked tasks include expenses, Check receipts appears in the bar. Select all shown ticks every task on the screen and Clear unticks them; nothing else unticks them, so you can search, filter and scroll with your ticks kept, and those still shown stay ticked. When a job is done the ticks clear and a note at the foot of the screen says what was done, with Undo, which puts every task back exactly as it was; while a filter is on, the number beside Filter says how many. The first ten tasks show, with the rest behind the more beneath them; a search, a filter or opening a task shows everything that matches. Pressing a count on the top line, such as the overdue, shows just those. New task on the list asks what needs doing, then About, where you choose what it concerns so the task is linked to it (the same choice as Link on a task, below), and Give to, the people at your organisation, so it can be handed to one or more of them; leave the people empty and it is yours alone.
Each task shows what it is for and who it is about, with its text in the lines it was written in, so a task that lists invoices reads one invoice per line; a task about a patient, a contact or an expense opens them from the task. Link, on an open task, is for anybody the task is on: choose the kind of record, then find it. Equipment, assets, risk assessments, operating lists, clinics and events are found at every organisation you work at, whichever you signed in at, and a record at one of them links as it would had you signed in there. Finding a contact does not offer anybody whose roles at our organisations have all ended; somebody with a role still running, or who has never had one, is found as before. A patient, contact or organisation is found by name. A letter, appointment, operation, quote or invoice is found by choosing the patient first and then one of theirs, newest first; a task already about a patient starts with them, and Another patient changes that. An operating list, clinic or event is found by typing a day, such as 21/10/2026, and otherwise shows those of the fortnight either side of today at your organisation; equipment, a document or a risk assessment by its name. Linking a patient's letter or other record links the patient too. While Link is open each link has Remove, which takes the link off and leaves the record itself untouched; an expense comes off a task only by the person who made it, since on a payment run that takes it off what is paid. Done closes it. A quote on a task opens its quotes with that quote chosen; a letter, investigation or log line opens the patient it belongs to; a complaint, a risk assessment or a payslip opens its own page. A purchase order, audit or email in is named on the task without a link, because it has no page here yet. Done, beside Postpone on each task, finishes it; it strikes through at once and leaves the list a few seconds later, and Reopen on it within that time puts it back if it was a slip. Tick Completed to see it again.
A task opened from somewhere else, such as a patient's to-do list or an email sent from a task, opens your list showing that task alone, unfolded. Show all tasks, above it, brings back the whole list, and so does searching, filtering or closing the list.
When payment requests are waiting for you, Payment run, on the top line of the list, lists them in place of your tasks, which come back when the run is cancelled or made, every payable one ticked, with the total of what is ticked underneath. All and None beside the heading tick or untick the lot, so a run of two or three is picked by pressing None and ticking those; name who pays by typing their name in Paid by and choosing them from the list, and press Create payment run, which stays greyed out until somebody is chosen and something is ticked; only the ticked requests go into it. Once the run is made, make the transfer and then press Transfer made: only then does the button to tell the payer on WhatsApp appear, because its message says the money has just gone. Nothing is sent until you press that button and send it in WhatsApp. Once pressed, the box says the payer was told and when, and the button becomes Tell them again. Pressing a request shows its money, log and attachment; Open expense there opens the expense on its own in a new tab, so the run stays as you left it, and the ticks you have changed are kept in this browser for the day even if you leave Start. Where the disbursement fee has been taken, Remove the fee pays that expense at its full gross instead; the payee's own arrangement on their contact card is not changed. A request whose expense is already paid is not in the run: Fedelsoft marks it done for you, with a line on its log saying why, and says which it closed. A request that cannot be paid is listed unticked with the reason underneath. A fee for an operation that is not on a list is one of them, because there is no surgery yet to pay for, and the task shows not on a list beside the operation. Where the invoice the fee came from is on a different operation, the reason names that operation's date and Move to that operation puts the request on it, after which it can be ticked. A request with a label on it is left out of the run, because a label means it has already been put into an earlier one; the run says how many were left out, and taking the label off brings a request back. To make a run of a set you have labelled yourself, search or filter the list down to them first, by typing the label in the search box or choosing it under Filter: Payment run then counts and lists only the payment requests the list is showing, labelled or not, and clearing the search and filters goes back to the unlabelled ones.
A payment run is a task given to whoever pays it. Open it in your list and each expense on it is listed with Mark paid beside it, for the one you have just sent; Mark all paid underneath marks the rest, and the run is finished once nothing on it is still owed. Remove beside an expense, while the run is open for editing, asks first and says it takes the expense off the run. An expense taken off the run, by mistake or on purpose, is listed under Taken off this run with Put back, which returns it to the run so it can be paid; one that has been paid since, or is on another run, says so instead. Its creator and whoever it is given to can do both.
Beside Filter, List shows the tasks one under another. Choose Columns by urgency, by when added, by who added, by type or by label and the same tasks stand side by side in columns, one for each urgency, each age (today, the last 7 days, the last 30 days, the last 3 months, older), each person who wrote them, each kind of task or each label, with the count at the top of each. Search and Filter still narrow what is shown, and a task opens in its column as it does in the list. Fedelsoft remembers the choice on the device you made it on.
A task headed Nightly job did not run, failed or did not finish names one of the jobs Fedelsoft runs overnight that went wrong, and the night. Nothing needs doing the first time: the task closes by itself on the first morning after that job runs cleanly again, and says which night that was. A task that stays open means the job is still going wrong, and is worth raising.
A Maintenance due task has Record beside its equipment. Choose the outcome, the date it was done and any notes, then Record: the maintenance goes on the equipment's log exactly as it would from the equipment's own page, and the reminder is done. A minor or major concern is also reported as an issue, with a task for whoever is responsible for the equipment.
A task can be put off to another day two ways, and both count as postponed. Overdue tasks are counted in the summary line so they are not lost in the list.
A task that is already postponed can be postponed again: choose paused under Show to see it, tick it, press Postpone in the bar, and the lengths in its list (1 day to 1 month) count on from the day it was already put off until, so it goes further rather than coming back sooner. Where you are the only person on a task, a new date replaces whatever it was put off until before, however it was put off. Where the whole task was put off by somebody else on it, their date still stands for everyone, and the page says so.
Reassign hands a task to somebody else who works at the organisation now, and anybody not on the list is named underneath with the reason, so a colleague who is missing is explained rather than simply absent. Somebody who has left is not offered, and each name shows their role at that organisation. On a task nobody raised, which is one Fedelsoft made itself such as an expiry reminder, anybody on it who is not alone on it also has Remove me, which takes them off and leaves it with the others, and Adopt, which takes everybody else off and leaves it theirs. A task a person raised has Reassign only. Both are written on the task's log with your name.
Somebody's open tasks can be handed on together from their contact page, by a holder of the Senior Manager or Financial privilege: the Open tasks fold lists them by kind (document reminders, documents to read, payment requests, patient portal requests, recovery diaries and the rest), each kind with its own Give to and Hand on, so one kind can go to one colleague and another to someone else. Only people working at the task's organisation now can be given it (a document reminder that names no organisation belongs to the document's), and anything that could not be handed on is named with the reason. The fold also lists the documents they are named on as Author or Responsible Person, whose reminders would otherwise keep coming to them; Hand on there puts the chosen person in their place on each, with the same roles. Ending a role or removing one there, while they still hold open tasks, opens this fold with a word saying so. Each task's log says who it was handed from and to.
Open a task and it shows any messages sent about it, oldest first, with who sent each and to whom and the time on the practice's own clock. Underneath, write a message and tick who it goes to: whoever raised the task, anybody else it is assigned to, or both. These are the same messages the old system holds, so what you send reaches people the way it always did. A task with nobody else on it does not offer this, because there is nobody to send to.
A message sent to you is counted on the Messages tile on Start, with who sent the latest and when, until you have read it, whatever has happened to its task since, so a message is not lost when somebody finishes the task it was on. The Messages window shows the unread ones, newest first, with a box to search them. Open task shows that task on its own, whatever search or filter the To do list had, among the completed ones if it has been finished, and opening a task marks the messages to you on it as read, here and in the old system alike. Reply opens a box under the message, addressed to the person who sent it, on the same task; Send delivers it as a message on that task, as the Message box on the task does, and marks the message you answered as read. Reply is not offered on a message that is not on a task or whose task has been deleted, and where the sender is no longer on the task, or two people on it share the name, nothing is sent and it says so, so you can answer from the task instead. Mark read clears one without opening anything. Read lists the ones you have read in the last two weeks, newest first, each still with Open task. The same message on the same task, from the same sender, shows once however many times it was sent, and Mark read reads every copy; a task's own messages show it once too.
On the task itself the conversation is under Messages, with how many there are, just below the task's dates, and Message about this task beneath it sends a reply to anybody on the task.
A task can wait for a reply. Tick Hide this task until they reply as you send a message about it, or open a task you have already written on and press Wait for a reply. It leaves your list and waits under Paused, saying waiting for a reply, until somebody sends you a message on that task; then it is back on your list marked reply in, and the message is in Messages as any other is. Opening the task ends the wait, and Stop waiting brings it back sooner. It is only your own list: anybody else on the task still sees it.
A task somebody sent you can be given your own name for it: open it and press Rename. The new name becomes the task's title on the list, and the title the person who raised it gave it is shown beneath it as renamed from, with who renamed it and when, so both of you can see both. The change is written on the task's log with your name and the time. Whoever raised a task changes its title with Edit instead.
A reminder that somebody's document has expired carries Chaser email and Send it now beside the document, to ask them for an up-to-date copy. Where that person's practising privileges here have lapsed, no chaser is offered or sent: the reminder says privileges lapsed and the date, with Close beside it, which finishes the to-do. A personnel record about somebody whose status here is not Active is not reminded about at all: overnight its expiry alert is switched off, any reminder still open for it is finished, and the record's log says why. The record itself is kept. A reminder for a document that has since been renewed is finished overnight, with a line on the record's log.
A reminder that a policy, guideline or other written document has expired shows an AI review of it, usually drafted overnight: what changed and why, the proposed document, which you can read and edit where it is, and a next review date, suggested from how fast that area changes and what a stale copy would cost, with the reason beside it. Approve puts the document in place, sets it as reviewed today with that next review date, keeps the previous text on its log, and finishes the reminder. Review again asks for a fresh review; one not yet drafted has Review with AI. Either first shows the instructions the AI will be given, which you can change or replace with your own before pressing Review; Standard instructions puts the usual wording back, and the review takes about a minute. Personnel records are not reviewed this way; they are asked for from their person.
When a policy or any other document the organisation holds expires, the people named on it as its Author or Responsible Person are given the reminder and are emailed about it too, from the organisation that holds it, once a week until it is renewed, five times at most. The email has Open the record under each document, which opens it in Fedelsoft, after signing in if need be, to upload the new version and set the next review date. Somebody with several documents due at one organisation gets one email listing them all. A document naming nobody as Author or Responsible Person goes to the first person linked to it. Somebody whose practising privileges there have all ended, or who has no email address, is left off the email, and the document's log says who and why; every email sent is on the log too.
Whether a patient is ready for their operation is checked every night, so the readiness task no longer comes to you. A patient is ready with two consultations with their surgeon in the year before (one booked counts), a quote marked accepted, the information sheets and consent forms their pathway names before its operation stage, and clinical photographs filed. What is missing is acted on: the patient is emailed to book their second consultation or accept their quote on the portal, and if nothing has changed five days later reception is given a task; the pathway's information sheets are given and its consent forms built into a consent document, both on the patient's portal; a consent not yet signed gets one reminder, and never holds anything up, since consent is taken again on the morning; a pathway that names no information or consent is put to its owner; no photographs once the consultations are done is put to the surgeon. Each step is on the patient's log, and readiness tasks for operations already done or cancelled are finished with a line saying so. This is done only for the patients of a surgeon who has switched on Readiness for surgery on their contact card, which they or a Director, Senior Manager, Human Resources or Admin can do, and which is off until somebody does; for any other surgeon nothing is emailed and no task is raised, and the same goes for the task raised when a patient accepts a quote on their portal, which also needs the operation's surgeon to be switched on.
A patient on no pathway for their operation is asked about where it can be answered. If a consultation with their surgeon is booked before the operation, no task is raised: on the day of that consultation, the appointment's page opens with Not on a pathway, the operation, and the pathway Fedelsoft suggests already picked, learned from the procedures of the surgeon's earlier patients on each pathway; where nothing matches well enough, nothing is picked and you choose. Add to pathway puts them on it, or pick another first; Not now leaves it until the page is next opened that day. Only where no consultation is booked before the operation is the surgeon given a task, Not on a pathway, linked to the operation and the last two consultations, with the same suggestion and Confirm on the task itself, which puts them on the pathway and ticks the task. A task raised before a consultation was booked, or before a pathway was chosen some other way, is finished overnight. Either way it is written on the patient's log.
A personnel record, or any other record that names a Subject, about somebody whose status here is Active is chased by itself, and nobody is given a reminder for it. When it expires, the person it is about (its Subject, or on a personnel record that names none, its Author) is emailed for the up-to-date copy, with a link to a page where they upload it or say why they cannot yet and by when; five follow-ups go a week apart until they do one or the other. An upload pauses the chase for a month and gives the organisation's compliance leads a task to check it and move the expiry on, and the upload is under Documents on the record; only a file the person sends counts as an upload; a reason pauses it until the date they gave, and the reason is on the record's log. If nobody answers the last follow-up within a week, somebody with no clinic, theatre list or operation here in twelve months has their practising privileges here ended, as Has left records it, and somebody still practising is given to the compliance leads as a task. The leads, and anyone set to be copied, are told either way. Every request and answer is on the record's log.
One person has one record of each document here. Overnight, two live personnel records for the same person with the same title and kind are merged into the one with the later expiry: the other's files move to it, the other goes to the recycle bin and its reminders are finished, and both logs say so. References are the exception, because two are needed. New on a contact's page opens the record they already have rather than making a second.
Tasks you raised and gave to somebody else sit behind the with others box, under Filter, out of your own count, so you can still open them and read any reply. That holds even where you are also named on one beside them: the person who raised a task is not one of the people it is for, so it is counted as with the others and your name is not listed among them. A task you raised for nobody but yourself stays on your own list. When the people you gave one to finish it, a message saying so, and who finished it, arrives in your messages, so you can pick up whatever comes next. You are not told about a task you finish yourself.
Every task Fedelsoft raises goes to somebody. Where nobody is named for a task, it goes to whoever allocates tasks at the organisation: every director there who uses Fedelsoft, or every manager who does where no director does. Somebody who has never signed in to Fedelsoft is passed over, since they would never see it. It stays with all of them until one gives it to whoever should do it, and says so at the bottom. Where the organisation has neither, it goes to the surgeon or practitioner on the operation or appointment it is about, and says why. Where there is nobody even there, it goes to one named fallback person, and names the kind of task so these can be sorted out by kind. A task you raise for yourself with nobody else on it stays yours, as before. Somebody who has switched a kind of task off is not handed it by any of these.
Some tasks close themselves overnight, once the job they are about is over: a booking form task when its operation has taken place or been cancelled, a request to pay when its expense is paid, and an invoice task when the invoice is paid, written off or not for payment. A task given to several people stops waiting for anyone who has left: their part is ticked for them, so the task closes once everyone still here has done theirs, and a task given only to people who have left stays open with whoever raised it. The task's log says what was done and why, and nobody is sent a message about it.
A recovery diary task shows a small table of pain and swelling by day, today's entry last, with a line saying which way each has gone since the first entry. Above it the diary itself: the patient's name, which opens their record, the day after the operation and the date, pain and swelling out of 10, the other answers in brief, and whether the entry was escalated and by which rule, with the drafted reply to the patient beneath it, its subject opening it. A line underneath traces the earlier entries for the same operation, and Earlier entries unfolds them. Where what the patient wrote is longer than the line allows it is shortened, and Show all beside it puts the whole of it on the page, so their own words never need the old system to read. Needed someone today? records your yes or no against the diary, with your name and the time, and Clear takes it back to unanswered; every answer, change and clearing is kept with the name and the time, so the escalation rules can be checked against the people who read the diaries.