A direct chat. It remembers the whole conversation and sees your projects, tasks and reminders. Saved together with everything else.
Business correspondence. Describe the situation and I will put together a polished letter in the right language and tone.
Short messages for chats and quick emails. Lively and to the point.
Every project in one line: status, current stage, deadline. Click to open the editor, mark closed stages and the export. Hold removes a project from reminders.
No holds. While a hold is active the deadline moves forward and contract working days are not burned.
Deadline pushed by + days due to holds.
A simple list: write a task down, come back later, tick off what is closed. You can add them as text, one line per task.
Paste or dictate text, one line per item (for example «3807 - remind them, they said they would check and went quiet»). Claude will make a separate task from each line, as written.
| Task | ||
|---|---|---|
| No tasks yet. | ||
The plan by people and days. Cell colour = complexity: green easy, yellow medium, red high. Click a cell for the task and the delivery day. A task can be dragged to another day or another person: that person's following tasks shift along, and the changes go to Odoo. An orange bar on the left means several tasks that day.
Column order always follows the role: designers, concept architects, architects, finishing managers, others, PM. Drag ⠿ to reorder within your own group. Change the role and the person moves to another group.
Take one person from another team for a while. They join this board as a guest: they get a schedule column, a tracking link and a row in TT, and Sync team never removes them. When you give a guest a task, the tool also adds them to that project in Odoo, otherwise they would not see the task. Remove the guest from the board when you are done and the tool offers to close those project accesses; the hours they logged stay in Odoo either way.
Pull team adds the department's people from Odoo (name, job title) and links them to Odoo users; it never removes anyone. Sync team also removes people who have left the department, and shows exactly who will go and how many schedule cells are affected before doing it. Tasks already sent to Odoo stay there either way.
| Date | Add people with the People button | |
|---|---|---|
|
DLV
|
Plan weeks ahead (1, 2 or a month), page through with Prev/Next. Excel is exported with the button above.
The team's projects in one list: current stage with its deadline, progress, status. Planned hours are entered per stage, not for the whole project: open a row with the arrow. You see plan, spent and remaining, and the collapsed row shows the total for the project. Hours go straight to Odoo.
| Code | Project | Current stage · deadline | % | Status | Plan · spent · remaining | ||
|---|---|---|---|---|---|---|---|
| — all stages closed — | stages ▸ | ||||||
|
The project has no milestones and no top-level tasks. Project stages · hours are written to the stage container task in Odoo
closed
hours not set
no container task, nowhere to enter hours
IDTaskPlan
SpentRemaining
|
|||||||
How many hours each person logged in the Odoo timesheet, by weeks of the month. Red means no time was logged. Orange +2 in the corner of a cell is overtime inside those hours. The period is the same month as in the Calendar tab.
| PERSON | TOTAL | |
|---|---|---|
|
|
Counted from Odoo, nothing is typed by hand here. Planned hours of a stage divided by 8 are spread over the working days of the stage window and land on the roles the stage belongs to. Enter the hours in the Odoo tab, in the PLAN field of the stage.
|
TEAM |
TOTAL | UNTIL | |
|---|---|---|---|
Person-days per month. Capacity is the people of that role on this board multiplied by the working days of the month; type a number into a capacity cell to override it. UNTIL is the last month with planned work. Stages whose deadline is already in the past are spread from today. A stage with no hours or with the default 8 hours is not counted, it is marked red in the Odoo tab.
The plan of a task is its Contract Plan baseline in Odoo and it does not move. The current date moves while the task is open, so the real signal is the gap between the two, not a date in the past. Read only, nothing is written back.
GAP is days between the plan and the current date of the task: plus means the task moved later than planned. MOV is how many delay records Odoo registered on the task, REASONS is what they were and for how many days. If a task has several Contract Plan baselines, the latest one is taken. Tasks with no Contract Plan are not shown, there is nothing to compare them with.
Three lists for this board: tasks with nobody on them, stages with no planned hours, and projects nobody ever logged time to. You can fill them in right here, the change goes straight to Odoo.
Writes go into Odoo one record at a time, so a single bad task does not stop the rest: the counter at the top says how many went through and which ones failed. Rows disappear from the list as soon as they are filled.
The numbers of the week are already collected by the tool: hours, overtime, who logged nothing, milestones closed and overdue. Here you see them and get a ready text to send, written from these numbers only.
| Hours logged | ||
| People on the board | ||
| Hours with no stage | ||
| Overtime | ||
| Milestones reached | ||
| Milestones past deadline, all open | ||
| Median logging delay |
Phases, weeks and dates of a project. The export repeats the studio schedule sheet exactly: same columns, same colours, same logo.
Pick a project and the schedule is created from the standard template: seven phases with a client review after each. A tick means the schedule already exists.
| # | PHASE | WEEKS | START | END | |||||
|---|---|---|---|---|---|---|---|---|---|
| TOTAL PROJECT DURATION | |||||||||
Dates are chained from the start: a phase runs its weeks, the pause after it starts the next day, and the following phase begins on the day the pause ends. Recalculate dates rebuilds the whole chain; any single date can be corrected by hand afterwards.
Your tasks on the left, days on the right. Type the hours into a cell, they are saved right away. An empty cell removes the entry. The button on the right closes the task in Odoo.
Pick the project and the stage it belongs to, say what you did, and the entry appears as a row below. It goes into Odoo as a subtask of Expedite or Project Coordination of that stage.
Overtime mode. The hours you type now are saved as overtime on the same task, the normal hours stay untouched. Every entry goes to your PM for approval. Switch the button off to go back to normal hours.
| Task | Due | Total | ||
|---|---|---|---|---|
|
unplanned
нет связи с Odoo
|
DLV
|
|||
| TOTAL |
Green cells are the days this task is planned for you. DLV marks the delivery day, and the Due column repeats it. Pale cells are days the task is not planned for: you can still log hours there if you worked on it. A small orange +2 in the corner means overtime already logged that day.
Each person gets a personal link. They see only their own week, enter hours and can close a task. Hours land in Odoo under this board's Odoo access, so no licence is needed for them.
No links yet.
Each task has its own deadline, its own stage and its own task in Odoo. Several tasks in a day split the cell evenly, the row height does not change.
↳ ·
The deadline applies to the selected task; a neighbouring task may have its own. The task fills every day from the open one to the deadline, and the delivery day gets a DELIVERY badge. For a one-day task leave the deadline empty. Saturday and Sunday are never included in a range. A weekend task can only be set by hand, by opening that day, and that is for overtime.
If the person delivered late, enter by how many days. It shows red in the schedule and lands in the monthly summary (Load).
The settings below apply to the selected task:
Internal work: no project code and no stage needed. Pick what it belongs to, or leave nothing selected and a new internal task will be created.
code not found among projects
No code, or the project is not in the system? Pick it by hand:
nothing found
selected:
this project has no milestones in Odoo, the task will go without one
The project comes from the code in the title, the assignee from the person's card, the dates from the open day and the delivery date. The task is created in the project and linked to the chosen milestone.
Recurring items like Vacation, Sick Leave, Day off and Public holiday take the hours on themselves, nothing new is created in Odoo. Any other internal task you pick gets your line as a subtask.
One button: tasks land in the schedule and go straight to Odoo if the task has a project and a stage. Existing ones are updated, no duplicates appear.
↳
shift by d. · the assignee changes
These will move too tasks :
·
·
What we doThe subtask takes these days in the schedule, weekends are skipped.
While «End» is empty the hold is active and pushes the deadline one day forward every day, so contract working days are not burned.
Expected payments: add the invoices you issued, tick them off when received. The longer a payment is missing, the brighter the highlight: yellow from one week, red from two.
Paste or dictate text about issued invoices, one line per invoice. Claude will split it into separate records (project, amount, issue date, if given).
| What for | Project | Amount | Issued | Hold | ||
|---|---|---|---|---|---|---|
| No records yet. | ||||||
Meetings are pulled from Circleback with the button and arrive with the Circleback summary ready, which is free. Your own detailed analysis with quotes is started with a button on a specific call, when it is worth it. Only meetings you took part in are taken; ones already added or deleted do not come back. From the transcript Claude builds an analysis: what was discussed, remarks and concerns, what was promised, tasks. Every item has a ? shows the source quote. The team sees a call only if you opened it to them.
Real time across US time zones and ours (Paris). The offset is given relative to Paris. «Office hours» means Mon-Fri 09:00-18:00 local.
The board is snapshotted automatically before every overwrite, at most once every 10 minutes, plus one snapshot per day. The 24 most recent and one per day for 30 days are kept.
Status: ●●
Everything is already saved locally in the browser. To keep the data on a server and make chat and letters work, deploy to Cloudflare Pages:
Paste the token of a second board and it will be remembered, with a switcher appearing in the header. No need to log out of the current one.
Full instructions are in the README next to the file.