Outsourced Philippines guide
Keep a Client Preference Register for Recurring Deliverables
A short register of client preferences, with a source and a date for each entry, keeps recurring work consistent when the team changes.
Clients repeat the same small corrections because the preferences behind them live in old messages. A preference register collects those corrections in one place, with enough context to apply them without guessing. It is not a style guide for the whole company and it is not a place to store opinions. It is a working record of what this client expects from a recurring deliverable, and it should be short enough to read before starting the work.
On this page
Choose the preferences worth recording
Record a preference only when it changes the output in a way the client would notice. The subject line they expect, the order of columns, the label they use for a status, and the file format they open first are all good candidates. Leave out personal remarks and one-off requests that will never repeat. A register full of trivia becomes noise that the team stops reading.
Ask the team which corrections they have made more than once in the last month. Those repeats are the strongest evidence that a preference belongs in the register. Add the client's exact wording where it is short and clear. If the wording is ambiguous, write the rule the team agreed on and note who confirmed it.
Write each entry as a testable rule
A useful entry says what to do, not what the client likes. Write use the client's legal name in the footer rather than the client prefers formal language. The first version can be checked against a finished file, while the second depends on interpretation. Testable rules let a new team member apply the preference without a conversation.
Include an example where the rule is easy to misread. A short before-and-after line shows the difference between the old format and the new one. Keep the example next to the rule rather than in a separate document. The pair is what makes the register usable during a busy handover.
Record the source and the date
Every entry needs a source and a date. The source may be an email, a meeting note, or a comment on a reviewed draft. The date tells a reader whether the preference is current or inherited from an older process. Without both, the register turns into folklore that nobody can verify or safely change.
Note who confirmed the preference when the source is a conversation. A name is more useful than a subject line because it points to the person who can answer a follow-up question. If the client contact changes, review the entries that came from the previous person. A preference confirmed by someone who has left may still be valid, but it deserves a fresh check.
Put the register beside the template
Store the register where the work starts, next to the template or the checklist for the deliverable. A register in a separate knowledge base is only useful to people who remember to search it. Link it from the template header and from the onboarding note for the account. The goal is to make the correct version easier to find than the old one.
Keep one register per client rather than one for the whole team. Clients often want opposite things from the same report, and a shared list creates contradictions. If several clients share a template, keep the shared rules in the template and the client-specific rules in the register. The split keeps each file short and unambiguous.
Handle conflicting preferences
When two entries conflict, do not average them into a vague rule. Find the newer confirmation and ask the client which version is current. Record the decision and retire the older entry with a note that it was replaced. A visible retirement prevents the same conflict from returning in three months.
Sometimes a preference conflicts with a contractual or legal requirement. In that case the requirement wins, and the register should say so. Explain the limit to the client in plain language and offer the closest compliant alternative. Recording the exception keeps the team from quietly choosing between a promise and a rule.
Review the register each quarter
Read the register at each quarterly account check and mark entries that have not been used. Remove the ones that no longer apply and update the ones the client has changed. Ask the client whether any preference has shifted since the last review. A short conversation prevents a stale rule from shaping a whole quarter of work.
Give the updated register to the person who covers the account during leave. A current register is one of the cheapest forms of continuity because it carries decisions that would otherwise be re-explained. Date the revision at the top so a reader knows which version they have. Then the register becomes part of the account record rather than a personal note.
Teach the register during onboarding
Give the register to a new team member on the first day and ask them to apply three entries to a sample file. The exercise shows whether the rules are clear and whether the examples are enough. Record the questions that came up and improve the entries before the next person arrives. A register that only the original author can use is not yet finished.
Pair the new person with someone who has done the work for this client and ask them to compare the sample. Differences in interpretation point to a rule that needs a sharper example or a missing source. Update the register once, then test it with a second sample a week later. The goal is a document that teaches without needing a meeting.
Sources and next steps
Continue with operations support, then confirm scope, authority, and review ownership before expanding the role.
