User manual & FAQ

How AuditSchedule works, feature by feature. This is the same reference available inside the app, published here so you can read it before you sign in.

Getting started

What is AuditSchedule used for?

AuditSchedule is a tenant-specific planning workspace for internal audit teams. It combines people, projects, allocations, leave, holidays, travel, events, conflicts, approvals, analytics, capabilities, permissions, settings, and billing into one live scheduling system.

Something went wrong while I was signing up or creating my workspace. What do I do?

Both onboarding steps carry a support link, and it becomes more prominent when an error is showing. If the account step reports a problem, check the wording first: an invalid password, an email that already has an account, an address that was never confirmed, or unaccepted terms are all fixable on the spot, and a confirmation email that has not arrived can be re-sent from the same screen, in either sign-up or sign-in mode. Re-sending never changes the password on a pending account, so if someone else has tried to sign up with your address, the password you chose is still the one that works. If we say we can no longer deliver to your address, that one will not work no matter how often you retry: sign up with a different address or write to support@auditschedule.com. If workspace creation fails, the message may include a reference code. Email support@auditschedule.com using the link on the page, which prefills the workspace URL you tried, the reference, and the time, and we can create the workspace for you.

I clicked the confirmation link in my email. Why does it ask me to confirm again?

The link opens a page with a single Confirm my email address button, and pressing it is what actually confirms you. That extra press is deliberate. The link works only once, and many corporate mail systems open every link in an incoming message to scan it, which would use your link up before you ever clicked. Waiting for a real press is what keeps the link yours. Once you press it you go straight on to workspace setup. If confirmation fails because of a connection problem, a temporary service failure, or too many requests, wait a moment and press the same button again; you do not need another email. If the page says the link is invalid or has expired, request a new one.

The workspace URL check could not finish. Can I still create my workspace?

Yes. The availability check stops waiting after ten seconds and shows "Could not check availability. You can still continue." Enter a workspace name and valid URL, accept the terms, and press Create workspace. The server checks the URL again when creating the workspace and reports if it is already taken. If it says the workspace is still being set up, that is your own create still finishing: wait a moment and press Create workspace again, and do not change the URL. If the workspace was created but your session could not be activated, sign in again to continue. If we cannot confirm whether setup completed, try signing in; if you still cannot access the workspace, contact support with the reference shown on the page.

What are the password rules, and why was my password refused?

A new password needs at least 8 characters, an uppercase letter, a lowercase letter and a number. A symbol does not count in place of the number. The limit is 72 characters, and fewer if the password has accents or emoji, because those take more room. A password that meets all of this can still be refused if it has appeared in a known data breach, so choose a different one. The rules apply whenever a password is set. A password you already have keeps working, even if it would not meet them today.

I am sure my password is right, but sign-in says my email or password is wrong.

Check whether you ever confirmed your address. An account that was created but never confirmed cannot sign in, and that is a separate thing from a wrong password. Sign-in now says so directly: on the sign-up page it offers a Resend confirmation email button in the same message, and on the login page it links you to the page that can send one. Press it, open the link, press Confirm my email address, and sign in as normal. Re-sending does not change the password on a pending account, so the one you first chose is still the one that works. If the message says your email or password is wrong instead, that is what it means: use Forgot your password to reset it.

I have an account but never finished creating a workspace. Why can I not sign in?

You can. Signing in with an email and password takes you back to workspace setup, and so does Continue with Google. Google used to sign you back out at that point and ask you to accept the terms again, which was wrong when you had already accepted them; it now recognises the acceptance already on record and returns you to the setup step you left. Fill in the workspace name, URL and work week and you are through. If you are genuinely being asked to accept the terms, it is because we hold no acceptance for your address, and ticking the box is what records it.

Why do I have to accept the terms to continue with Google when I already have an account?

Google does not tell us whether your address already has an account, so the button creates one when there is not, and we cannot accept a new account without a recorded acceptance. Ticking the box costs you nothing if the account already exists, and it is what stops a first-time Google sign-in from being turned away after the fact. Signing in with an email and password does not ask, because it only ever reaches an account that already exists.

How do I move between features?

Use the left navigation. Your visible menu is permission-based, so it only shows modules your organization role can view. The main modules are Grid, Tasks, Overview, Events, Dashboard, Approvals, Conflicts, Travel, Leave, Capabilities, Manage, and Settings.

Why do I see different pages or buttons than someone else?

Access is controlled by base role and named organization role permissions. A module can be view-only, editable, or hidden. Some modules can also be scoped to All, Team, or Own records, which limits what a linked user can see or change. Admin-level users normally have broad access; custom roles can grant or remove view and modify rights per module.

Where is billing now?

Billing now lives inside Settings as a Billing tab. Users with billing permission also see a lower-left billing status row. If billing becomes overdue or blocked, the workspace directs users to Settings so billing can be fixed.

Is there a guided setup for a new workspace?

Yes. The Guided Tour link in the sidebar opens a setup checklist that walks you through getting a workspace running in five steps: upload people, upload projects, bulk allocate, fine-tune allocations on the grid, and grant access. Projects unlock once people exist, and the two allocation steps once projects exist; granting access is open from the start so you can invite a colleague to help with setup. Each step tracks live progress from your real data (for example how many people or allocations exist) so you can see how many steps are complete. An "Explore further" section adds optional tours for customizing your workspace in Settings, Events, Travel, Leave, Capabilities, Approvals, Conflicts, and Dashboard.

Can I try the app with sample data first?

Yes. In a workspace with no active people and no projects, users who can edit in Manage see "Load sample data" on the Guided Tour: eight sample people, six projects marked "(sample)", and several months of allocations starting two months ago, including one over-allocation so the Conflicts page has something to show. While it is loaded, a "Remove sample data" button appears on the Guided Tour and at the top of Settings (Settings stays reachable even when an ended trial has paused the workspace). Removing deletes exactly the people and projects that were loaded (with their allocations) and also removes a sample person or project you edited. Anything you added yourself stays; if it named a sample person as director, team manager or line manager, or a trip was linked to a sample project, it keeps its place with that field cleared. Sample data cannot be loaded once billing has been set up (a checkout started or a subscription created), and a subscription cannot be started until the sample data is removed, so you are only billed for your real team. Under a plan lock, loading is refused for anyone the lock applies to if a locked period that ticks Projects covers the months the sample is loaded into, and removal is refused for them if it would remove or change anything the lock covers, such as the leave of a sample person inside a locked period or a locked project that a sample person is director of. The lock does not hold back administrators or the roles that keep access, though they still need edit access to Manage, and the other conditions above still apply.

What emails does a new workspace owner receive?

When a workspace is created, its owner gets a welcome email with the workspace address, the trial end date, the three steps to a working plan (add people, add projects, allocate) and a link to the Guided Tour. If the workspace still has no active people 3 days after signup, its admins get one reminder to add their team (sent once, and not after the first 14 days). Trial reminders are covered under Billing. Replies to these emails go to support.

I'm a member of someone else's workspace. Can I start one of my own?

Yes. Each account can own one workspace of its own, and being a member of other people's workspaces does not count against that. If you open Start free trial while signed in, you are asked whether to open the workspace you already belong to or create your own, which gets its own free trial. Your access to the other workspace stays as it is. Once you belong to more than one workspace, signing in asks which one to open. If you already own a workspace, Start free trial takes you straight back to it instead.

Why does the Plan Grid say my plan is empty?

The Plan Grid shows "Your plan is empty" while the workspace has no people at all (a workspace whose people are all inactive still shows the grid, where Show inactive reveals them). Users who can edit in Manage get buttons to open the Guided Tour or go straight to adding people; everyone else sees a note that the workspace admins have not added anyone yet. The grid appears as soon as the first person is added.

What are the in-page tooltip walkthroughs?

Each Guided Tour step links into the relevant page and starts a short tooltip walkthrough that highlights the key controls in place: where to upload people, how the five Bulk Allocate steps work, or how to edit dropdown options and color defaults in Settings. Use Back, Next, and Done to move through a walkthrough, or close it at any time. They are launched from the Guided Tour rather than shown automatically on every visit.

Is there an in-app help assistant?

Yes. A round help button with a robot-reading-a-book icon sits in the bottom-right corner of every workspace page. Open it to ask questions about how AuditSchedule works in plain language; it is an AI assistant that answers from this manual and, when relevant, offers a button to jump straight to the right page. Because it relies on your own role, it explains where a feature lives rather than promising you can access it, and it does not change any of your data. If it cannot answer something, it points you to the Feedback button or a workspace administrator.

How do I send feedback or report a problem?

Use the Feedback button at the bottom of the left sidebar. It opens a short form for sharing suggestions, questions, or issues with the team. It is available to every signed-in user regardless of role. After sending, you can track your feedback on the Feedback tab of My Profile, where each item shows its current status and any reply from the team.

Can I see the feedback I have already sent?

Yes. Open My Profile (click your name near the bottom of the sidebar) and select the Feedback tab. It lists every rating and message you have sent, each with a status badge (New, Planned, Done, or Won’t fix) and, when the team has replied, their response shown beneath your message. Use the All, Unresolved, and Resolved buttons to filter the list; Resolved covers items marked Done or Won’t fix, and Unresolved covers items still New or Planned. You can link straight to it at /profile?tab=feedback.

Can I use AuditSchedule on my phone?

Yes. On a phone the sidebar opens from the Menu button, and a tab bar along the bottom of the screen holds the Plan Grid, Leave and Approvals (with its count of requests waiting). If you cannot see one of those pages, Travel, Overview or Events takes its place. List pages such as Leave, Travel, Approvals, Conflicts, Capabilities and Manage show each record as a card; tap a column name at the top of the list to sort by it. On the Plan Grid, the layer toggles and filters sit behind the Filters button at the top, which shows how many of them are hiding something from the view; tap Hide filters to close them again. Select and Legend stay beside it. On Manage, choose a section from the dropdown at the top. On Overview and Events, tap a bar or an event to see its details at the bottom of the screen, and tap anywhere else to close them. Building a plan is easier on a larger screen, but everything works on a phone.

Where do I see my own schedule and details?

Click your name near the bottom of the sidebar to open My Profile. It shows your person card (team, role, location, access role, and active status), your current, upcoming, and past projects and events, your recorded skills and certifications, summary stats (projects, man-weeks, leave days, holidays, and travel trips) for a date range you choose. A separate Feedback tab lists the feedback you have sent with its status and any reply from the team. If your account is not yet linked to a person record, the page asks an administrator to link it under Manage > People.

Grid

How do I read the allocation grid?

Rows represent people and columns represent time. Project pills show scheduled allocation, leave badges show time away, holiday styling marks public holidays, travel icons show planned or confirmed trips (only for the people your Travel access covers, and none if you have no access to Travel), event pills show organization events, and red cells indicate over-allocation conflicts. Amber cells are conflicts that were accepted on the Conflicts page; hover one to see who accepted it and when. Hovering a project pill, leave badge, holiday badge, travel icon, or event pill shows its detail. On a touchscreen, tap a leave badge, holiday badge, travel icon, or event pill instead and the same detail stays up until you tap elsewhere. Tapping a project pill is different: if you can edit the grid it opens the cell editor, which shows the same detail and lets you change it, and if you cannot it shows the detail like the other markers.

How do I change the grid display?

Use the layer toggles to show or hide Projects, Leaves, Holidays, Travel, Conflicts, Events, and Notes, and Tasks if you can view Tasks. Group people by project, director, team manager, or location, then sort by name, location, team, or role. Four checkbox filters sit beside them: Project Category, Roles, Team, and Line Manager. They all work the same way: a ticked box is shown and an unticked one is hidden. Project Category hides the allocations of projects in an unticked category; the other three hide people. Line Manager shows each ticked manager together with everyone who reports to them, directly or further down the line. Once anything is unticked, the filter button shows a count of what is still ticked. Each list has Show all, which ticks everything again, and Untick all, which starts from nothing so you can tick just the ones you want. With nothing ticked in Roles, Team, or Line Manager the grid shows no one; with nothing ticked in Project Category the people stay but no project allocations are drawn. The starting selection for Project Category and Roles comes from Settings > View Defaults, and your filters are remembered on this browser. A team or manager that appears later (for example a new team) starts unticked if you had unticked any, until you press Show all. You can also show inactive people and allocation percentages.

How do I see a summary of one period on the grid?

Right-click a column header (or long-press it on a touchscreen, or press the context-menu key on a focused header) to open a summary of that month, week, or day. It counts only the people in the grid’s current view, so your people, role, and inactive filters and any grouping and its filters all apply; people in a collapsed section still count. It shows who is off (people, leave days, and how many have leave awaiting approval), who is travelling, public holidays and how many people they affect, who is over-allocated, the projects with allocations in the period, events that involve someone in view, and unallocated capacity in FTE with the people who have no allocation at all. Projects with allocations lists only projects someone in view is allocated to in that period: a project nobody is allocated to is left out, and allocations still awaiting approval are not counted. Projects in a category you have hidden are left out of that list but still count against capacity. Click any figure to expand it in place and see the people or records behind it. Clicking a person jumps to their cell, and Show only these people in the grid narrows the grid to that group; clear the people filter to see everyone again. If a plan lock hides part of the period from you, the summary says some figures may not be counted. Sort by availability and Clear sort are at the bottom of the summary. Press Escape or click elsewhere to close it.

How do I filter the grid to certain people?

Use the Filter people button in the Person column header. Click it to open a list with a search box and a checkbox per person; tick as many as you like and the grid shows only them. When the list opens, the people already selected are at the top under Selected, with a Clear all link, and everyone else is below; the order holds while the list is open, so ticking someone does not move them. Typing a name narrows the list, and pressing Enter ticks the person when only one matches. The button reads the person’s name when one person is selected and a count such as 12 people when more are; hover it to see who is selected. The x next to it clears the filter. Your selection is remembered on this browser.

How do notes work on the grid?

Turn on the Notes layer toggle (next to Events) to show note markers in the grid. Anyone who can view the grid can add a note: hover a person and period cell, click the note icon, and write the note. You then answer two separate questions. Who can see this note (everyone with grid access, or only the people you name) and who needs to act on it, chosen as specific people and/or whole roles. The two are independent, so you can post something the whole team can read while asking only one person to do something about it. When you choose everyone, the label tells you how many people that actually is before you commit to it. Sharing with everyone also offers Require acknowledgement: the note then stays in each person’s badge until they press Got it, rather than clearing when they simply open it, and you get a list of who has confirmed and who has not. A note shared with everyone stops counting toward people’s badges once it expires (the end of the period it is pinned to, or thirty days, whichever is later), so an old announcement cannot keep nagging someone who was away when it went out. Notes addressed to named people never expire; those stay until closed. A small chat icon appears in cells that have a note. Open the note to read it and exchange comments with anyone who has access. The note details show who wrote it and how long ago (hover the relative time for the exact timestamp), and a View in grid button that jumps back to the cell the note is anchored to. Only the note author can edit the note text or change who can see it after it is posted. Any recipient can close a note (closed notes switch to the closed color set in Settings > Color Defaults); only the note author can delete it. The Notes button in the left sidebar opens a panel listing every note available to you, and shows a badge counting only the notes that need you. The panel groups them the same way: Needs you, Other notes, and Closed. A note addressed to you (one you wrote, one that names you, or one aimed at your role) counts until it is closed. A note shared with everyone that is not addressed to you counts only until you have read it: opening it clears it from your badge, and Mark all read at the top of the Needs you section clears the rest in one go. Where a note does both (everyone can read it, and it names you or your role), being addressed wins: it stays until the note is closed, and Mark all read leaves it where it is rather than pretending you have dealt with it. Unread shared notes are shown in bold with a New marker, so a note that has already been round the team stops competing for attention with the ones still waiting on you. Editing a shared note does not put it back in anyone’s badge: people who already read it are not asked to read it again, so correcting a typo will not re-notify the whole team. If a change genuinely needs everyone to see it, post a new note. Notes live in the app. Nobody can email a note directly to somebody: what reaches people by email is their own summary, set up under My Profile > Notifications, which lists the notes addressed to them alongside their approvals and conflicts. A note shared with everyone that does not also name them never causes that email, and appears in it only if they have switched announcements on there. The open and closed marker colors are configured in Settings > Color Defaults > Notes.

What does the View in grid button do?

It jumps the Plan Grid to a particular person and period and flashes that cell. You get the button in note details (open a note from a grid marker or the Notes panel), on each row of the Conflicts page, and on the Allocations, Leaves, and Travel tabs of the Approvals page. The grid switches to the view, year, and month the cell belongs to before flashing it. If the person is on the grid but their row is hidden by your current filters, the grid relaxes those filters rather than failing: first it shows inactive people, un-hides that person’s role, adds them to the people filter (the Filter people button in the Person column header), ticks their team in the Team filter and their nearest line manager in the Line Manager filter, and expands the collapsed sections that person sits in, and only when every one of them is collapsed, since a single open section already shows their row, so the rest of your collapsed sections are left as they are. If that still is not enough it clears the grouping and its section filters, because a grouped section only lists people allocated to that section’s project and so has no row for an empty cell. It stops as soon as the cell is visible, so the second step only happens if the first was not enough, and a message tells you what moved. A filter that was relaxed stays relaxed once the jump succeeds, because putting it back would hide the cell you just jumped to. If the jump still fails nothing is kept: every filter is put back exactly as it was. When the cell simply is not in the current grid (a period outside the loaded range, or a weekend hidden by work-week-only display), your filters are left alone and you are told the cell is not shown in this view instead.

What are month, week, and day views for?

Month view gives the annual plan, week view gives near-term scheduling detail, and day view gives the most granular availability picture. On the current year, month view opens scrolled to the current month and week view to the current week, so you start at today rather than January; scroll left for earlier periods. Other years open at the start. If work-week filtering is enabled in Settings, day view can hide non-working days across allocations, leave, holidays, and travel. To see another year, use the arrows either side of the year, or type a year from 2020 to 2040 into the year field: the grid loads it once all four digits are in, and an unfinished entry goes back to the year on screen when you leave the field or press Escape.

How do allocation phases and inherited allocations work?

Allocations can have phases such as Planning, Fieldwork, and Reporting. When an allocation created at one granularity appears in another view, it is shown with the configured inherited-allocation style so planners can tell it came from a coarser or different time level. In the cell editor, an inherited row is marked with an inherited badge; hover it to see where the value comes from. Where the cell averages finer records, such as a month cell fed by week allocations, changing the phase or team applies to those records and leaves the weeks as they are, while changing the percentage replaces them with one value for the whole cell. Where the value comes from a coarser record that also covers other periods, any edit creates an override for this cell alone and leaves the coarser record untouched. Removing a project from one week of a month allocation converts the month to weekly allocations: the other weeks keep their percentage, phase and team, weeks with their own value keep it, and a toast confirms it. Week and month cells, conflicts and dashboard figures do not change apart from the week you removed. Man-week totals on a person’s profile count a month by its calendar days, so they can move by a different amount, and dates worked out from allocations can move to the Monday of the first week and the end of the last. This also applies when the week has a value of its own, so the trash icon empties the week; to go back to the month’s percentage, type it in instead. If the month cannot be converted because of an open approval request, removing a week’s own value takes the week back to the month’s percentage instead, and a message says so. You can remove several weeks at once with Multi-select, and months that have to be converted are converted the same way. In Day view, days at the edge of the month can read differently afterwards, because a weekly allocation runs Monday to Friday: days before the month’s first Monday lose the allocation, and days of the next month in the last week take its value. When your workspace requires approval for the change, the conversion goes to an approver as one request: the month stays as it is, the week shows as a pending removal, and approving converts the month while rejecting leaves it alone. If the allocation or another week of that month already has an approval request on it, it cannot be converted, so you are asked whether to remove the whole month instead. Removing a day from a month or week allocation in Day view also asks first, and removes the whole allocation. When a cell averages finer records in more than one phase, for example a month whose weeks move from Planning to Fieldwork, its pill is drawn in bands: one per phase in time order, each in that phase’s style and as wide as its share of the cell, so a phase that comes back later gets a band of its own. Hover the pill to see Mixed phases and each phase’s share of the percentage. With the outlined inherited-allocation style the pill stays a plain outline.

Does the cell editor show leave, holidays and travel?

Yes, and you can change them from there. When you click a cell that has allocations, the cell editor shows that person’s leave, public holidays, and travel for the period in a Time away this period section at the foot of the editor, below the allocation rows and the project search box. Each kind gets its own labelled group: the Leave group lists each booking as one row with its type, number of days, dates, and status, the Public holidays group lists each holiday with its date, and the Travel group lists each trip with its status, destination, length, and dates. Anything awaiting approval carries an Awaiting approval badge on its row. Public holidays are matched on the person’s country, so when no country is set the section says so rather than showing none. A cell with no allocations opens the project picker rather than the cell editor, and the picker carries the same Time away this period section under its project list, above its Add Leave and Add Travel buttons, with the same groups, badges, and edit and delete buttons, so leave and travel can be corrected from a cell that has no projects on it. Deleting from the picker closes it, unlike deleting from the cell editor, because the picker is pinned to the cell you opened it from and the grid reloads underneath it. Leave and travel rows have edit and delete buttons when you have modify access to that area for that person and the period is open. Editing opens the same compact form as Add Leave or Add Travel, pre-filled with the record, and replaces the cell editor, so if you have unsaved allocation changes you are asked first. Because travel is stored as one record per traveller, editing a trip opens the whole trip rather than one person’s share of it: the Travelling box lists everyone booked on it that you have access to change, so a change to the destination, dates, or any other detail moves them all together instead of splitting the trip in two. Remove a name there to delete that person’s record, or search someone in to add theirs, exactly as on the Travel page. If someone on the trip is outside your access, the form says how many rather than naming them, and warns that their records stay as they are, so use the Travel page or ask an administrator when the whole trip has to move. Deleting is the opposite and stays with the one person: it takes them off the trip and leaves the other travellers’ records untouched, which is what its confirmation names. Deleting asks to confirm and then reloads the grid with the editor still open. Two limits, both about leave being stored one day at a time and grouped into runs for display. A run that reaches the edge of the period you opened may continue into the next one, so its dates are locked in the form and a link points you to the Leave page to move them; its type, status, and notes can still be changed there, and deleting removes exactly the days the row listed. And when a plan lock window starts or ends part-way through the period you opened, the buttons are withheld altogether, because the editor may be holding only the part of a booking that window leaves visible or writable. A trip is judged on its own dates as well, so one that runs out of the period you opened and into a locked window loses its buttons even when the period you clicked is open. Use the Leave page or the Travel page in that case, where each day is handled on its own.

What does the percentage bar in the cell editor mean?

It is a plain 0 to 100 percent scale of that person for that period, so a bar filling the whole track means fully booked. Past 100 percent the bar stays full and turns red, and the exact figure is beside it; the Conflicts page carries the detail of what overlaps. When the person has time off in the period, a hatched band marks that share at the right of the track and a line beneath reads, for example, Away 6 of 22 working days, with a note of how many of those days are still awaiting approval. Working days come from the work week configured in Settings, and leave awaiting approval counts as time away, the same as it does on the grid and the dashboard. That line counts days and stops there: it gives no share of remaining capacity, and it never restates the allocation against the days left. An allocation percentage is a share of that person rather than a draw against a budget, so time off lowers what a booking delivers instead of capping it. That is why the Dashboard scales its person-weeks down by the same days off, and why the Conflicts page ignores leave entirely and flags a week only when the percentages across projects add up to more than 100. The one exception is a period the person is away for entirely, where the line also names what is booked, for example Away 22 of 22 working days, allocated 100% while away. Note that the analysis export takes the other view on purpose: its Capacity & Utilization sheet divides allocated man-weeks by available ones, so it reports a booking that outruns someone’s remaining days as over-allocated. That is a reporting measure for planning capacity, not the same judgement the grid makes.

How do editors update allocations?

Users with Grid modify permission can edit cells directly. Multi-select mode lets editors add allocations, apply a phase, or remove allocations across multiple cells. The percentage field controls the amount of capacity assigned to the selected project and period. A percentage must be above 0 and no more than 100, and decimals are allowed. You can clear a percentage field and type a new value; while a field is empty or out of range it is outlined in red, and Save changes in the cell editor, Add in the cell editor, and Allocate in multi-select mode wait until it is fixed. In Month view, Allocate in multi-select mode leaves out a month where the person is planned week by week on that project (for example after a week was taken out), so a removed week stays empty; the other selected cells are still allocated, and a message names the month. Use Week view to change those weeks.

How do I add someone to a project from the grid?

Group the grid by project. Under each project section, editors see + Add person. It lists the people shown on the grid who have no allocation to that project in the period on screen, with how much of their capacity is free over the project’s dates within that period, the most free first; type to search. Picking someone adds an empty row for them at the bottom of the section, marked Not allocated yet. The row is not saved on its own: click its cells to allocate as anywhere else on the grid, and the project is offered first. Once they have an allocation to the project they become an ordinary row in the section. The x on the row removes it, and an added row that never got an allocation is gone when the page reloads. On the new row, copy from… copies another person’s allocations on the project. It offers the people with approved allocations on the project in the period shown, outside any locked planning period, with how far those run and their average there. Picking one previews their allocations on the new row. Click a cell to leave out the allocations behind it, or click again to put them back; an allocation covering several cells goes out or back as a whole. Scale sets a percentage of the original to copy, rounded to whole numbers; one that scales to 0% is not copied. The bar warns when the copy would take the person over 100% and says what was not copied: allocations awaiting approval or rejected, ones you left out, and ones in a locked planning period. Copy saves everything in one go, each with the same period and phase as the original and the scaled percentage, and the team too where the original set its own team. If your workspace requires approval for allocations, the copied ones wait for it like any other. Cancel or Esc ends the preview without copying. A copy of more than 500 allocations is refused, so leave some out or narrow the grid to a shorter period.

Can I add leave or travel directly from the Plan Grid?

Yes, from any cell. You need modify access to Leave or to Travel; modify access to the Plan Grid itself is not required, and each button appears only for the one you have. If you can also edit the plan, clicking a cell that already has allocations opens the cell editor, which carries Add Leave and Add Travel in its footer beside Add Note, and clicking an empty cell opens the project picker, which carries the same two buttons under its project list, with anything already booked in that cell listed above them. If you cannot edit the plan, clicking any cell opens that picker with no project list, just the buttons you have access to. A period the plan lock has closed for leave or for travel drops that button on its own, so a window that freezes the plan can still leave both open. Each opens a compact form pre-filled with the cell period, in a single date field you can type over or re-pick from its calendar, so you can log a trip or leave without leaving the grid. Opening one from the cell editor closes it, so if you have unsaved allocation changes you are asked first, the same as when you edit a leave or trip from the Time away section. Leave is for the cell person only. Travel starts with the cell person in a Travelling box, and you can search there for anyone else on the same trip and add them, or remove the cell person, exactly as on the Travel page; each traveller gets their own travel record with the same destination, dates, and details. The optional Project field is a search box as well: type part of a project code or name to narrow the list instead of scrolling it, and use its clear button to record the trip against no project. The record is created the same way as on the Leave and Travel pages, so if your workspace requires approval it waits for sign off before it is confirmed, and if one traveller cannot be saved (for example someone outside your scope) the form says who was saved and who was not.

Why is there a dashed pill on the grid?

When your workspace requires approval for a Plan Grid change, that change shows as a dashed, greyed "ghost" pill that does not count toward capacity or conflicts, sitting next to the live allocation it affects (which stays on the grid and keeps counting). An hourglass marks a change awaiting approval; a crossed circle marks a rejected one, with its label struck through; and a pending removal is struck through with a trash icon. Hovering shows the status and what the change proposes, for example New allocation 50%, Capacity to 80%, or Removal requested. Editors can click the cell to open its editor, where live allocations are editable at the top and requested changes are listed below showing current to proposed; from there an editor can edit the live allocation to revise a proposal, or use Cancel to withdraw one. Approving or rejecting a change happens on the Approvals > Allocations tab. See "How do allocation approvals work?" for the full process.

What does the Legend explain?

The Legend is dynamic. It explains project colors, allocation phase styling, conflict styling, event styles, travel icons, holiday styling, leave styling, the shared awaiting-approval marker, and the dashed ghost pills for Plan Grid changes awaiting approval or rejected, using the organization color defaults configured in Settings.

Overview

What is the Overview page for?

Overview is the high-level timeline view for projects and events. It offers a Gantt-style view for schedule shape and an Outlook-style calendar view for calendar inspection.

What happens when Overview is scoped to Own?

Own-scoped Overview shows the linked user only when that person record is a Director. If the linked person is not a Director, the page explains that the overview is not available for that account.

How do I filter Overview?

Toggle Projects and Events, filter by project type when available, filter by director, and navigate by year. The arrows step a year at a time in the Gantt view and a month at a time in the Outlook view; in the Gantt view you can also type a year from 2020 to 2040 into the year field, and it loads once all four digits are in. The view the page opens in, whether Projects and Events start on, and which project categories and phases start ticked come from Settings > View Defaults > Overview, but users can change them during a session. The Phase filter narrows projects to the phases you tick: with every phase ticked (the default) each project is drawn across its full dates, and once you untick one, each project is drawn as its remaining phases instead, labelled with the phase name and with its own team member count, and a project with none of them is left out. The (no phase) entry covers projects with no phase recorded at all, which are drawn across their full dates while it is ticked. A phase runs across the dates set for it in Auto-Allocate, or otherwise across the approved allocations tagged with it, as one bar for each stretch of consecutive periods, so a phase worked in February and again in October shows as two bars. A project without both a start and an end date has no place on the timeline, so it is left out of both views, and so is an event with no dates at all. An event with only one of its dates is shown as a one-day event on that date, as on the Events page. A note above the timeline says how many of the projects and events your filters include are missing a date, and hovering it lists them with the date each one lacks (press Escape to close the list). Set the missing date in Manage to bring one back. With Overview access scoped to Own or Team, a project only reaches the Overview when someone in scope directs or manages it, or is staffed on it in the year you are viewing, so an undated project can be listed in the note for one year and not another.

How should I use Overview with Grid?

Use Overview to understand project and event timing at a glance, then use Grid to inspect who is assigned, how much capacity is allocated, and whether leave, holidays, travel, or events create availability pressure.

Events

What is the Events page for?

Events shows organization-level activities in month, week, day, and Outlook-style calendar views. It is useful for leadership meetings, training windows, audit committee dates, reporting milestones, or other context that should sit beside the project plan.

How do I move between month, week, and day views?

Use the month, week, and day buttons at the top, or drill in by clicking a period header: in month view click a month header to open the full year of weeks scrolled so the week holding the 1st of that month sits at the left edge, and in week view click a week header to zoom into that weeks days. A year can begin with a week that starts in the December before it; that week is shown in both years, with both years in its title and month headers. The arrows step through years. Clicking an event name or colored bar opens the event details instead of drilling.

Why do I only see some events in a year?

In the month, week, and day views the calendar lists only the events that fall in the period on screen, so an event from an earlier year does not leave an empty row in every year after it. An event that runs across the new year is listed in both years, and so is one in the December week that opens a year in the week view. When the period has no events, the calendar says so and links to the nearest event before and after it; click one to go there. Events with no dates at all have no period, so they are kept in a No dates section at the bottom of every year, collapsed until you click it, where you can open one to set its dates. The Outlook view shows events by their days and is unaffected.

Can I group and sort the events list?

Yes. Use the Group control to organize the calendar rows into collapsible sections by Category (the default), Director, or Attendees, and click a section header to collapse or expand it. The Sort control orders the events by Date, Category, Director, or Attendees, both within each section and overall. Grouping and sorting apply to the month, week, and day views; the Outlook view is unaffected.

How do attendee filters work?

Events can target attendee groups such as Everyone, VP, Director, Team Manager, Manager, and Assistant. The Events page and Grid event layer can filter by those groups so each audience sees the relevant planning context.

Can I open or edit an event from the calendar?

Yes. In any calendar view, click an event name or its colored bar to open its details. If your organization role has the events modify permission, the panel opens as an editable form for name, code, category, dates, color, pattern, director, contributors, visibility, and active status, and you can also delete the event; view-only users see the same details as read-only. Saves and deletions apply immediately and are recorded in Manage > Change Log. If a save gives the event dates outside the period on screen, or a filter now hides it, a note says so, and Show it moves the calendar to the event. If the save moves it to another section (a new category, for example) or its section is collapsed, the section opens and the event is highlighted there.

How do I add an event?

If your organization role has the events modify permission, press Add event at the top of the Events page (on a phone it is the + button next to the title). The form starts on today when the period you are viewing includes it, and otherwise on the first day of that period. In the Outlook view you can also click a day, or the + that appears in its corner, to add an event starting that day. When the calendar is grouped by Category or Director, the + on a section header adds an event already set to that category or director, so its color and pattern follow the color defaults. The end date follows the start date until you change it yourself. Save & add another keeps the form open with the same category, director, attendees and dates, ready for the next event. Closing the form after typing into it asks before discarding. After saving, the calendar moves to the new event and highlights it. If the Attendees filter or Hide past events would keep it out of sight, a note says so and Show it clears that filter; an event saved as inactive is not shown on the calendar. While a locked planning period covers events, a start date is required and must fall in a period you have access to.

How do I set up an event that happens every year?

Each year of a recurring event, such as an annual conference, is its own event with its own dates and attendees, linked to the other years as a series. To add next year, open the latest year’s event on the Events page and press Repeat next year, or press the repeat button on its row in Manage > Events. Only the latest year with dates can be repeated, so a repeat never copies into a year the series already has. The form starts as a copy: the year in the name and code moves on by one (Summit 2026 becomes Summit 2027), and the dates are suggested for the same weekday in the same week of the month next year, so an event on the second Tuesday of March stays on the second Tuesday of March, for as many days as before. Check the dates before saving, since the real ones may differ. Anyone who is no longer active is left out of the copy, and the form says how many. If next year’s dates are not known yet you can save it without dates; it waits in the No dates section until you set them. To link events that already exist, open one and choose the other in Same event as. The form then lists the other years under Also held (on the Events page you can click one to open it), and Manage marks each one as Recurring. Choose (not a recurring event) to take one out again; the first year others were linked to stays in its series, and cannot move to another, until they are unlinked. Once the latest year of a series is over and the next has not been added, people who can edit events see a Due to repeat reminder at the top of the Events page, with a button to add it. Not now hides it on this browser. The reminder ends by itself two months after the suggested date, so a series that has stopped does not keep asking; marking its latest year inactive ends it sooner. Repeating a past event is allowed even when a plan lock has made it read-only, because only the new event is written; the new event still follows the plan lock for its own dates.

Where are events created and maintained?

Events can be added from the Events page with the Add event button, or from Manage under the Events tab. Existing events can be edited from either place: on the Events calendar, click an event. Event records can include name, code, category, dates, color, director, contributors, visibility, pattern, active status, and the other years of a recurring event they are linked to.

Dashboard

What does the Dashboard summarize?

Dashboard summarizes total man weeks, projects with allocation, allocated people, average allocation per project, monthly allocation trends, project totals, person totals, planning stats, total travel per person, travel locations, and breaks between trips (for each person: how many breaks they had between trips, the shortest, and how many were under 14 days, to check a rule such as no new trip within 14 days of the last), and a timeline of each person’s trips and the breaks between them. The Travels tab follows your Travel access rather than your Dashboard access: without access to Travel the tab is not shown, and if your Travel access covers only yourself or your team, the tab shows only those trips and says so. It says so too when the plan lock may hide some trips from you, or the projects they are on. In Total Travel per Person, and any other travel chart split by region (such as Travel Days per Person from the gallery), each region is one part of a person’s bar holding all their days there, and the parts run in order of that person’s first trip to each region, so a bar reads through the year; a later return to a region is added to its part rather than drawn again. Trips with no region come after the regions. When there are more than nine regions, the smaller ones share one Other part, which always comes last. Click a bar, a column or a table row to narrow the other charts and tables on the tab to it. The chart or table you clicked is not narrowed by its own pick: it highlights it instead. Picks in different charts combine, so you can pick a project and then a person to see that person on that project. Picks only apply on the tab where you made them, and are still there when you go back to it. Click the same item again to clear it; changing any filter clears them all. The headline figures and Planning Stats always show the whole filtered set.

Can I make my own dashboard?

Yes. Anyone who can open the Dashboard can keep up to 50 dashboards of their own. The built-in one is called Standard and cannot be changed, so to start from it press Duplicate, give the copy a name, and change the copy. To start from nothing, open the dashboard menu beside the page title and choose New dashboard. A new or duplicated dashboard opens in edit mode. There, each chart, table or panel has a bar above it to move it earlier or later, set its width, or remove it, and its Move to button (an arrow leaving a box) puts it on another tab or in the row above the tabs, which spans the page on every tab and holds up to 4 widgets. To put a gallery widget there, add it to a tab and then move it. The button is greyed out when there is nowhere to move it: the row above the tabs is full and the dashboard has no other tab. Add widget opens a gallery of ready-made charts, tables and stats to put on the open tab (the travel ones are offered only if you have access to Travel, the task ones only with access to Tasks, the leave ones only with access to Leave, and the approval ones only if you can view Approvals). You can also add, rename, reorder and remove tabs; a dashboard holds up to 6 tabs and 30 widgets in all. Tick Save the filters set now with this dashboard to have it open with the filters and switches as they are set in the toolbar; leave it unticked and it opens with the default filters set for the workspace. The year is never saved. Editing a dashboard saved with filters starts from those filters, and Cancel puts them back. Press Save to keep your changes or Cancel to drop them. Use the dashboard menu to switch between Standard and your own dashboards, Edit to change one again, and the menu beside Edit to rename or delete it. The page reopens the dashboard you last had open in that browser, or the workspace default if you have not chosen one there, and the address bar holds a link to the open dashboard. Your dashboards are private unless you share them. A saved dashboard stores its layout and filters, never figures, so it always shows the latest data your own access allows. If you leave a workspace, your private dashboards there are deleted; the ones you shared stay, for an administrator to look after.

Can I share a dashboard with my colleagues?

Yes. Open one of your own dashboards, press the menu beside Edit and choose Share with the workspace. Everyone who can open the Dashboard can then find it under Shared dashboards in the dashboard menu, open it, and pin it to keep it in their menu. It is read-only to them: only you can change it, and they can press Duplicate to make a copy of their own. Sharing shares the layout and saved filters, never figures. Titles, and widget filters on named values such as a trip location, are shared as you set them, so do not name in them what colleagues may not see. Each person sees their own data in it, as far as their own access goes, so a chart of travel shows nothing to someone without access to Travel, and a saved line manager filter is not applied for someone whose access does not include reporting lines (the page says so). Choose Stop sharing in the same menu to make it private again; anyone who pinned it loses it. People who can change the Dashboard (administrators, unless your roles say otherwise) can also make a shared dashboard the workspace default, which opens for everyone who has not chosen a dashboard in that browser, and can stop sharing, take over or delete a dashboard someone else shared, for example after its owner has left. Sharing, stopping sharing, these administrator actions and changes to the default are recorded in the change log.

How do I build my own chart, table or figures for a dashboard?

On one of your own dashboards, press Edit, then Add widget, then Build your own. Choose Chart, Table or Figures at the top. For a chart, pick the measure (man weeks, travel days, tasks, overdue tasks, available, booked, free or over-booked weeks, leave days, requests, breaks between trips, the shortest break, breaks under a number of days you set, or how many people or projects), what to group the bars by, and optionally a second thing to split each bar by; with more than 9 values, a split shows the 8 largest and adds the rest together as Other. Only bars across can be split. A count of people or projects cannot be split, because one person can sit in several parts of a bar. Bars can run across, as a ranking, or stand upright, as over time, and you can choose how many to show before Expand, the height, and a table under the chart. For a table, pick what each row is for, optionally a second level, and up to three columns of figures. For figures, add up to 8, each a total, a count, an average, a median or the largest, with its own label. Under Only include you can add up to 3 filters of the widget's own, such as one category, a few teams or certain people; they narrow the widget on top of the filters at the top of the page and never widen them. Untick Narrow this widget when something is picked in another to keep it showing everything when you click a bar or row elsewhere. The preview beside the settings shows the widget as it will look. Press Add to dashboard, then Save. To change a widget later, including one added from the gallery, press Change on the bar above it in edit mode. Travel data is offered only if you have access to Travel, task data only with access to Tasks, leave data only with access to Leave, and approval data only if you can view Approvals.

Can a dashboard show leave?

Yes, if you have access to Leave. In edit mode, Add widget offers leave figures and charts (leave days per person by type, per month, and by type), and in Build your own you can choose Leave as the data. It counts days of leave in the year on screen, approved and pending; rejected leave is not counted. Group or split by person, team, role, month, leave type, or approval (approved or pending). Leave types are your workspace's own, as set in Settings, so what they are called, and whether a type such as Sick Leave exists at all, is up to your workspace. You see the leave of the people your Leave access covers, the same leave the Leave page shows you, and the page says so when that is not everyone. The people filters at the top of the page apply; the project filters do not. A shared dashboard shows each person the leave their own access covers, and shows someone without access to Leave that the widget is not available to them.

Can a dashboard show approval requests?

Yes, if you can view Approvals. In edit mode, Add widget offers approval figures and charts (requests by type and state, pending requests per person, per month, and a requests per person table), and in Build your own you can choose Approvals as the data. It counts the requests made in the year on screen, whoever decided them: allocation, leave, travel, skill and certification requests, approved, pending or rejected. A leave request covering several days counts once. Each request also needs the access its own page asks for: you see leave requests only for the people your Leave access covers, travel requests for those your Travel access covers, skill and certification requests under your Capabilities access, and allocation requests under your Plan Grid access. Group or split by request type, approval state, the person a request is about, their team or role, or the month it was made. Requests about planning the plan lock hides from you are left out, and the page says so. Requests on planning the lock only freezes are counted, though the Approvals page does not list them for deciding. The people filters at the top of the page apply; the project filters do not.

Can a dashboard show who has time free?

Yes. In edit mode, Add widget offers capacity figures and charts (free weeks per person, over-booked weeks per person, free weeks per month, a capacity per month table, a capacity per team table), and in Build your own you can choose Capacity as the data. Capacity is worked out week by week: each working week (Monday to Friday) is one available week, less the days of leave and public holidays when Exclude leaves and Exclude holidays are on, and pending leave as Include pending leave says. Booked weeks are the person's approved allocations in the same weeks, adjusted the same way. Free weeks are the available weeks a person has not booked, and over-booked weeks the booked weeks beyond what they have. Both are worked out for each person and month before they are added up, so one person's spare time never hides another's overload. Group by person, team, role or month. People marked inactive are left out of capacity, since when they left is not recorded, so Include inactive does not change it. Capacity counts all of a person's allocations, so the project filters (category, type, director, phase) do not narrow it; the people filters do. If the plan lock hides some planning from you, the weeks it hides are left out rather than shown as free, and the page says so. Leave is taken out only for the people your Leave access covers, so the leave switches do not change anyone else's capacity; the page says so here too.

Can a dashboard show tasks?

Yes, if you have access to Tasks. In edit mode, Add widget offers task figures and charts (tasks per person by status, tasks by status, overdue tasks per project, tasks due per month, a tasks per project table), and in Build your own you can choose Tasks as the data. A dashboard counts the tasks due in the year on screen, and open tasks that are not due in a later year: those with no due date, and overdue ones from earlier years. It counts only the tasks your Tasks access covers, the same ones the Tasks page lists for you, and the page says so when that is not all of them, or when the plan lock may hide projects whose tasks would be left out. A task counts against the person it is assigned to; unassigned tasks have their own (unassigned) row. Overdue means still open (not started, in progress or paused) with a due date before today. Group or split by Status to see where tasks stand, or by Month to see when they fall due; tasks not due in that year are left out of a month chart and shown as (not due this year) elsewhere. The filters at the top of the page apply through each task's project and assignee, so an unassigned task is kept or left out by its project alone. The Phase filter and the leave and holiday switches do not apply to tasks. A shared dashboard with task widgets shows each person their own tasks, and shows someone without access to Tasks that the widget is not available to them.

Can a dashboard show travel by month?

Yes, if you have access to Travel. In edit mode, Add widget offers Travel days per month, a column for each month of the year, and in Build your own you can group or filter travel by Month. A trip's days count in the month they fall in, so a trip from 28 March to 3 April counts 4 days in March and 3 in April; only days in the year on screen are counted. Clicking a month in another chart on the same tab narrows travel to that month too. Like every travel widget, it shows the trips your Travel access covers.

Can a dashboard show how long people are home between trips?

Yes, if you have access to Travel. Use it to check a rule such as no new trip within 14 days of the last one. The Standard dashboard’s Travels tab shows the Breaks between Trips table, with the Trips and Breaks timeline under it; to use a different number of days in the table, duplicate Standard and change the table in your copy. The Shortest break column also gives that break’s dates, such as 4 (10 to 14 Mar). In edit mode, Add widget offers the Breaks between trips table (for each person: how many breaks, the shortest, and how many were under 14 days), Shortest break per person (shortest first), Short breaks per month, and the Trips and breaks timeline. The timeline shows each person’s trips across the year as bars on one line per person, with the location written in the bar where it fits and pending trips outlined with dashes. Breaks under 14 days are marked in red with their number of days. People with the shortest break come first, ten at a time; Expand shows everyone. Point at a trip to see where and when it was, its project and region, and whether it is pending; point at a break to see how long it was and the trips on either side. Click a person’s name, here or in the Breaks between Trips table, to list that person’s breaks under the timeline: for each, its days, the day they came back and from where and which project, and the day they left again and for where. Clicking a person or a month in another chart or table narrows the timeline to them, and clicking a trip picks its project for the other charts on the tab. On a phone the timeline shows only the list of breaks, for everyone shown. The timeline marks short breaks with the same number of days as the first table, chart or figure of breaks under a number of days shown with it, such as the Breaks between Trips table or Short breaks per month, on the same tab or above the tabs: change that widget’s days and the timeline follows. With no such widget it uses 14 days. The timeline is added from Add widget only: Build your own does not make one, and it has no Change button of its own. In Build your own, choose Breaks between trips as the data; when a widget shows breaks under a number of days, you set that number, from 1 to 365, and its column or label says it, such as Breaks under 21 days. A break is the days from the day one trip ends to the day the person’s next trip starts: back on the 10th and off again on the 14th is a break of 4 days. Trips that overlap, or where one ends on the day the next starts, count as one stretch of travel with no break between them. A break counts in the month the next trip starts, and the first break of a year is measured from the last trip before it, as far back as 1 January of the year before. Pending trips count as well as approved ones; rejected trips do not. Breaks are about people, not projects, so the person filters at the top of the page apply to them and the project filters do not: every trip counts, including one on a project marked inactive, while Include inactive still decides whether inactive people are shown. Clicking a project or region elsewhere does not narrow them; clicking a person or a month does. They are worked out from the trips your Travel access covers, so a trip hidden from you can make a break look longer than it was, and the page says so when that may be the case.

Which Dashboard filters are available?

Filter by year, project categories, project types, directors, people roles (with a (no role) option for anyone without one), teams, line managers, allocation phases, and whether leaves or public holidays should be excluded from capacity. The Line managers filter works like the one on the Plan Grid: a ticked manager takes in themselves and their whole reporting line, so someone stays in while any manager above them is ticked. To see one line, use Untick all and tick that manager. It lists active managers only, so the reports of a manager who has left stay under the manager above. People with no listed manager above them show under (no manager listed), which can include someone who has left and whose manager has no active reports. It follows reporting lines as they stand today, including for past months, and applies to both the Allocations and Travels tabs. It is offered only to people whose Plan Grid access covers the whole workspace. The Include inactive people and projects toggle covers both at once: leave it off and allocations and travel belonging to a person or a project marked inactive are left out of every chart, table, and headline figure on the page; turn it on to count them for historical review. Charts and tables update from the same filtered dataset.

When should I exclude leaves or holidays in Dashboard?

Exclude leaves or holidays when you want project workload converted to available working capacity. Include them when you want raw allocation weeks without absence or public holiday adjustments. When leaves are excluded, an Include pending leave toggle (on by default) controls whether leave still awaiting approval reduces capacity; leave that has been rejected is never counted. On the allocation side, only approved allocations count toward allocated capacity here and on the grid and Conflicts page; a pending or rejected allocation change is never counted until it is approved.

Can the Dashboard open with default filters?

Yes. Settings > View Defaults includes Dashboard defaults for excluding leaves, excluding holidays, including inactive people and projects, and hiding selected project categories or project types by default. Users can still change filters during a session.

Approvals

What appears in Approvals?

Approvals has five tabs: Allocations, Leaves, Travel, Skills, and Certifications, each with its own pending count. The Allocations tab lists Plan Grid changes that an editor made directly and that are awaiting approval, one row per record showing person, project, period, percentage, phase, and a Change or Remove label that says whether the pending item is an edit or a requested removal. Its policy is configured under Settings > Approvals > Plan Grid. The Leaves tab lists leave awaiting approval. The Travel tab lists travel awaiting approval, one row per trip. The Skills tab lists skills awaiting approval and the Certifications tab lists certifications awaiting approval, each one row per record. Every queue starts with the most recently requested item at the top, and every column header sorts: click one to sort by it, click it again to reverse the direction. On the Leaves tab, Dates sorts by the first day off and Days by how long the request is.

How do allocation approvals work?

Plan Grid approvals, shown on the Allocations tab, follow the same prepare and approver process as leave and travel, but you choose which kinds of change need approval. Under Settings > Approvals > Plan Grid you turn approval on and tick which change types are gated: new or removed allocations (this also covers a percentage change), phase changes, and team changes. A change whose type is not ticked is applied immediately without approval, so phase or team edits can be left ungated while capacity changes still need sign off. Editing an already approved allocation never changes it straight away: the current allocation stays live and keeps counting, and your change is held as a proposal for an approver. The proposal appears on the Allocations tab with the person, project, period, percentage, phase, and a Change or Remove label, plus a View in grid button that jumps to that person and period on the Plan Grid. Approve to apply it to the allocation, or reject to decline it and leave the current allocation as it was; when rejecting you can add a note explaining why. A gated removal works the same way: the allocation keeps counting until the removal is approved (which deletes it) or rejected (which keeps it). A brand-new allocation that needs approval waits as pending and does not count until confirmed; removing an allocation that is still pending or was rejected happens immediately. An allocation added or changed by an exempt person, or for an exempt person, is approved automatically, and the auto-allocate wizard bypasses the gate. A pending or rejected proposal does not count toward a person's capacity or raise a conflict, but it still shows on the plan grid as a dashed, greyed ghost pill next to the live allocation so you can see and resubmit it: an hourglass marks one awaiting approval, a crossed circle marks a rejected one (whose label is struck through), and hovering shows both the status and what the change proposes (for example New allocation 50%, Capacity to 80%, or Removal requested). A pending removal is shown struck through with a trash icon. Clicking a cell opens its editor: the live allocations stay editable at the top, and any requested changes for that cell are listed below under a Requested changes heading showing current to proposed, so you can compare. If you are an approver for a pending item in that list, it also carries approve and reject buttons so you can decide it there without leaving the grid, with an optional note when you reject. To change a proposal, edit the live allocation and save; to call it off, use its Cancel button, which withdraws the requested change and leaves the allocation as it is (you do not need an approver to cancel your own request). Once approved, the proposal is applied and counts as usual. You only see the requests you are an approver for, while administrators see all.

Can I require approval for only some Plan Grid changes?

Yes. Settings > Approvals > Plan Grid has separate toggles for new or removed allocations, phase changes, and team changes. Tick only the change types that should need approval; unticked types are applied immediately without approval. A percentage change follows the new or removed allocations toggle. This lets you, for example, require approval when capacity is added, changed, or removed while letting planners adjust phase and team freely. The approvers and exemptions set on the same page apply to whichever change types are gated.

How do leave approvals work?

When a workspace requires approval for leave, newly added leave waits for an approver before it is confirmed. Anything waiting on you also shows as a count on the Approvals item in the sidebar. The Leaves tab groups pending leave back into the range it was submitted as and shows the person, dates, number of days, leave type, leave status (Planned or Confirmed, or whatever statuses your workspace configured, shown as Mixed if the days of one request no longer agree), who requested it, and when, with a View in grid button that jumps to that person on the Plan Grid. Approve to confirm the leave or reject to decline it; when rejecting you can add a note explaining why, which the submitter sees under the Rejected badge on the Leave page. A rejected leave is removed from the plan grid but stays on the Leave page, tinted red with a Rejected badge. Rejected leave is hidden on that page by default: when a year has any, a Rejected button above the list says how many and shows them, and an editor can clear them out from the same place. There are two ways to send it back for approval: edit it, or simply add leave for the same dates again. Either way the approver policy is re-run and the days return to pending (or are approved if approval is no longer required). Adding the same dates again also confirms how many rejected days went back for approval. If you are an approver, you can also decide leave straight from the Plan Grid: a leave cell awaiting your approval shows an hourglass marker you can click to open an approve or reject dialog, with an optional note on reject, and approving a day approves the whole range it was submitted as. You only see the leave requests you are an approver for, while administrators see all. Who approves is configured under Settings > Approvals.

How do travel approvals work?

Travel approvals mirror leave approvals. When a workspace requires approval for travel, newly added travel waits for an approver before it is confirmed. The Travel tab shows one row per trip with the person, location, dates, travel status, who requested it, and when, with a View in grid button that jumps to that person on the Plan Grid. Approve to confirm the trip or reject to decline it; when rejecting you can add a note explaining why, which the submitter sees under the Rejected badge on the Travel page. A rejected trip is removed from the plan grid but stays on the Travel page, tinted red with a Rejected badge. Rejected trips are hidden on that page by default: when a year has any, a Rejected button above the table says how many and shows them, and an editor can clear them out from the same place. To send a rejected trip back for approval, edit it: saving the change re-runs the approver policy and returns the trip to pending (or approves it if approval is no longer required). Pending trips still appear on the grid with the plane icon and a small hourglass awaiting-approval marker; if you are an approver for that trip you can click the hourglass to approve or reject it without leaving the grid, with an optional note on reject. You only see the travel requests you are an approver for, while administrators see all. Approvers, exempt roles, and exempt people are configured per area under Settings > Approvals.

How do skill and certification approvals work?

Skills and certifications follow the same prepare/approver process as leave and travel. When a workspace requires approval for skills or certifications, a newly added record waits for an approver before it is confirmed. The Skills tab shows one row per skill with the person, topic, level, and interest; the Certifications tab shows one row per certification with the person, issuer, certification, and dates. Approve to confirm the record or reject to decline it; when rejecting you can add a note explaining why, which the submitter sees under the Rejected badge on the Capabilities page. A rejected record is left out of profiles and analytics but stays on the Capabilities page with a Rejected badge, and a pending record is tagged there with a Pending badge. Rejected records are hidden on that page by default: when there are any, a Rejected button beside the filters says how many and shows them. There is no bulk clear here; delete the individual row if you want it gone. To send a rejected skill or certification back for approval, edit it: saving the change re-runs the approver policy and returns the record to pending (or approves it if approval is no longer required). A record added by an exempt person, or for an exempt person, is approved automatically. You only see the requests you are an approver for, while administrators see all. Approvers are configured per area under Settings > Approvals.

Where did my rejected leave, trip, or skill go?

It is still there, hidden by default. A rejected record is kept rather than deleted, so you can read the reason and send it back for approval, but it is not a booking anybody is acting on: the plan grid, the dashboard and the exports all leave it out, and so does the list it lives on until you ask for it. On the Leave and Travel pages, when the year you are looking at has any, a Rejected button appears above the list with the number in it, for example Rejected (3); switch it on and the rows appear, tinted red with their Rejected badge and the approver note. The Capabilities page works the same way on both its tabs. If a period has nothing but hidden rejections the list says so rather than claiming there is nothing there, so a refused booking is never silently missing. Editors get a Clear rejected button next to the toggle on Leave and Travel, which deletes the rejected rows currently listed, keeps any that fall inside a locked planning period, and leaves the decision itself in the change log. There is deliberately no bulk clear on Capabilities, because that list has no year to scope it to; delete the individual row instead. You are also told about a refusal without going looking for it: your summary email reports anything of yours turned down since the last one, with the reason and a link back to the record. That link opens the page with the rejected rows already shown, and on the year the record is in, so you land on it rather than on an apparently empty list. A refusal that spans several days is reported once, as the booking you submitted, not once per day. Nothing badges you about a refusal in the sidebar, because a refusal has no end state of its own and a badge for it could never be cleared.

Can a rejected leave, trip, skill, or certification be resubmitted?

Yes, by editing it. A rejected record keeps its normal Edit button; read the rejection note, correct the record, and save. Saving rechecks the current approver policy: if approval is still required the record returns to pending and reappears in the approver queue with a fresh request, and if approval is no longer required, because the policy is off or the person is now exempt, it is approved right away. For leave, editing a rejected range re-runs the check for every day in it at once. If nothing needs changing, opening Edit and saving as-is still resends it. Leave has a second route, because a rejected day stays booked in the calendar: adding leave for a date that was rejected, from the Leave page or the Plan Grid, resubmits that day rather than creating a duplicate, applies whatever type, status and notes you just entered, and tells you afterwards how many rejected days went back for approval. Editing a rejected range resubmits it just as reliably, but says so through the badge changing to Pending rather than a message. A date that already has leave which is approved or still pending is never overwritten: it is left as it is and the confirmation says how many days were left alone, and if every day in the range is already taken that way the save is refused outright rather than appearing to work. Both modals also warn you about either case before you save.

Can an approver explain why a request was rejected?

Yes. When you reject a leave, trip, skill, or certification request, a box opens where you can add a note explaining the reason. The note is optional, so you can leave it blank. If you add one, the submitter sees it under the Rejected badge on the Leave, Travel, or Capabilities page, so they know what to fix before resubmitting. The note is cleared once the record is resubmitted.

Can I approve or reject several requests at once?

Yes. Every tab on the Approvals page has a checkbox at the start of each row. Tick the requests you want, or use the checkbox in the header to tick every request on that tab (it shows a dash when only some are ticked). To tick a run of rows, tick the first, then hold Shift and tick the last; the run follows the order on screen, so sort first if that helps. On the Leaves tab one row is a whole submission, so ticking it covers every day in it. One decision can cover up to 2000 requests, counting each day of leave separately; on a very long queue, decide it in parts. Once anything is ticked, a bar appears at the bottom of the screen showing how many requests and how many people are selected, with Approve and Reject buttons and a Clear button (Esc also clears). Approving several asks you to confirm first, and on the Allocations tab it warns you how many of them are removals, because approving a removal deletes that allocation. Rejecting asks for one optional note, which goes to every submitter in the selection, and the dialog says how many people will see it. The selection is decided as one: if any of it is a request you cannot decide, nothing is changed and the message names the person, so you can untick that row and try again. If another approver decided some of them while you were looking, the rest go through and the message says how many were already decided. Each person gets their own entry in the change log. A row's own approve and reject buttons still work as before and decide just that row. You only see the checkboxes if you can decide approvals.

Can I approve requests directly from the Plan Grid?

Yes, for the requests you qualify to decide. Pending Plan Grid changes, leave, and travel each show an hourglass awaiting-approval marker on the grid. For an allocation change, click the cell to open its editor and use the approve or reject buttons beside the pending item under Requested changes. For leave or travel, click the hourglass marker on the cell to open a short approve or reject dialog. Rejecting always offers an optional note that the submitter sees, and approving a leave day approves the whole range it was submitted as. You only see these controls for requests you are an approver for; everyone else sees the marker as a plain status icon. Skills and certifications do not appear on the grid, so they are decided on the Approvals page as before.

Conflicts

What counts as a conflict?

A conflict is a person-period where total allocation exceeds available capacity. A week total averages day allocations across the five working days, exactly as the Plan Grid does, so someone booked full time on two days of a week counts as 40% of that week rather than 200%. A week is also flagged when a single day inside it is over capacity, which happens when two projects book the same day; the row then names that day and shows what the week averages, because the grid week and month cells for that period will look within capacity. Conflicts are always measured by week, so a month row on this page reports its worst week rather than the month as a whole. Where a month has uneven weeks, its grid column averages them and can read within capacity while a week inside it is over; the row says so and names the week. The Conflicts page groups these issues so planners do not need to scan the whole grid manually.

How do I inspect conflicts?

Switch between week and month views, filter by role or person name, and use the grid shortcut to jump directly to the conflicting period. The shortcut opens whichever grid view actually shows the figure on the row, so a week the month column averages away opens in week view, and a single over-booked day opens in day view. The table shows total percent, overage, and the allocations that caused the issue. Accepted conflicts are hidden by default; turn on the Show accepted toggle to include them.

How can editors resolve conflicts quickly?

Users with conflict modify access can remove an editable allocation directly from the conflict row, split multiple editable allocations equally, or accept the conflict as intentional. Aggregated day allocations still need to be edited in the grid.

What does accepting a conflict do?

Accepting marks an over-allocation as intentional: the conflict is hidden from the default list and no longer counts in the sidebar Conflicts badge, and its grid cells turn amber instead of red. In week view Accept covers that week; in month view it covers every conflicting week of that month. You can add an optional note, and the accepted row shows who accepted it and when. Turn on Show accepted to review accepted conflicts and use Un-accept to reopen one. If the allocation total later grows beyond what was accepted, the conflict automatically reappears as active.

Tasks

What is the Tasks page?

Tasks tracks the work to be done on each project. Open it from Tasks in the sidebar, just below Plan Grid; on a phone it is in the Menu. Every task belongs to one project, and within a project tasks can be sorted into named groups, such as Planning or Fieldwork testing, each of which can be mapped to one of the project's phases. Groups are optional. The page lists projects as sections, each with its groups and their tasks underneath, showing each task's status, assignee, start and due dates, checklist progress, and numbers of comments and linked documents. By default it lists My projects: every active project you are assigned to, meaning you have an approved allocation on it, contribute to it, or are its director or team manager, even when it has no tasks yet. Choose All projects in the project box to see every project that has tasks, or pick a single project; the box is searchable, so type part of a project code or name to find one. The buttons beside it switch between All, Open (not started, in progress or paused), To review (finished and not yet reviewed) and Done (finished, reviewed or cancelled). The page opens on All unless an administrator has chosen another view in Settings > View Defaults > Tasks, where they can also make the page open in the Flow view rather than as a list, choose how the list is sorted, and choose whether the Flow view places cards by due date (the default) or by start date. You can also narrow the list to one person, to tasks assigned to you or to unassigned tasks, and search titles and descriptions. A project header shows how many tasks it holds and how many are overdue. Projects start folded, showing only their headers: click a header to open the project and again to fold it. A project opens by itself when you pick it in the project box, when you search, or when you follow a link to one of its tasks. The info button beside it opens the project's details in place under the header, and pressing it again closes them: the project's dates, category and type, director and team manager, its phases with their dates (the phase today falls in is marked Now, and dates worked out from the project's approved allocations, because none are saved for that phase, are marked from allocations), and how many of its tasks are in each status, with how many are overdue or will start late. Those counts cover every task on the project you can see, whatever the filters. If you have edit access to Tasks, the details also count the people on the project; click the number to list them. Under the details, Open in Plan Grid (if you can view the Plan Grid, and only on an active project, since By Project lists only active projects) opens the grid By Project, showing only that project and on a year it runs in, with its category shown even if the grid hides it; a note above the grid names the project, says so when nobody booked on it is shown or when the project is inactive (By Project lists only active projects), and has Show all projects to go back to your usual grouping, project filter and categories, which the link does not change. Edit Project (if you have edit access to Manage) opens Manage > Projects with the project's row ready to edit; a project in a locked planning period is picked out instead, since it cannot be edited. Within a group, tasks are listed in Plan order unless you choose another sort (see How do I sort tasks or change their order?). Finished and reviewed tasks are shown in grey and cancelled ones are struck through. A due date that has passed on an open task shows in red, and one within the next three days in amber. The list loads about 100 tasks at a time, always whole projects, so a project is never shown with only some of its tasks; when there are more, a line under it says how many are shown, for example Showing 104 of 240 tasks, with a Load more button that adds the next projects at the bottom. The number beside the page title counts every open task you can see, whatever the filters. Everything is changed right in the list, without pop-up windows.

How do I sort tasks or change their order?

Use the Sort list beside the List and Flow buttons. It orders the tasks inside each group; projects are always listed by name, and groups in their own order. Plan order, the default, lists tasks in the order they were planned: a template adds its tasks in the template's order, a new task goes to the end of its group, and so does a task moved to another group. In Plan order a finished task keeps its place, so the steps still read in sequence. Due date lists the earliest due date first, so overdue tasks come first and tasks without a due date last. Start date does the same with start dates. Status lists tasks in progress first, then paused, then not started, then the rest. Assignee lists tasks by the assignee's name, with unassigned tasks last. Under every sort except Plan order, finished, reviewed and cancelled tasks are at the bottom of their group. When you change a task's status or edit it, its row stays where it is so it does not jump away from the pointer; the list sorts afresh when you change the sort or the filters, load more, or reload the page. An administrator can choose the sort the page opens with in Settings > View Defaults > Tasks. To change the order, you need edit access to the task, and the list must be in Plan order: drag the task by the handle at the start of its row and let go where the blue line shows. You can also focus the handle and use the up and down arrow keys, and on a phone use the up and down buttons on the task instead. A task moves within its own group; to move it to another group, edit the task and pick the group. The order is shared: everyone who sorts by Plan order sees it.

How do I add groups and tasks, or edit them?

You need modify access to Tasks. Under each project's tasks is Add task: it opens a row at that spot with fields for the title, the assignee and the dates. The dates are picked the way leave is: click the dates box to open the calendar, click the start day, and the span follows the pointer until you click the due day; pick one day for a one-day task. You can also type the dates, for example 4/11/2030 - 29/11/2030. Dates are optional: empty the box, or press Clear in the calendar, to take them off. Picking dates always sets both the start and the due date; a task that has only one of them shows a note under the box saying which, and keeps it that way until its dates are changed. Press the tick or Enter to save it, or the cross or Escape to drop it. To organise a project's tasks, use Add group of tasks on the project's header: a row opens for the group's name and, optionally, the project phase it covers, picked from the phases in Settings > Dropdown Options. When the project has dates for that phase, they show beside the group's name: the dates saved for it by Auto-Allocate or, when it has none, the first to the last week (or month) of the project's approved allocations tagged with that phase, which the badge's tooltip then says. Pending allocations do not count, and the allocations are used only for someone who can view the Plan Grid, and only those of the people their Plan Grid access covers. Saving the group opens a new task row in it straight away, and every group has its own Add task under its last task. Groups are optional: a project without any lists its tasks directly, and once a project has groups, tasks in none of them are listed under Not in a group. To change a task, press its pencil: the row turns into the same fields, saved the same way, the way projects are edited in Manage > Projects. When the project has groups, the row also has a group list: pick another group to move the task there, or Not in a group to take it out of every group. To rename a group or change its phase, press the pencil on the group's heading. To delete a group, press the bin on its heading. If the group holds tasks you choose what happens to them: Delete the group, keep the tasks moves them to Not in a group, while Delete the group and its tasks asks once more and then deletes every task in it, including any your current filters hide, with their checklists, comments, documents and history. The confirmation says how many tasks that is and how many tasks elsewhere on the project will lose their dependency links to them. If your Tasks access covers only your own or your team's tasks and the group holds a task outside it, only the group can be deleted. To delete a task with its checklist, comments and documents, press its bin and then Delete in the row. A new task starts unassigned. If your Tasks access covers only your own or your team's tasks, a task has to stay inside it: assigned to someone it covers, or unassigned on a project you are assigned to; on any other project a new task starts assigned to you. Moving a task to another project takes it out of its group and removes its links to other tasks, since a link only joins tasks of the same project. If any of those links is one you could not remove yourself (it joins a task you cannot see, or you cannot change the links on that project), the move is refused until someone who can removes it. Deleting a project deletes its groups and tasks, and deleting a person leaves their tasks unassigned. Renaming a phase in Dropdown Options renames it on the groups mapped to it too.

Who can be assigned to a task?

Anyone in Manage > People. The assignee list puts the people on the task's project first, under On this project, and everyone else after them. Someone counts as on the project when they have an approved allocation on it, are one of its contributors, or are its director or team manager. When you pick someone who is not on the project, a note under the field says so. People without a login in the workspace are marked "(no login)", and picking one shows a warning: they cannot update the task themselves, so the people on the project update its status for them.

How do task statuses work, and who can change them?

A task is Not started, In progress, Paused, Finished, Reviewed or Cancelled. Its Status column shows the current status, followed by a button for each move you are allowed to make: a play button to Start or Resume, a pause button to Pause, a tick to Finish, a double tick to Mark reviewed, a circular arrow to Reopen, and a return arrow to Request changes. Point at a button to see its name. Cancel task is the crossed-circle button at the end of the row, between the task's pencil and its bin; a cancelled task can be reopened. A finished task is done; review is optional. The assignee can change a task's status, and so can anyone with edit access to Tasks who is assigned to the task's project. When the assignee has no login, or the task is unassigned, anyone on the project can change it. A change made by someone other than the assignee is recorded in the history as done for the person the task was assigned to at the time. Edit access alone, without being on the project, is not enough. On a task you may not change, its buttons are greyed out; pointing at one says who can. The one exception is Mark reviewed: anyone who can see a finished task can mark it reviewed, except the person it is assigned to. The assignee sees the Mark reviewed button greyed out on their own finished task; pointing at it explains that someone else has to review it. Anyone else who may change the task's status sends a finished or reviewed task back with Request changes, which opens the task and asks what needs changing; Send back returns it to In progress with that note in its history. When the assignee has no login, or nobody is assigned, the people on the project reopen it with Reopen instead, recorded as done for the assignee, since they are acting for them rather than reviewing them. Someone who can only see the task can mark it reviewed but cannot send it back. The assignee sends their own task back with Reopen, which needs no note.

What is in an opened task: checklist, documents, comments and activity?

Click a task's title, or the arrow beside it, to open it right under its row; click again to close it. On the left are its description, its checklist, its documents, and the tasks it is linked to (Waiting on and Leads to); on the right its comments, and below them its activity. Editors change the description in place; it saves when you leave the box. A checklist shows a progress bar and a count such as 2 of 5 done, and the task list shows the same count. Editors add items by typing in the box under the checklist and pressing Enter, and remove them with the cross beside each. An item can be ticked by the task's assignee, by the item's own assignee, or by anyone with edit access to Tasks, and a ticked item shows who ticked it. Anyone who can see a task can comment on it: write in the comment box and press Post comment, or Ctrl+Enter. You can edit your own comments in place, and delete them after confirming in the comment itself; an edited comment is marked as edited. Activity lists when the task was created, every status change, and every change to its dates, each with who made it and when, including dates moved to make room after a linked task slipped; it starts folded, so click Activity to show it.

How do I link supporting documents to a task?

Open the task and use the Documents section on the left. Paste a link to the document, for example a SharePoint or OneDrive sharing link, a link to a file in a SharePoint library, or any other web address starting with https://, give it a name if you like, and press Add link. Each document shows an icon for its kind, so Word, Excel, PowerPoint, PDF, OneNote, folders, images, videos and archives are told apart at a glance. The kind is read from the link itself: SharePoint and OneDrive sharing links say what they point at, and other links by the file name at their end; Google Docs, Sheets and Slides links are recognised too. A link whose kind cannot be told shows a plain link icon. Without a name, a document is shown by its file name when the link names one, else by its site. Clicking a document opens it in a new tab, where SharePoint asks you to sign in as usual: linking a document does not change who may open it. The task's assignee and anyone with edit access to Tasks can add and remove documents; everyone who can see the task can open them. The task list shows a paperclip with the number of documents on each task.

Can I see tasks on the Plan Grid?

Yes. Turn on the Tasks layer toggle on the Plan Grid, after Notes. It is offered to anyone who can view Tasks and starts off unless your workspace turns it on in Settings > View Defaults; your choice is remembered on this browser. Only open tasks are shown (Not started, In progress and Paused), and only those you can see on the Tasks page. Each task appears on its assignee's row, in every cell from its start date to its due date; a task with only one of the two dates appears on that one day, and a task with no dates is not drawn. An open task that is past its due date, or that has a start date but no due date, carries on up to the current period, so it stays in view until it is done. In each cell the tasks are shown as a small chip per project, with the project's color and the number of tasks. A red chip has an overdue task; an amber outline means a task falls due in that period. A chip with a dashed border and a warning icon means the person has open tasks on that project in that period but no time booked on it: no allocation to the project in that cell, approved or awaiting approval. Hover a chip to list its tasks. Click it to open them: each task links to the Tasks page, where it opens with its row briefly highlighted, and you get the same status buttons as on the Tasks page (Start, Pause, Finish, Mark reviewed and so on) for the moves you are allowed to make. On a task you may not move, the buttons are greyed out, as on the Tasks page: hover one to see who can. Cancel task and Request changes are on the Tasks page. On a chip with no time booked, editors also get Book time, which opens the cell with that project offered first. In By Project view, anyone with open tasks on a project but no time booked on it gets a row under that project, marked Has tasks, no time booked, and editors can click a cell in it to book time. A project with tasks but nobody booked on it gets a section of its own. Each project heading also counts that project's tasks (open, overdue, unassigned, undated and done) and links to them on the Tasks page. While the layer is on, the cell editor lists the tasks in its period under Tasks in this period. Projects in a hidden category hide their tasks too.

How do I link tasks so that one waits on another?

A link means one task starts after another finishes. The List and Flow buttons at the top of the Tasks page switch every project on the page between the list and the Flow view at once; the page opens as a list unless an administrator has chosen Flow in Settings > View Defaults > Tasks. In Flow, each project still has its own flow under its header (links never cross projects), and a folded project stays folded until you open it. Flow shows a project's tasks as cards joined by arrows, laid out for you from their dates, so there is nothing to arrange: cards run left to right in date order, tasks running at the same time share a column, each arrow points right, and each group has its own band. The Place by buttons beside List and Flow choose which date orders the cards. Due, the default, orders them by due date, so a long task sits further right, near the tasks due around when it is, and each column is headed by its earliest due date (for a task that will start late, the date it can now be due; a task with only a start date does not head a column). Start orders them by start date, so a long task sits near the tasks starting when it does, and each column is headed by its earliest start. An administrator can make Start the default in Settings > View Defaults > Tasks. A task that will start late is placed where it can really start, after the task holding it up. The coloured edge on the left of each card is its status: grey for not started, blue for in progress, amber for paused, and green for finished or reviewed, while a cancelled task's card is faded; the key above the flow names each one. A card with both a start and a due date shows its length in working days after its dates, for example 5d, and a thin bar along its foot: the longest task in the project fills the bar and shorter tasks fill their share of it, so long and short tasks stand out at a glance even though the columns are not drawn to scale. Tasks with no dates wait in the No dates column on the left, which only shows while there are any; once you link one, it moves onto the canvas next to the task it is linked to. To link two tasks, drag from the dot on the right edge of the task that comes first and let go on the task that comes after it. To add the next task in a chain, point at a card and press its plus button: type the title and press Enter, and the new task is created already linked after it, ready for the one after that. Click an arrow, then Remove link, to remove it. A flow always shows every task on its project, so that no chain is broken: inside each project's flow, the status, assignee and search filters fade the cards they leave out instead of removing them, and a note above the projects says so. Which projects are shown works as on the list: with All projects, a project appears only when at least one of its tasks matches the filters, while My projects and a single chosen project are always shown. Adding a group of tasks and using a template are done in the list. Point at a card for a quick view of the task, and click it to open the task in a panel beside the flow, where it can be worked and edited. Links can also be added without the Flow view: open a task and use Add under Waiting on or Leads to, then pick the other task. Only tasks of the same project can be linked, and a link that would make a loop (a task ending up waiting on itself) is refused. A link never stops anyone starting a task; it only shows what the task is waiting on and works out when it can really start. Drawing and removing links needs edit access to Tasks on that project: with Own or Team access, only on projects you are assigned to. Everyone who can see the tasks sees the links. A linked task you cannot see is shown as a grey card, Task outside your view, without its title, assignee or dates; a dashed arrow joins tasks whose chain runs through tasks you cannot see. On a phone the Flow view is read-only. The list marks a linked task with a small diagram icon; point at it to see how many tasks it waits on and leads to.

How do I see and edit a task from the Flow view?

Point at a card and a quick view appears beside it: the task's status, assignee and dates, its length in working days, how late it will start and what is holding it up, its group, how many tasks it waits on and leads to, its checklist, comment and document counts, and the start of its description. Click the card to open the task in a panel on the right of the flow; the cards stay in sight, and the open card's arrows are picked out in blue. The panel is the same task the list opens. At the top are its status buttons (Start, Finish and so on), which work at once. Below them are its assignee, dates and group: press the pencil to change them, with the title, then Save, or Cancel to leave them as they were. The pencil is greyed out, with the reason, on a task you cannot edit. Saving new dates redraws the flow straight away, so the card moves to where its new dates put it, and when the change pushes the tasks after it, the panel offers to move them (see the next question). Below come the description, checklist, documents, the tasks it waits on and leads to, comments and activity; click a task under Waiting on or Leads to to open it in the panel instead. Cancel task and Delete are at the foot of the panel. Click another card to open that task, or press Escape, the close button or an empty part of the flow to close the panel; Open in list switches the page to the list and opens the task there. On a phone the panel fills the screen, with a back arrow to return to the flow.

What happens to later tasks when a task's dates change or it runs late?

A task that has not started is flagged when the tasks it waits on will not finish in time: on the list it gets an amber flag with the number of working days it will start late, for example +3d, and in the Flow view its card turns amber and the arrow from the task holding it up turns red. A task waits for every task linked before it to finish, and can start on the next working day after the last of them is due. A task that is still open past its due date is assumed to finish today at the earliest, so the tasks after it are pushed from today. Finished, reviewed and cancelled tasks hold nothing up, a task already in progress or paused is never flagged, and tasks without dates are left out. Working days follow the work week in Settings > General and leave out the public holidays of the assignee's country, so each task is judged on its own assignee's calendar; an unassigned task, or one whose assignee has no country, uses the work week alone. Flags are worked out from the dates every time, so they clear by themselves once the dates fit. Nothing moves on its own. When you save new dates on a task that other tasks wait on, and that pushes them later, a note under the task lists each task that would move and its new dates: press Move them to move them, or Just flag to leave every date as it is and keep the flags. A flagged task also has Fix dates when it is opened, on the list or in the task panel of the Flow view, which offers the same move for that task and everything after it. Moves only push tasks later, and only as far as needed: a task with room to spare stays put, nothing is pulled earlier when a task finishes early, and each task keeps its length in working days. Only tasks you may edit are moved; the rest are listed as flagged, not moved, and the tasks after them are measured from their unchanged dates. If someone changes the dates in the meantime, nothing is moved and the new plan is shown instead. Every moved task records the move in its activity, naming the task that slipped when you can see it, and in the change log. Moving and fixing dates needs edit access to Tasks.

How do I make a task template?

A template is a set of groups and tasks you can add to any project, for work that repeats from project to project. Open Tasks and press Templates at the top of the page. Everyone with edit access to Tasks can see the templates, but only someone whose Tasks access is modify with the All scope can create or change them. Press New template, give it a name and, if you like, a description, and press the tick. Click a template to open it. It works like a project on the Tasks page: Add group of tasks on its header adds a group, which can be mapped to a phase from Settings > Dropdown Options, and Add task under each group adds a task. Press a task's pencil to change it and its bin to delete it. Press Flow on an open template's header to see its tasks as linked cards, like a project's Flow view, in group bands. A template has no dates, so the cards are placed by what they wait on: each one a column after the tasks it waits on, and the tasks linked to nothing wait in the Not linked column on the left. Each card shows the task's assignee rule, its dates as working days (for example Phase start + 3d to Phase end) and its checklist and document counts; pointing at one shows more. Someone who can change templates links two tasks by dragging from the dot on a card's right edge onto the task that comes next, removes a link by clicking its arrow and pressing Remove link, and presses + on a card to add a task straight after it, in the same group and starting the working day after that task is due, as a task waiting on another does. Clicking a card opens it in the list, in its editor. A link that would make a loop is refused. Press List to go back. A template task has a title, a description, a checklist and documents, added the same way as on an opened task (type an item and press Enter; paste a link, optionally name it and press Add link; the cross beside one removes it), and the other tasks of the template it waits on. Instead of a person, it has an assignee rule: Unassigned, the project's Director, the project's Team Manager (each in your workspace's own terms), or Ask when the template is used, with a name for who to ask for, such as Senior auditor; everyone using the template picks one person for each such name. Instead of dates, it counts working days: from the start or the end of the group's phase on the project when the group has a phase, otherwise from the start or the end of the project, and a number of days after or before it. A phase's dates on a project are the ones saved for it by Auto-Allocate; when it has none, the phase runs from the first to the last week (or month) of the project's approved allocations tagged with that phase, so a phase worked in two stretches counts from the start of the first to the end of the last. Pending allocations do not count, and allocations are used only for someone who can view the Plan Grid, and only those of the people their Plan Grid access covers (anyone without it gets the saved dates alone, and the note on an undated task says what was looked at). When a project is saved as a template, allocations in a locked planning period that hides them from anyone are left out, since everyone with edit access to Tasks can read the template. A phase that has since been removed from Settings > Dropdown Options counts as no phase: its tasks count from the project, and the group is added without a phase. For example, Phase start and 0 days after is the first working day of the phase, and Phase end and 2 days before is two working days before the phase ends. Either date can be left as No date. Working days follow the work week in Settings > General and the public holidays of the assignee's country. The quickest way to build a template is from a project that already has the work planned: press the Use a template button (the copy icon) on that project's header in the task list, then Save this project as a template, name it and press Save as template. Its groups, tasks (except cancelled ones), checklists, documents and links between tasks are copied, and each date becomes a number of working days from the start of the task's phase (worked out the same way), or of the project, counted on the working days of the person the task is assigned to. Everyone with edit access to Tasks can read templates, including the copied descriptions and document links, even when their own access does not cover that project's tasks. A project in a locked planning period that hides it from anyone cannot be saved as a template. A template holds up to 300 tasks in up to 50 groups, with up to 100 checklist items and 50 documents per task; a bigger project is refused rather than copied in part. A task assigned to the project's director or team manager keeps that rule; anyone else's task becomes unassigned in the template, so set it to Ask if someone should be picked each time. A task whose date cannot be counted, because the project or phase it would count from has no dates, is saved without that date. Use the pencil and bin on a template's header to rename or delete it. Changing or deleting a template never changes tasks already added from it.

How do I add tasks from a template to a project?

You need edit access to Tasks; with Own or Team access, only on projects you are assigned to. To add a template to many projects at once, see the next answer. For one project, on the Tasks page press the Use a template button, the copy icon, on the project's header (it is not shown in the Flow view or on an inactive project). A strip opens under the header: choose a template, and before anything is added it shows exactly what will be created. Each of the template's groups is listed with a tick box to include or leave it out, the dates on this project its tasks count from (for example Fieldwork phase: 3 Nov 2026 to 12 Dec 2026, or Fieldwork phase, from its allocations: 3 Nov 2026 to 13 Dec 2026 when the phase has no saved dates), and whether it joins a group of the same name already on the project or becomes a new group. Under each included group, every task is listed with its assignee and its dates worked out for this project. A task whose date could not be worked out, because the project has neither saved dates nor approved allocations for that phase, or has no start or end date, has no date, and an information icon on it says why; so does a due date that was moved to the start date because it would otherwise come first. If the template asks for people, a picker for each one appears at the top, for example Senior auditor; tasks for a role nobody is picked for are added unassigned. A Director or Team Manager rule on a project without one also leaves the task unassigned. If this project already has tasks from the same template, a warning says how many, since using it again adds another copy. Press Add, which says how many tasks it will add, to create them all at once with their checklists, documents and links between them; they appear at the end of the project's list with the first one highlighted. If your Tasks access covers only your own or your team's tasks, every task added has to stay inside it: a task that would be assigned outside it is marked, and Add stays greyed out until you leave its group out or pick someone else. The tasks added are ordinary tasks from then on: edit, move or delete them as usual, and changing the template later does not change them. Each one is recorded in the change log, which names the template it came from.

How do I add a template to several projects at once?

Open Tasks, press Templates at the top of the page, and press Use on projects on the template's header. You need edit access to Tasks; with Own or Team access, only the projects you are assigned to are offered. First choose the projects: only active ones are listed, and you can search by name or code and narrow the list by category, project type, Director and Team Manager (in your workspace's own terms), or tick My projects. Tick projects one by one, or press Select all shown to tick every project the filters leave; projects you ticked stay ticked when you change the filters. Up to 100 projects can be used at once. Press Preview to see one row per project: how many tasks would be added there, how many would have no dates because that project has no dates for the phase (or for the project itself) they count from, and a warning when the project already has tasks from this template, since using it again adds another copy. Press the arrow at the end of a row to see every task with the dates and assignee worked out for that project. If the template has more than one group, tick the groups to add; that choice is the same for every project. If the template asks for people, for example Senior auditor, pick each one once for every project; to pick someone else on one project, open its row and change it there. A row also says when the person picked is not on that project. Untick a row to leave that project out. A project where a task would be assigned outside your access scope cannot be ticked. Press Add to add the tasks to every ticked project. Each project is added on its own, exactly as the Use a template button on that project would add it, so if one fails the others are still added: its row shows why, and Try the failed ones again retries just those. Rows that were added say how many tasks they got.

Which tasks can I see?

That depends on the Tasks permission of your organization role in Manage > Access. View lets you open the page and modify lets you create and edit tasks. The access scope is matched on the task's assignee: Own shows the tasks assigned to you (your account needs a linked person record), Team shows the tasks assigned to anyone in your team, and All shows every task. Own and Team also show unassigned tasks on projects you are assigned to, meaning you have an approved allocation on the project, contribute to it, or are its director or team manager, and any task holding a checklist item assigned to someone they cover, so you can reach an item that is yours to tick. A task you cannot see is treated as if it does not exist. The starter roles give Member view access with Own, Lead view access with Team, and Director and Admin full access to all tasks. A role created before Tasks existed gets view access with Own, unless it already had full access to every other module, in which case it gets full access to Tasks too. If the plan lock hides a project from you, its tasks are hidden with it. A project that is only View only stays fully workable on Tasks: freezing a planning period fixes the plan, not the work on the project.

Travel

What is Travel used for?

Travel records planned and confirmed trips by person, project, location, date range, status, purpose, and notes. The dates come first on the form and are one field holding the whole range: type it, or open its calendar and click the first and last day of the trip. Travel appears in the grid and dashboard so planners can understand travel load and availability. If your workspace locks a planning period and that lock covers travel, trips running through it are frozen or hidden; a trip that crosses the edge of the period is treated as inside it.

Can I add travel for multiple people?

Yes. Editors can add or edit travel with person search and selected tags, which allows one travel workflow to create or maintain records for multiple people. The same person search is in the Add Travel form opened from a Plan Grid cell, which starts with that cell person and lets you add the rest of the party. Project is optional on a trip and is chosen the same way on both forms: type part of a project code or name to narrow the list rather than scrolling it, pick the match, or clear the box to leave the trip with no project. Only active projects are offered, except the one already recorded on a trip you are editing, which stays selectable. The Travel page can also filter by year, status, and one or more selected people.

What is the difference between Planned and Confirmed travel?

Planned travel is tentative and useful for forecasting. Confirmed travel is committed and should be treated as stronger scheduling context. The app uses distinct status badges and grid icon colors for each.

Where do the travel regions come from?

The Region list on Add Travel comes from Settings > Dropdown Options > Travel. It starts with seven built-in regions (North America, South America, Europe, Africa, Middle East, Asia, and Oceania) and an admin can add, remove, reorder, or rename them there. Renaming a region also relabels the trips already recorded under the old name. Region is optional on a trip, and each region can be given a color under Settings > Color Defaults > Travel.

Why does some travel show as pending approval?

If your workspace requires approval for travel, newly added travel is held as pending until an approver confirms it. This is separate from the Planned/Confirmed status. Pending travel still appears on the plan grid with the plane icon plus a small hourglass "awaiting approval" marker and is flagged in the cell hover tooltip; the Travel page tags it with a Pending badge; and it shows in Approvals > Travel for the line manager or approving roles to approve or reject. A rejected trip is hidden from the plan grid (and left out of travel figures) but remains on the Travel page, tinted red with a Rejected badge. Rejected trips are hidden on that page by default: when a year has any, a Rejected button above the table says how many and shows them, and an editor can clear them out from the same place. Travel added by an exempt person, or for an exempt person, is approved automatically. Approvers are configured under Settings > Approvals.

Leave

What is Leave used for?

Leave tracks absences by person, date range, leave type, status, source, and notes. Records are grouped into readable ranges in the Leave page and appear as leave badges in the grid.

How do I pick the dates for leave or a trip?

Leave and travel dates are one field holding the whole range, not separate start and end boxes. You can type it: 1/12/2026 - 31/12/2026, or a single date for one day. Days can be written day-first (1/12/2026) or as 2026-12-01, with . / or - between the parts, and the two ends split by a dash or the word to; if you type them the wrong way round they are swapped for you. Text the field cannot read is outlined in red and put back to the saved range when you leave the box. Or click in the field, or the calendar button beside it, to open the calendar (Down arrow does the same from the keyboard): two months open below the field, you click the first day of the range and then the last, and the days between are highlighted as you move the pointer. The calendar closes itself on the click that completes the range. For a single day, click that day and press Apply. Cancel puts back the dates the calendar was opened on, and Escape does the same. Single arrows move a month, double arrows move a year, and Today comes back to this month; the arrow keys move a day at a time, Page Up and Page Down move a month, and Enter picks the focused day. Under the calendar it states the range and how long it is, and on leave forms how many working days that is, because leave is only recorded on those: a Friday-to-Monday range is four days but two days of leave. Days outside your organization's working days are dimmed, and a public holiday for that person carries a dot. Only holidays that fall on a working day are dotted, which is exactly the set the 'Skip public holidays' tick box acts on: a holiday on a weekend or other non-working day is already left out of the leave, so nothing is skipped for it. On the Leave and Travel pages the calendar opens on the year the page is filtered to, so planning a later year does not start you at today. The field is the same on the Leave page, the Travel page and the grid quick-add forms.

What happens if leave overlaps a public holiday?

Days that are already a public holiday are left out of the leave you add. When the range you pick covers one, the Add Leave form names the days and offers a "Skip public holidays" tick box, which is on by default, so the leave is recorded on the remaining working days only. Untick it to record leave on the holidays as well. The same tick box appears when you change the dates of an existing leave range, on the Leave page and in the grid cell editor's quick add, because moving a range re-expands it. Public holidays are matched on the person's country, set under Manage > People, so when no country is set nothing can be matched and the form says so instead of showing a tick box. A workspace with no holidays on record sees neither the tick box nor that message, since there is nothing to skip. Only holidays ticked as non-working under Manage > Holidays count, so a holiday your organization works through never blocks leave. A public holiday that falls outside your working days is not counted either, because leave was never going to be recorded on that day: over a Christmas that runs Friday and Saturday on a Monday-to-Friday work week, the form names the Friday only. If every working day in the range is a public holiday, the save is refused and you are asked to untick the box if you meant it. Skipping is about counting: leave on a public holiday never made the person any less available, since they were already away, but it did add to their leave days. Bulk import is not affected and still records those days, because it mirrors your leave system; the validation step reports how many days in the file fall on a public holiday so you can check them.

Why does some leave show as pending approval?

If your workspace requires approval for leave, newly added leave is held as pending until an approver confirms it. Pending leave still appears on the plan grid like normal leave, marked with a small hourglass "awaiting approval" icon and split out in the cell hover tooltip; the Leave page tags it with a Pending badge; and it shows in Approvals > Leaves for the line manager or approving roles to approve or reject. A rejected leave is hidden from the plan grid (and left out of capacity figures) but remains on the Leave page, tinted red with a Rejected badge. Rejected leave is hidden on that page by default: when a year has any, a Rejected button above the list says how many and shows them, and an editor can clear them out from the same place. Because the day is still booked there, adding leave for that date again resubmits it for approval instead of creating a second record. Leave added by an exempt person, or for an exempt person, is approved automatically. Approvers are configured under Settings > Approvals.

Can I change the leave statuses?

Yes. Leave statuses come from Settings > Dropdown Options > Leaves and start as Planned and Confirmed. Add, remove, reorder, or rename them there and the Leave page, the grid quick-add, and the leave import template all follow, with the first status in the list used as the default. Leave saved with a status you later removed keeps it until you edit that record. Each status can be given its own color, fill, and pattern under Settings > Color Defaults > Leaves.

What do Import and Manual filters mean?

Import and Manual are leave sources. Import covers leave added via file upload or the API. Manual covers leave entered directly through the Leave page. Use the source toggles to show or hide each type.

How does leave import work?

Manage includes a leave import wizard for .xlsx and .csv files. Download the template, upload the completed file, validate rows, preview errors, and import valid rows. Date ranges are expanded to individual days and non-working days are skipped unless configured otherwise. Public holidays are not skipped on import, unlike leave added by hand, because an import mirrors your leave system; the validation step reports how many days in the file fall on a public holiday for the person concerned so you can check them before importing. Rows dated inside a planning period whose lock covers leave are reported as failed rows with a reason, and the rest of the file still imports.

Can leave uploads be automated?

Yes. Manage > Leaves includes an error report email and an API key panel. Editors can generate or revoke a leave API key, copy it once, download a Windows upload script with the leave template, or use the documented curl pattern to validate or import files programmatically. Three endpoints accept the key as a Bearer token: GET /api/[org]/leaves/people returns active people with their emails (used to build the file), GET /api/[org]/leaves/leave-types returns configured leave types, and POST /api/[org]/leaves/upload?import=true imports a completed file. API imports are logged as API import and set the leave source to Import. Keep the key private because it can import leave without a user login.

Can I sort the Leave page?

Yes. The Leave table can be sorted by date, person, type, status, source, or notes. Imported leave is read-only in the Leave page, while manually entered leave can be edited or deleted by users with modify access. If your workspace locks a planning period and that lock covers leave, days inside it show a padlock instead of the edit and delete buttons, or do not appear at all; ask an administrator what is locked.

Capabilities

What can I track under Capabilities?

Capabilities has Skills and Certifications tabs. Skills track person, topic or area, experience level, and interest. Certifications track person, issuer, certification, issue date, and expiry date.

How do filters and editing work in Capabilities?

Search by person, topic, or certification and filter by topic, level, interest, or issuer. Users with modify permission can add, edit, and delete skills or certifications; view-only users can use it as a staffing reference. Own-scoped Capabilities limits both the Skills and Certifications tabs to the linked person record.

Why does a skill or certification show as pending approval?

If your workspace requires approval for skills or certifications, a newly added record is held as pending until an approver confirms it. The Capabilities page tags a pending record with a Pending badge and a rejected one with a Rejected badge. It shows in Approvals > Skills or Approvals > Certifications for the line manager or approving roles to approve or reject. A rejected record is left out of person profiles and analytics but remains on the Capabilities page. Rejected records are hidden on that page by default: when there are any, a Rejected button beside the filters says how many and shows them. There is no bulk clear here; delete the individual row if you want it gone. A record added by an exempt person, or for an exempt person, is approved automatically. Approvers are configured under Settings > Approvals.

Manage

What does Manage control?

Manage is the operational data workspace. It contains People, Projects, Access, Events, Holidays, Leaves, and Change Log tabs. It powers the planning views, filters, permissions, and audit trail.

How do people records work?

People records include name, email, team, person role, line manager, city, country, color, and active status. The line manager can be used as an approver for that person under Settings > Approvals. Active people appear in planning by default, while inactive people can be included with filters for historical or future review. A person record can also be linked to a user account so Own-scoped permissions know which records belong to that user.

How do project records work?

Projects include name, code, category, type, color, start and end dates, director, team manager, and active status. These fields drive grid display, Overview timing, grouping, filtering, dashboard analytics, and default color rules. The project table has its own From and To date filter, which starts on the current year, plus a search box, so a project planned for a later year is not listed until you widen the range. Saving still works either way: when you add or edit a project that falls outside the current filter, the range stretches to include it and a search term it does not match is cleared, so the row you just saved stays on screen.

What does Bulk Allocate do?

Bulk Allocate is a five-step wizard: select projects and a date range, split each project into phase date windows (a default percentage split with per-project overrides), pick people per project and choose each person's role, set an allocation percentage per role and phase, then review before creating allocation records. Alongside the built-in director, team manager, and contributor roles you can define your own roles (e.g. Backup Team Manager) in Settings → Bulk Allocate, where you also set the default phase split and the percentage matrix. Allocations are tagged with the matching phase, existing allocations can be skipped or overwritten, and phase windows plus people-and-role picks are saved for the next run. A month that someone is planned for week by week (or day by day) on a project, with no month allocation, counts as existing. This includes a month converted to weekly when a week was removed on the Plan Grid. Skipping leaves it alone, and overwriting gives the weeks it already has the new percentage and the phase of the window each week falls in, so a removed week stays empty. Week or day allocations still waiting for approval, or rejected, do not make a month count as planned week by week. The capacity warnings on the review step count each period the way the Plan Grid shows it, so weekly allocations count in a monthly run and monthly ones in a weekly run. Review the result because generated allocations still need planning judgment.

How do People and Project Excel uploads work?

Each upload wizard provides a template, accepts completed Excel files, validates rows, previews valid and invalid rows, and imports only valid rows. People upload supports teams, roles, city, country code, colors, and active status. Project upload supports categories, types, dates, director, and team manager. On Manage > Projects, Upload Excel is a menu with two choices: Projects, and Allocations (see the allocation upload entry).

How do I upload allocations from Excel?

Open Manage > Projects, click Upload Excel and choose Allocations. It needs edit access to Manage, the same as Bulk Allocate; without it the Upload Excel button is greyed out. Download the template first. It has an Allocations sheet to fill, a People sheet and a Projects sheet listing who and what you can plan for, and an AI Instructions sheet. If you keep allocations in a spreadsheet of your own, give your AI tool the template and your file and ask it to fill the Allocations sheet following those instructions. Fill one row per person, project and period from row 4, under the instruction and example rows of the template (you can delete those two and start straight under the header instead): Person Email (matched to people by email only), Project (its code, or its exact name if it has no code), Period Start (YYYY-MM-DD), Granularity (Week or Month), Percentage, and optionally Phase and Team. A percentage is the share of the person for that period; do not reduce it for leave. Before uploading, choose what happens when a cell already has an allocation: update it with the value in the file, or keep the current value and skip that row. An upload never removes allocations that are not in the file. Validate shows every row as New, Update (with the old and new percentage), Unchanged, Kept or Error, with filters for each. Rows with errors are left out of the import: an unknown or inactive person, a project that is not found or is locked, a date that cannot be read, a Day granularity, a percentage that is not a number above 0, a phase or team that is not on your lists, a period the plan lock closes to you, the same person, project and period appearing twice in the file, or a Month row for a month the person is planned for week by week on that project, in your workspace or by Week rows in the same file (for example one converted to weekly when a week was removed), since a month value would fill the week that was removed; use Week rows for that month instead. When you choose to keep current values, such a row shows as Kept. Warnings are imported but shown: a date moved back to the Monday of its week or the 1st of its month, a percentage over 100 reduced to 100 (the most one allocation can hold), a period outside the project dates, an inactive project, and a person whose total would go over 100% in a week, judged the same way as the Conflicts page. The review also says how many allocations will need approval; those land as pending, exactly as if they were entered on the grid. Download issues report returns your file with an Upload Status and Upload Issues column for each row, so you can fix the errors and upload it again; rows already imported then show as Unchanged. A restore point is saved before the import, and the import is written to the change log as one entry. At most 5,000 rows per file.

How do holidays work?

The Holidays tab groups public holidays by country, supports country search, date filtering, manual add/edit/delete, collapsible country groups, and a sync flow that can include extra countries. Every column sorts: click Date, Name, Type or Non-working to order the rows inside each country group, and click Country to flip the order of the groups themselves. Sorting by Non-working is the quick way to bring the days still waiting on a decision to the top, and ticking a box does not move its row out from under you: rows hold their place until you sort again or reload. Sync pulls from a public holiday calendar for every country your people are in, for this year and next, and covers three kinds of day: public holidays, bank holidays, and optional holidays. School holidays and observances such as Valentine's Day or Mother's Day are never included, because they are not days off work. Each row shows which kind it is, next to a Non-working tick box. That tick box is the one that matters: it says whether your offices are actually closed that day, and it is what the rest of the app reads. Public holidays arrive ticked. Bank and optional holidays arrive unticked, because only you can say whether your organization closes for them: a bank holiday is often an eve such as Christmas Eve or New Year's Eve, which some offices close for and others work, and an optional holiday is a day most people take off without it being a general public holiday. After a sync, the tab tells you how many newly added days are waiting for an answer, then filters the list to every day currently marked as worked and opens the country groups holding them, so you can settle them together. Untick anything your organization works through, such as a public holiday that is official but not generally taken off. A holiday that is not ticked is an ordinary working day everywhere else: it shows no marker on the plan grid, does not count as time away, does not reduce capacity on the Dashboard or in the analysis export, and does not stop leave being booked on it. It stays listed here so you can change your mind. Your answers survive future syncs, so a day you unticked is not re-ticked the next time you press Sync, and a holiday with no classification recorded shows as Unclassified: either you added it by hand, or it was synced before this tab started storing them.

How do I lock next year while the plan is still being built?

Open Manage > Projects and use the Plan lock card above the project table. Turn the plan lock on, then add a locked period: give it a name, a start month, and optionally an end month (leave the end month empty to lock everything from the start month onward). Periods are set by month because allocations are locked by the period they start in. Press Save to apply, including the on/off switch. Under "This locks", tick what the period closes: Projects, Grid notes, Leave, Travel, Events. Anything left unticked is untouched and stays visible and editable inside the period as usual. For each thing you tick, choose what the lock means: "Hidden" removes it for everyone else, and "View only" leaves it visible but unchangeable. The two choices are independent, so you can hide the projects while making the leave view only, or lock the leave and nothing else. New locked periods start with Projects hidden and nothing else ticked, because the usual reason to lock a period is keeping an upcoming engagement confidential rather than closing the period for work. A period must lock at least one thing; if you untick everything, remove the period instead. Ticking Projects covers every project that starts inside the period (a project with no start date counts from its earliest allocation), together with every allocation made in the period. A hidden project does not exist for everyone else: it is gone from Manage, the Overview, the Plan Grid, Bulk Allocate, the Dashboard, Conflicts, Approvals, profiles and the change log, along with all of its allocations and any trips linked to it. Everyone else also cannot create a project that starts in a locked period, or move a project into one. While the plan lock is on and any locked period that has not ended ticks Projects, every project needs a start date, for everyone including administrators: a new project cannot be saved without one, an existing one cannot have its date cleared, and a project upload rejects rows without one. Events work the same way while any period ticks Events. Projects created before that with no start date are placed by their earliest allocation, so adding an allocation before a locked period makes such a project visible to everyone; Manage marks them "No start date" so you can set one. A project that started before the period and runs on into it stays visible, although its allocations inside the period are still locked. A view only project stays visible but cannot be edited or deleted, and takes no new allocations; its tasks stay open to work on. A hidden project takes its tasks with it. Ticking Events does the same for events, by the date each one starts, on the Events page, Manage > Events and the Overview. In Manage, projects and events covered by a lock carry a Hidden or View only badge, so the people who keep access can see which ones everyone else is missing. Deleting a person or a project also removes or changes the records that hang off it, so everyone else cannot delete one while that would reach anything the lock covers: the allocations, leave, trips or grid notes of that person inside a locked period, a locked project or event the person is director or team manager of, contributes to or attends, a locked note the person receives, a task on a hidden project assigned to the person, or the allocations and linked trips of that project inside a locked period. The delete is refused with a message that the planning period is locked, and nothing is removed. Hiding something removes it from the Plan Grid, Overview, Dashboard, Conflicts, Approvals, the change log and profile pages, and view only leaves it there but refuses every change, including approving a request against it. Ticking Leave or Travel applies everywhere those records appear, including the Leave and Travel pages, so days a person has already booked inside the period are hidden or frozen for them too, and an imported leave row dated inside the period is reported as a failed row rather than imported. Travel is judged on its whole date range, so a trip that runs across the boundary is treated as inside the locked period. A locked period still appears on the Plan Grid as a normal column, emptied of whatever is hidden, so people can carry on using it for everything that is not locked; the column disappears altogether only when Projects, Grid notes, Leave and Travel are all set to hidden (events are not on the grid, so Events makes no difference to that). Then tick the roles that keep access. A role you tick works in the locked period exactly as it does elsewhere, so a role with view-only access to the grid still cannot edit it. Access is granted by role rather than to named individuals, so to give one person access, put them on a role that has it. Administrators always keep full access, so a workspace cannot lock itself out. An API key has no role, so an integration is treated like anyone else and cannot write into a locked period. On the Plan Grid, a Locked marker appears beside the year picker whenever the year you are viewing has locked or hidden periods; for administrators it is a button that opens this setting. Excel exports are administrator-only and are not filtered, so an export run by an administrator still contains the locked period.

What is the Change Log?

The Change Log records key create, update, delete, approve, and reject actions, including role changes, role definitions, API key events, imports, and allocation, leave, travel, skill, and certification approval decisions. Each download of a workspace export is recorded too, as an Exported entry naming who took it and, for the Export for analysis workbook, the date range it covered. Those entries are shown to everyone with Manage access, and a download that cannot be recorded is stopped. Where available, it stores old and new values so reviewers can see what changed. A bulk action, such as deleting a leave range, changing a phase across the grid, or a leave import, is written as one entry that names the people and projects it touched and the date span it covered, alongside the count, so you can tell what the batch actually did without opening the records. Long lists are shortened to the first few names followed by a count of the rest. Entries about a locked planning period are withheld from anyone the plan lock hides that period from, so two people with Manage access can see different entries. Grid note entries follow the note's audience as it stood when the change was made: you see an entry only if every version of the note it records was visible to you because you wrote it, because it named you as a recipient, because it was visible to everyone, or because it was addressed to your role and the note is still addressed to that role today. A deleted note is not matched by role, and neither is one whose role has since been renamed. So a private note addressed to someone else does not appear here, even to an administrator, and neither does an edit that later shared it. The administrator-only Excel export includes the whole change log, these entries too. Changes to the plan lock are listed for everyone with Manage access, but the details, including which roles keep access, are shown only to full admins, the only people who can change the plan lock. The list shows the most recent entries first; when there are older ones, a Load older entries button at the bottom fetches the next set. Entries are kept for up to two years from the day they were written, then removed automatically.

Settings

How do I set who approves leave or travel?

Open Settings > Approvals and select the area (Leaves or Travel). Turn on Require approval, which selects Line Manager by default, then choose the approvers: the person's line manager (set per person under Manage > People), anyone holding one or more selected roles, and/or specific named people. At least one approver is required while approval is on. You can also list roles or specific people who are exempt: their own records, and any they add for other people, are approved automatically. While the switch is off, everything in that area is approved automatically. If a particular person has no line manager or matching approver, administrators can approve. Leaves and Travel are configured independently. The remaining areas (Allocations, Skills, Certifications) are shown for a future release.

What do Notification settings do?

Settings > Notifications sets the workspace default for the summary email: how often it goes out, on which day, at which hour, and, most importantly, in which timezone. The built-in fallback is every Monday at 08:00 Amsterdam time, which is the middle of the evening in Sydney and the small hours in California, so setting this once is worth doing. It applies to everyone who has not chosen their own schedule, including people who join later. Nobody is sent a summary until they have signed in at least once, so accounts created for people who never use the app stay quiet. It is a default and never a rule: it cannot override an individual’s own setting, and changing it does not move anybody who has already chosen. There is deliberately no control here for deciding who receives the summary or forcing it on somebody. Nobody can send this email to anyone; each person subscribes to their own, so the only thing an administrator sets is where everybody starts. Setting the workspace to Never means nobody is emailed unless they switch it on for themselves. Each person changes their own under My Profile > Notifications.

Somebody is not getting any emails from the app. Why?

Settings > Notifications has a Delivery problems panel below the schedule. It lists anybody in this workspace whose address the app has stopped sending to, and it covers every message the product sends, not only the summary email: set-password links and import reports stop arriving too. An address lands there for one of three reasons. It bounced, which usually means a typo or a mailbox that no longer exists. The person marked one of our emails as spam, in which case we stop sending to them and the right fix is to ask them, not to force it. Or our email provider is refusing the address outright after earlier failures. When the panel is empty it says so, which is the answer to whether email is working at all. Correcting the address under Manage > Access is the usual fix, and it works straight away because the corrected address was never blocked. Try again tells the app the address is worth another attempt: it does not repair anything at the email provider, so if the address is genuinely dead the next failure puts it straight back on the list. Allow a minute for a Try again to take effect. The list itself updates within seconds of a failure, because our email provider tells us as it happens rather than us checking periodically. This panel is the only place this information is shown, so an administrator who can reach Manage but not Settings will not see it.

What is configured in General settings?

General settings control the organization name, workspace URL slug, working days, and whether day view hides non-working days. Changing the workspace URL changes the /org/... address, so old bookmarks and shared links stop working, and other signed-in users may need to sign out and back in. Your restore points in Settings > Backups are kept and can still be restored. While any of them were taken under the old URL, that URL stays reserved to your workspace: nobody else can create a workspace with it, and you can switch back to it. It is freed once those restore points have aged out.

What are Dropdown Options?

Dropdown Options define selectable values used across the app: teams, people roles, project categories, project types, project phases, event categories, travel regions, leave types, leave statuses, capability topics, capability levels, interest levels, certification issuers, and certification names. Admins can add, remove, reorder, save groups, or rename values. Renaming a value updates every existing record that used the old name, and every setting that referred to it: its color, the view defaults that hide it, and any approval policy that names it all follow the rename instead of being left behind under a value the dropdown no longer offers. Because a rename rewrites records in every period, a plan lock limits it: while a locked period ticks Projects, a team or phase can only be renamed by people who keep access to that period, and the same goes for leave types and statuses under a leave lock, travel regions under a travel lock, and people roles under a grid notes lock. Project categories, project types and event categories can always be renamed, since renaming a label changes no plan.

What do Color Defaults control?

Color Defaults control project color rules, event color rules, event and phase fills or patterns, holiday styling, leave status styling, and inherited allocation styling. Defaults can also be applied to existing projects or events where supported.

What does Terminology change?

Terminology lets authorized users rename key labels such as Director and Team Manager. These terms appear in project forms, event ownership, grouping controls, filters, dashboards, grid labels, and upload templates.

What are View Defaults?

View Defaults set the starting state for grid, timeline, and dashboard views. Grid defaults include visible project categories, visible people roles, default grid view, grouping, sorting, holiday display, inactive people, percentage display, and layer visibility for projects, leaves, travel, conflicts, events, notes and tasks (the Tasks layer starts off unless it is ticked here). Dashboard defaults include leave and holiday exclusion, inclusion of inactive people and projects, and default visible categories and types. Overview defaults include the starting view (Gantt or Outlook), whether projects and events are shown, and the default visible project categories and phases. Tasks defaults set which status view the Tasks page opens on: All (the default), Open, To review or Done. Until Overview categories are saved, the Overview uses the Grid's shown categories.

Access

How do users and custom roles work?

Manage > Access has Users and Roles sub-tabs. Users assigns email addresses to named roles, links users to person records, removes access, and can set a password directly or email a set-password link to an existing workspace user. Setting a password directly takes effect at once, and because somebody other than the account holder chose it, that person is required to replace it with one of their own the next time they sign in. The link is the alternative that avoids a shared password altogether: it lets that person choose their own straight away and stays valid for an hour. A password they already have keeps working until they use it, though any earlier reset link they were sent stops working as soon as a new one is issued. If the email cannot be delivered an error is shown and their password is left unchanged, so the action can simply be retried. Roles defines named permission sets with module-level view and modify rights. System roles cannot be modified, while custom roles can be created for your organization.

What is the difference between base access and module permissions?

Base access is the broad role level, admin or member. Module permissions decide whether a role can view or modify each product area. Scoped modules can be set to All, Team, or Own. The left navigation and API access both use these resolved permissions.

Which modules support Own and Team scope?

Own and Team scope are available for Grid, Overview, Conflicts, Travel, Leave, and the Skills side of Capabilities. On the Overview, scope shows the projects the people in scope direct, manage or are staffed on that year and the events they direct, contribute to or attend, and team member counts include only people in scope. Phases drawn from allocations count only the allocations of people in scope too. Both use the user account linked in Manage > Access to a person record: Own limits access to that person only, while Team limits it to everyone sharing that person's Team (set in Manage > People). If no person is linked, scoped pages may show no records or block writes until the link is fixed; if the linked person has no Team, Team scope behaves like Own.

What does Sync People do?

Sync People creates or updates user access rows from people records that have an email address, links each user to the matching person record, and assigns the default member role where needed. It reports synced, linked, already complete, and skipped-no-email counts. It is useful after bulk people uploads or email cleanup. Syncing sends no email. The new accounts receive nothing until an administrator sends them a password, and no summary email until they have signed in, so a person record with a placeholder address can be synced safely.

How do role/sign-out controls work?

Your signed-in name and resolved organization role appear at the bottom of the sidebar. Your name links to My Profile, and Sign out ends the current session. The sidebar footer also holds the Feedback button, the Manual FAQ, the Guided Tour link (for users who can view Manage), and, when permitted, the billing status. A separate help assistant button sits in the bottom-right corner of the page.

How do I get a summary email of everything waiting for me?

My Profile > Notifications has a Summary email schedule. Choose every day, every week or every month, pick the day and the hour, and pick the timezone the hour is measured in. The timezone list starts on your own computer’s zone if it is not already one of the common ones. The summary lists what is currently waiting for you: approvals you can decide, over-allocations in your scope, and notes that need you. It also tells you when a request of yours was turned down, with the reason the approver gave and a link to the record so you can change it and resubmit it or remove it; the link shows the rejected rows and opens on the right year, since they are hidden by default. That part covers what was decided since your last summary rather than everything ever refused, so you are told once. It is the one thing in here that nothing else chases you about: a refused booking simply sits on its page, hidden by default, and the app will not badge you about it. It is only ever sent when there is something in it, and only to an account that has signed in at least once, so an account created for somebody who has never used the app (for example by Sync People) is not emailed. A summary that arrives to say nothing needs you is one you stop opening. The same panel tells you when one was last actually sent to you, so a stretch with no email is visibly a quiet stretch rather than something broken. Notes shared with everyone are the one thing it treats differently, and only when they are not addressed to you as well: a note that names you counts as yours however widely it was shared. An announcement asks nothing of you, so it never causes a summary on its own, and it is left out of one entirely unless you switch on Include notes shared with everyone. Even then it only rides along in a summary that an approval, an over-allocation or a note addressed to you had already earned, or that a request of yours being turned down had earned. That is the one place the summary and the sidebar badges differ on purpose: the badge counts an announcement you have not read yet, the email does not chase you about it, and a refusal works the other way round because only the email reports it. Everything in it links straight to the page or the note it came from. Until you choose, you follow your workspace default, which an administrator sets under Settings > Notifications, so a workspace in Sydney is not left on a UTC morning that lands at six in the evening. If nobody has set one, that default is every Monday at 08:00 Amsterdam time, so the app can tell you something before you have discovered any settings screen at all. Choosing your own schedule stops you following the workspace: change it there later and yours stays put. There is a link to go back to following it. Setting yours to Never means never, whatever the workspace says. No administrator can override an individual choice in either direction. Turning it off means this app will not email you at all about work in progress; the badges still show everything when you are in it. You do not have to come here to stop it: every summary email carries its own link to turn itself off, and mail programs that show an Unsubscribe control next to the sender name can use it too. Following the link in the email turns off the summary for the workspace that email came from, and leaves any other workspace you belong to alone. Using your mail program's own Unsubscribe control is broader, because it is a message to the sender rather than to one workspace: it turns the summary off everywhere. Either way the choice lands in this panel, so you can turn it back on here whenever you want. If you set a schedule for a time that has already passed today, the first summary arrives on the next one, not within the hour. Monthly schedules stop at the 28th so that February never skips a month.

Billing

What does the billing status in the lower-left corner mean?

The lower-left status shows the current subscription state: trial days left, active billing, scheduled cancellation, overdue payment, canceled billing, or not started. It links to Settings > Billing when your role can view billing.

What can I do in Settings > Billing?

Billing shows seat count, estimated monthly or annual total, subscription status, trial end, renewal or access end date, invoice history, and payment method. It can start card checkout, start invoice billing, open the Stripe portal, and show checkout success or cancellation messages.

How long is the free trial, and will I be reminded before it ends?

A new workspace gets a 90-day free trial. Workspace admins receive an email about 14 days and about 3 days before it ends, and another within a day after it has ended (the reminders go out once a day, in the morning UTC). When the trial ends without a subscription, the workspace is paused and shows a "Your free trial has ended" page until an admin adds a subscription in Settings > Billing. While a workspace is paused after its trial, Settings stays open to everyone and Manage stays open to workspace admins, so they can add their team first: billing counts active people as seats and needs at least one. Workspaces that have a subscription (including a canceled one) or a billing override get no trial emails.

How do invoice billing and overdue blocking work?

Invoice subscriptions use the configured net payment period. If an invoice remains overdue after the grace period, the workspace can be blocked until billing is resolved. Billing-blocked users are routed to Settings so payment can be fixed.

Our subscription was canceled. How do we start it again?

Once a subscription is fully canceled, Settings > Billing shows the start options again (card checkout or invoice billing). Starting one creates a new subscription and lifts the billing block. The free trial only applies to first-time signups, so a workspace that already had a subscription starts billing immediately on resubscribe rather than getting another trial. A subscription that is only scheduled to cancel at period end is not canceled yet: use Resume subscription instead while it is still active.

Data

Does the app keep backups of our data?

Yes, at two levels. The database itself is on a hosting plan with automated daily backups kept for 7 days, which covers the whole platform and is only used for disaster recovery. Separately, your workspace gets its own restore points: a copy of your planning data is saved every night, immediately before every bulk change such as an import, a bulk edit or an auto-allocate run, immediately before any restore, and whenever a full admin asks for one. Those restore points are listed in Settings > Backups, where a full admin can download one or roll the workspace back to it. We keep the last 7 nightly restore points (up to 8 days), the last 10 you create by hand (up to 30 days), and ones taken before a bulk change or a restore for 7 days. A restore point has to be inside both limits to survive, so a nightly copy goes once seven newer ones exist even if it is not yet 8 days old. The Backups tab shows when each one will be removed.

How do I restore our workspace to an earlier point?

Go to Settings > Backups. Only a full admin can use it; anyone else with Settings access sees the tab but only an explanation of who can. Pick a restore point and press Restore. You then choose whether to restore everything or only certain areas such as Leave, Allocations, Travel, Events, Public holidays, Skills and certifications, Grid notes, Tasks, Saved dashboards or Settings. Press "Check what this will change" to see exactly how many rows would be removed and restored before anything happens, then type the workspace name to confirm. People and projects can only be restored as part of a full restore, because allocations, leave, travel and everything else are attached to them. A restore point is saved automatically just before the restore runs, so a restore you did not mean to do can itself be undone.

Who can restore data, and will anyone be told it happened?

Only a full admin, meaning someone whose role grants view and modify on every module. Holding the Settings page alone is not enough. Every restore is written to the change log with who ran it, which restore point was used and how many rows moved, and every other full admin is emailed afterwards. The notification is sent after the restore rather than before, because the restore is already reversible by then.

I ran the wrong import or bulk edit. Can I undo it?

Yes. A restore point is taken automatically immediately before every Excel import of leave, people or projects, every bulk edit of allocations or leave, and every Bulk Allocate run. Go to Settings > Backups and look for the entry marked "Before a bulk change" with a time just before you ran it, then restore it. One caution: these are taken at most once every ten minutes, so if you ran several in quick succession the restore point may predate the first of them, and restoring will undo all of them together. If the change could not be backed up for some reason it still runs. An Excel import or a Bulk Allocate run then says so on its result screen; a bulk edit made on the grid or the Leave page runs without that warning.

Can I export organization data?

The app includes an organization-scoped export route for major planning data, including people, projects, allocations, leaves, travel, events, holidays, changelog, and settings. It is intended for audit review, backup, analysis, and migration support. Each download is recorded in the Change Log, and one that cannot be recorded is stopped.

How do I export an Excel workbook for analysis (Extract to Excel)?

From Manage, anyone who can edit Manage sees an "Export for analysis" button in the top-right corner. It opens a small dialog where you pick a date range, then downloads a multi-sheet Excel (.xlsx) workbook for that range. Unlike the raw data export, this is a denormalized, analysis-ready workbook: foreign keys are resolved to names and it opens with About and Data Dictionary sheets that explain the domain and every column. It includes People, Projects, Project Phases, a denormalized Allocations fact table (with man-weeks), a computed Capacity & Utilization sheet (working days, public holidays, leave, available vs allocated man-weeks, utilization percentage, and over-allocation), an Allocation Heatmap shading each person by month from idle through fully booked to over-allocated, a native stacked-column Allocation Chart with its editable Chart Data sheet, a Skills Matrix, Certifications with expiry, Time Off, and Travel. It is built to drop straight into a pivot table or be handed to an AI assistant to answer questions such as who is over-allocated and when, which projects consume the most man-weeks, or where skill gaps exist. If a plan lock closes part of the range to you, the records it hides are left out and the About sheet says so, so utilization there counts only what you can see. Every download is recorded in the Change Log with who took it and the date range.

Does the help assistant use my data to train AI, and what is sent to the AI provider?

No. The in-app help assistant only receives the message you type into it, together with the product manual it answers from. It never sends your organization's workspace data (people, projects, allocations, leave, travel, capabilities, or any records) to the AI provider, and it is read-only, so it cannot see or change your data. Messages are processed by our AI sub-processor (Anthropic) purely to generate a reply. Under Anthropic's commercial terms, inputs and outputs sent through the API are not used to train their models, and they are deleted within 30 days by default. Anthropic is listed as a sub-processor in our Privacy Policy.

Where can I find privacy, terms, and cookie information?

The public site links to Privacy Policy, Terms of Service, Cookie Policy and Sub-processors pages, and a Security page covering how to report a security problem. The app uses strictly necessary authentication/session cookies and shows a first-visit cookie notice with Accept analytics / Decline options. Accepting sets one optional first-party analytics cookie so visitor counts are more accurate; declining keeps measurement fully cookieless. Either choice is remembered and can be changed by clearing cookies.

How do I report a security problem?

Email security@auditschedule.com. The public Security page at /security is the full policy: what is in scope, what we ask of you while you are testing, how quickly we reply, and the safe harbour that applies to good-faith research. We acknowledge a report within 5 working days and reply substantively within 10. We do not run a bug bounty. The same contact details are published in machine-readable form at /.well-known/security.txt. Test only in a workspace you created: every other workspace holds another company's data.

How do I see what is new in the product?

The public site has a What's New changelog page listing product releases with their dates and a summary of new features, improvements, and fixes. This is the product-wide release history; for changes made inside your own workspace, use Manage > Change Log instead.

What should I check before making large updates?

Check project date ranges, active people, linked user/person records, role permissions and scopes, default filters, leave and travel records, event visibility, and color defaults. After bulk uploads, auto-allocation, approvals, API-key imports, or syncs, use validation results and the Change Log to confirm what changed.

Superadmin

How do I reuse the spreadsheet-planning marketing template?

This feature is for platform superadmins, not workspace admins. At /superadmin/marketing, open Choose a template next to New campaign and select Spreadsheet planning. It fills a new draft with a campaign name, a personalized subject and a plain-text-style message with one Explore AuditSchedule link to the homepage. Review the copy and save the draft before selecting recipients. Choosing a template does not send email. The unsubscribe footer is added automatically when sending.

How do I schedule a marketing campaign to send later?

This feature is for platform superadmins, not workspace admins. At /superadmin/marketing, save the campaign as a draft, tick the prospects you want in Send to prospects, set a date and time in Send at, then choose Schedule send. Times are read in your own timezone, and the campaign starts going out within five minutes of the time you pick. You can close the page once it is scheduled. Use Send now instead if you want it to go out immediately.

Can I change or cancel a scheduled campaign?

This feature is for platform superadmins, not workspace admins. A scheduled campaign stays editable until its send time arrives: open it from the campaign list to change the name, subject, body or recipients, then choose Reschedule to set a new time. Cancel returns it to draft and discards the queued recipients without sending anything. Once the send time passes the campaign is marked Sending and can no longer be edited, rescheduled, cancelled or deleted, because part of the mail may already have gone out. A campaign that is sending still shows Stats, where each recipient reads as Queued, Sent, Failed or Skipped, so you can watch it land.