Team capacity and evidence

Team member records include role, work email, bill rate, cost rate, weekly capacity hours, active state and organization. Logged billable and total hours roll into the member record, along with delivered service amount and utilization percentage. Delivery Director can compare this information with engagement budget hours and dates before making a staffing or margin decision. The team member link on a service line, time entry or expense keeps the contribution attributable to a person.

Review decisions and operation receipts answer a different question: what happened when the team or a workflow acted? A review decision records a subject, decision, reviewer, date and notes. An operation receipt records the operation type, reference, date, result, actor and optional document URL. Record attachments hold a file name, kind, URL and parent record identification. Together, those records let staff follow a commercial event back to its owner and evidence.

• Capacity. Team members hold weekly capacity, rate context and logged hours for utilization review.
• Decisions. Review decisions identify approved, rejected or returned outcomes against service, time, expense, milestone or engagement subjects.
• Operations. Receipts identify whether an approval, invoice or payment-record action succeeded, failed or was partial.

Choose who maintains active team members, rates and weekly capacity. Decide how part-time weeks or changes in capacity are represented in the current record and how reports should read historical periods. Confirm when the team uses a record attachment rather than a URL on an expense. The attachment parent name and record ID must point to the intended record, because they are the trail a reviewer will use later.

Define who can view rates, cost and margin information. Engagement Manager needs enough detail to investigate delivery economics; Engineer should see the work they entered. Finance Manager needs payment and invoice context. Test these boundaries using actual role accounts after configuration. Preserve failed operation receipts alongside successful ones so an exception is not erased when work is corrected.

A Principal Engineer records time and a service line for an Active engagement. Delivery Director reviews that team member’s logged billable hours, total hours, weekly capacity and utilization percentage before assigning more work. The service line is submitted and approved after its guard succeeds. The reviewer opens the linked decision and operation receipt, then checks the underlying engagement and any attached deliverable. If a later milestone invoice fails for missing amount, its Failed receipt stays visible even after the milestone is corrected and invoiced.

Run an access rehearsal with an Engineer and a Finance Manager. The Engineer should work on the delivery records assigned by policy; the finance role should investigate an overdue payment and its receipt trail without changing an engineer’s time entry.

• My Engagements — The manager’s assigned work and its timing context.
• Service Review Board — Delivery lines whose approval results need inspection.
• Payments Overdue Or Disputed — Collection exceptions with due-date context.

Review time and expenses and trace payment evidence.