Each structure is an interpretation. Its shape does not measure a market.
01 · BELOW THE VISIBLE WORLD
Read the promise. See the hidden system.
Eight original studies follow the small missing fact that changes an entire commitment. Enter a scene. Inspect the break. Follow what the evidence makes possible.
01 · THE PROMISE
The instruction with no address
Light and typography interpret the selected case. They are not live measurements.
AE / EVIDENCE STREAM
Authored fictional study · a comparison to inspect, not a report of an actual organisation.
No dedicated study is claimed for this classification. Choose one of the eight authored studies, or continue to its explicitly inherited field guidance.
Across the three occupied blocks, an apparently complete repair list still contains an unidentified door. The repair description can be detailed while its object remains uncertain.
Trace one incomplete entry through location, proposed repair, reviewer and resident access. Mark exactly which link lacks evidence; do not infer technical acceptability from a completed record.
Across the three occupied blocks, an apparently complete repair list still contains an unidentified door. The repair description can be detailed while its object remains uncertain.
The hidden break
Follow the repair description alone and the work instruction reaches an uncertain location. Resolve the register identity first and the proposal can be tied to the right door for competent review and access planning.
The evidence test
The instruction remains held at the register. The review record and access log must carry the same location reference before the route can continue.
The handover
Trace one incomplete entry through location, proposed repair, reviewer and resident access. Mark exactly which link lacks evidence; do not infer technical acceptability from a completed record.
Identity is a dependency of scope: adding detail to a repair does not identify the door.
The fictional morning rota lists support visits across a dispersed neighbourhood. Contact time fills the visible schedule; travel and handover determine whether those appointments can connect.
The hidden break
Compare a rota containing only contact minutes with the same route including travel, handover and absence cover. Delay the first visit in both versions: the second exposes which later commitments need review.
The evidence test
The travel-inclusive rota exposes an affected visit window and its escalation route. It does not establish individual clinical suitability.
The handover
Use the anonymised needs matrix to trace one delayed first visit through the route. Identify who contacts the next person and who can agree a changed arrangement.
A full calendar can conceal a missing journey. Spare minutes matter only where they can absorb the actual disruption.
The customer portal connects to another system, but the fictional assessment has a written boundary. Technical connection and authority to assess are different relationships.
The hidden break
Extend activity because a system is reachable and the agreed scope has been bypassed. Record the boundary question instead and the owner can explicitly approve or exclude the additional asset.
The evidence test
The exception log records the connected asset as outside scope; the finding register cannot imply that it was assessed.
The handover
Compare the approved asset list, exclusions and exception log. Find who may change the boundary, and keep any retest agreement separate from the initial permission.
A deliberate stop can be evidence of control. It must remain visible as untested scope rather than disappear into an assurance claim.
The early conversion design for a community building depends on missing survey information. A drawing can become more polished without becoming less provisional.
The hidden break
Treat the layout as settled and later information can reopen an apparently completed decision. Keep its survey dependency explicit and the client can distinguish design progress from an authorised stage decision.
The evidence test
The deliverables schedule shows a provisional layout; the dependency register names a survey owner and date. Any ensuing revision remains traceable to its instruction.
The handover
Trace one layout decision back to the building information it requires. Record who commissions that input, who accepts it and which fee or programme assumption needs review if it changes.
Visual completeness and decision readiness can move independently. The missing information belongs in the programme, not just in a drawing note.
The evening cleaning plan assumes a sequence through the building while part of it remains open. The occupied corridor is a shared dependency between cleaning and continued use.
The hidden break
Keep the assumed wet-floor sequence and the occupied route blocks it. Agree another access window and the task can be rescheduled with its drying and inspection steps still visible.
The evidence test
The access plan exposes the conflicting area and moves its task window. The inspection log still needs to show completion and any correction.
The handover
Compare actual opening hours with one area-and-task entry. Trace access, work, drying and inspection, then identify who can agree the revised window.
Area alone does not describe the job. The same corridor at another time can require a different sequence without changing its size.
The fictional collection joins inconsistent waste descriptions to a planned receiving route. An unexpected contaminant reveals that a booked collection and an acceptable destination are separate commitments.
The hidden break
Continue with the original destination despite the disputed stream and the receiving assumption remains unresolved. Clarify the description and acceptance first, then obtain approval for any changed destination and charge.
The evidence test
The stream register, receiving details and exception record must agree on the revised route; an unexplained destination change leaves the chain incomplete.
The handover
Follow the disputed stream from its site description to acceptance and transfer evidence. Identify who owns rejection handling and who can approve an alternative route and price.
Transport completion does not close the promise if the receiving end cannot accept the load. Custody evidence must follow the exception as well as the normal route.
Stream description → acceptance → transfer → exception ownership
England and Wales context; no German waste-law equivalence is asserted.
The fictional school journey serves pupils with different assistance needs. A replacement vehicle can match the seat count while leaving access, assistance or handover requirements unresolved.
The hidden break
Approve substitution by seats alone and important journey requirements have not been checked. Compare the replacement with the agreed needs and handover plan, then seek agreement on any changed arrangement.
The evidence test
The substitution check exposes the unresolved requirement before it becomes a route instruction. Personal records remain unpublished.
The handover
Use an anonymised journey-needs entry to compare vehicle access, assistance, timing and school/family handover. Record which requirement prevents immediate agreement.
Capacity is multidimensional. An equal count can conceal a different service when the journey depends on access and personal assistance.
The fictional learning-support programme overlaps with existing provision. Both schedules can name an activity while neither makes its working responsibility clear.
The hidden break
Add support hours without resolving the overlap and responsibility remains ambiguous. Agree the activity owner with the learner, family and setting, then align the timetable and review route.
The evidence test
The activity-and-needs map identifies one accountable arrangement for the overlap, with a named review route when needs change. It makes no learning-outcome guarantee.
The handover
Trace one overlapping activity through purpose, existing provision, proposed staffing and review. Ask who acts, who coordinates and how the learner and family can influence a change.
Duplication in a timetable can coexist with a gap in accountability. More scheduled input does not by itself clarify what the support is for.
Derived from the eight retained preparation cases. Existing case jurisdiction and specialist limitations continue to apply. Consequences describe the teaching model, not measured outcomes.
02 · CHOOSE YOUR WORLD
Ten ways to carry a promise.
Buildings, care, ideas, systems and journeys ask different things of the people who deliver them. Choose a world. Then come closer to the actual work.
An original moving study · change the world above
Built worlds
A joint carries the whole promise.
Section-cut architecture
Refine the field
Loading the independent field directory…
AUTHORED ILLUSTRATIVE CASE
Fire doors
One fictional preparation problem. Its context source and limits remain visible.
desk:fire-doorsRead this world’s field notes ↓120 working territories · 1,838 specialist fields · independently maintained here.
THE WORK BENEATH THE SURFACE · AUTHORED FAMILY LENS
A drawing can define an object without defining the complete purchase. Separate the asset, site conditions, interfaces and acceptance criteria before turning a specification into a price or programme.
Follow one detail from design responsibility into installation and handover. Record who checks compatibility, which inspection is required and what the receiving team needs to operate or maintain the result.
A sole specialist may need an external survey; a large contractor may still lack authority over a subcontracted interface. Headcount does not close either gap.
Inspect classification and original labels
Working territories are editorial groupings. Official CPV hierarchy is shown separately when a purchasing field is selected.
England SEND framework; the example creates no German legal entitlement.
04 · OPEN THE RECORD
The artwork opens a world. The record keeps it honest.
Inspect a retained public notice beside your selected lens. Classification and text matches explain a possible connection; they do not establish suitability.
Retained market snapshot: 2026-11-14T21:16:43.010375+00:00. Processing and source dates remain separate.
Snapshot observations appear when retained records load.
Retained source records also remain available in the Market Observatory.
Covered public notices only. Missing private-market information stays unknown. Closed and award-stage records are never relabelled as open opportunities.
05 · THE ANATOMY OF THE WORK
Open the system. Follow the evidence.
Go beyond a product name. Examine what enters a technology, how it processes information, who works with it and what still needs human judgement.
120 working territories4,190 selectable CPV codes30 working patterns20 technology anatomies
YOUR SELECTED FIELD
Fire doors
Authored working-territory application. Check the actual specification; this is not a record of technology adoption.
desk:fire-doors
Every selection has an explicit mapping. Some are inherited from a reviewed classification ancestor or a working territory. That coverage does not mean every niche has its own researched adoption study.
Technology choice follows the task, available people and authority to approve the result.
AN AUTHORED APPLICATION · NOT OBSERVED ADOPTION
Inspection to remedial scope
Translate asset findings into traceable proposed remedial work.
INPUT
Asset IDs, findings and acceptance criteria
Inspection dates, inspector competence and instrument checks
Site access restrictions and evidence photographs
PROCESS
Associate findings with assets and route uncertain diagnoses.
Compare each finding with the applicable criterion and distinguish observed defects from suspected causes.
Separate confirmed remedial quantities from items needing further survey; retain exclusions in the priced scope.
OUTPUT
Remedial schedule with unresolved exceptions
Further-survey and access dependency list
Approval, failure points and applicability
A competent person approves the diagnosis and scope.
A finding is attached to the wrong asset.
The scope calls for this output: Remedial schedule with unresolved exceptions. Required starting evidence: Asset IDs, findings and acceptance criteria.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Source→Processing→Candidate result→Human approval
Select a field to inspect its relevant technology mechanisms. The complete anatomy library remains readable below.
Open the complete technology anatomy library
TECHNOLOGY ANATOMY
Response libraries
A governed collection of reusable answers and supporting evidence.
How it works and where it is used
Information entering the system
Approved answers, evidence, expiry dates and permissions.
Store each answer with an owner, topic and review date.
Search for content matching the buyer’s question and context.
Assign gaps to specialists and approve a tailored response.
The result
A traceable first response and review tasks.
Suitable-use inference: repeated RFPs, supplier questionnaires and due diligence.
Who has documented use?
Aspen Medical · Loopio
Failure boundary and human review
A reusable answer can be accurate yet irrelevant to this contract.
The subject owner checks applicability, currency and evidence.
Evidence notes
Loopio · Proposal response library and workflow — Aspen Medical · Undated historical case; checked 2026-11-14
Official case study describes a global business-development team using shared RFP content and cross-specialist collaboration.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
Drafting from trusted content, assignments, notifications, deadlines, CRM integration; current vendor feature claims.
Product documentation describes capability, not adoption by every named customer. Preserve version and scope distinctions.
TECHNOLOGY ANATOMY
Generative assistance and retrieval
A language model drafts from instructions; retrieval-augmented generation adds selected source passages. This is a representative mechanism, not a claim about a vendor’s internal architecture.
How it works and where it is used
Information entering the system
Question, approved documents, access rules and review criteria.
Split approved documents into meaningful passages, keeping source, revision and access metadata.
Retrieve relevant passages using text or vector search, filtering by the requester’s permissions.
Give retrieved passages and the question to the model; attach verifiable source references to claims.
Review each claim against its cited passage and requirement before export.
The result
A proposed answer, references and unresolved gaps.
Suitable-use inference: evidence-based drafting across proposal and assurance teams. A general AI chat does not automatically supply response-library ownership, approval workflow, deadlines or audit history; a response platform may combine these with AI.
Who has documented use?
PCBB · Drata AI Questionnaire · Pilot only; no claim that this proves a particular RAG architecture.
Failure boundary and human review
Retrieval can miss evidence; a citation can be irrelevant; generated text can exceed what its source supports.
A competent reviewer verifies claims, permissions and contract-specific promises.
Customer-location-asset-request-quote-work-order model. New service module must not be inferred for older named users.
Product documentation describes capability, not adoption by every named customer. Preserve version and scope distinctions.
MaintainX · CMMS and service work management — Cintas; Duracell · 2025-07-15 displayed page date
Official 2025 press release names both customers: Cintas discusses maintenance insights; Duracell discusses parts/equipment evaluation. This is vendor-reported evidence.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
TECHNOLOGY ANATOMY
Product and batch traceability
A chain of identifiers linking materials, batches and handling events.
How it works and where it is used
Information entering the system
Lot identifiers, supplier records and transaction events.
Assign identifiers to items, lots and relevant certificates.
Record receipt, transformation and dispatch relationships.
Query affected lots when a defect or recall is investigated.
The result
Provenance chains and affected-product lists.
Suitable-use inference: food distribution, medical supplies and component manufacturing.
Who has documented use?
No organisation-specific adoption example is retained for this class. Its mechanism is presented as a reference pattern.
Failure boundary and human review
A barcode identifies a record; it does not certify product quality or authenticity.
Quality staff verify chain completeness and release decisions.
Evidence notes
TECHNOLOGY ANATOMY
Care and clinical records
Structured records support continuity by connecting plans, observations and review.
How it works and where it is used
Information entering the system
Agreed care information, observations and staff permissions.
Identify the person and authorised access context.
Record plans and observations with author and time.
Review changes and escalate concerns through the agreed route.
The result
A shared record and review history.
Documented example: residential care planning; broader clinical use requires its own evidence.
Who has documented use?
Orchard Care Homes · PCS mCare
Failure boundary and human review
An entry does not prove the action occurred or replace professional assessment.
Qualified staff check accuracy and required care decisions.
Evidence notes
PCS · Digital care planning — Orchard Care Homes · 2024-08-21; updated 2026-07-02
Official case study records a 2017 trial and subsequent use across the care-home organisation.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
TECHNOLOGY ANATOMY
Care rostering and visit planning
A constrained schedule connects care needs with staff capacity and travel.
How it works and where it is used
Information entering the system
Visit needs, skills, availability and journey times.
Define visit windows, skills and continuity requirements.
Allocate staff while including travel, breaks and cover.
Test disruption and route changes before confirming visits.
The result
A deliverable rota and exception list.
Suitable-use inference: domiciliary support and mobile community services.
Who has documented use?
No organisation-specific adoption example is retained for this class. Its mechanism is presented as a reference pattern.
Failure boundary and human review
Optimising contact minutes alone can hide travel and continuity failures.
The care coordinator checks individual agreements and safe cover.
Evidence notes
TECHNOLOGY ANATOMY
Security evidence and assurance
A controlled process for gathering and reviewing security claims.
How it works and where it is used
Information entering the system
Security questions, approved documents and access rules.
Map requested controls to current policies and evidence.
Draft answers using the question and any additional instructions.
Review exceptions and disclose only authorised evidence.
The result
Reviewed assurance answers and unresolved control gaps.
Suitable-use inference: software procurement and supplier due diligence.
Who has documented use?
PCBB · Drata AI Questionnaire · Pilot.
Failure boundary and human review
An automated answer does not establish that a control is operating effectively.
A security owner confirms the actual control and disclosure boundary.
Product documentation describes capability, not adoption by every named customer. Preserve version and scope distinctions.
Inspire Brands · Maverick Studios · The Vault digital asset management · Historical account mentioning June 2024; retrieved 2026-11-14
Maverick Studios describes The Vault, built on Bynder, as a shared media library with version, rights and usage controls for brands, agencies and production partners.
The organisation’s own deployment account. It does not establish independent performance results or adoption by other creative organisations.
TECHNOLOGY ANATOMY
Learning and training records
A platform connects course content, assigned activities and learner records.
How it works and where it is used
Information entering the system
Courses, assignments, learner identities and assessment rules.
Assign relevant content to learners or study roles.
Deliver activities and capture submissions or completion.
Review assessment and overdue training records.
The result
Learning histories, submissions and completion reports.
Documented examples: university teaching and clinical-study staff training.
Who has documented use?
Nepal Open University · Moodle
Bayer · Veeva Vault Study Training
Failure boundary and human review
A completion flag does not independently demonstrate competence.
Educators or training owners verify suitability and assessment.
Evidence notes
Moodle · Learning management and remote delivery — Nepal Open University · 2019-12 source path
Official case study states Moodle was its official LMS for academic programmes, integrated with Teams/Office 365 and external laboratory software.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
Veeva · Clinical trial content and training — Bayer · 2024-11 source path
2020 announcement selected Study Startup and eTMF globally. 2024 study-training case reported 42 studies in 50 countries; site-training subset was 11 studies, about 10,000 users and 1,000 sites in 37 countries.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
TECHNOLOGY ANATOMY
Research data management
A documented chain from collected observations to reusable research datasets.
How it works and where it is used
Information entering the system
Observations, protocols, metadata and access restrictions.
Define formats, identifiers, consent and collection methods.
Store versions with metadata and validation checks.
Prepare a governed archive or sharing package.
The result
A documented dataset and reproducibility information.
Suitable-use inference: laboratory, survey and commissioned research.
Who has documented use?
No organisation-specific adoption example is retained for this class. Its mechanism is presented as a reference pattern.
Failure boundary and human review
A managed dataset does not guarantee valid methods or reproducible conclusions.
Researchers check provenance, ethics and release conditions.
Evidence notes
TECHNOLOGY ANATOMY
Route optimisation
A model searches for a feasible sequence of stops under operating constraints.
How it works and where it is used
Information entering the system
Addresses, constraints, travel estimates and capacity.
Enter stops, time windows, vehicle limits and service durations.
Calculate candidate routes against an explicit objective.
Check access and disruption before assigning the route.
The result
Proposed routes, timings and infeasible stops.
Suitable-use inference: deliveries, waste rounds and mobile maintenance.
Who has documented use?
No organisation-specific adoption example is retained for this class. Its mechanism is presented as a reference pattern.
Failure boundary and human review
A mathematically short route may violate real access or working conditions.
Dispatchers confirm feasibility with operational knowledge.
Evidence notes
TECHNOLOGY ANATOMY
Telemetry and fleet signals
Connected devices send time-stamped operational observations to a platform.
How it works and where it is used
Information entering the system
Gateway observations, vehicle identity and inspection reports.
Install and associate gateways with the correct vehicle or asset.
Transmit and organise observations in operational dashboards.
Review alerts and connect defects to maintenance follow-up.
The result
Operational trends, alerts and maintenance context.
Documented example: school transport fleet safety and maintenance communication.
Who has documented use?
Birmingham City Schools · Samsara
Failure boundary and human review
Coverage gaps, sensor errors and context can change interpretation.
Fleet staff validate alerts and agree appropriate action.
Evidence notes
Samsara · Fleet telematics and inspection — Birmingham City Schools · Story contains February 2020 metrics; checked 2026-11-14
Official customer story reports gateway installation, driver safety scoring and electronic inspection reports in its school transport fleet.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
TECHNOLOGY ANATOMY
Case management
A shared record connects intake, support activity and case progression.
How it works and where it is used
Information entering the system
Client information, referrals, assessments and permission rules.
Capture intake and establish authorised handling.
Connect relevant notes, referrals and planned actions.
Review progress and record decisions or closure.
The result
A case history and accountable next actions.
Documented example: UK debt advice delivered with partner churches.
Who has documented use?
Christians Against Poverty · Salesforce Nonprofit Cloud and Experience Cloud
Failure boundary and human review
More complete records do not by themselves establish better client outcomes.
The case owner checks accuracy, consent and appropriate next steps.
Evidence notes
Salesforce · Human-services case management — Christians Against Poverty · Undated; checked 2026-11-14
Official story documents Nonprofit Cloud and Experience Cloud for UK debt-advice case management through partner churches. Proposed AI uses are future interest, not documented adoption.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
Legacy managed-package architecture uses Accounts/Contacts/Cases plus Case Plans/Notes/Assessments; avoid silently equating with newer Nonprofit Cloud.
Product documentation describes capability, not adoption by every named customer. Preserve version and scope distinctions.
TECHNOLOGY ANATOMY
Financial modelling
A transparent calculation of costs, revenue, cash timing and uncertainty.
How it works and where it is used
Information entering the system
Cost and revenue drivers, payment terms and scenario assumptions.
Separate assumptions, source data and calculation logic.
Model volumes, rates, timing and dependencies.
Test scenarios and reconcile totals to the proposed offer.
The result
Price, margin and cash-flow scenarios.
Suitable-use inference: service pricing, investment appraisal and contract affordability.
Who has documented use?
No organisation-specific adoption example is retained for this class. Its mechanism is presented as a reference pattern.
Failure boundary and human review
Numerical precision cannot remove uncertain demand or unsupported assumptions.
Finance and commercial owners approve assumptions and exposure.
Evidence notes
TECHNOLOGY ANATOMY
Document control
A controlled lifecycle for creating, reviewing, issuing and retaining documents.
How it works and where it is used
Information entering the system
Documents, metadata, workflow rules and retention requirements.
Register document identity, owner, version and intended audience.
Route changes through review and approval.
Issue the approved version and preserve superseded records.
The result
An identified issued document and change history.
Documented example: clinical trial startup and trial master files; other uses are suitability inferences.
Who has documented use?
Bayer · Veeva Vault Study Startup and eTMF · Selected globally in 2020; selection date is not completed-migration evidence.
Failure boundary and human review
A controlled document can still contain an incorrect claim.
A responsible reviewer approves content and issuance.
Evidence notes
Veeva · Veeva Startup · 2020-07-23
2020-07-23 selection announcement, not proof of completed migration on that date.
Product documentation describes capability, not adoption by every named customer. Preserve version and scope distinctions.
Veeva · Clinical trial content and training — Bayer · 2024-11 source path
2020 announcement selected Study Startup and eTMF globally. 2024 study-training case reported 42 studies in 50 countries; site-training subset was 11 studies, about 10,000 users and 1,000 sites in 37 countries.
Vendor-reported example limited to the named organisation, reported period and stated scope. No market-share or universal-adoption inference.
Read all thirty working patterns
Requirement and clarification matrix
Turn the actual request into assigned, checkable obligations.
Inputs, processing and review
Inputs
Request and amendments
Submission instructions and evaluation headings
Clarification deadlines and approval owners
Processing
Link each obligation to its source and clarification owner.
Separate mandatory conditions, requested evidence and optional statements; assign each to a named owner.
Reconcile amendments against the baseline and retain unresolved questions before approving a response.
Outputs
Versioned requirement matrix
Clarification log with due dates and decisions
Failure points
An amendment is omitted.
An optional example is mistaken for a mandatory condition.
Human review
An authorised reviewer confirms completeness.
The submission owner verifies that every mandatory item has an approved disposition.
Applicability
The scope calls for this output: Versioned requirement matrix. Required starting evidence: Request and amendments.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Controlled evidence retrieval
Find reusable evidence without treating an old answer as a current fact.
Inputs, processing and review
Inputs
Approved answers, owners and expiry dates
Permissions and confidentiality restrictions
Claim-specific scope and supporting attachments
Processing
Retrieve by requirement and check ownership, date and scope.
Compare the retrieved evidence with the current requirement; preserve qualifications rather than copying a whole answer.
Record the chosen evidence version and request renewal from its owner when the scope or validity differs.
Outputs
Evidence references with review status
Renewal queue identifying unsupported claims
Failure points
An expired claim is reused.
Access rights permit internal reading but prohibit disclosure to the buyer.
Human review
The evidence owner confirms present applicability.
An authorised information owner approves disclosure of restricted material.
Applicability
The scope calls for this output: Evidence references with review status. Required starting evidence: Approved answers, owners and expiry dates.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Source-bound draft assistance
Prepare a draft from permitted material with visible unsupported gaps.
Inputs, processing and review
Inputs
Permission-checked source extracts
Required answer structure and length limits
Approved terminology and prohibited disclosures
Processing
Draft against cited extracts and mark missing support.
Compare each generated claim with its cited extract; reject unsupported names, numbers and promised capabilities.
Route technical and commercial claims to their owners, then produce a submission copy only from approved changes.
Outputs
Draft and claim-to-source register
Unsupported-claim and disclosure review list
Failure points
A plausible statement lacks support.
Source instructions or misleading extracts contaminate the draft.
Human review
A human verifies every submitted claim and disclosure permission.
The accountable client approves the final promises; drafting access does not confer authority.
Applicability
The scope calls for this output: Draft and claim-to-source register. Required starting evidence: Permission-checked source extracts.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Do not enter confidential or personal information into an unapproved service. Draft fluency does not verify facts or authorise a promise.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Scope and cost assumptions
Connect quantities, rates and exclusions to an inspectable price.
Inputs, processing and review
Inputs
Quantities, rates and delivery assumptions
Supplier quotations with validity dates
Labour availability, overhead basis and risk allowances
Processing
Calculate with versioned assumptions and expose sensitivity.
Reconcile units, quotation dates and scope exclusions before aggregating costs.
Test volume, timing and input-price changes; route material exposure for a commercial decision.
Outputs
Estimate and assumption register
Sensitivity range and unpriced-scope list
Failure points
A missing quantity hides cost exposure.
A supplier quotation excludes an essential delivery element.
Human review
The commercial approver accepts the priced scope.
The delivery owner confirms that priced resources and sequence are feasible.
Applicability
The scope calls for this output: Estimate and assumption register. Required starting evidence: Quantities, rates and delivery assumptions.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Commitment and delivery handover
Carry approved promises and exceptions into delivery planning.
Inputs, processing and review
Inputs
Approved response and agreed exceptions
Clarification decisions and change approvals
Delivery milestones and acceptance responsibilities
Processing
Assign each commitment to a delivery owner and acceptance record.
Compare the approved response with the contract and identify changed or unresolved commitments.
Obtain explicit acceptance from each delivery owner and preserve the route for subsequent controlled changes.
Outputs
Controlled handover baseline
Commitment-to-owner and acceptance register
Failure points
An unapproved draft becomes an instruction.
An exception disappears between bid approval and contract mobilisation.
Human review
Delivery and commercial owners approve the baseline.
The contract owner resolves differences between the response and signed terms.
Applicability
The scope calls for this output: Controlled handover baseline. Required starting evidence: Approved response and agreed exceptions.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Inspection to remedial scope
Translate asset findings into traceable proposed remedial work.
Inputs, processing and review
Inputs
Asset IDs, findings and acceptance criteria
Inspection dates, inspector competence and instrument checks
Site access restrictions and evidence photographs
Processing
Associate findings with assets and route uncertain diagnoses.
Compare each finding with the applicable criterion and distinguish observed defects from suspected causes.
Separate confirmed remedial quantities from items needing further survey; retain exclusions in the priced scope.
Outputs
Remedial schedule with unresolved exceptions
Further-survey and access dependency list
Failure points
A finding is attached to the wrong asset.
A photograph is used to assert a condition outside the inspected area.
Human review
A competent person approves the diagnosis and scope.
A scope approver accepts further-survey needs before a fixed commitment is made.
Applicability
The scope calls for this output: Remedial schedule with unresolved exceptions. Required starting evidence: Asset IDs, findings and acceptance criteria.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Drawing and model coordination
Resolve design interfaces against a controlled information baseline.
Inputs, processing and review
Inputs
Models, drawings and information requirements
Model revision identifiers and responsibility matrix
Survey tolerances and discipline interface requirements
Processing
Compare revisions, record clashes and allocate decisions.
Test whether an apparent clash is geometrical, informational or a responsibility gap; assign resolution to the correct discipline.
Publish only approved revisions to the shared baseline and notify dependent estimating or construction work.
Outputs
Coordinated issue and decision register
Approved revision and downstream-change list
Failure points
A superseded model drives quantities.
Conflicting coordinate systems produce false clashes.
Human review
The responsible designer approves changes.
The information manager verifies revision and distribution control.
Applicability
The scope calls for this output: Coordinated issue and decision register. Required starting evidence: Models, drawings and information requirements.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Do not assume every building-related purchase includes model authoring, design responsibility or access to a common data environment.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Planned and reactive maintenance
Plan work around asset condition, access and service continuity.
Inputs, processing and review
Inputs
Asset history, work requests and access constraints
Service priorities and permitted interruption windows
Parts availability and required worker competence
Processing
Prioritise work, assign resources and record completion evidence.
Check whether priority, parts and access permit the proposed visit; expose dependencies instead of silently rescheduling.
Capture work performed, measured results and outstanding defects against the same asset before closing the job.
Outputs
Work programme and asset history
Deferred-work and unavailable-parts register
Failure points
Closure is recorded without proof of completion.
A completed visit is confused with restoration of service.
Human review
A responsible supervisor accepts completion and exceptions.
The service owner approves deferrals and residual operational risk.
Applicability
The scope calls for this output: Work programme and asset history. Required starting evidence: Asset history, work requests and access constraints.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Location and asset planning
Use location evidence to examine coverage and site interfaces.
Inputs, processing and review
Inputs
Georeferenced assets, boundaries and survey dates
Layer licences and survey precision
Coordinate reference systems and site access permissions
Processing
Overlay verified layers and identify conflicts and gaps.
Normalise coordinate systems and retain each layer's age and precision before measuring distances or coverage.
Export identified constraints with coordinates and uncertainty so a site team can verify them.
Outputs
Mapped constraints and survey questions
Field verification schedule with uncertainty notes
Failure points
An outdated boundary is treated as authoritative.
A low-resolution layer supports an unjustified precise location claim.
Human review
A competent owner verifies critical locations and permissions.
The site owner confirms access and any necessary field verification.
Applicability
The scope calls for this output: Mapped constraints and survey questions. Required starting evidence: Georeferenced assets, boundaries and survey dates.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Product specification and equivalence
Compare offered products with the documented intended use.
Inputs, processing and review
Inputs
Specifications, technical sheets and permitted alternatives
Required certificates and permitted evidence formats
Installation interfaces, operating conditions and exclusions
Processing
Compare attributes and expose missing conformity evidence.
Map each proposed model and revision to required attributes; leave missing attributes explicitly unresolved.
Separate confirmed matches from proposed alternatives and obtain approval before pricing them as compliant.
Outputs
Product compliance and exception schedule
Alternative-product and missing-evidence register
Failure points
A similar name masks a different specification.
A certificate covers another model or operating condition.
Human review
The technical approver accepts any claimed equivalence.
The buyer or designated authority approves substitutions where required.
Applicability
The scope calls for this output: Product compliance and exception schedule. Required starting evidence: Specifications, technical sheets and permitted alternatives.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
An equivalent-looking product is not automatically approved. Do not infer installation, clinical or maintenance responsibility from goods classification.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Batch and product traceability
Keep identity and custody evidence through product handling.
Inputs, processing and review
Inputs
Batch IDs, certificates and custody events
Storage conditions and expiry or release status
Supplier identities and recall contact routes
Processing
Link receipts, transformations and dispatches by controlled identifiers.
Check identifier continuity at each handover and quarantine entries whose identity, condition or status cannot be reconciled.
Produce a backwards and forwards trace showing affected inputs, outputs and recipients for a selected batch.
Outputs
Traceability record and exception list
Quarantine and recall action register
Failure points
A relabelled item breaks the custody chain.
A recorded batch is dispatched after its release status changes.
Human review
The quality owner verifies release and recall arrangements.
An authorised quality lead approves release of quarantined items.
Applicability
The scope calls for this output: Traceability record and exception list. Required starting evidence: Batch IDs, certificates and custody events.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Production and material planning
Test whether materials and production capacity support the promised output.
Inputs, processing and review
Inputs
Bill of materials, lead times and production capacity
Process yields and inspection hold points
Supplier commitments and machine changeover constraints
Processing
Reconcile material needs with availability and process dependencies.
Calculate material and process-stage demand using verified yields and setup times; identify the limiting resource.
Sequence feasible production lots and hold unverified capacity or materials outside the firm delivery promise.
Outputs
Production plan with shortages and assumptions
Bottleneck and material-shortage register
Failure points
An unconfirmed lead time becomes a promise.
Nominal machine capacity ignores changeover and quality losses.
Human review
Production and procurement owners approve feasibility.
The quality owner accepts inspection hold points before schedule release.
Applicability
The scope calls for this output: Production plan with shortages and assumptions. Required starting evidence: Bill of materials, lead times and production capacity.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Stock and fulfilment control
Connect available stock to agreed quantities and delivery windows.
Inputs, processing and review
Inputs
Stock positions, orders and delivery constraints
Supplier replenishment dates and allocation priorities
Packaging, handling and receipt requirements
Processing
Reserve stock, reconcile substitutions and record dispatch exceptions.
Distinguish available, reserved and incoming quantities; flag commitments that rely on unconfirmed replenishment.
Record picking and dispatch against the order, then reconcile shortages and receipt discrepancies.
Outputs
Fulfilment schedule and exception record
Stock-allocation and receipt reconciliation
Failure points
The same stock is committed twice.
An incoming replenishment is counted as usable stock before receipt checks.
Human review
The fulfilment owner authorises substitutions and commitments.
A receiving owner confirms acceptance or records the discrepancy.
Applicability
The scope calls for this output: Fulfilment schedule and exception record. Required starting evidence: Stock positions, orders and delivery constraints.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Journey and resource planning
Plan feasible journeys around real time and assistance constraints.
Inputs, processing and review
Inputs
Stops, time windows, vehicle limits and assistance needs
Driver availability, duty limits and competence
Travel-time assumptions and emergency contact arrangements
Processing
Calculate candidate routes and check capacity and contingency.
Check stop order against realistic travel time, boarding duration and individual assistance needs.
Present infeasible journeys and required trade-offs to the planner; preserve contingency for late or unavailable vehicles.
Outputs
Reviewed route and resource plan
Uncovered-journey and contingency register
Failure points
A short route ignores a passenger requirement.
An optimisation uses average travel times that cannot meet a fixed appointment.
Human review
A transport planner approves safety and service suitability.
The service coordinator confirms passenger arrangements and exception escalation.
Applicability
The scope calls for this output: Reviewed route and resource plan. Required starting evidence: Stops, time windows, vehicle limits and assistance needs.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Measurement and condition exceptions
Turn validated measurements into reviewable operational exceptions.
Inputs, processing and review
Inputs
Timestamped sensor readings and calibration records
Sensor identifiers, units and expected sampling intervals
Operational baselines and alert ownership
Processing
Validate units and missingness before comparing agreed thresholds.
Distinguish genuine threshold breaches from stale readings, calibration issues and communications gaps.
Send qualified exceptions with supporting measurements to the named operator and record acknowledgement.
Outputs
Condition report with data-quality flags
Measurement-quality and alert acknowledgement log
Failure points
Sensor drift appears as genuine deterioration.
Missing readings are displayed as normal operating conditions.
Human review
An operator confirms any intervention and safe operating decision.
A competent engineer approves threshold changes and calibration actions.
Applicability
The scope calls for this output: Condition report with data-quality flags. Required starting evidence: Timestamped sensor readings and calibration records.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Waste classification and custody
Preserve the documented identity and movement of waste streams.
Inputs, processing and review
Inputs
Waste descriptions, analysis and transfer records
Carrier, destination and acceptance information
Quantity measurements and sampling limitations
Processing
Reconcile descriptions and flag uncertain classification before transfer.
Check whether the receiving facility accepts the documented stream and retain uncertain descriptions for competent review.
Reconcile collection and receipt quantities and preserve discrepancies across the custody chain.
Outputs
Stream register and transfer evidence
Quantity discrepancy and rejected-load register
Failure points
An uncertain description is accepted as a verified class.
An approved destination is assumed suitable for every waste stream.
Human review
A competent responsible person confirms classification and routing.
The receiving or transfer owner confirms acceptance and rejected-load handling.
Applicability
The scope calls for this output: Stream register and transfer evidence. Required starting evidence: Waste descriptions, analysis and transfer records.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Do not assign a legal waste classification from a product name or CPV label; uncertain streams require competent assessment.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Care scheduling and continuity
Check whether authorised care needs can be covered consistently.
Inputs, processing and review
Inputs
Authorised needs, staff availability and competence records
Travel allowances and individual continuity preferences
Escalation contacts and authorised cover arrangements
Processing
Match availability and competence while exposing uncovered visits.
Check travel and visit duration as well as skill match; expose overlaps and unavailable cover.
Route uncovered or changed visits to the care manager and record an agreed continuity response.
Outputs
Reviewed roster and escalation list
Uncovered-care and continuity action register
Failure points
A filled slot conceals missing competence.
A feasible schedule disregards a person's agreed support arrangement.
Human review
A qualified care manager approves suitability and continuity.
A responsible practitioner approves material changes to individual support.
Applicability
The scope calls for this output: Reviewed roster and escalation list. Required starting evidence: Authorised needs, staff availability and competence records.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Not automatically applicable to medical devices, medicines, laboratory equipment or generic staff supply. A roster does not establish safe care.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Referral and service coordination
Track an authorised request across service boundaries.
Inputs, processing and review
Inputs
Referral criteria, permissions and receiving-team contacts
Information-sharing permissions and minimum required fields
Acknowledgement deadlines and escalation criteria
Processing
Record eligibility decisions and explicit acceptance of handover.
Check the receiving service's requirements and share only authorised information needed for the decision.
Track acceptance, rejection and missing information separately; escalate when acknowledgement or action is overdue.
Outputs
Referral status and unresolved dependencies
Acknowledgement and consent exception register
Failure points
A sent referral is assumed to have been accepted.
Information crosses a service boundary without the necessary permission.
Human review
The responsible practitioner approves eligibility and escalation.
The receiving service confirms ownership of the next action.
Applicability
The scope calls for this output: Referral status and unresolved dependencies. Required starting evidence: Referral criteria, permissions and receiving-team contacts.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Clinical evidence and record handling
Organise authorised clinical evidence without replacing professional judgement.
Inputs, processing and review
Inputs
Approved clinical records and access rules
Record timestamps and provenance of amendments
Purpose-limited disclosure permissions
Processing
Associate records with verified identities and retain provenance.
Check identity, version and authorship before assembling evidence; separate recorded observations from interpretation.
Limit the output to the approved purpose and retain an audit of access, corrections and disclosure.
Outputs
Controlled clinical evidence bundle
Access and disclosure audit with correction requests
Failure points
A record is associated with the wrong person.
An outdated note is presented without its later correction.
Human review
An authorised clinician verifies interpretation and disclosure.
The information owner confirms necessity and lawful authorised access.
Applicability
The scope calls for this output: Controlled clinical evidence bundle. Required starting evidence: Approved clinical records and access rules.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Not a tool for diagnosis, treatment selection or disclosure of patient information into a bid. Product-only purchases do not inherit clinical record handling.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Research data and reproducibility
Keep methods, datasets and analytical changes inspectable.
Inputs, processing and review
Inputs
Protocols, datasets and consent or reuse permissions
Analysis code versions and instrument calibration
Data dictionaries and uncertainty assumptions
Processing
Version transformations and retain links to original observations.
Apply documented validation and transformation steps while retaining excluded records and reasons.
Re-run the analysis from retained inputs and report sensitivity, missing data and reproducibility limits.
Outputs
Reproducible analysis package with limitations
Method deviation and uncertainty register
Failure points
An undocumented transformation changes the result.
A reused dataset exceeds its consent or licence scope.
Human review
The research lead approves methods, ethics and interpretation.
A data steward approves access and reuse conditions.
Applicability
The scope calls for this output: Reproducible analysis package with limitations. Required starting evidence: Protocols, datasets and consent or reuse permissions.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Do not infer research ethics approval, consent, clinical validity or permission to reuse a dataset from its availability.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Case and matter control
Keep decisions, deadlines and authorised actions attached to the right matter.
Inputs, processing and review
Inputs
Case records, instructions and deadlines
Confidentiality boundaries and conflict checks
Decision authority and escalation thresholds
Processing
Allocate actions and retain the evidence behind each decision.
Distinguish reported facts, verified evidence and professional opinion before setting the next action.
Track deadlines and authorised instructions, escalating missing evidence instead of closing an unresolved matter.
Outputs
Matter history and outstanding action register
Deadline and authority exception register
Failure points
An automated status hides a missed deadline.
Information from one matter is disclosed in another.
Human review
An authorised professional approves consequential decisions.
The matter owner verifies confidentiality and conflict handling.
Applicability
The scope calls for this output: Matter history and outstanding action register. Required starting evidence: Case records, instructions and deadlines.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Financial modelling and reconciliation
Make financial assumptions and reconciliations inspectable.
Inputs, processing and review
Inputs
Source figures, periods and calculation assumptions
Currency, tax and accounting treatment
Scenario assumptions and approval thresholds
Processing
Reconcile inputs, expose formulas and test scenarios.
Separate source figures from calculated values; check units, dates and accounting treatment before comparison.
Produce scenario changes without overwriting the base case and reconcile the result to retained sources.
Outputs
Reviewed financial model and reconciliation log
Scenario and unreconciled-item register
Failure points
A period mismatch produces a misleading total.
A hard-coded override bypasses the visible model assumptions.
Human review
The financial owner approves assumptions and use.
An independent reviewer checks material formulas and unexplained differences.
Applicability
The scope calls for this output: Reviewed financial model and reconciliation log. Required starting evidence: Source figures, periods and calculation assumptions.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Workforce and credential planning
Check availability and evidenced competence before assigning work.
Inputs, processing and review
Inputs
Availability, role needs and dated credentials
Working-time constraints and location requirements
Subcontractor commitments and verification permissions
Processing
Match requirements to verified records and flag expiry gaps.
Check credential scope, expiry and relevance rather than treating any recorded certificate as sufficient.
Resolve overlaps and unverified availability before presenting a named-resource commitment.
Outputs
Resource plan and credential exceptions
Uncovered-role and renewal schedule
Failure points
A qualification is mistaken for current availability.
The same specialist is promised to overlapping assignments.
Human review
The responsible employer verifies appointment and competence.
The named person or resource owner confirms actual availability.
Applicability
The scope calls for this output: Resource plan and credential exceptions. Required starting evidence: Availability, role needs and dated credentials.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Software requirements and testing
Trace agreed software behaviour through implementation and acceptance.
Inputs, processing and review
Inputs
Requirements, interfaces and test environments
Versioned source changes and dependency inventory
Acceptance criteria and known defect records
Processing
Link changes to tests and record unresolved defects.
Exercise normal, failure and permission boundaries in the agreed environment and retain actual results.
Compare achieved behaviour with acceptance criteria and release only with an explicit residual-defect decision.
Outputs
Test evidence and release decision record
Defect and dependency exception register
Failure points
Passing tests omit a critical user need.
A staging pass is treated as proof of production configuration.
Human review
The service owner approves residual defects and release.
An authorised technical reviewer verifies release configuration and rollback readiness.
Applicability
The scope calls for this output: Test evidence and release decision record. Required starting evidence: Requirements, interfaces and test environments.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Security evidence and vulnerability triage
Assess verified findings within an explicitly authorised boundary.
Inputs, processing and review
Inputs
Authorised scope, asset list and findings
Permitted testing methods and system-owner contacts
Evidence timestamps and remediation responsibilities
Processing
Validate findings, assess impact and route remediation priorities.
Deduplicate findings and verify affected versions and exposure; retain uncertainty where exploitation is untested.
Assign fixes and retest within the authorised boundary before changing the finding's closure status.
Outputs
Reviewed finding register and remediation evidence
Authorised-scope and retest record
Failure points
An unverified scan becomes a compliance claim.
A finding is closed because a patch was scheduled rather than verified.
Human review
A security owner approves scope, risk decisions and closure.
The system owner authorises any disruptive testing or production change.
Applicability
The scope calls for this output: Reviewed finding register and remediation evidence. Required starting evidence: Authorised scope, asset list and findings.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Testing requires explicit authorisation. A product purchase alone does not authorise scanning or establish supplier compliance.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Data integration and reporting
Build a traceable report from defined source data.
Inputs, processing and review
Inputs
Source datasets, definitions and refresh times
Join keys, coverage limits and access permissions
Reporting period and aggregation definitions
Processing
Validate joins and units, reconcile totals and expose missingness.
Measure unmatched and duplicate records before aggregation; keep exclusions visible in the report lineage.
Reconcile report totals with source totals and label freshness and partial coverage before distribution.
Outputs
Report with lineage and quality caveats
Data-quality and unmatched-record report
Failure points
A join duplicates records and inflates totals.
Different metric definitions are merged into one misleading trend.
Human review
The data owner approves definitions and interpretation.
The report owner approves audience access and publication caveats.
Applicability
The scope calls for this output: Report with lineage and quality caveats. Required starting evidence: Source datasets, definitions and refresh times.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Controlled creative production
Keep briefs, usage rights and approved assets connected.
Inputs, processing and review
Inputs
Brief, source assets and rights records
Output dimensions, channels and accessibility requirements
Named review stages and publication deadlines
Processing
Version assets and route proofs through named approval stages.
Check source rights and adaptation limits before creating derivatives; retain the asset lineage.
Render channel-specific proofs, reconcile review comments and lock the approved publication version.
Outputs
Approved production assets and rights record
Proof decision and channel-version register
Failure points
An unlicensed or superseded asset is published.
An approved proof is altered during channel resizing.
Human review
The client and rights owner approve publication.
The production owner checks final rendering against the approved proof.
Applicability
The scope calls for this output: Approved production assets and rights record. Required starting evidence: Brief, source assets and rights records.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Accessible publishing and language review
Check meaning, access and format against the actual audience and brief.
Inputs, processing and review
Inputs
Source text, audience needs and format requirements
Approved glossary and source version
Test environments and representative access needs
Processing
Review terminology, structure and assistive-technology behaviour.
Compare critical terms and obligations with the source, recording ambiguous meaning for clarification.
Test the delivered format with relevant assistive technology and review reading order and alternative content.
Outputs
Reviewed accessible language or publication package
Terminology and accessibility issue register
Failure points
Fluent wording changes a material obligation.
A tagged document has an unusable reading order.
Human review
A qualified reviewer accepts meaning and access evidence.
The content owner approves any meaning-changing revision.
Applicability
The scope calls for this output: Reviewed accessible language or publication package. Required starting evidence: Source text, audience needs and format requirements.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Automated checks and fluent translations do not establish accessibility compliance, legal equivalence or suitability for every reader.
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Learning delivery and assessment records
Connect learning objectives, participation and verified assessment.
Inputs, processing and review
Inputs
Learning objectives, learner permissions and assessment criteria
Support adjustments and assessor responsibilities
Evidence retention periods and credential requirements
Processing
Track delivery and retain evidence against agreed assessment criteria.
Distinguish participation, attempted tasks and demonstrated outcomes; retain evidence for each assessment judgement.
Route missing evidence and support needs to the educator before confirming completion or competence.
Outputs
Learning record with assessment and support gaps
Assessment moderation and support action register
Failure points
Attendance is mistaken for demonstrated competence.
An automated completion badge bypasses the agreed assessment.
Human review
The responsible educator approves assessment and support decisions.
A qualified assessor confirms evidence sufficiency and any adjustment.
Applicability
The scope calls for this output: Learning record with assessment and support gaps. Required starting evidence: Learning objectives, learner permissions and assessment criteria.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Event resources and operating plan
Coordinate an event around verified access, resources and contingency.
Inputs, processing and review
Inputs
Programme, venue constraints and supplier responsibilities
Accessibility arrangements and capacity limits
Supplier confirmations and emergency responsibilities
Processing
Reconcile schedules and record dependencies and escalation routes.
Check setup, live operation and breakdown dependencies against venue access and resource availability.
Exercise disruption scenarios and distribute the approved operating version to responsible teams.
Outputs
Approved operating schedule and contingency record
Supplier confirmation and disruption action register
Failure points
A schedule change removes a required resource.
A capacity assumption ignores access or evacuation constraints.
Human review
The event owner and competent safety leads approve operation.
The venue authority approves access, capacity and required operating conditions.
Applicability
The scope calls for this output: Approved operating schedule and contingency record. Required starting evidence: Programme, venue constraints and supplier responsibilities.
Use when the selected purchase includes this task and the listed inputs and responsible reviewer are available.
Scope limits
Classification alone does not establish this task, system ownership, adoption or suitability. Do not apply without checking the actual scope.
Named customer accounts support only the organisation, period and scope described. A documented capability, an editorial application and a deployment case are different kinds of evidence. No popularity ranking or predicted award result is implied.
06 · ORIGINAL WORK, VISIBLE BOUNDARIES
Imagination has a place. Evidence has its own.
This atlas is independently authored and maintained on AchmedEsser.com. Its reference classifications and source records retain their actual provenance.
Classification reference
120 working territories are editorial groupings. The 1,838 purchasing fields retain official CPV 2008 codes and hierarchy. No automatic SIC equivalence or universal company behaviour is implied.
Directory review: 2026-11-14. Case review: 2026-11-14.
Authored and inherited
Eight fictional cases explain specific preparation problems. Other fields use a clearly labelled family lens. A goods category never silently inherits service-specific guidance.
Observed and derived
Source titles, dates, organisations and codes come from retained records. Relevance matching is derived and inspectable. Neither reveals unpublished intentions or internal working practices.
Art and interpretation
The ten sculptures and their movements are original visual interpretations. Their size, orbit and colour do not measure market value, demand, confidence or a chance of winning.
Confirms UK use of CPV for goods/services/works, searching, planning and past-spend grouping; does not establish exact matching of the editorial sector tree
Checks distinction between economic-activity classification and procurement subjects; UK SIC 2026 is published but operational implementation is phased
Verifies reuse conditions: editorial content CC BY 4.0 with credit/change indication; system metadata CC0; logos require separate permission. Existing CPV attribution and original-label fields are retained.
Publications Office of the European Union · 2026-11-02
Official CPV labels and hierarchy: Publications Office of the European Union. German labels use the checksum-verified multilingual reference. Editorial territories, teaching cases and visual work are maintained independently by Achmed Esser.
Source changes request review and never silently rewrite guidance. Existing Observatory windows refresh bounded records; failed replacements retain their last valid data.