People searching quick add term CAT tool, add term to termbase while translating, working termbase, capture terminology from source and target, or how to add glossary terms without leaving the translation editor are trying to remove a small but expensive interruption: the translator has just solved a recurring source term, but saving that decision requires opening another window, retyping both languages, navigating a terminology database, and then finding the original segment again.
A fast translation workflow uses quick-add terminology to capture a stable source–target term pair at the moment the decision becomes trustworthy. Current CAT-tool workflows commonly let translators select source and target text, use an Add Term or Quick Add Term command, and send the pair into a designated working termbase without leaving the active document. The mechanism is simple: solve the term once, store it once, and let later occurrences become cheaper.
This article owns one narrow reader job: turn a stable terminology decision made during translation into a reusable termbase entry with the smallest possible interruption. It is different from term extraction before translation, glossary compliance after terms are established, or full terminology governance. Here the decision has already been made in context. The productivity question is how to capture it before it disappears into one finished sentence.
Quick answer
Quick-add a term when:
- the source concept is clear;
- the target equivalent is stable;
- the term is likely to recur;
- the selected source and target spans contain the actual lexical unit;
- the working termbase is the correct destination.
A practical loop is:
translate → recognize a recurring term → verify the concept → select source term → select target equivalent → quick-add to working termbase → continue
Do not quick-add every interesting phrase.
Capture reusable decisions.
Why terminology capture is a speed problem
A translator solves many terms while reading context.
Some decisions are expensive:
- product component names;
- regulatory terms;
- financial instruments;
- medical procedures;
- institutional roles.
If the decision remains only inside one target sentence, the next occurrence can trigger the same research again.
The translator has to remember:
What did I call this three pages ago?
Or search the document.
Or open concordance.
Or inspect the previous segment.
A termbase converts local memory into project memory.
Quick-add reduces the cost of creating that memory.
The best moment to capture a term
Too early is dangerous.
Too late is expensive.
The best moment is usually after the first context has made the concept clear and the target form has been verified enough to reuse.
For example, source term:
retention period
The first occurrence is ambiguous.
The next sentence explains:
the period for which customer records must remain stored after account closure.
Now the concept is clear.
The translator chooses the approved target.
This is the capture moment.
Quick-add.
Later occurrences become easier.
Worked example 1: technical component
Source:
differential pressure transmitter
The translator checks the client manual and confirms the approved target.
The term appears repeatedly.
Instead of retyping it into a glossary later, the translator selects both terms and quick-adds them.
The termbase can now:
- highlight later source occurrences;
- offer the target equivalent;
- support QA;
- reduce spelling variation.
One decision compounds.
Worked example 2: role title
Source:
case owner
The first occurrence is unclear.
Later context shows the role is the staff member responsible for approving closure.
The translator chooses a stable institutional equivalent.
This is a good quick-add candidate because the role will recur.
Do not quick-add before the responsibility is clear.
The cost of a wrong term multiplies faster than the cost of an unstored term.
Worked example 3: one-off descriptive phrase
Source:
slightly uneven grey-blue surface
The phrase is translated well.
Should it be quick-added?
Probably not.
It is a one-off description, not reusable terminology.
Quick-add is not a scrapbook.
A lean termbase is easier to trust.
Working termbase versus reference termbase
Many projects attach several termbases.
One may be:
- client master;
- product glossary;
- regulatory reference;
- project working termbase.
The quick-add command needs a destination.
A useful architecture is:
reference resources = mostly read working termbase = new validated project decisions
This prevents new project terms from being scattered across authoritative databases before review.
Choose the correct working termbase
Before translation begins, confirm which termbase receives new entries.
Otherwise quick-add can create:
- duplicate entries;
- client terms in personal glossaries;
- project-specific wording in master resources;
- terminology that reviewers cannot see.
Fast capture requires correct routing.
A one-key shortcut is only useful if it writes to the right place.
Capture the smallest useful lexical unit
Suppose source says:
annual retention period requirement
The reusable concept may be:
retention period
not the entire noun phrase.
If you store too much context, later matching becomes weak.
If you store too little, meaning becomes ambiguous.
The ideal term entry captures the stable concept.
Context and definition can carry the rest.
Source selection matters
When selecting the source term:
- exclude surrounding punctuation unless it belongs to the term;
- avoid unnecessary articles;
- preserve meaningful capitalization;
- include required modifiers;
- exclude temporary context.
Bad source selection creates poor lookup.
The termbase can only match what you store.
Target selection matters
Select the exact reusable target equivalent.
Avoid:
- surrounding sentence words;
- articles that vary by grammar;
- inflected endings if the termbase should store a lemma;
- punctuation;
- a target paraphrase that only fits this sentence.
The stored target should be useful later.
Lemma versus surface form
In highly inflected languages, the target sentence may contain an inflected form.
Should you quick-add that exact form or the dictionary form?
It depends on termbase design.
A strong workflow may store:
- lemma as preferred term;
- grammatical properties;
- variants where useful.
If quick-add blindly stores every surface form, the termbase can fill with duplicates.
This is where fast capture needs later enrichment.
Quick-add first, enrich later
Quick-add is optimized for speed.
It often stores only the source and target pair.
Later, a terminologist or translator can add:
- definition;
- subject field;
- usage note;
- forbidden terms;
- case sensitivity;
- matching rules;
- grammatical gender;
- approved context.
This creates two stages:
capture now → enrich when needed
The first stage prevents knowledge loss.
The second improves quality.
When the full Add Term dialog is better
Use a detailed entry instead of quick-add when the term requires:
- definition;
- disambiguation;
- multiple approved variants;
- forbidden alternatives;
- client note;
- source citation;
- unusual matching rule.
The shortcut should not become a reason to omit critical terminology metadata.
Use quick-add for straightforward stable pairs.
Use full entry for ambiguous or consequential concepts.
Worked example 4: forbidden synonym
Source concept:
adverse event
The project has one approved target and one dangerous near-synonym.
Quick-add alone may not capture the prohibition.
Open the detailed term entry.
Add:
- preferred target;
- forbidden target;
- definition;
- domain.
A slower entry now can prevent many later corrections.
Worked example 5: product feature capitalization
Source:
Smart Relay
The target keeps the brand feature unchanged.
Quick-add stores the term.
But capitalization matters.
If the termbase supports case sensitivity, set it.
Otherwise the entry may match ordinary “smart relay” prose unexpectedly.
Term matching belongs to the term entry, not only the word string.
Worked example 6: plural variation
Source term appears first as:
data retention policy
Later:
data retention policies
If matching rules are permissive enough, one entry can cover both.
Do not create duplicate entries simply because grammar changes.
Store the lexical concept with sensible matching.
Use quick-add after terminology research, not instead of it
The command does not verify the term.
It merely stores it.
Research may still require:
- client glossary;
- official website;
- domain reference;
- standard;
- previous approved translation.
Quick-add should shorten the transition from verified decision to reusable resource.
It should not shorten verification itself.
The “will this recur?” test
Before storing, ask:
Will this concept appear again enough that retrieval will save time?
If yes, capture.
If no, leave it in the sentence.
A termbase with 500 useful recurring entries is more valuable than one with 10,000 one-off phrases.
The “will somebody else need this?” test
Even if you personally remember the term, another translator may not.
Quick-add becomes especially valuable in team projects.
The entry can immediately help:
- another translator;
- reviewer;
- later file;
- next release.
Termbases externalize team memory.
The “is the decision global?” test
Some terms are valid only in one section.
Example:
“charge” means electrical charge in one chapter and fee in another.
Do not store a global source-target pair without context if the source is polysemous.
Use:
- domain metadata;
- definitions;
- context notes;
- narrower source phrase.
Fast capture should not erase sense distinctions.
Duplicate detection
Quick-add can create duplicates when:
- term already exists;
- surface form differs slightly;
- another translator adds the same term simultaneously;
- capitalization differs.
If the tool warns about duplicates, inspect before creating another entry.
Duplicates reduce trust.
They also create competing suggestions.
Merge rather than multiply
If a concept already exists, add a variant or update the existing entry instead of creating a parallel entry where possible.
One concept should ideally remain one coherent entry.
This improves:
- lookup;
- QA;
- maintenance.
Quick-add and term extraction
Term extraction is broad and pre-emptive.
It identifies candidate terms from the corpus.
Quick-add is local and evidence-driven.
It captures a term after context has proved useful.
The two workflows complement each other.
Extraction builds the starting glossary.
Quick-add catches important terms that appear during real translation.
Quick-add and glossary compliance
Once the term is stored, glossary compliance can check whether later segments use it.
That creates a powerful loop:
discover → decide → quick-add → reuse → QA
The shortcut is the bridge between decision and enforcement.
Quick-add and predictive typing
Termbase entries can feed predictive suggestions.
A term captured early may appear at the cursor later.
This reduces typing.
Again, one terminology decision can compound across several productivity tools.
Quick-add and fragment assembly
A trusted term can become a reusable fragment in later sentences.
The target syntax still changes.
The lexical decision does not need to.
Quick-add and project search
Before storing a new term, a quick project search can show how the source term behaves across current files.
If multiple senses appear, avoid one global entry.
If usage is consistent, quick-add with confidence.
This is especially useful for ambiguous nouns.
Failure mode 1: adding before meaning is clear
The translator sees a technical-looking phrase and stores the first plausible target.
Later context proves it wrong.
Now the termbase is actively spreading the error.
Wait until the concept is stable.
Failure mode 2: adding too many phrases
Every collocation becomes an entry.
The termbase becomes noisy.
Translators stop trusting suggestions.
Capture concepts, named entities, controlled phrases, and high-value recurring expressions.
Not every fluent phrase deserves governance.
Failure mode 3: storing sentence grammar
Target entry includes an article and case ending that belong only to one sentence.
Later insertion produces awkward grammar.
Store reusable lexical form.
Failure mode 4: writing into the master resource too early
A provisional project term is quick-added directly into a client master termbase.
Other projects begin seeing it before review.
Use a working termbase when governance requires promotion.
Failure mode 5: ignoring language direction
A multilingual termbase may support several languages.
Make sure the source and target selections go into the correct language fields.
A shortcut cannot correct wrong language routing.
Failure mode 6: adding unverified names
A source contains a person’s surname with an OCR error.
Translator quick-adds it.
Now termbase suggests the wrong name everywhere.
Verify identity before storing names.
Quick-add workflow for one translator
A simple personal routine:
- solve term;
- decide if recurring;
- search termbase quickly;
- select source/target;
- quick-add;
- continue;
- enrich only if needed.
This should take seconds.
Quick-add workflow for a team
A team routine can add governance:
- translators quick-add into project working TB;
- reviewer checks new entries;
- duplicates merged;
- definitions added for ambiguous concepts;
- approved entries promoted to master.
This separates capture speed from master-quality control.
Use a “new terms” review queue
At the end of each day or section, review entries created during translation.
Check:
- spelling;
- concept clarity;
- target preference;
- duplicate status;
- domain;
- matching rule.
This prevents the working termbase from accumulating weak entries.
A terminology promotion gate
Before moving an entry into master:
- concept recurs;
- target approved;
- source form stable;
- duplicates resolved;
- definition sufficient;
- forbidden variants recorded if needed.
Promotion should be deliberate.
Capture can be fast.
Master knowledge should be clean.
Quick-add and case sensitivity
A product name may require exact case.
A common noun may not.
If quick-add uses default case settings, check whether the default is appropriate.
Project termbase defaults can make capture faster when most terms share the same behavior.
Quick-add and matching rules
The term may need:
- exact match;
- prefix match;
- fuzzy match;
- custom stem/wildcard behavior.
Do not open matching settings for every ordinary entry.
But recognize when default matching will cause:
- missed inflections;
- false positives.
Termbase matching is a separate optimization layer.
Quick-add and forbidden terms
If a reviewer rejects a variant, add it as forbidden where the system supports this.
Now later use becomes visible.
A terminology decision is more powerful when the tool can detect both:
- what to use;
- what not to use.
Quick-add and definitions
Definitions are worth adding when source terms are:
- ambiguous;
- technical;
- cross-domain;
- easily confused.
One sentence of definition can save repeated interpretation later.
Quick-add and usage examples
A usage example can show:
- collocation;
- grammar;
- domain;
- intended meaning.
Do not add examples to every term.
Use them where context changes interpretation.
Capture from reviewer corrections
A reviewer changes a recurring target term.
Do not fix only the current sentence.
Ask:
Is this a reusable terminology decision?
If yes:
- update termbase;
- search current project;
- correct other occurrences;
- run glossary QA.
This turns one review correction into system improvement.
Capture from client feedback
Client says:
Use “member account,” not “user account.”
Update:
- preferred term;
- forbidden term;
- existing project occurrences.
Quick-add is not the right action if the entry already exists.
Edit the existing concept.
Capture from subject-matter experts
SME answers can be high-value terminology evidence.
Record:
- preferred target;
- definition/context;
- source of approval.
This prevents the same query next month.
Measuring quick-add value
Track informally:
- new terms captured;
- later occurrences;
- number of repeated lookups avoided;
- reviewer terminology corrections.
If many captured terms never recur, you are adding too much.
If reviewers keep correcting repeated terms that were never stored, you are adding too little.
A five-minute practice drill
Translate 300 words of technical prose.
Mark every potential term.
Then classify:
- one-off;
- recurring;
- ambiguous;
- controlled.
Quick-add only recurring stable concepts.
At the end, compare how many candidates became entries.
This trains selectivity.
A clean quick-add policy
A strong policy can be one sentence:
Add a source–target pair when it represents a stable recurring concept and the target has been verified enough that you want the tool to suggest it again.
That is sufficient for most daily work.
The deeper principle: capture solved terminology before working memory lets it go
Translators solve expensive lexical problems.
If those solutions remain trapped in one segment, the project pays again later.
Quick-add turns a local solution into reusable project memory with almost no navigation cost.
The shortcut is valuable because it happens at the exact moment when the translator already knows:
- the source concept;
- the target equivalent;
- the context.
No reconstruction is needed.
Capture once.
Reuse often.
Advanced practice: separate capture certainty from promotion certainty
A useful terminology workflow distinguishes two questions:
- Is this term pair stable enough to help the current project?
- Is this term pair authoritative enough to enter the long-term master glossary?
The answer to the first can be yes while the answer to the second is not yet.
This is why a working termbase is valuable.
A translator can capture a project decision quickly without pretending that the organization has completed full terminology governance.
The project gets immediate leverage.
The master resource remains curated.
A four-state term lifecycle
You can think of terminology as moving through four states.
Candidate
The source expression looks important but meaning or target is still uncertain.
Do not quick-add yet.
Working
The concept is clear enough for current project reuse.
Quick-add to project TB.
Reviewed
A reviewer or terminologist has checked the pair, duplicates, matching, and metadata.
Use confidently in the project.
Master
The term is approved for future projects within a defined scope.
Promote.
This lifecycle keeps speed and governance from competing.
Capture after the first stable occurrence, not necessarily the first occurrence
The first appearance of a term may be the worst place to decide it.
Source writers often introduce a concept before defining it.
Later text may include:
- a parenthetical definition;
- an example;
- a diagram;
- a longer full form;
- an acronym expansion.
Therefore the capture rule should be:
Quick-add at the first stable occurrence.
This may be sentence one.
It may be page three.
Worked example 7: abbreviation expansion
Source first says:
CDR
Later:
Clinical Data Repository (CDR)
If you quick-add “CDR” before seeing the expansion, you may attach the wrong target concept.
After the expansion appears, create the entry:
- source full term;
- abbreviation variant;
- approved target full term;
- target abbreviation if applicable.
One later, better entry can serve every earlier occurrence.
Worked example 8: nested term
Source:
high-pressure fuel pump controller
Possible candidates:
- fuel pump;
- high-pressure fuel pump;
- controller;
- fuel pump controller;
- high-pressure fuel pump controller.
Which should be stored?
Look at reuse.
If the full component name is a controlled part, store the full term.
If “fuel pump controller” recurs across several variants, that may deserve a separate entry too.
Do not automatically store every substring.
Terminology should mirror real concepts.
Worked example 9: adjective plus term
Source:
provisional approval
The project already has an entry for “approval.”
Should you quick-add “provisional approval”?
Only if it functions as a recognized concept that recurs.
If “provisional” is ordinary composition, keep the existing noun term.
This prevents termbases from filling with predictable combinations.
Worked example 10: verb terminology
Terminology is not only nouns.
Controlled verbs can matter:
- decommission;
- authenticate;
- reconcile;
- indemnify.
If a verb has a domain-specific target and recurs, capture it.
Choose a base lexical form according to language/termbase design.
Do not store every conjugated occurrence separately.
Quick-add and source capitalization
A source term can appear at sentence start with a capital letter.
If capitalization is not conceptually meaningful, store the normal lexical form.
If case matters—for brand, gene, acronym—preserve it and configure matching accordingly.
The selection itself becomes a small terminology-editing decision.
Quick-add and punctuation
Do not include:
- comma;
- colon;
- quotation marks;
unless punctuation is part of the official term.
Example:
Source text:
“Secure Mode,”
Termbase entry should probably be:
Secure Mode
not the quotation and comma.
Clean entries improve matching.
Quick-add and hyphenation
A source may alternate:
- risk-based;
- risk based.
Before creating two concepts, ask whether this is:
- orthographic variation;
- style inconsistency;
- genuinely different term.
One concept can often hold several source variants.
Quick-add and plural forms
Same principle.
If “sensor” and “sensors” are grammatical forms of one concept, do not create two concept entries merely because the string differs.
Matching rules or variants should handle it.
Quick-add and source errors
If source contains a typo:
transimitter
do not quick-add the typo as the official source term unless the workflow intentionally records source variants.
Correct/query source if appropriate.
A termbase should not normalize bad source silently without a reason.
Quick-add and transliteration
For names or terms crossing scripts:
- source original;
- target transliteration;
- approved local form.
Capture only after transliteration policy is clear.
A termbase can stabilize romanization across a long project.
This is high-value.
Quick-add and units
Units usually belong to auto-translation or non-translatable rules rather than terminology.
Do not add “kg” as a term simply because it recurs.
Choose the resource that owns the object.
This keeps terminology clean.
Quick-add and strings
Software UI labels can be terminology when they function as exact product labels.
Example:
Account Security
If the label must match the interface everywhere, termbase capture is useful.
If it is ordinary prose, sentence-level TM may be enough.
Quick-add and client questions
When a translator has an unresolved query:
Should “member” mean registered customer or loyalty-program member?
Do not quick-add until the client resolves it.
Mark the term as pending.
Capture certainty, not guesses.
Quick-add and definitions from the source
Sometimes the source provides a perfect definition.
Store it.
Example:
“Recovery time” means the period between service restoration and return to normal capacity.
A one-sentence definition can prevent cross-project ambiguity.
Quick-add and external standards
If the term comes from an ISO, legal, medical, or technical standard, record the source where useful.
This helps future reviewers trust the entry.
It also prevents someone from replacing a standardized term with a stylistic synonym.
Avoid capture debt
Capture debt occurs when dozens of important terms are translated consistently but never stored.
Later:
- new translator joins;
- reviewer changes terminology;
- next release begins.
The project must reconstruct decisions from text.
Quick-add reduces capture debt in real time.
Avoid capture overload
The opposite problem is capture overload.
Every interesting phrase becomes terminology.
The termbase turns into a phrasebook.
Symptoms:
- too many hits;
- ambiguous suggestions;
- duplicate entries;
- slow cleanup.
Selectivity is part of speed.
Create a daily terminology digest
In a team project, review newly quick-added entries once per day.
The digest can show:
- source;
- target;
- creator;
- date;
- comment.
A lead translator can approve, merge, enrich, or reject.
This is faster than waiting until final QA when incorrect terms have already spread.
Use creator metadata
Knowing who added an entry can help when context is unclear.
Not for blame.
For clarification:
“What did you mean by this entry?”
Project memory becomes more traceable.
Quick-add and concurrent translators
Two translators can solve the same term at the same time.
Possible outcomes:
- duplicate identical entries;
- competing targets.
Reduce this with:
- shared online working termbase;
- quick search before add;
- regular digest review.
Real-time shared terminology produces more leverage than isolated local glossaries.
Quick-add and offline work
Offline translators may capture terms locally.
When merging back:
- deduplicate;
- resolve conflicts;
- preserve metadata.
Do not assume two local termbases can be combined blindly.
Quick-add and terminology versioning
If terminology changes mid-project:
- update the entry;
- search project;
- correct existing occurrences;
- note effective date if important.
Do not create a second competing entry unless both variants remain valid for different scopes.
A capture quality score
For high-value projects, rate new entries informally:
Green
Clear concept, approved target, recurring.
Amber
Useful current-project decision but needs review.
Red
Unresolved/temporary — do not add.
This keeps quick-add fast while preserving caution.
A source–target boundary check
Before capturing, look one word left and right in both languages.
Did you accidentally include:
- article;
- adjective;
- punctuation;
- verb particle?
This two-second check prevents messy entries.
A target naturalness check
The selected target term should be the reusable expression, not a source-shaped phrase that happens to work in this sentence.
If the target is unnatural outside the full clause, do not store it as terminology.
Quick-add and collocations
Some collocations are stable enough to store:
- file a claim;
- conduct an audit;
- administer a dose.
But decide whether your termbase is designed for multiword phraseology.
Some teams keep collocations in separate resources.
Architecture matters.
Quick-add and reviewer trust
Reviewers are more likely to trust a termbase when entries are:
- few;
- clean;
- contextualized;
- non-duplicative.
Capture speed should not destroy resource credibility.
Search after quick-add
After adding a high-impact term, search the current project for prior occurrences.
You may discover earlier translations using another target.
Fix now.
This prevents inconsistent terminology from reaching final review.
QA after quick-add
If glossary compliance runs live, later source occurrences should show the new preferred target.
Test one.
If the system does not recognize it:
- matching rule may be wrong;
- language field may be wrong;
- termbase may not be active.
Quick-add is only valuable if retrieval works.
Capture high-risk negated terms carefully
Some terminology pairs differ by one modifier:
- active / inactive;
- insured / uninsured;
- compliant / non-compliant.
Do not store a truncated source that drops the modifier.
The full conceptual distinction belongs in terminology.
Capture numbers only when part of official identity
Example:
ISO 9001
The number is part of a standard name.
This can be terminology.
A random “12 months” duration is not.
Object identity determines resource choice.
Capture legal defined terms
Contracts often define capitalized terms:
Effective Date
These are excellent terminology candidates because:
- definition exists;
- exact consistency matters;
- capitalization may matter.
Quick-add after confirming the definition.
Capture scientific names
Species names, gene names, and chemical names can benefit from terminology capture.
But verify:
- spelling;
- capitalization;
- italicization policy;
- target convention.
Scientific precision raises the bar.
Capture educational terms
Curriculum terms can recur across:
- lesson plans;
- assessments;
- parent communication.
A project termbase can stabilize them.
Again, store the concept, not every sentence phrase.
A quick-add stop rule
If you spend more than 30–60 seconds deciding whether to quick-add, stop.
The term probably needs full terminology treatment or is not stable enough.
Quick-add should remain quick.
Measure resource cleanliness
At project end, sample 50 quick-added entries.
Classify:
- definitely useful;
- duplicate;
- too broad;
- one-off;
- wrong.
If more than a small fraction are weak, tighten capture policy.
The mature capture loop
In a mature project:
- important terms are noticed;
- stable decisions are captured immediately;
- ambiguous concepts wait;
- working TB stays lean;
- reviewer enriches selectively;
- master receives only approved knowledge.
That is the balance.
Quick-add is fast because governance happens at the right layer, not because governance disappears.
Final quick-add stress test
Before the termbase becomes crowded, sample ten recently captured entries and ask three questions.
Would I want this term suggested again? If no, remove it.
Would another translator understand the concept from the entry? If no, add a definition or context note.
Would this entry still make sense outside the sentence where it was created? If no, the selected source or target span is too broad, too narrow, or too grammatical.
This small audit protects the speed benefit. Quick-add works because the capture action is cheap, but cheap capture must be balanced by selective cleanup. Otherwise the project trades repeated lookup for repeated terminology noise.
Use capture frequency as a signal
If translators keep quick-adding variants of the same concept, stop and inspect the resource. You may need:
- one merged concept entry;
- better matching rules;
- clearer preferred/forbidden status;
- a terminology decision from the client.
Repeated capture of “new” terms can reveal that the glossary is not serving retrieval well. The correct fix may be resource design rather than more entries.
The mature behavior is simple: quick-add when the decision is genuinely new, edit when the concept already exists, and escalate when the concept is not yet stable.
Final capture check: one entry should remove future uncertainty
Before saving a new pair, imagine the next translator seeing the source term two days later.
Will the entry answer the real question quickly?
If the termbase result still forces them to ask:
- Which sense is this?
- Is this target actually approved?
- Does the capitalization matter?
- Is this only for one file?
then the entry needs a little more context or should wait.
Quick-add is successful when one small action now removes a larger future decision. That is the standard: not maximum glossary growth, but maximum reusable certainty per entry.
Keep capture friction deliberately low
The capture action should remain faster than rediscovering the term later. If adding a normal stable pair requires navigating several dialogs, configure a working termbase and a shortcut so the basic operation stays lightweight. Reserve detailed metadata entry for the terms that need it.
This separation matters because translators stop capturing terminology when the storage process feels heavier than the immediate translation task. A practical system keeps simple decisions simple while preserving an escalation path for complex terminology.
Capture decisions that change later work
A useful final rule is to ask whether saving the entry will alter what the tool does later. If later occurrences will be highlighted, suggested, checked, or reused more reliably, capture has real leverage. If nothing in the later workflow will use the entry, the storage action may not be worth taking.
Quick-add earns its place by changing future behavior, not by increasing glossary size.
Summary
Quick-add terminology helps people translate quickly by storing stable source–target term pairs directly from the active segment into a working termbase.
The reliable loop is:
verify concept → select source and target → check destination → quick-add → continue → enrich or review later when needed
Do not quick-add every phrase.
Do not store uncertain concepts.
Do not send provisional terms into authoritative master resources without governance.
The goal is a lean termbase containing decisions worth reusing.
Frequently asked questions
What is quick-add terminology?
It is a CAT-tool workflow that saves selected source and target text directly into a termbase, often through a shortcut, without opening a full terminology-entry dialog.
When should I quick-add a term?
When the concept is clear, the target is stable, and the term is likely to recur.
Is quick-add the same as term extraction?
No. Term extraction identifies candidate terminology from a corpus. Quick-add captures a term during active translation after context has helped verify it.
Should every quick-added term go to the master termbase?
Not necessarily. Many workflows capture new terms in a project working termbase, then review and promote them later.
What if the term already exists?
Update or merge the existing entry rather than creating unnecessary duplicates.
Should I store an inflected target form?
Usually store the reusable lexical form according to your termbase design. Add variants or grammar information if needed.
Can quick-add create bad terminology?
Yes. It accelerates storage, not verification. A wrong decision can spread faster if stored too early.
How does quick-add save time?
It avoids retyping, navigation, repeated research, and repeated decisions on later occurrences.
Should I add definitions?
For ambiguous, technical, or high-risk concepts, definitions are valuable. Straightforward terms may not need them immediately.
What is a working termbase?
A working termbase is the designated project resource for capturing new terminology before entries are reviewed or promoted into a more authoritative master glossary.
Internal-link opportunities
- How People Translate Quickly | Term Extraction — for building candidate terminology before drafting.
- How People Translate Quickly | Glossary Compliance — for enforcing captured terminology later.
- How People Translate Quickly | Cross-File Project Search — for checking current usage before storing ambiguous terms.
- How People Translate Quickly | Predictive Typing — for inserting approved terms quickly.
- How People Translate Quickly | Termbase Priority — for ranking multiple terminology resources.
- How People Translate Quickly | Termbase Matching Rules — for controlling how captured terms are recognized.