The system must distinguish recorded, validated and additionally authorized hours using the agreement version applicable to the period.
Index
An activity can start within contracted hours and continue beyond them; recording only its total makes customer review difficult.
The rule that changes the scope
The system must distinguish recorded, validated and additionally authorized hours using the agreement version applicable to the period.
Existing time tracking covers entries; a custom extension allocates work by contract and obtains approval before consuming extra time.
Decide how balances cross periods and contracts before implementing calculations. An hour can be worked on one date and checked later without changing its reporting period. The interface should help the customer identify the activity and owner rather than present only an aggregate number. Keep subsequent billing separate from operational validation: an accepted time entry does not mean payment occurred or that every commercial condition has been fulfilled.
Specify operational deliverables
- Connect each activity to its contract, reporting period and the balance it may consume.
- Show where the activity exceeds included hours without automatically approving additional work.
- Retain entry adjustments and their effect on a report already sent to the customer.
Test the exception before acceptance
In a hypothetical scenario, the customer rejects some additional hours; the report must retain recorded work and separate its authorized portion.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a disputed report and the agreement used to review included and additional hours.