In short:
Numbers & finances in OS/, tasks & times in awork.
Who does what?
Both tools work perfectly together:
OS/: Here you do your calculations, write offers, and keep an eye on the total costs.
awork: Here your team plans the tasks and records the working time.
Basic data synchronization between OS/ and awork
Data type / Field | Direction | When does synchronization occur? | Logic & behavior in the system |
Project master data | OS/ -> awork | In real-time upon creation & every change | The project is created or updated identically in awork. Manual duplication is not necessary. |
Project team (Team members) | OS/ -> awork | Automatically upon assignment | The team assignment is taken directly from OS/ and keeps your project team up to date in awork. |
Services | OS/ -> awork | Automatically upon creation of calculation | Stored services are passed as activities. If the selection is missing in OS/, the placeholder |
Working hours | awork -> OS/ | Automatically after booking (usually within a time window of 10 minutes) | Recorded times on tasks/subtasks flow back to OS/. |
Task synchronization (From budget to task)
If you use the function to directly transfer your project budget to awork as tasks, OS/ automatically transforms your calculation into an operational framework for your team.
You can set this option directly in the Integration settings.
This way, you maintain cost control in OS/ while your team can immediately start working in awork.
This is how synchronization works:
The outline sets the framework: Each main heading (outline point) of your calculation in OS/ becomes its own task list in awork.
Your budget becomes a task: The individual calculation items you defined in OS/ are sorted as concrete tasks into the respective awork lists.
The activity automatically follows: The service selected in OS/ (e.g., “Concept” or “Design”) is directly assigned as an activity to the task in awork, ensuring everything is correctly assigned when booking times later.
Flexibility for your team: Your team can create their own subtasks or additional tasks in awork at any time to plan the job in detail. These operational details remain in awork – only the time booked on them flows back to the respective project in OS/ for controlling.
Overview
Element in OS/ | What does it become in awork? | How does synchronization behave? |
Outline point | Task list | Is created 1:1 as a list. Important: Nested OS/ subpoints are displayed as equal lists side by side in awork. |
Calculation item | Task | Appears as a task within the respective task list in awork. |
Calculated effort (e.g., 12 hours) | Planned value / Budget | Is attached as a visible budget limit to the awork task. |
Stored service (Service) | Activity | Is automatically assigned as a fixed activity to the awork task. If the specification is missing in OS/, |
Not available in OS/ | Additional tasks & subtasks | Can be freely created by the team in awork. These tasks are not transferred back to OS/. However, the recorded working time flows back automatically into the variance analysis in OS/! |
Important: What is NOT synchronized?
Task structures from awork: Additional tasks or subtasks that your team creates directly in awork remain in awork and do not clutter your OS/ structure. Only the time booked on them flows back.
Financial documents & purchases: External cost markups, service fees, and incoming invoices from suppliers are exclusively managed in OS/ and are not transferred to awork.
Tip: The 3-step guideline for your project
Just follow this order when starting a new project:
Step 1: Create project in OS/
Always create the project first in OS/. The following data will automatically transfer in real-time to awork:
Project name, client, project type, end date, and status.
Also, add your team members directly in OS/, so the team is ready to start in awork immediately.
Step 2: Build calculation in OS/
Whether you calculate based on hours, days, or flat rates, OS/ transfers the data to awork:
Outline points: Each main point from your OS/ calculation becomes its own task list in awork.
(Important: Nested subpoints are displayed as normal lists side by side in awork).Services: Always select a specific service in OS/. If you forget this, your team will later book on the unattractive placeholder OS-Budget-Item in awork.
Planned values: The calculated times become planned values in awork, so your team can see how much budget is available.
Step 3: Work & record times in awork
Now your team gets started in awork:
You can create as many tasks and subtasks in the lists as you want. This structure remains in awork and does not clutter your OS/.
The best part: Every second you book on these tasks automatically flows back to OS/.