Different sectors. Specific evidence.

What a sourcing brief could look like.

Start with a question and work back to the evidence. These illustrative briefs show the records, relationships and assessment points that matter in different sectors.

01

Haulage and logistics

Booking → dispatch plan → manifest → delivery event → exception → resolution.

Potential records

Transport bookings, dispatch sheets, routes and schedules, load manifests, driver or depot updates, proof of delivery, failed-delivery notes, customer communications and related charges.

Where a business uses Mandata or another transport system, investigate the links between job instructions, progress updates, messages and proof of delivery. Include failed attempts, shortages and disputed deliveries. A final delivery document may support extraction without explaining the original dispatch decision or every subsequent exception.

What to establish

Reliable links between the booking and delivery, the sequence of revised instructions, whether the recorded route reflects a plan or an actual journey, and the treatment of driver and customer information.

Example task

“Why was this delivery late, what did the customer get told and which parts of the explanation are documented?”

02

CNC and precision engineering

Enquiry → drawing revision → quote → job setup → manufacture → inspection.

Potential records

Customer specifications, drawings and CAD exports, quotation revisions, material and tooling requirements, CNC programmes, setup sheets, job cards, inspection results and rework notes.

What to establish

Revision consistency, permissions for customer-owned designs, meaningful links between programmes and jobs, and the domain expertise required to assess an answer.

Check whether the saved CNC programme is the version actually run, including shop-floor changes, and whether inspection results retain tolerances, units and the relevant part revision. Keep failed inspections, rework and customer concessions visible rather than retaining only the final accepted result.

Example task

“Which drawing revision applied to this job, and does the inspection record address its stated tolerances?”

03

Manufacturing and plastics

Production order → materials and setup → run → quality checks → rework or release.

Potential records

Bills of materials, material grades and lots, mould or tool identifiers, batch and run sheets, recorded process settings, production counts, scrap, downtime, maintenance and quality investigations.

What to establish

Whether the material lot, mould or tool, machine and run can be matched across systems; whether measurements are comparable; and whether the explanation is confirmed, disputed or absent.

Example task

“What changed between these production runs, and which recorded facts support the explanation for additional scrap?”

04

Printing and packaging

Customer specification → estimate → artwork or proof → approval → print job → finishing and dispatch.

Potential records

Job specifications, quotation changes, artwork versions where rights permit, proof approvals, job tickets, substrate and finishing instructions, production checks, reprint records and delivery notes.

What to establish

The approved version, the sequence of changes, rights to artwork and customer content, and whether a defect or reprint reason was documented.

Example task

“Did the final job reflect the approved specification, and where did the reprint request originate?”

05

Wholesale, ecommerce and product businesses

Product listing → customer order → stock allocation → fulfilment → support or return.

Potential records

Catalogue and variant data, supplier quotations, stock histories, substitutions, orders, dispatch events, support threads, return reasons, authorised manuals and recorded resolutions.

What to establish

Stable product identifiers, the information available at the time, customer-data restrictions and a recorded link between the support case and its outcome.

Example task

“Was the customer's question answered using the right product variant, and what happened after the proposed resolution?”

06

Construction and project delivery

Enquiry and scope → estimate → instruction or variation → valuation → final account.

Potential records

Estimates, bills or schedules of quantities, quotations, tender clarifications, project correspondence, instructions, variation records, progress records, valuations and final accounts.

For a business using Procore, a candidate case could connect drawing revisions, requests for information, site logs and attachments with estimate spreadsheets, emailed instructions, variation valuations and the final account. The assessment would check which revision was issued at the time and whether an instruction, approval and agreed value can be traced separately. Export coverage and the underlying files would need testing.

What to establish

Consistent scope and tax treatment, links between an instruction and its commercial effect, evidence of approval, and the difference between an amount claimed, agreed, invoiced or paid.

Example task

“Why did the final cost change, which changes are documented and what remains unexplained?”

Explore the synthetic construction example →

07

Maintenance, repair and field service

Fault report → diagnosis → parts or repair decision → service work → test and outcome.

Potential records

Customer fault descriptions, diagnostic histories, equipment details, parts selections, repair specifications, technician notes, service records, follow-up questions and test results.

What to establish

Equipment and job identifiers, the sequence of tests and interventions, whether a diagnosis was confirmed and whether the outcome was checked rather than assumed.

Example task

“What evidence supported the repair choice, which checks were performed and was the reported fault resolved?”

08

Business services and commercial operations

Enquiry → proposal → agreement → delivery → handover → invoice or renewal.

Potential records

CRM histories, proposals, service specifications, authorised contracts, delivery correspondence, project plans, action logs, handovers, invoices and support records.

What to establish

A clear case boundary, the accepted agreement or scope, changes in responsibility and permission to use client communications.

Example task

“What was agreed, what changed during delivery and which commitments are still open?”

Beyond text and spreadsheets

Where a brief needs images, audio or demonstrations.

Some research questions need a visual or time-based record of the work. We can discuss whether these formats belong in a sourcing brief and what would have to be established before a source could be considered.

Images and video

Potential examples include authorised product or inspection images, recorded process demonstrations, first-person footage and workplace or CCTV recordings. The task might involve recognising a documented state, relating a visual observation to a work record or following a sequence of actions.

Audio and conversations

Potential examples include recorded service conversations, spoken instructions or consented demonstrations. A brief would need to specify whether it needs the recording, a transcript, speaker or timing information, or links to an associated case. The capture context and any alignment with video or operational records would need to be established.

Meetings linked to the work that followed

A Teams or Zoom meeting bundle might combine original audio or video, a time-aligned transcript, shared screens, saved chat, the proposal or drawing discussed, and reviewed decisions and action items. Each component needs its own availability check; a transcript or recording link does not establish that the original media is still retrievable.

The case becomes more useful when the discussion can be linked to a Salesforce opportunity, Jira task or project change and its later outcome. A task could test whether a model extracts the agreed requirements, recognises an uncertain deadline and distinguishes a proposal from a commitment. Original statements, automated summaries and human-approved minutes should remain distinguishable.

Recording permissions and any proposed AI use need their own assessment, including people heard or shown, screen content, client confidentiality and retention. The first enquiry should describe the requirement without sending recordings.

Audiovisual installation and support records

An audiovisual business may hold room designs, signal diagrams, equipment and firmware records, commissioning tests, support tickets and call-quality or device-health logs. A case could trace an intermittent microphone fault through diagnosis, configuration change and a verified room test.

Teams Rooms or Crestron XiO Cloud telemetry may help describe equipment behaviour. It does not establish access or rights to the conversations held in the room. Meeting content and room-system records require separate inventories and permission checks.

Software demonstrations and screen recordings

Potential examples include an authorised demonstration of completing a business task in software, with the visible steps connected to a task description and outcome. Credentials, personal information, customer records and restricted software content would need specific consideration.

A useful demonstration would identify the task, application version, starting records, visible steps and final state. Where authorised logs exist, timestamps and case IDs can link actions across applications. Preserve errors, retries and unresolved steps. A narrated video or final screen should not be presented as a complete action log, and a recording does not by itself provide an environment that another model can run and reset.

Robotics-related product and task material

Potential examples include authorised robot product documentation, manuals, specifications, capability or compatibility information and demonstrations. A product catalogue is different from a robot action dataset. Requests for sensor streams, trajectories, synchronised observations or annotated physical actions would require a separate technical and sourcing assessment.

These are exploratory formats, not a claim that Maevar holds, has licensed or can currently deliver these materials. Rights to recording, people depicted or heard, locations, equipment, software and underlying content would need review. Removing names alone may not resolve the risks.

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.