An approval can be overdue for several reasons. The reviewer may not have had time. They may be waiting for another person. Or the submission may not make clear what they are being asked to decide.
A tracker that says “awaiting client” cannot distinguish between those situations.
For a fit-out team, improving design approvals starts with the quality of the request. The useful outcome is a recorded decision that allows the appropriate next step to happen.
Be clear about the decision you need
Break broad approval requests into decisions that a named person can make.
Take decorative lighting for a restaurant. The client may be choosing the visible finish, while a designer is resolving a separate technical question. An email saying the lights “look good” does not tell the buyer whether both matters are complete.
The submission should identify the item, the exact drawing or sample reference and the question being asked. State what the decision will allow the team to do and when it is needed.
Keep questions separate when they need different reviewers. That makes it easier to see which part is complete and who is holding the next action.
Distinguish approval from a request for information
A request for information, or RFI, seeks clarification. An approval submission asks the appropriate person to review or accept a defined proposal within their responsibility.
The two can be connected. A missing dimension may need an RFI response before a supplier can complete a drawing for approval. Keep the records linked, with their separate purposes visible.
If an answer introduces a change to scope or requirements, refer it through the project’s change-control procedure. The commercial and project teams need to assess the consequences; closing the question in the RFI log does not complete that work.
This distinction helps the team chase the right outcome. A reminder for “approval” is unhelpful if the reviewer is still waiting for information that someone else must provide.
Make the submission complete enough to review
Before issuing it, check that the reviewer can understand the proposal without searching through unrelated correspondence.
A useful request includes:
The item, location and current document or sample reference.
The specific decision or clarification required.
Supporting information relevant to that decision.
Any unresolved point that limits what can be agreed.
The named reviewer and the required response date.
The order, drawing or activity waiting for the answer.
Where several options remain, explain the choice clearly. Avoid treating a partially described alternative as ready for approval.
A sample may also need a clear relationship to the specification. Record what the sample represents and any aspects being assessed separately. The reviewer should be able to see the limits of the decision they are making.
Set a decision date that reflects the next step
A generic response period can miss what the project actually needs. Agree the required date with the project and procurement teams, taking account of review, possible comments and resubmission.
Show the consequence in practical terms. “Decision needed before the supplier releases production” is more useful than marking every item urgent.
Keep the required date separate from a reviewer’s promised response date. If the promise falls after the required date, the team needs to address that difference.
Also identify who can cover an absence or resolve a disagreement between reviewers. An approval process that depends on one unavailable person needs an agreed escalation route.
Track the reason it is still open
Use statuses that describe the real position. An item might be awaiting information, submitted for review, returned with comments, resubmitted or awaiting confirmation that conditions have been met.
Keep the formal status wording required by the project where that applies. Add a short action note if the code alone does not explain what happens next.
For the lighting example, the visible finish might be accepted while the technical query remains open. Showing both avoids sending repeated finish reminders while the actual blocker receives little attention.
An effective review looks at the age of open items, the decision date and the work affected. The oldest item is not always the most urgent. A recently raised question may need attention first if it affects an imminent release.
Check that the response can be used
When a reply arrives, confirm that it refers to the correct item and revision, comes from the appropriate reviewer and answers the question asked.
Record any conditions and who will deal with them. “Approved subject to comments” needs the comments to remain visible and their effect on the next step to be understood.
Then tell the person waiting for the decision. A completed approval that remains in one inbox can still delay an order.
An AI colleague could help identify missing responses, group linked questions and prepare a draft list of decisions needed. It could also flag a reply that appears to refer to a different revision. The nominated reviewer would confirm the status and whether the next step is authorised.
If an approval keeps circulating without a usable decision, talk to Build Agents about that example. A focused paid pilot could support the checking and follow-up around your existing process, with the decision staying with the people responsible.
