These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Requirements Management
- Features
- Time and evidence
Time and evidence
Record submitted hours, approval results and evidence of delivery operations.
OverviewTime Entries Awaiting Approval×
Requirements Management · Time and evidence
New
Time Entries Awaiting Approval
Approval conditions
| Entry number | Team member | Project | Task | Work date | Hours | |
|---|---|---|---|---|---|---|
| TE-58577 | PRJ-2079 | RI-2457 | 05 Oct | 4 | ||
| TE-31218 | PRJ-1542 | RI-3580 | 19 Oct | 12 | ||
| TE-49586 | PRJ-4156 | RI-7795 | 23 Oct | 2 | ||
| TE-36392 | PRJ-3575 | RI-5217 | 19 Oct | 7 | ||
| TE-75476 | PRJ-3009 | RI-8910 | 10 Oct | 4 |
6 of 6 records
PRJ-2079Time entries · TE-58577
SubmittedTaskRI-2457
Work date05 Oct
Hours4
What you can do
Trace effort and its outcome
A team member records a work date, positive hours, project and their own team-member record in a time entry. An entry can also reference a requirement item, connecting the hours to the task that caused them. Draft entries can be checked before submission. The configured approval action handles eligible submitted entries and records both a review decision and an operation receipt. The project and team-member records then show logged hours for later comparison with estimates and actual work.
How the work is organized
- Time entries. Capture the work date, hours, project, team member, billable choice and optional item reference.
- Review decisions. Keep the recorded decision and reviewer reference with the affected project or parent requirement when available.
- Operation receipts. Show when an operation ran, whether it succeeded or failed, and why a failed attempt could not proceed.
An entry can be draft, submitted, approved or rejected. Submission is the trigger for the approval action. It checks that the hours are positive and that the entry is still submitted. A successful action approves the entry; a failed attempt is recorded rather than silently disappearing. Receipts also identify the operation, its reference and the actor when supplied.
What to agree during setup
Agree how team members describe time, when they submit it, and whether each entry should point to a requirement item. Use the billable choice consistently, especially across projects with different delivery methods. Decide who reviews failed operations and how they resolve the underlying record before another attempt. A failed receipt is evidence of a problem to investigate, not an approved time entry.
Review access to attachments and decisions separately. Files have internal or shared visibility, and a file can be linked by parent record identifiers or a parent requirement. Decide which evidence types your team uses and who may upload or share each file. The reference and parent links should be checked in a pilot so a reviewer can find the actual supporting record.
Check the handoff on an actual case
Create a time entry for an assigned requirement item, with its correct project, work date and positive hours. Submit it and confirm the approved status, review decision and successful receipt. Then try an entry with invalid hours and inspect the failed receipt and reason. A Project Manager should be able to trace both outcomes back to the entry and explain which hours count in the project’s logged total.
What your team sees
- Time Entries Awaiting Approval — Submitted entries with project, item, date and hours for outcome review.
- My Time Entries — Each team member’s entries and current status.
- Failed Operation Receipts — Operations that need investigation, with recorded failure reasons.
Follow the work through
Use time and evidence to rehearse valid and failed submissions. The reports page describes the related operating questions.
What it keeps track of
Data model- Time entries
- Hours booked by a team member against a task and project.
- Requirement items
- Line items that decompose a requirement and carry its acceptance detail.
- Projects
- Engagements delivered for an organization, with budget and schedule.
- Team members
- Delivery staff with role, practice and weekly capacity.
- Review decisions
- Recorded approval decisions on delivery subjects.
- Operation receipts
- Evidence that a delivery operation was executed.
- Record attachments
- Files attached to delivery records.
Who uses it
Permissions- Team Member
- Submits time; Project Manager reviews project effort and failures; Delivery Lead sees exceptions; Admin maintains access.
Set up Requirements Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.