Make each review decision easy to follow.
Build an ACC approval workflow for a defined review package. Give reviewers a queue, make the available decisions explicit, and keep the comments and decision history connected to the work.
Use this template to build your own app with Conduit. Describe your requirements in plain English and review the plan. Conduit writes the code; you test the result and ask for refinements.
When to use this starter
Teams coordinating document signoff, submittal reviews, or a repeatable package-approval process.
Bring these details
- The package or documents being reviewed.
- Who can review and decide, and which states the package can move through.
- The comments or decision details your team needs to retain.
Shape the first version
- Present the review work to the intended reviewers.
- Support the approve, reject, and comment steps defined in the brief.
- Keep a clear history of decisions so the team can understand the package’s current state.
A brief you can adapt
Start with this example, then add your project’s requirements and rules.
Build an ACC app for reviewing a defined document package. Ask me who the reviewers are and which decision states we use. Give reviewers a queue, allow approve or reject decisions with comments, and keep the decision history visible with the package.
Check the result before sharing it
- Walk a sample package through approval and a separate package through rejection.
- Verify reviewer access and the decision state after each step.
- Confirm comments and decision history show enough information for the next reviewer.
From your first build to your team
Test the generated app against the intended ACC project and access permissions, then make it available to the team. ACC apps run in the browser, with hosting managed by Conduit.
Your versions stay in Conduit. Every app reports how it’s running for your team, helping Conduit diagnose problems and make improvements.
Ready to make it yours?
Build your team’s version of Approval Tracker.