Resources

Manage people's allocation across projects: percentages, periods and conflicts. Use it before taking on a new project — real capacity, not guesswork.

"Can I take on one more project this month?" It shows who is on which project and with what share of their time, adding up per person. It's the difference between promising a deadline based on a feeling and promising based on what is really left.

It is the share of that person's month committed to that project. In a month of 160 working hours, 40% ≈ 64 h. The total per person is what matters: 60% on one project and 60% on another makes 120% and doesn't fit in the month, even if each line, on its own, looks reasonable.

The platform doesn't block: allocating 120% is legitimate information that the promise made to the customer doesn't fit in the month. What it does is show this BEFORE the delay, so that the way out is chosen — reassigning people, renegotiating the deadline or hiring — and not discovered on the eve of delivery.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

Almost never. In practice it is UNRECORDED allocation — the person is working and nobody entered the line. The effect is worse than that of the excess: the project's cost comes out too cheap and the margin lies upward, which leads to accepting the next contract at the wrong price. Before concluding that the team has slack, check that the month's allocations are all entered.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".