# Troubleshooting & FAQ

> Task questions are mostly about classification and completion. Which type to choose, when a task is genuinely finished, and owners versus contributors.

Source: https://tidalcontrol.com/docs/tasks/troubleshooting-and-faq

Task questions are mostly about classification and completion: which type to choose, when a task is genuinely finished, the difference between owners and contributors, and what to do when a task keeps being reopened.

## Frequently asked questions

### Which task type should I choose?

**Choose based on what you're going to do:**

**Execution - For implementation work:**
- Configure or install systems
- Roll out new procedures
- Organize and conduct training
- **Test:** Are you going to build, install or implement something?

**Assessment - For evaluation work:**
- Assess effectiveness of controls
- Conduct audits and reviews
- Check compliance
- **Test:** Are you going to check, assess or evaluate something?

**Practical tip:** If you're torn between both types, think about the end result. Execution delivers a working system or process, Assessment delivers a report or evaluation (effective / ineffective).

> **tip:**

**When in doubt choose Execution**: Most compliance work is implementation-focused. Use Assessment only for real evaluations and audits.

### When is a task actually completed?

**A task is ready for closure when:**
- **All instructions** from the description have been executed
- **Evidence** has been collected and uploaded
- **Testing** proves everything works (for implementations)
- **Stakeholders** have given approval where needed
- **Follow-up actions** have been identified and planned

**Don't complete if:**
- You're still waiting for approval from others
- Evidence is missing or incomplete
- Testing shows implementation doesn't work
- Related tasks must be completed first

### What's the difference between owners and contributors?

The owner is accountable for the outcome; contributors do the work that gets them there.

**Owners:**
- **Ultimately responsible** for task completion
- **Approval** of the end result
- **Escalation** for problems or delays
- **Resource planning** and setting priorities
- **Quality assurance** of deliverables

**Contributors:**
- **Practical execution** of work
- **Collect evidence** and upload
- **Progress updates** via comments
- **Collaboration** with other contributors
- **Provide input and expertise**

**In practice:**
- **One owner** is usually most effective
- **Multiple contributors** can work in parallel
- **Owner checks** before task is closed, or reviews the closed task
- **Contributors** do the actual work

### How do I plan realistic deadlines?

Base the deadline on real complexity and who's actually available, then add a buffer rather than assume nothing goes wrong.

**Estimation factors:**
- **Complexity** - How many steps and dependencies?
- **Resources** - Who is available and when?
- **Dependencies** - Which other tasks must be completed first?
- **Time needed for testing** - Time for validation and corrections
- **Buffer** - 20% extra for unexpected problems

## Common problems

### Task keeps getting reopened by owner

This is almost always an incomplete fix or missing evidence, not a communication problem.

**Possible causes:**
- **Solution doesn't work** - Implementation has bugs or problems
- **Insufficient evidence** - Owner cannot verify result
- **Miscommunication** - Expectations about end result differ
- **Scope expansion** - New requirements are added during execution

**Direct solutions:**
1. **Ask for specific feedback** - What exactly is missing for closure?
2. **Test more thoroughly** - Check if implementation really works
3. **Collect more evidence** - Screenshots, logs, test results
4. **Plan review meeting** - Discuss expectations face-to-face

**Prevention for next time:**
- Ask owner to define **closure criteria** upfront
- Test solution **together with owner** before closing
- Document **agreed steps** in the control description for next time

### Linked tasks are not visible or don't match

Linking tasks is what shows the dependency between them and lets evidence get reused instead of re-collected.

**Why linking is important:**
- **Workflow understanding** - How tasks build on each other
- **Dependency tracking** - Which tasks must be completed first
- **Evidence sharing** - Reuse of evidence
- **Complete overview** - of related activities

**If links are missing:**
1. **Check task configuration** - Are tasks linked to the same controls, assets and period?
2. **Verify task types** - Assessments link ONLY to Executions and vice versa
3. **Empty fields don't link** - Tasks must always contain at least one control, asset and/or period otherwise tasks don't link

### Still can't figure it out?

Send an email to support@tidalcontrol.com, and we'll get back to you as soon as possible.

> **info:**

**Gathering support info:** Note which browser you're using, exact error messages, and which steps you've already tried. This significantly speeds up the solution.