Choose requests, visits, tasks or projects
Start with what you need to organize: staffing coverage, a work period or an outcome. A project can group these elements but is not required for every job.
Before you start
Open the actual workflow available in your organization. Historical screens and newer workflows may coexist; similar names do not identify the same record.
Steps
- For “two people from 8 to 12,” prepare the staffing request or coverage requirement offered in your workflow. Specify period, destination and skill.
- For a shift, review its period, segments and allocated people. A shift is not declared availability.
- For an outcome, open the task or visit from its existing context. Describe result, place and requested period. Assigning someone does not declare completion.
- For an objective with several tasks, use a project when useful. Explicitly attach tasks; the project does not replace staff scheduling.
- Use the action belonging to the subject: assign, answer, perform, complete or validate. Read its saved state before moving to another workflow.
Example and expected result
Fictional example: maintaining three sites is a project objective. Each visit may have its own expected outcome. A two-person request describes staffing and assignments identify who attends. Time tracking records presence without proving all visits are complete.
If something goes wrong
Do not recreate old work in a new model to bypass refusal. Buying a plan or changing views does not convert history or trigger billing. If writing is unavailable, have workflow activation and permissions checked rather than changing migration rules.