# Activities These are named things that senders work on or ascribe time to. So they may represent a project, or a type of work, but they could be the name of a shift, like "Nights" or "7am to 3pm". An Activity has three parts X > Y > Z to help people organise and structure their names. It doesn't much matter what you name an activity, but short, recognisable names are best. Activities must be linked to Workflows so that Zipwire can collect up all the journal data and organise it by assignment, i.e. put the right stuff on the right timesheet and send it to the right people. Activities can be assigned to senders within the assignment, in which case they will already have a linkage. Otherwise, activities are created by the sender when entering time in their journal and they make the link later when they come to create their timesheet. See also: {% content-ref url="/pages/x69tXPz2BDx962KBCF7f" %} [Naming activities](/use-cases/for-senders/naming-activities.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.zipwire.io/zipwire-approve/unboxing-key-concepts/activities.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.