Configuration delivery

A configuration deliverable describes a service line, delivery date, consultant, engagement, hours and rate. Its calculated amount, cost and margin connect delivery to the engagement’s commercial picture. The consultant can prepare the line in Draft and submit it when the work is ready for review.

Submission starts the configured approval check. A billable line with hours and an engagement moves to Approved. The action records a review decision and an operation receipt. A line that is not billable, has no hours or has no engagement stays Submitted and gets a Failed receipt. The service reviewer uses that result to find the missing support and correct the line. Approved lines are visible for later invoicing review.

• Service line. Record the delivery date, description, consultant, hours and rate against an engagement.
• Submission check. A billable line with hours and an engagement can move from Submitted to Approved.
• Traceable result. Compare the review decision and operation receipt with the line’s status before billing review.

• Billable policy. Decide which configuration work should carry the billable flag.
• Evidence ownership. Give each line a consultant and engagement before submission.
• Exception follow-up. Assign the reviewer who checks Failed receipts and submitted lines that need correction.

Agree a representative implementation for rehearsal. Use the same client and engagement across delivery, service review and billing. Keep the person who enters a record distinct from the person who makes the business decision when the team requires that separation. Make the ownership rule clear before a busy billing period, because a status alone does not explain who should take the next action.

Prepare a deliverable for a client environment with positive hours, an engagement and a billable flag. Submit it and inspect the Approved state, review decision and operation receipt. Next submit a line without an engagement. Confirm it remains Submitted and a Failed receipt records the attempt. After correcting the engagement, submit the line for review again and check its approved amount against the engagement’s delivered amount. Trace both attempts by their source references.

The reviewer should open the source record behind each amount and compare it with the engagement. If a correction is needed, keep the earlier outcome visible and explain the new one in the appropriate decision or operation record. A manager should be able to identify the client, the responsible person and the next action without reconstructing the history from messages.

• Approved Not Invoiced — Inspect approved service lines and their approved amounts before invoicing.
• Rejected Configuration Deliverables — Revisit rejected lines and their supporting engagement details.

Start with Submit deliverable and use implementation planning to rehearse the handoff with your team.