Import a resource plan

Type /plan-import and tell Claudioo who works on what. It reads the plan, works out what each person's days are worth against their own working month, shows you the whole thing, and only then creates the planning entries in muchdoo. Everything it creates is a draft, so nothing reaches the published plan until you publish it yourself.

How to run it

Type /plan-import in any chat, then say what you want planned. All of these work:

/plan-import Plan Max on Inform for August, 8 days

/plan-import 10 days a month on ÖAV for the next 3 months

/plan-import Split 30 days over the next 3 months across the people already
planned on Inform, except Andrey

You can also paste a table with the people, projects, months and days in it, or attach a team-planning sheet. With a sheet, Claudioo asks which tab and which months to read before it does anything else.

Ask for a preview at any time — say "preview" or "what would you do" — and it stops at the table without writing a thing.

Days become a share of a real month

Planning in Odoo stores a share of a person's working time, not a number of days. Claudioo does that conversion from each person's own working-time calendar and their booked time off — not from a flat eight-hour week.

That matters more than it sounds. Ten days in August against a full-time calendar is about 48% of the month. The same ten days for someone on a two-day week is over 100% — the person is booked past everything they have. A flat calculation reports both as 48%, and the second one lands in muchdoo with nobody the wiser.

Public holidays, part-time weeks, two-week rotas and booked leave all come out of the same calculation, so the number you see is the number that month really holds.

What you get

Before anything is written, a preview table: each person, the project, the month, the days, the hours, the capacity that month, the share of it, and what will happen to the row. Under it, in plain language, anything that needs your attention — a person who is booked past a full month, a month that came out with no days in it, or someone whose calendar can't be measured.

Then Claudioo asks: import everything, import only the clean rows, or cancel. Cancel writes nothing at all.

Afterwards you get a table of what was created, with the entry numbers and a link into muchdoo Planning, plus a file in your workspace holding both the plan and the result — the answer to "where did this entry come from" three months from now.

It checks its own work

Odoo recalculates the hours from each person's calendar, so what it stores is not always exactly what you asked for. Claudioo reads every entry back after it writes it, corrects the ones that drifted, reads those back again, and tells you about any it could not settle. Nothing is reported as done on the strength of the write alone.

Good to know

• Everything is created as a draft. Publish in muchdoo under Planning → Schedule when you are happy with it.
• Nothing is ever deleted. Ask to remove a planning entry and Claudioo empties it — sets it to zero — and tells you plainly that the entry is still there. Delete it yourself in muchdoo if you want it gone.
• Existing entries are kept, not replaced. If someone is already planned on that project that month, Claudioo shows you both numbers and asks what you want.
• "The team on a project" means the people whose planning entries on it are current or still to come. It is not everyone with a task, and it is not the macroplanning lines. Claudioo says which it used, every time.
• You only see and write what your own muchdoo login allows.
• On a re-run, rows that already landed are marked as duplicates and skipped, so running the same import twice does not double-book anybody.

What's next

• Pull project data from muchdoo — Other ways Claudioo reads muchdoo for you.
• Run a pipeline review — The same kind of guided pass over a sales team's deals.
• Run a skill — The full list of guided workflows.