Video 9 of 10 · 2:40
The Resource Calendar tab
One person’s year, and bringing a team’s leave in from a spreadsheet. For: Planners and Admins
Music: "Deliberate Thought" by Kevin MacLeod (incompetech.com), licensed under Creative Commons: By Attribution 4.0.
Read more
Transcript
One person's year
The Resource Calendar shows one person's whole year, day by day. Choose a person and a year. Each day shows what fills it: work, approved leave, pending leave, public holidays and weekends. Public holidays follow the person's country: Lena works in Sweden. Red is an overloaded day: more work than the hours she has. A conflict is work planned on a day off: on leave or a public holiday. Point at a day to see what is on it.
Her leave
Below the year, her leave: its dates, type and status; Remove takes away leave entered by mistake. Approved leave lowers her capacity everywhere in Mermix; pending leave doesn't, until it's approved.
Importing leave
Most teams keep leave in a spreadsheet: one row per absence, with the person's email, a start and an end date, and if you like, a type and a status. Dates can be real date cells, or typed: year first, with the month as a word, or all in numbers. Dates written as numbers are read in one order for the whole file: day first, unless a date only makes sense month first, and the preview says which. Approved, Accepted, Yes or an empty cell means approved; Cancelled, Declined or Rejected removes that leave; any other word means pending. The type is free text; left empty, it's Holiday. Import time-off reads the file; if it has several sheets, choose the one that applies. Mermix matches the columns by their names; check them, or pick another. The preview shows what each row will do, added, status changed or removed, before anything changes. Rows it can't read, like a missing email or a date that doesn't exist, are listed with their row number and the problem; the rest still import. If a row overlaps leave already in Mermix for the same person, it's a clash: you choose to replace that leave, or skip the row. Import waits until every clash is decided; Mermix never keeps two overlapping absences. Import, and the leave is on the calendar at once. That's the Resource Calendar: one person's year, and the leave that shapes it.