ArchHubBABOOMDownload

Office Task Information Delivery Plan (TIDP)

TIDP · V0.3 · Use one TIDP for each task team's appointed information production scope.

Download WordWorkbookAll standards

Office BIM Standard · Revision V0.3 · 4 November 2026 · Controlled office method / project-population template · Owner: Task-team lead

1. Purpose, scope and control#

Use one TIDP for each task team's appointed information production scope. It records the containers that team must produce, why and to what information need, who produces/checks them, their dependencies, preparation/review time and agreed exchange dates. An originator token, drawing number, RACI assignment or single finalisation date cannot provide this production commitment on its own.

This is the first explicitly versioned markdown successor to the header-only BBM-STD-TIDP.md export; that source has no issued revision number or populated deliveries. V0.1 was the first reusable method/template revision; V0.3 is the current one. A real project plan has its own TIDPID/Rnn and baseline approval. The source remains unchanged privately; client-owned form wording, branding and layout are not reused. Models, drawings, schedules, reports and controlled non-file datasets can all be information containers when their stable identity, version, scope and exchange are defined.

Plan control fieldProject copy entry / validation
TIDPID / project plan revision / baseline[task-team plan ID / Rnn / immutable baseline ID]; method V0.3 separate
Appointment / task team / discipline[appointment ID / producing team ID / scope and trade/role mapping]; an originator organisation is not a named task team
Plan prepared / independently checked / verified / approved[planner ID / independent planning checker ID / discipline lead ID / authorised task-team lead ID; dates/evidence]; no self-check substituted for independence
Requirements and responsibility baseline[EIR, confirmed BEP, detailed production responsibility matrix, LOIN IDs/revisions, naming register, authority annex]
MIDP interface[MIDPID, exact baseline/revision, LAP owner, exchange register, delivery row IDs, distribution acknowledgment]
Calendar and capacity[working days, hours/day, holidays, time zone, author/checker allocation and absences]
Formats, tools and security[native/exporter/checker/receiver full builds, exact profiles/preset hashes, authorised private locations and access test]
Approval / effective date / next review[decision evidence / date / weekly review and change trigger]

ISO 19650-2:2018 is the delivery-phase basis (still in force; ISO/DIS 19650-2 at stage 40.93 is not). IMI Framework archived Guidance F, edition 1 (September 2020), distinguishes delivery plans from responsibility matrices. ISO 7817-1:2024 defines purpose-led information need; ISO 19650-4:2022 supports exchange checks and decisions; ISO 29481-1:2025 supports describing the exchange purpose/actors; ISO 19650-5:2020 and ISO 19650-6:2025 support security-minded and health/safety information arrangements. RIBA Plan of Work 2020 stage labels inform timing; stage alone does not supply the information requirement. [S02, G-F, S07, S04, S18, S05, S06, S21]

2. Office decisions and interfaces#

Apply the single Clash Matrix V0.3, sections 2–3 O3-POL-01/02/03 policy register and the MIDP V0.3, sections 2 and 4 O3-POL-04/05 decisions. They adopt the external grammar CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext, internal Rnn revision, SU-WIP/SU-COORD/SU-INFO/SU-REVIEW/SU-ISSUE suitability and WIP/Shared/Published/Archive states. Bind actual token dictionaries, formats and appointment overrides in one project register; preserve historical IDs and do not create another tolerance/code list.

L1=2 working days, L2=2, correction/retest contingency=2, L3=1, authorisation/release=1, recipient acceptance=3 are the normal-package office planning minima. The task team estimates production time. Binding recipient periods and complex checks increase these allowances; a forecast does not authorise removing quality checks. L1 is held on each producer row; L2 onwards belongs to the coordinated MIDP package, referenced here so it is neither forgotten nor added repeatedly for every container.

Issue severity is S1 Critical/S2 Major/S3 Minor, distinct from SU suitability and responsibility labels. All applicable mandatory geometry/data/documentation must be valid, and no unresolved required hard-intersection or mandatory access/safety failure may remain in the issued scope. A 95% non-mandatory progress target never authorises missing mandatory information. Hard, clearance and access tests reference the one rule register; no automatic stage/LOD tolerance is created here.

Decision (BIM Manager, 2026-10-14): The task-team lead owns the TIDP commitment; the LAP owns the coordinated MIDP baseline; every approved delivery-row change must propagate by the same ChangeID before the affected new commitment takes effect. Basis: Separate production ownership and coordinated delivery authority with exact source-row lineage and review evidence G-F.

The task-team lead cannot change a client milestone by changing this spreadsheet. The LAP cannot silently change preparation assumptions without resource and discipline confirmation. A requirement, code, appointment or safety constraint takes precedence over a schedule shortcut. PM releases after the required technical/authorisation decisions; appointing-party acceptance remains separate.

3. Workbook / field specification#

Use normalised linked tables with one container-delivery row per exchange. Keep prior baselines immutable, reject broken joins and use real date values rather than dates mixed with comments. Input columns have code/value validation; calculated dates/views are reproducible from the stored calendar and assumptions.

Table / keyFields, types and validationRelationship / owner
Control / TIDPID+RevisionHeader in section 1; approval and distribution evidence URIs; baseline/timezone/calendar versionTask-team lead
Deliveries / DeliveryIDContainerID, title/description, TeamID, producer/checker/lead IDs, responsibility/appointment reference, EIR/LOIN IDs, object/location scope, FormatIDs, ExchangeID, recipient/use, required revision/suitability/state, SensitivityClass (Public / Internal / Confidential / Restricted per BBM-STD-87 §2), H&S information flag and record ID (BBM-STD-88), MIDP row/source keyOne stable container per identity; separate delivery occurrences by ExchangeID; required strings and valid foreign keys
InformationNeed / LOINID+RevisionPurpose, actor/producer/receiver, timing, object population, required geometry, alphanumeric properties/types/units/values, documentation, source, test and acceptance criterion; mandatory flagDiscipline designer defines need with recipient; bare LOD is insufficient
Timing / DeliveryIDPrepStart/Finish, PrepDays, L1Start/Finish/Days, SharedDue, forecast/actual dates; package L2/rework/L3/release/acceptance windows referenced by PackageID; SubmissionDue and AcceptanceDueNumeric working-day durations and parsed dates; finish follows start; checked inputs available before dependent event
Dependencies / DependencyIDPredecessor delivery/interface ID, required event/state/revision/use, FS/SS/FF relation, lag, promised/actual receipt, validated-input decision, latest safe date, owner and risk/change linkProducer confirms sufficiency, LAP coordinates external impact
Formats / FormatIDNative/open/readable extension, schema/profile, exporter/full build, preset/hash, required objects/property mapping, receiving product/build, validation and receiving-use testsActual approved baseline, not latest; each variant has deterministic identity and manifest link
Drawing detail / DeliveryIDDrawing/task reference, sheet size, scale or N/A reason, covered levels/zones, model source ID/revision, title/element and production toolConditional: required for drawings; no fabricated scale/sheet size for datasets/models
Review / ReviewIDExact container/revision, L1 author/checker evidence, comments/marked-up and clean links, dispositions/date; package L2/L3 evidence, release and recipient decision linksIndependent checker differs from author; competence and capacity evidenced
Progress / DeliveryID+SnapshotDateBaseline/forecast/actual stage dates, remaining estimate, issue/non-conformance IDs, evidence URI, next action/owner/dueEvidence-based status, never guessed completion percentage
Changes / ChangeIDOld/new requirements/scope/dates/LOIN/revision, impact/dependency/capacity assessment, authority/date, TIDP and MIDP new baseline IDs, notices/acknowledgmentsSame ChangeID in every affected plan; no silent rebaselining

Controlled progress statuses: Planned / In Production / In Discipline Check / Checked for Shared / In Coordination Review / Authorised / Submitted / Accepted / Rejected / Superseded / Hold. These are delivery-progress meanings, not CDE state or suitability. Each transition has actor/date and evidence; Submitted needs a transmittal, Accepted needs recipient decision, Rejected retains the reviewed revision/reason.

Old header intentNew location / correction
ProjectCode, Originator, DocType, Discipline/Subdiscipline, Level, Zone, SequenceProject token/code register plus ContainerID; map to eight-field external grammar rather than concatenate inconsistent fields
Drawing/Task Number and titleDeliveryID, description, production responsibility and conditional Drawing detail
Production tool / Model ReferenceExact tool/build/profile and model ContainerID+source revision, not software brand alone
Drawing Scale / Sheet Size / Levels CoveredDrawing detail; meaningful N/A for non-drawing outputs; explicit object/zone scope
RemarksTyped risk/issue/change/disposition fields with owner/evidence, not hidden schedule decisions
First planned finalisationSeparate preparation finish, L1, Shared, submission and acceptance dates; baseline/forecast/actual

4. Information need and responsibility worksheet#

Derive need from an EIR requirement and actual decision/use; identify required objects, geometry, data and documents before estimating effort. Stage or LOD 300 cannot replace these fields. Security and residual health/safety records are planned deliverables when required, not untracked attachments.

LOINID / requirement (synthetic)Purpose / actors / timing / objectsGeometry requirementAlphanumeric requirementDocumentation / acceptance
LOIN-SYN-ME01 R01 / EIR--M01Spatial-coordination decision; mechanical producer, independent checker, coordination reviewer; EX-; Z01/L01 air distribution, one unit AHU-001 and two valves VLV-001/002Located extents, insulated routes, connections/support interfaces and explicit 600 mm withdrawal envelope for fictitious SYN-REQ-A01 R01; controls SYN-CRS01Stable GUID/Asset_ID, system/type, location, classification where required, units/source evidence; three unique maintainable IDsNative+IFC manifest, known-value/count comparison, hard/access run, design note; all mandatory values valid, three assets present, routes/interfaces/envelope unobstructed
LOIN-SYN-ME02 R01 / EIR--M02Equipment selection/service-planning review; mechanical producer/checker, designated design/asset reviewer; EX-; same three assetsNo new geometry; exact model GUID/location linkAsset_ID, type, system, location, design flow where applicable, access need/units, manufacturer/source reference; valid N/A for inapplicable propertiesItemised dataset/readable PDF; model↔dataset keys/counts/values reconcile; fictitious sources replaced before issue
LOIN-SYN-ME03 R01 / EIR--M03Design-basis/access decision; competent mechanical designer, cross-discipline reviewers; EX-; same zone/assets/interfacesDimensioned critical viewpoints tied to model revision; no verified existing-condition claim without surveySource/requirement IDs/revisions, assumptions/uncertainties, residual-risk owner/action date and changed interfacesTechnical note, evidence index, issue dispositions/safety records; source-linked design/code checks by competent reviewer; required links open

The 600 mm value is a completed fictitious requirement consistent with the clash example, not a general office access tolerance. Actual envelopes come from design/code/manufacturer evidence in the single rule register. Classification codes are entered after table/release validation; never invent a code to fill a cell. ISO 7817-1:2024 is the current concept reference; EN 17412-1:2020 is not used as the current basis. [S07]

Production responsibility rowProducer / independent checker / leadRequirement / delivery / authority
PR-SYN-ME01SYN-MA01 model author / SYN-MC01 model checker / mechanical team leadEIR--M01; DEL-SYN-ME01; structural/architectural designers retain their design decisions
PR-SYN-ME02SYN-MA02 schedule author / SYN-MC02 data checker / mechanical team leadEIR--M02; DEL-SYN-ME02; designated asset/design reviewer confirms required values
PR-SYN-ME03SYN-MA03 competent note author / SYN-MC03 independent designer/checker / mechanical team leadEIR--M03; DEL-SYN-ME03; committee and appointing-party decisions remain separate

These are synthetic role identifiers, not real appointments. Insert identifiable authorised people/IDs, competencies, hours and deputies. The separate IM-activity RACI remains in the BEP; it cannot replace these container commitments.

5. Completed task-team delivery rows — original synthetic example#

Plan TIDP-SYN-ME R01 / baseline BL- (scenario assumption only) rolls up into MIDP- R01 and EX-. Example calendar CAL-: Monday–Friday, 8 hours/day, Asia/Dubai, no holidays in the window. Preparation/L1 durations count start and finish working days inclusively; FS+0 begins the next working day after the required predecessor event. Real approval receipts, actual dates and executed outputs have not been supplied.

DeliveryID / source rowContainerID and descriptionTeam / preparation start→finish / daysL1 window / days / Shared dueDependenciesExchange
DEL-SYN-ME01 / ME-01CLI-OFF-P001-Z01-L01-M3-M-0001; mechanical modelME / 2026-11-04→2026-11-10 / 52026-11-11→2026-11-12 / 2 / 2026-11-12DEL-SYN-AR01 + DEL-SYN-ST01 checked Shared R01 on 2026-11-03; FS+0EX-
DEL-SYN-ME02 / ME-02CLI-OFF-P001-Z01-L01-SH-M-0002; equipment scheduleME / 2026-11-11→2026-11-11 / 12026-11-12→2026-11-13 / 2 / 2026-11-13DEL-SYN-ME01 prepared model R01 on 2026-11-10; FS+0 at preparation interface, not early releaseEX-
DEL-SYN-ME03 / ME-03CLI-OFF-P001-Z01-L01-RP-M-0003; design/access noteME / 2026-11-11→2026-11-11 / 12026-11-12→2026-11-13 / 2 / 2026-11-13DEL-SYN-ME01 prepared model R01; separate author/checker capacity from ME-02EX-
DeliveryIDProducer / checker / responsibilityNeed and formats / source identityRequired share / final use and package dates
DEL-SYN-ME01SYN-MA01 / SYN-MC01 / PR-SYN-ME01LOIN-SYN-ME01 R01;.rvt +.ifc; synthetic model R01; IFC 4.0.2.1 (IFC4 ADD2 TC1) Reference View, profile SYN-X74-BASE (office default). IFC 4.3.2.0 (profile SYN-X01) only by recorded approval after the sender build and receiver both pass a test exchangeShared/SU-COORD after L1 on 2026-11-12; formal SU-REVIEW submission 2026-11-26; recipient decision due 2026-12-01
DEL-SYN-ME02SYN-MA02 / SYN-MC02 / PR-SYN-ME02LOIN-SYN-ME02 R01;.csv +.pdf; itemised model R01 snapshot; SYN-X02 field mapping with unitsShared/SU-COORD after L1 on 2026-11-13; same package submission/acceptance dates
DEL-SYN-ME03SYN-MA03 / SYN-MC03 / PR-SYN-ME03LOIN-SYN-ME03 R01;.pdf + linked issue/BCF records; exact model R01 and requirement/source IDsShared/SU-COORD after L1 on 2026-11-13; same package submission/acceptance dates

Each format variant is explicitly listed in the exchange manifest with the same logical stem and approved extension. Data/readable variants map to one snapshot and must not drift. Native model, IFC and report carry actual source/export revisions/hashes; R01 here is scenario input, not observed office state. Correction triggers reassessment of derived schedules/notes/exports. Receiving native/full build, exporter/preset and open-profile support must be tested before use; a schema label does not prove capability. Models/data/notes have drawing scale and sheet size N/A; any actual drawing is planned separately with its required scale/sheet size and model source.

Coordinated package window (same MIDP baseline)Dates / allowanceEvidence and release condition
Coordination report production and its L12026-11-16; report L1 2026-11-17→2026-11-18All AR/ST/ME inputs checked Shared; independent report checker; IM producer
L2 cross-discipline review2026-11-19→2026-11-20 / 2 working daysExact six-container set; revised-model hard/access and information checks
Correction / retest reserve2026-11-23→2026-11-24 / 2 working daysChanged outputs repeat affected L1 and independent L2; reserve is not a pass or waiver
L3 technical committee2026-11-25 / 1 working dayRelease or Resubmit affected documents; L1/L2 evidence verified
Delivery-team authorisation / PM release2026-11-26 / 1 working dayExact approved set, immutable manifest and actual transmittal
Appointing-party review / acceptance2026-11-27→2026-12-01 / 3 working daysRecipient decision/permitted use; no deemed approval

The model starts after checked architecture/structure inputs. Schedule/note production uses the controlled prepared mechanical model internally; release still depends on model L1 and coordinated checks. Parallel model review, schedule and note work assumes distinct authors/checkers with verified capacity; a small team must stagger/re-estimate and propagate changed package dates.

6. Worked equipment data and check record#

This original dataset is fictitious and unsuitable for design/construction reliance. The example requires all three assets to be itemised; grouped schedule rows cannot substitute for object-by-object checks.

Asset_IDObject reference / type / locationApplicable design value with unitsAccess / evidence referenceExpected check
AHU-001SYN-GUID-ME-001 / air unit / Z01-L01Example airflow 2000 L/s600 mm withdrawal envelope / SYN-REQ-A01 R01 and fictitious technical noteUnique ID; numeric flow/unit retained; envelope linked to model; receiving value matches
VLV-001SYN-GUID-ME-002 / isolation valve / Z01-L01Example nominal diameter 80 mmOperation envelope per SYN-REQ-V01 R01 (fictitious requirement)Valid diameter/unit; actual envelope source/value needed in live rule record
VLV-002SYN-GUID-ME-003 / isolation valve / Z01-L01Example nominal diameter 80 mmOperation envelope per SYN-REQ-V01 R01Distinct ID/GUID despite identical type; no grouping loss/duplicate deletion

No real manufacturer documents or classification codes are fabricated. Evidence fields remain explicit until actual sources are available. LOIN may require more properties/documents than these illustrative columns; enumerate the live mandatory population in the worksheet.

Check IDScope / expected resultPerformer / evidence to recordResult in this revision
SYN-QC-01Three unique assets in model/itemised dataset; exact key/type/location/value/unit reconciliationIndependent data checker; complete-population comparison and snapshotsExpected test defined; no real artifact execution
SYN-QC-02Required hard overlaps absent; 600 mm withdrawal envelope unobstructed; actual valve-envelope basis present before activationIndependent coordinator and competent designer; rule/model revisions, viewpoints and run resultsMissing live envelope basis blocks activation; no real run supplied
SYN-QC-03Native/IFC preserve object IDs/counts/values; known omitted mandatory value detected; document links openIntended receiver/build and checker; failure/correction/retest fixture and use decisionNo installed/exporter/receiver qualification supplied
SYN-QC-04L1 comments closed/withdrawn; L2 interfaces retested; L3/release/recipient decisions present in orderQA auditor; record IDs/dates and non-conformance linksNo actual signed package supplied

Schema/IDS checks, if selected, require exact rule/profile/version and known pass/fail cases: IFC schema and normative-rule conformance is checked first with the buildingSMART IFC Validation Service or an equivalent qualified validator (report and hash recorded); information requirements are then checked with an IDS 1.0 file (buildingSMART, June 2024) per BBM-STD-89, recording rule IDs, IDS file hash and the named checker and version. Neither check establishes complete geometry/access or design safety. All mandatory applicable obligations must be valid. ISO 19650-4:2022 supplies exchange-decision context; this table states local checks rather than claiming a tool implements every normative requirement. [S04]

7. Step-by-step production, review and roll-up#

  1. Confirm appointed scope, requirements, exchanges, production responsibilities, recipients and actual tool/CDE readiness. Record clarifications; never invent a needed design/survey/manufacturer input.
  2. Decompose scope into identifiable containers and format variants. Give each delivery a DeliveryID and each container a stable controlled identity. Plan models/datasets/reports alongside drawings and each required exchange occurrence.
  3. Complete purpose/actor/timing/object and geometry/data/documentation worksheets. Identify mandatory tests, competent design/code reviewers, sensitivity and residual health/safety information with source/requirement IDs.
  4. Name actual producers, independent checkers and lead/deputies. Estimate preparation/remaining working days and allocate hours/capacity. Check actual builds/profiles and receiving-use qualification on representative artifacts.
  5. Record predecessor inputs by exact revision and required event/state. Agree interface dates with providers/LAP; resolve cycles, missing inputs, resource collisions and review allowances before commitment.
  6. Calculate L1/Shared handoffs and agree coordinated L2/rework/L3/release/acceptance windows with MIDP owner. Separate baseline/forecast/actual dates; independent planning checker verifies calendar arithmetic, joins and responsibility coverage.
  7. Task-team lead approves the exact TIDP commitment. LAP imports rows into MIDP and resolves team/interface constraints; record shared baseline and distribution acknowledgments. Until actual approvals exist, the live plan is Draft/Hold.
  8. Produce in WIP. L1 requires originator and independent discipline checker, marked-up review, every comment closed or formally withdrawn by checker, identifiable IDs/signatures, clean set and required design/supporting reports. Model/data/drawing checks precede Shared.
  9. L2 uses the exact revised federation, cross-discipline issue log, clash tests each comment round and visual/model-health checks against BEP. Designers disposition changes; independent retest closes issues. Changed geometry triggers related data/notes/drawing checks.
  10. L3 committee verifies L1/L2 evidence and package, recording Release or Resubmit affected documents. Delivery-team approver authorises use; PM transmits after required technical decision. Retain separate recipient acceptance/rejection.
  11. Update evidence-based progress weekly and for changed input/requirement, failed review, scope/tool change or lateness. Raise one ChangeID, obtain appropriate task-team/LAP/recipient decisions and propagate every affected TIDP/MIDP row before using the new commitment.
  12. Audit adherence/evidence, raise corrective actions for non-conformance, and apply lessons to next baseline. QA plans means/criteria, QC verifies outputs, audit verifies process; PDCA verifies correction/prevention by retest.

8. Change propagation, rejection and progress templates#

ChangeIDTask-team change / impactTIDP decision / revisionMIDP propagation / interface notice
SYN-CHG-01 (hypothetical, same MIDP example)Supplier envelope changes; ME-01/02/03 impacted; rerun access/hard/interfaces, re-estimate L1/L2/datesPending scenario: team lead records actual source/revision, resource and date proposal; no change approved hereLAP assesses IM-01, EX-, milestone/other teams; records decision, paired baselines and recipient acknowledgments
[ID][trigger, old/new requirement/dates, dependency/capacity/risk impact][authority/date/evidence; old/new TIDP][old/new MIDP, affected rows/recipients, notices and effective date]

Rejected information returns to WIP in a new controlled revision with reviewed revision, reason, issue/requirement and decision retained. Resubmit affected documents only where technical/recipient authority permits and coupled interfaces remain valid; otherwise revise the package. Independent retest closes the issue; authorised recipient accepts the exchange. Notify dependent teams and reassess dates; never overwrite rejected evidence or treat submission as acceptance.

DeliveryID / reporting dateBaseline Shared / submit / acceptForecast / actual evidenceBlocker / remaining effort / action
DEL-SYN-ME01 / scenario snapshot2026-11-12 / 2026-11-26 / 2026-12-01Forecast equals baseline under assumptions; Planned; no actual model/approvalLive inputs/tool evidence required; mechanical task-team lead owns mobilisation
[row / date][immutable baseline dates][forecast and actual stage/time/record URI][issue/change, estimate, accountable owner and due date]

Report observed stages with actual evidence and counts/remaining effort; arbitrary percentages or a filename cannot establish progress. Retain marked-up/clean sets, product/source evidence, model/data reports, committee comments, corrective actions and quality-document index revisions in authorised private custody.

9. Acceptance criteria / self-check and common mistakes#

  • Every container/exchange has DeliveryID, controlled identity, description, producing team, actual author/checker and responsibility reference.
  • LOIN states purpose, actors, timing, objects, geometry, typed/unit-bearing data, documentation and measurable checks; no bare LOD or unvalidated classification/source substitutes for need.
  • Preparation, dependencies/required input events, L1/Shared and submission/acceptance dates are feasible on stored calendar with real capacity.
  • Exact native/open/readable profiles, source/export/tool/receiver versions are recorded and receiving use tested; all mandatory geometry/data/document obligations pass.
  • Each TIDP row matches approved MIDP container, producer, exchange, dates, durations, LOIN, source key and baseline; no unresolved change or divergence.
  • L1 comments, L2 interfaces/model-health/clash retests, L3 committee, authorisation/PM release and separate recipient decisions are evidenced in order; safety cannot be waived by schedule/severity.
  • Rejection/change records retain baselines/evidence and notify affected teams/recipient; coupled outputs revised and corrective actions/lessons retested.

Common mistakes: treating originator as producer; planning only drawings; one finalisation date for everything; unvalidated provisional input; repeating package review allowance for every row; grouped counts passed as itemised; signing for the independent checker; equating upload with acceptance; renaming historic issues; silently overwriting the other plan.

10. Research coverage, correction trace and activation boundary#

Item / gap / crosswalkPresent section / evidence
T08.1Sections 3/5: complete mechanical container deliveries/format variants and plan structure for every team output
T08.2Sections 3–6: ID/description/producer/checker, explicit LOIN and worked equipment data
T08.3Section 5: preparation duration, event-specific dependencies, synthetic dates/calendar; section 7 actual commitment procedure
T08.4Sections 4–5: EIR, exchange, production responsibility and MIDP delivery/source keys
T08.5Sections 2/5/7/8: review/rework/acceptance windows and approved cross-plan change propagation
O08 P1 / C03Header-only source replaced by original populated synthetic producer/LOIN/date/dependency/preparation rows
O08 P2 / C04 / C07Exchange/acceptance fields, controlled states/separate authorities, paired changes and mandatory thresholds
O08 P3Known-value/model/dataset/recipient test protocol; real exchange test requires artifacts and is not claimed executed
C02/C06/C08/C10/C11/C12/C16/C19Single naming/rule policy, private original examples, evidence-qualified existing conditions, correct stages/current LOIN, tested tools/competent safety and itemised reconciliation

Editorial revision is complete. Real appointments/names, approved requirement/input/tool baselines, producer/checker capacity/signatures, produced artifacts, executed tests, MIDP approval and recipient decisions remain operational records to populate. SYN examples demonstrate commitments; they are not an approved project TIDP or real exchange. Missing mandatory live evidence blocks activation under section 9 rather than being labelled complete by a template.

One delivery row links requirement, responsibility, dates, exact revisions and acceptance evidence.

References#

RESEARCH.md source tags below identify editions actually used. References establish scope and practice; no unverified ISO clause is asserted. Office defaults are local decisions, not ISO-mandated numerical limits.

TagTitlePublisherYear / editionURL / evidence
S01ISO 19650-1 — Concepts and principlesISO2018, ed.1Catalogue / abstract; published, revision underway
S02ISO 19650-2 — Delivery phase of the assetsISO2018, ed.1Catalogue / abstract; publisher result exposes English abstract and status
S04ISO 19650-4 — Information exchangeISO2022, ed.1Catalogue / abstract
S05ISO 19650-5 — Security-minded approach to information managementISO2020, ed.1Catalogue / abstract
S06ISO 19650-6 — Health and safety informationISO2025, ed.1Catalogue / abstract
S07ISO 7817-1 — Level of information need: concepts and principlesISO2024, ed.1Catalogue / abstract
S11ISO 16739-1 — IFC: data schemaISO2024, ed.2Catalogue / abstract
IDSInformation Delivery Specification 1.0buildingSMART InternationalJune 2024, finalIDS releases, checked 2026-11-04
IFC-VALIFC Validation ServicebuildingSMART Internationallive serviceValidation service, checked 2026-11-04
S12Industry Foundation Classes (IFC)buildingSMART InternationalUndated live page; 2024 ISO editionVersion and implementation context
S18ISO 29481-1 — Information delivery manual: methodology and formatISO2025, ed.3Catalogue / abstract
S21RIBA Plan of Work 2020Royal Institute of British Architects2020Current resource page; 2020 template
G-AGuidance A — The information management function and resourcesIMI Framework (formerly UK BIM Framework, renamed May 2025)archived edition 2, February 2021Official PDF; archived Guidance Parts A–F listed on ukbimframework.org/resources, checked 2026-11-04
G-CGuidance C — Facilitating the CDE workflow and technical solutionsIMI Framework (formerly UK BIM Framework, renamed May 2025)archived edition 1, September 2020Official PDF; archived guidance
G-FGuidance F — About information delivery planningIMI Framework (formerly UK BIM Framework, renamed May 2025)archived edition 1, September 2020Official PDF; edition actually verified. Its federation section is a placeholder; use other sources for technical federation guidance.

Internal concept source: office QMS concept notes (working record), 14 October 2026; the controlled QMS is BBM-STD-96; original procedures here use concepts only. Immutable office spreadsheet export remains private evidence; no third-party template wording is reused.

Document history
VersionDateChange
V0.114 October 2026First versioned markdown successor to BBM-STD-TIDP.md.
V0.2not recordedFile re-issued as V0.2 (header text still read V0.1).
V0.34 November 2026closure: header equals filename version and link texts point to Clash Matrix V0.3 / MIDP V0.3; DEL-SYN-ME01 IFC profile aligned to the office default IFC 4.0.2.1 Reference View; IMI Framework naming with archived Guidance editions; IDS 1.0 and IFC Validation Service named in the §6 check record. + cross-doc pointer pass.