Guides for your business

Build a content matrix for website copy, images, evidence and approvals, with an owner and a next step for each section.

Give delivery a source-linked brief covering the agreed work, client priorities, exceptions and unanswered questions.

Record comments, requested changes and explicit approvals against the exact file and version each reviewer saw.

Use a change register to describe an additional request, its estimated impact and the decision needed before the delivery plan changes.

Place a new request beside the agreed scope, identify the evidence and decide what needs clarification before proposing a change.

Clarify the element, intended effect and constraints behind vague feedback before a designer starts revising.

Build a dated, source-linked chronology that separates recorded events from recollections and unresolved questions.

Select the agreed final files, record their versions and give the client an index with open items and access checks.

Record client-specific operating terms with their scope, owner and a direct path to the agreement or approved message.

Maintain one approved reusable master and track older copies that still need replacement or retirement.

Help your team find the right logo, image or guideline, along with its version, intended use and source of approval.

Set a clear discount boundary, name the decision maker and record what happens when approval is unavailable.

Compare price list versions by item, scope, approval and effective date before deciding which price applies.

Record the decision, reason, owner, effective date and the earlier rule it replaces so your team can follow the history.

Check a quote against its agreed scope, current price reference, discount decision, dates and delivery commitments.

Record your team's promises to clients with the original wording, owner, trigger, status and evidence of the next action.

Give writers paired examples, a reason for each choice and practical boundaries for different customer situations.

Turn real recurring questions into checked answers with a source, an owner and a reason to review each entry.

Prepare a temporary cover brief with the current state, next action, decision limits and accessible source for each open item.

Inventory the client work affected by a role change and confirm an accountable owner for each next action.

Prepare one project for a new lead with its current scope, decisions, dependencies, open questions and next actions.

Write decision boundaries with named decision makers, conditions, evidence and a usable escalation path.

Give each onboarding action an accountable owner, a completion condition and a clear handoff to the next role.

Audit an existing task list for missing ownership, unclear next actions, stale work and duplicate records, then decide what needs a human decision.

Make a project's waiting party, open dependency, blocked stage, internal owner and next review date visible in a simple register.

Explain what has happened, what the work still depends on and when the client will next hear from you, without inventing a finish date.

Preserve the original request, give the work a clear owner and next action, verify the result, then record the reply that closes the client loop.

List recurring work, estimate its real time demand against available owner capacity, and decide what to keep, reduce, delegate or pause.

Map each agreed service to its own frequency, visit window and billing reference, while keeping the accepted package as the source of scope.

Separate client-supplied records from the office work that depends on them, then show who owns the next action in a month-end workflow.

Define the proposed outcome, included work, exclusions, client inputs, open questions, and the exact decision a client is being asked to make.

Gather the recipient, project reference, purchase order if supplied, agreed billing trigger, and source records before an invoice draft is prepared.

Test a procedure with a realistic input, observable output, and exception case, then record where the reader needs clarification.

Record the approved artwork version, quantity, actual production milestones, evidence references, and shipment handoff for each print order.

Create a factual inventory of advertising platforms, account and campaign references, visible assets, source dates, unknowns, and confirmation owners.

Compare a manual email list, a form, and a client portal using the same request, documents, follow-up, and recorded observations.

A practical shared inbox workflow for assigning each message, setting the next action, escalating a blocked thread, and closing it with a clear reason.

Build a manageable review cycle for company wiki pages by assigning owners, setting review triggers, and recording what changed.

Decide whether your current shared inbox can support real service work by testing ownership, case status, handoffs, history, and review needs.

Create field-level rules for customer contact data so a CRM, inbox, and spreadsheet do not overwrite conflicting values without review.

Inventory the fields, relationships, activities, and files in a CRM export before choosing a destination or starting a migration.

Build a review queue that separates likely duplicate customer records from similar names before importing data into a CRM.

Use a representative test set to check CRM field mappings, associations, and import behavior before moving the full data set.

Define rollback triggers, preserve the data you can restore, and track changes made after a software cutover.

Define the few customer fields and habits that make the next action clear before adding more CRM structure.

Create a shared naming dictionary for campaign links so source, medium, campaign, and creative values stay consistent.

Use a fictional company packet to test source retrieval, conflicting instructions, work ownership and export before choosing a business workspace.

Build a short, usable view of what needs attention, who owns the next step and what counts as finished.

Find the current document, preserve its context and create a usable record when files and decisions arrive in different channels.

Prepare a handoff that tells the next person what happened, what remains uncertain and what they need to do next.

Check the information needed to begin a client project, identify actual gaps and ask one clear question for each unresolved item.

Keep one clear record of a customer inquiry as the conversation moves between messages, a quote and a decision.

Compare a spreadsheet and a CRM by the information, handoffs, follow-up and control your business actually needs.

Choose a useful first task, give AI the right context and review its result before relying on it.

Compare a chatbot, an automation and an AI agent through one business task, including the limits and approvals each may need.

Frame a business request, follow the information behind it and keep the next decision in the same conversation.

Follow a business question from relevant records through a calculation to an answer you can check against its sources.

Review an AI-prepared answer, calculation, document or proposed action against the information and decision it is meant to support.

Keep the current agreement easy to find while preserving the source and history needed to understand what changed.