With the integration between awork and OS/, your team gets the best of both worlds: awork for operational project management, and OS/ for financial control, budget monitoring, and billing.
The Core Principle: Who Does What?
In OS/ (Calculation & Controlling):
Projects are set up, offers are created, and budgets/services are defined in OS/. In the background, OS/ calculates your true labor costs and ensures that your projects remain profitable.
In awork (Operational Work & Time Tracking):
In awork, you plan your tasks, deadlines, and capacities. This is also where the team tracks their daily working hours.
Automatic Synchronization:
If desired, tasks/lists are automatically generated in awork based on the OS/ budgets. Every hour tracked by your team in awork is transferred to OS/ and immediately converted into actual project costs using the logged labor costs.
How to Track Your Time in awork
Select a Task: Track your time directly on the tasks/activities synchronized from OS/ into awork.
Enter Time: Whether via stopwatch, manual entry at the end of the day, or straight from your calendar—simply use your usual awork routine.
Done! As soon as the time entry is saved in awork, it automatically syncs over to OS/. You do not need to enter anything extra or perform manual exports/imports in OS/.
Important:
The time tracking synchronization from awork to OS/ usually takes about 10 minutes.
Prerequisites: Requirements for Successful Synchronization
For your tracked times to transfer smoothly from awork to OS/, the following criteria must be met:
Email Address: The email address of your user profile must match exactly in both awork and OS/ (otherwise, the system cannot assign the hours to the correct person).
Project Status: The project must be active in OS/ (time entries cannot be synchronized to closed or canceled projects).
Tracking Period (Cut-off): The logged times must fall within the current tracking period. Once a time frame is locked in OS/ and/or awork (cut-off date), no new or modified time entries can be processed for that period.
Project Exists in OS/: The project must exist in OS/. If a project was created exclusively in awork, time entries cannot be synchronized to OS/. Additionally, rebooked time entries onto such a project will not be processed in OS/.
Key Framework & System Rules
To prevent misunderstandings in your workflow, please keep these system rules in mind:
One-Way Direction (awork -> OS/): Time entries are synchronized exclusively from awork to OS/.
No Duplicate Tasks: Tasks created directly in awork do not generate new budget line items in OS/. However, time tracked on these tasks will still be transferred to OS/.
Budget Structure Originates from OS/: Budget items from OS/ serve as the foundation for tasks in awork. You can, however, flexibly add additional tasks in awork.
Subsequent Modifications: If you update a time entry in awork after the fact, it will also be updated in OS/—provided the requirements listed under "Prerequisites: Requirements for Successful Synchronization" are met.
Tip: Use a type of work for Your Tasks in awork
Always assign matching type of work (e.g., Concept Creation, Design, Frontend Development) to your tasks in awork.
The Advantage: When your team tracks time on these tasks, the type of work is transferred directly as services to OS/. This allows for detailed project controlling evaluations regarding where budgets and time were spent in detail—even if additional tasks were created in awork outside the original OS/ budget structure.