Philippines staffing guide · Published
On this page
Track recurring client requests with a request pattern log
A request pattern log that groups repeat asks by trigger, measures the rework they create, and turns the most common ones into a defined service.
Most assistant teams can describe their busy weeks but cannot name the requests that cause them. A client asks for the same report twice, a manager forwards the same file request, and a weekly task quietly expands. A request pattern log records the ask itself, not just the response, so the team can see what keeps coming back. The log turns anecdote into a list that can be designed against.
Keep the log small enough to maintain during a normal week. One line per request with a trigger, a category, and the time it consumed is enough to start. Do not try to capture every interaction. The goal is to find the patterns worth changing, not to build a complete audit trail.
Log the request, not the response
Write down what the client asked for before describing what the team did. The request might be a status update, a file, a meeting change, or a decision. Record who asked and through which channel. The response belongs in the task record, where it can be reviewed for quality.
Use the client's wording in a short phrase rather than a polished category. That preserves the signal you might otherwise smooth away. Add the date and the work lane so the entry can be found later. A log that begins with the request is easier to analyze than one built from completed tasks.
Group requests by trigger and season
A trigger is the event that produces the request, such as a month-end close, a new client onboarding, or a missed delivery. Label the trigger beside each entry. After a few weeks, the same triggers will appear across different clients and channels. That is the point where a repeated ask becomes a process problem.
Note the month or quarter as well, because some requests follow a calendar. Tax season, annual reviews, and holiday coverage can all change the volume. A pattern that appears only in one period needs a seasonal plan, not a permanent new role. Review the log with the calendar open.
Measure the rework each pattern creates
Record the time spent and whether the request required a redo. A request that takes ten minutes but happens daily is more expensive than a one-hour task that happens once. A request that is reopened because the first answer missed the mark signals a unclear brief. Both measures point to different fixes.
Keep the measure simple, such as a small time band and a yes or no for rework. Precision is less important than consistency across entries. If the team cannot agree on the band, define it once and apply it to the next month. The comparison matters more than the exact minutes.
Turn repeated requests into a standing service
When the same request appears at least weekly, define it as a standing service with a format, a due time, and an owner. A standing weekly summary is easier to staff than five separate asks. Write the definition in the client brief so the client knows what is already covered. That reduces the need to ask and makes the scope visible.
Do not absorb every repeated request into the service quietly. Some requests are out of scope and should be priced or declined. Others are symptoms of a client process that should change. Review the pattern with the account lead before adding permanent work. A standing service should reduce coordination, not hide it.
Decide what to stop doing
Some patterns exist because an old report or check no longer serves a decision. Ask who uses the output and what they do with it. If nobody can name a decision, propose stopping the task for one cycle. Record the agreement and watch whether anyone notices the gap.
Stopping work is harder than adding it, so make the decision explicit. Put the paused task on a review date instead of deleting it silently. If a client asks for it again, the log shows the request and the reason it was paused. That evidence makes the next conversation easier.
Keep the log clean enough to trust
A log becomes unreliable when entries are added days later from memory. Ask the assistant to add the request when it arrives, using a short phrase and a trigger. If that is not possible, mark the entry as reconstructed rather than presenting it as exact. The confidence label matters more than a false sense of precision.
Review the categories once a quarter and merge any that no longer differ in practice. Remove duplicate entries caused by a request moving between channels. Keep the log small enough that someone can scan a month in a few minutes. A short, trustworthy log beats a complete one that nobody maintains.
Review the log with the client quarterly
A quarterly review can show the client which requests are growing and which have faded. Bring three patterns and one proposed change to each review. Ask the client whether the pattern matches their experience. The conversation is more useful than a chart alone because it surfaces the reason behind the volume.
Keep the client discussion at the level of service, not individual messages. The aim is to agree on what should be standard, what should be exceptional, and what should stop. Record the decisions in the client brief and update the service definition. A log that never changes the service is just extra administration.
Questions and operating boundary
How many requests should we log?
Log client requests that require a response or a decision. Routine internal checks can stay in the task queue without a separate entry.
Who maintains the log?
The assistant who handles the request adds the entry at the point of service. The account lead reviews the patterns weekly or monthly.
Should the client see the raw log?
Usually not. Share the patterns and proposed changes in the quarterly review, and keep raw entries internal.
Source
sba.gov provides authoritative background and does not endorse this service.