App / Professional services and client delivery
Build a client deliverable tracker
Build a Proforma App for client deliverables, owners and review status. Keep acceptance criteria and evidence links visible in one engagement tracker.
Engagement manager · Client delivery lead
Bring this question into Chat
Your starting prompt.
Build one Proforma App for [engagement deliverables], using an existing App if available. Show owners, deadlines, review status, acceptance criteria and links to permitted evidence. Include a summary route and a deliverable detail route within the same App. Store operational updates in Workspace Tables and display missing approval separately from completion. Keep the App private until its visibility and client access are explicitly reviewed.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Use the engagement scope, supplied evidence and delivery dates. Separate client facts from assumptions, retain source references and identify decisions that need client approval.
For this task, check
Agree what completion and acceptance mean before interpreting the tracker as proof of client sign-off.
Before you begin
- Permission to create or update the engagement App
- Defined owners, statuses and Workspace visibility
Build one App from data you have permission to query. Review its definitions and calculations with your team.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Private tracker design at 30 September 2026. Completion and client acceptance are separate states.
These invented records explain the method. They are not a recorded Proforma run.
| Deliverable | Owner / due date | Work status | Acceptance evidence |
|---|---|---|---|
| D-1: analysis | Rae / 25 Sep | Completed | Not supplied |
| D-2: dashboard | Sam / 5 Oct | Draft | Not requested |
| D-3: handover | Rae / 29 Sep | In progress | Not supplied |
| Deliverable | Tracker state | Review priority | Evidence next step |
|---|---|---|---|
| D-1 | Completed; awaiting acceptance | Owner review | Collect designated reviewer response |
| D-2 | Draft; due 5 Oct | Scheduled review | Attach criteria before review |
| D-3 | In progress; 1 day overdue | Delivery review | Confirm revised plan |
Method
Keep one App with summary and deliverable-detail routes. Link supplied documents; store operational statuses in Workspace Tables. A due-date comparison identifies delay while acceptance requires its own recorded evidence.
What the result tells you
A completed task does not establish client sign-off. This is an illustrative private App structure; no App is installed, access granted or client approval invented.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.