Start with the evidence you need

Business records, in useful detail.

A brief can focus on one record type or a connected set across several systems. The following families show the kinds of material that could be investigated, the relationships that may matter and the AI tasks an evaluation could test.

01

Linked workflow and case histories

Link an enquiry, its correspondence, job records and close-out notes to reconstruct what happened, identify an outstanding action or explain an exception.

Records to explore

Initial requests, task or job records, correspondence, attachments, status changes, approvals, exception notes, handovers and close-out records. A case may span an inbox, spreadsheet, operational system and document folder.

Connections that matter

Case identifiers, timestamps, document versions, the order of events and links between the request, action and result. A useful history may include failed attempts and unresolved issues as well as completed work.

Tasks to scope

Reconstruct a timeline; identify the next action supported by the current case; summarise a handover; explain a delay; compare a requested outcome with the recorded result.

Assess before use

How complete the history is, whether timestamps are reliable, which links are explicit and which have been inferred, and whether later information must be withheld when testing an earlier decision.

02

Email, internal communication and CRM

Connect emails, CRM notes and support threads to the relevant quote, order or issue, so an answer can recover the customer’s requirements and the commitments still open.

Records to explore

Email threads and attachments, internal messages, CRM notes, lead and opportunity histories, customer enquiries, support tickets, service notes and recorded follow-up actions.

Connections that matter

Link a conversation to the relevant customer case, quotation, order, project or issue. Preserve thread order, attachment references and changes in status where the source allows it.

Tasks to scope

Retrieve an answer with evidence; extract a customer's requirements; identify outstanding commitments; classify an issue; summarise a long case; draft a response grounded in the authorised records.

Assess before use

Personal information, confidential negotiations, third-party correspondence and whether the business has authority for the intended use. A mailbox export does not establish permission to license everything inside it.

One case across Salesforce, Slack and Jira

A customer request might start in a Salesforce case, be discussed in Slack and lead to a Jira issue, fix and follow-up. The useful bundle preserves the links between those records, the order of the discussion and any later correction. A proposed task could ask a model to identify the unresolved commitment and draft an evidence-backed reply. Case closure alone would not prove that the underlying problem was fixed.

The source check would establish whether comments, attachments and historical states survive export. These product names illustrate possible source systems; they do not imply a partnership, integration or access to a company’s records.

03

Quotations, pricing and commercial changes

Connect specifications, quote revisions, supplier prices and accepted orders to explain a commercial change or identify which scope and price were agreed.

Records to explore

Enquiries, specifications, estimates, quotation versions, line-item prices, supplier price lists, proposals, scope changes, customer questions, accepted orders and relevant contract documents.

Connections that matter

Match revisions to the original request, identify changed quantities or specifications, and connect the accepted offer to the order and subsequent fulfilment or project record.

Tasks to scope

Compare quotations; extract inclusions and exclusions; explain a price change; flag inconsistent quantities; identify the accepted revision; produce an evidence-backed scope summary.

Assess before use

Whether quoted and accepted prices are distinguishable, how discounts and tax are represented, whether supplier information can be shared and whether the acceptance record is present.

04

Invoices, credits and financial administration

Link orders, invoices, credits and delivery or completion records to reconcile a charge and distinguish what was billed, adjusted or recorded as paid.

Records to explore

Purchase orders, sales and supplier invoices, credit notes, delivery or completion records, remittance information where appropriate, reconciliation notes and correspondence about disputed or adjusted charges.

Connections that matter

Connect the ordered item or service to receipt or completion, invoicing, corrections and any recorded payment status. Keep quoted, invoiced, credited and paid amounts distinct.

Tasks to scope

Match documents; extract line items; reconcile totals; explain a credit; identify a missing reference; flag a discrepancy for review without inventing its cause.

Assess before use

Sensitive financial details, bank information and identifiers; consistent currencies and tax treatment; and whether the records actually establish payment or only an amount billed.

05

Procurement, stock and fulfilment

Connect purchase orders, stock movements, dispatch records and proof of delivery to trace a shortage, partial shipment, substitution or unresolved return.

Records to explore

Purchase requests, supplier quotations, purchase orders, stock records, goods-received notes, allocation and picking records, dispatch notes, manifests, proof of delivery, shortages, substitutions and returns.

Connections that matter

Product or part identifiers, order lines, locations, batches where recorded, quantities and event dates. Link an exception to the original requirement and the actions taken to resolve it.

Tasks to scope

Reconcile ordered and received quantities; trace a shortage; compare promised and recorded delivery dates; identify an unresolved return; answer a stock or order-status question from the available evidence.

Assess before use

Inconsistent item codes, partial deliveries, stock snapshots versus transaction histories, missing events and commercially sensitive supplier or customer information.

06

Product catalogues, ecommerce and support

Link product variants and catalogue versions to orders, shipments and support cases to answer specification questions or investigate a fulfilment or return issue.

Records to explore

Product descriptions, specifications, variants, catalogue revisions, stock and order exports, fulfilment events, return reasons, support tickets, FAQs and authorised product documentation.

Connections that matter

Join product and variant identifiers to orders, shipment records, returns and support cases. Keep the product information that applied at the time of the transaction where it can be established.

For a Shopify-based business, connect the order and line items to the product variant and policy version that applied at purchase, then to fulfilment, support, returns and refunds. An orders CSV alone does not establish the complete case: order events, comments, attachments and helpdesk conversations need separate checks.

Tasks to scope

Answer specification questions; compare variants; extract product attributes; assess whether a support response uses the right product evidence; explain a return or fulfilment exception.

Assess before use

Rights to manufacturer content and product images, personal customer data, changing catalogue information and whether outcomes such as refund or replacement are explicitly recorded.

07

Engineering, CAD and CNC job records

Connect drawing revisions, CAD files, CNC programmes, job cards and inspection records to check which requirement applied and how the recorded work relates to it.

Records to explore

Engineering drawings, CAD files or exports, revision histories, specifications, bills of materials, CNC programmes, setup sheets, tooling notes, job cards, inspection reports and non-conformance records.

Connections that matter

Link the part and drawing revision to the quotation, production job, programme or setup and inspection outcome. The relationship between files can be as important as the files themselves.

Tasks to scope

Retrieve the applicable revision; compare requirements; identify a mismatch between a drawing and job instruction; connect an inspection finding to its source specification; summarise a technical change.

Assess before use

Customer and third-party intellectual property, file interpretability, units and revision control, and the availability of appropriate domain review. Historical programmes or instructions are not automatically safe or correct for execution.

08

Production, quality, maintenance and repair

Join production runs, machine and maintenance logs, quality checks and rework records to reconstruct a stoppage or investigate a recorded output or quality issue.

Records to explore

Production schedules, work orders, batch records, machine logs or sensor exports where recorded, downtime entries, material usage, scrap or rework records, quality checks, fault reports, diagnostic notes, parts selection, service reports and corrective-action notes.

Connections that matter

Relate events to the machine, job, product, batch and time period where identifiers exist. Link a reported problem to the inspection, repair or follow-up outcome rather than treating each log entry in isolation.

Tasks to scope

Classify downtime; reconstruct a maintenance case; find repeat recorded issues; explain an output discrepancy; retrieve a relevant procedure; summarise the evidence behind a quality investigation.

Assess before use

Log resolution, timestamp alignment, missing operating context, consistency of fault labels and whether a reported cause was verified or merely suspected. Predictive uses would need a separate assessment of coverage and labels.

09

Procedures, contracts and project decisions

Connect SOPs, contract terms, checklists and decision logs to the relevant task and date, so a model can retrieve the applicable instruction and identify unresolved obligations.

Records to explore

SOPs, work instructions, checklists, handover notes, meeting records, project decision logs, agreed specifications and contracts or amendments that the source is authorised to share.

Connections that matter

Associate the applicable document version with the task or decision. Link a change in instructions to its stated reason and any evidence of implementation.

Tasks to scope

Retrieve the relevant procedure; compare versions; extract obligations or deadlines for human review; identify an unresolved action; test whether an answer distinguishes a stated rule from a practice observed in the records.

Assess before use

Confidentiality, ownership and third-party rights; whether a procedure was current at the relevant time; and the distinction between a recorded contractual term, an interpretation and legal advice.

10

Design, marketing and creative work

Connect briefs, working files, creative revisions, approvals and campaign records to understand what was requested, what changed and what was eventually released.

Records to explore

Design or campaign briefs, authorised working files and assets, copy and artwork versions, feedback, approval records, channel plans, advertising histories and associated performance reports.

Connections that matter

Link a brief and its requirements to the relevant asset version, review comments, approval and publication or campaign record. Keep reported outcomes separate from any explanation of what caused them.

Tasks to scope

Compare the final work with the brief; trace the reason for a revision; identify the approved asset; summarise outstanding feedback; retrieve evidence for a campaign review.

Assess before use

Rights to creative assets, stock material, brands, likenesses and third-party content; client confidentiality; and whether performance records can be reliably linked to the work being assessed.

Maevar privacy notice

21 October 2026

Who we are

Maevar is operated by Marcias Limited, company number SC653353. Marcias Limited is responsible for the personal information covered by this notice.

Registered office: 51 Watt Road, Hillington, Glasgow, G52 4RY, United Kingdom.

For privacy questions or requests, email hello@maevar.com.

This notice covers this website and enquiries sent to Maevar. Any proposed introduction of a record owner to a buyer, or any sale or licence they agree, requires a separate review of the relevant rights, privacy requirements and agreed terms.

Enquiries and information you provide

The enquiry fields help you prepare an email containing your work email address, organisation, task summary and any optional format or timing details. The draft is prepared on your device. The website does not submit or store it: you choose whether to open, review and send it using your email app. There is no file-upload facility.

Please provide only a non-confidential summary. Do not include datasets, personal records, passwords or other sensitive information.

When you send an email, we receive the message, your contact details and any other information you choose to include. Richard McKay handles enquiries. Authorised service providers and connected tools, including AI-assisted tools, may support the handling of correspondence.

Why we use your information

We use enquiry information to respond, understand your requirements, assess whether we can help and discuss relevant business opportunities. We rely on our legitimate interests in managing business enquiries and developing appropriate business relationships, while considering your rights and reasonable expectations.

We also have a legitimate interest in keeping the website and email services secure and reliable. Where we must retain or disclose information to meet a legal obligation, we rely on that obligation.

Website and email services

We use OpenAI's ChatGPT Sites to host this website, Cloudflare for website delivery, security and email routing, and Google Workspace to receive and manage email enquiries. These services process information needed to deliver and protect the website and email service. This can include IP addresses, browser information, access times and technical or security logs, as well as email information when you contact us.

Optional analytics is controlled separately from necessary hosting and security services. Cloudflare uses a bot-protection cookie called __cf_bm, which normally expires after 30 minutes of inactivity. More information is available in Cloudflare's cookie documentation.

Optional analytics and your choice

Google Analytics loads only after you accept analytics. Rejecting keeps optional analytics off.

We load Google Analytics only after you accept it. Rejecting does not stop you using this website or contacting us. Necessary hosting, delivery and security services continue to operate, including their technical logs.

With your permission, analytics measures page visits and limited website interactions. We use fixed page information without search queries or URL fragments. We do not send your name, email address, organisation, enquiry text, form answers or the contents of email-draft links to Analytics. Analytics is not a record of the contents of your enquiry.

The email preparation tool may record that an email draft was prepared, without any of its contents. This is an expression of interest only: the website cannot tell whether you send the email. It is not counted as a submitted enquiry.

No Google Ads, Meta or LinkedIn advertising tags are activated by these controls. Advertising storage, advertising user data and ad personalisation remain disabled. We do not use enhanced conversions or upload contact details to Analytics.

Your privacy choice is stored on this website in your browser for up to six months. If you accept analytics, Google Analytics may set first-party cookies named _ga and _ga_ followed by the property identifier. Our code sets a maximum cookie lifetime of six months; your browser may apply a shorter limit. Google processes the analytics information and may process it outside the UK. See Google’s privacy policy. Our Google Analytics property retains user-level and event-level data for two months, without restarting that retention period when you return. This setting does not limit how long Google retains standard aggregated reports. Optional Google data sharing, Google Signals, user-provided data collection, granular location and device collection, and advertising personalisation are switched off.

Use Cookie settings in the footer to change your choice. Withdrawing analytics consent stops new measurement and reloads the page into a no-analytics state, so save any unfinished enquiry first. It also removes the relevant first-party analytics cookies where the browser permits. This does not erase information already sent to Google. We do not replay interactions that happened before you consented.

Our service providers may process information outside the UK. Their published data-processing terms describe the applicable international-transfer safeguards, including recognised adequacy arrangements and contractual safeguards:

Contact hello@maevar.com if you would like further information about these arrangements.

How long we keep information

We review unsuccessful enquiries 12 months after the last substantive contact and delete them unless there is an ongoing business or legal reason to retain them. For example, information may still be needed for an active discussion, to meet a legal obligation, or to establish, exercise or defend legal claims. Where we retain information longer, we keep it only for as long as that reason applies.

Enquiries that lead to a business relationship and related contract records are kept according to the needs of that relationship and applicable legal requirements. The 12-month enquiry review period is not a guarantee that every provider's security log or backup is erased on the same date; those records are subject to the relevant service's retention and deletion arrangements.

Your rights and complaints

Depending on the circumstances, you may ask to access, correct or delete your personal information, restrict its use, or receive a portable copy. You may also object to processing based on legitimate interests. These rights are subject to applicable conditions and exceptions.

Email hello@maevar.com to make a request or raise a concern. You can also complain to the Information Commissioner's Office through ico.org.uk/make-a-complaint.

Changes to this notice

We will update this notice when our website or information-handling arrangements change. The date above identifies the version you are reading.