Loading…
Onsite visit schedule & annual client deadline view
Loading…
Use your Myconsult Google account.
A name and a date, and nothing more. Holidays are shown for context on every calendar — they do not block bookings, nobody is attached to them, and they count towards no hours. A client visit can still be booked on one.
Each year is entered on its own. Most holidays here move every year, and even the fixed ones shift when they fall on a Sunday, so there is no yearly repeat to get quietly wrong.
| Date | Holiday | Added by |
|---|
Hours from onsite calendar appointments are generated automatically for the month shown. Add manual entries for work that is not on the calendar — backlog, audit prep, ad hoc. Overtime is anything after 17:30.
| Date | Team Member | Client | Time | Regular | OT | OT Status | Source | Notes |
|---|
A client becomes bookable through its engagements — the service types listed against it. Adding a company on its own is not enough; open it and add at least one engagement. Nothing is ever deleted: an inactive client keeps its history and disappears from the pickers.
A group is a record, not a label. Rename it here and every client in it follows — nothing has a copy of the old name to be left behind. A client belongs to one group or none, chosen when you open the client.
| Client | Short form | Group | Services | Year end | Engagements | Status |
|---|
Every client’s services are worked out from the engagements booked against them, through the mapping below. Change a mapping here and every client using that engagement type follows at once. A client that needs a service its engagements do not imply — or needs one taken off — is amended on the client itself.
| Service | Engagement types | Clients | Status |
|---|
Every engagement type in use. The cadence stays on the engagement — “Acc - Qtrly” is still quarterly on the record and on the calendar chip; this only decides what it rolls up to.
| Engagement type | Engagements | Counts as |
|---|
Activity types are never deleted, so past appointments keep their label. Retiring one removes it from new bookings and leaves existing appointments untouched.
| Name | Description (calendar chip) | In use | Status |
|---|
Pick a colour to fix it for that person. Anyone without one is given a
colour automatically from their account, which stays put when somebody
new signs in. Roles and capabilities are granted from the command line
with npm run users.
| Colour | Name | Capabilities | Colour source |
|---|
Groups of people a meeting can be booked against, instead of naming everybody. Somebody can be in more than one. A department cannot be retired while it is still invited to a meeting that has not finished.
A WFH day is granted by an admin and cannot be moved by the person it belongs to. A client visit on that day always takes priority — the WFH day steps aside for that date only, and the weekly arrangement carries on. To change day, ask: it goes through the same approval.
| Name | Day | Since | Granted by |
|---|
Anything you would like this app to do. Everyone can see the whole list and vote for what they want; an admin sets the status. Nothing is hidden once it has been decided — a declined idea stays here saying so, with the reason, rather than quietly disappearing.
Loading…