A photograph is not yet an instruction
A close-up of a connection can show that something needs attention without saying who should act. A message saying “someone will handle it” does not provide a dependable handover. Describe the observed point, its location and the action needed. Keep factual observations separate from conclusions about contractual fault or legal responsibility; the application does not make that assessment.
Move from observation to a next step
Create a task linked to the project and, when useful, the relevant photograph. Choose a concise title and add enough description for the next person to act without reconstructing the entire conversation. A due date can support coordination but is not automatically a legally binding deadline. Avoid unnecessary personal details when the work itself can explain the issue.
Responsibility must reach the team
Owners can manage assignment within the current project access model. Workers have narrower mutation permissions. Assigned work can also appear in the personal cross-project task view. None of these screens sends an automatic reminder or notification. The business still needs an agreed communication routine so that an assignment is actually noticed and understood by the person expected to handle it.
Resolved needs an understandable response
Use open, in progress and resolved states consistently. Before marking a task resolved, agree what confirmation is needed and whether another record or image explains the result. A status change is not an independent inspection, a customer acknowledgment or legal acceptance. Previously issued PDFs remain unchanged when live task data changes; a correction requires a deliberately reviewed new version.
Start with a short daily review
Use invented project data to test creation, assignment, status changes and access removal. Review a manageable list at a regular point in the day. Physical-device usability, staffing arrangements and production operations remain separate gates. Keeping those limits clear allows the team to test a practical workflow without assuming that a software task list has replaced supervision or formal defect management.
WHERE FOTONACHWERK STANDS TODAY
Project tasks and personal assigned-work overview
Implemented locally; no automatic notifications or legal defect assessment.
View the product and current status ↗About this article
External sources may change. Examples describe typical workflows, not documented customer cases. This article does not replace an assessment of your specific project. General information, not individual legal advice.