Open Property Data Association
Smart Property Data Trust Framework
Become a member Join a working group

    Follow feedback, disagreement and revision

    Recognise a reasoned response: the evidence considered, meaning changed, checks made and questions left open. A retained distinction can be a successful outcome.

    Two ink-and-watercolour moments show a participant raising a question and later comparing a revised sketch while a remaining issue stays visible.

    A comment opens a question; it does not settle the model

    A contribution may lead to clearer wording, a missing distinction, a request for evidence or a reasoned decision to keep the existing meaning. It can also expose a disagreement which is not yet resolved. None of those outcomes is measured by the number of comments, reactions or agreeing AI agents.

    What matters to a contributor is whether the response engages with the actual issue. Can you see which evidence was considered, what the proposal now means and what your difficult case revealed? “Thanks, resolved” tells you almost none of that.

    The sequence here illustrates reasoning and handoffs using a fictional access question. It is not an implemented issue tracker, a promised response time or an adopted lifecycle state machine. Check the relevant working-group and candidate records for the standing of real work.

    Follow one question until the remaining difference is visible

    An illustrative review journey — not a record of actual candidate changes
    1. Question. A participant notices that the draft choice list combines “Completed” and “Limited access”. “Our report can be complete even though an agreed area was inaccessible. Which choice describes that case?”
    2. Request for evidence. A facilitator asks what “complete” means in the example, which areas were agreed and whether the report describes access or completion of work. Those facts would distinguish overlapping meanings from inconsistent data.
    3. Evidence and proposed correction. The fictional Harbour Court case identifies the living room, bedroom and enclosed area as the agreed areas. The first two were accessed; the enclosed area was locked. Contributors propose all/some/none physical-access outcomes, keeping completion of the report separate.
    4. Checks and review. The supplied case fits “some but not all”. Reviewers test all-access, no-access and empty-scope cases. Technical specialists examine whether the representation preserves the subject, visit and scope and whether declared checks express the proposed requirements.
    5. Disposition and next challenge. The response explains the revised scope and its limits. A later reviewer asks how old “Completed” records can be interpreted. The correction does not recover information those records never distinguished; that migration question remains open.

    The evidence request is substantive, not a demand to complete paperwork. Without an identified nonempty set, the revised choices could still overlap or answer the wrong question. The later challenge is also substantive: improved definitions do not make ambiguous historical values unambiguous.

    In this teaching example, proposing the distinction is warranted. Claiming that the group has adopted it, that all earlier records can be converted or that a released implementation now enforces it would not be warranted. Real human dispositions and release authority must be separately recorded.

    What an understandable response should tell you

    A worked, reasoned response

    Teaching draft B separates physical access from completion of work. Its three outcomes concern the identified nonempty set of agreed areas during one visit. Harbour Court is some-but-not-all access. The empty-scope case is excluded from this list and needs separate treatment. An old “Completed” value does not determine an access outcome without more evidence. This remains a teaching proposal, not a release.

    The better response does not need to accept every suggestion. It connects the original question to a stated change and explains the boundary. In actual review, it should also identify the affected candidate version, the responsible decision or review record and the standing of that disposition.

    A technical result answers a bounded question

    Which judgement and authority are still needed?

    A technical validation result and the Technical Working Group's determination are not the same event. For the Property Pack, the recorded accelerated arrangement separates that determination from later domain review. Neither automatically establishes release, adoption or external government recognition. Consult the maintained determination page and review and release record rather than inferring status from this sequence.

    AI and facilitators can assemble evidence, propose alternatives and explain consequences. They do not gain decision authority because several drafts agree. Human domain judgement and recorded OPDA authority retain their separate roles.

    Distinguish three reasons for not having one answer

    A wording problem

    Two reviewers intend the same physical-access scope, but one reads “partial” as including no access. A precise definition and exclusions may resolve the disagreement. Test the revised wording with both the some-access and no-access cases.

    A source conflict

    Two sources make incompatible access claims about the same identified area and visit, and neither is known to supersede the other. Renaming a term does not reconcile those accounts. Keep both, their versions and the evidence needed to investigate. “Use the newest” is not a general authority rule.

    A legitimate difference of purpose

    One user needs to know which areas were entered; another needs to know whether a document contains all required sections. Both questions can be valid. The useful outcome is to preserve the two meanings and identify how they relate, not force them into one universal “complete” status.

    Try it: what is missing from “no change”?

    A response to a multi-day inspection example says: “No change: the date field is optional.” What should you ask next?

    A reasoned response

    Optionality does not explain how a multi-day event can be described when information is available. Ask whether the intended scope includes such events and, if so, how their occurrence period is preserved. The response may legitimately show that the existing model already supports a period, or explain a justified exclusion. It needs to address the supplied case, not merely say that the troublesome value can be omitted.

    A useful follow-up keeps the original reference, identifies this unanswered part and avoids reopening unrelated questions. If new evidence changes the premises, say so; a revised conclusion is not automatically evidence that the earlier reasoning was careless.

    Follow the existing record, not an invented process

    The current discussion guidance explains working-group threads and page-specific comments where available. A comment is not a vote, an approval or a standalone decision record. Source intake has its separate authorised route.

    ADR-0065 and ADR-0068 describe wider proposed operating arrangements; their proposals do not create live response deadlines or ratification mechanics. The accepted Property Pack method and its accelerated determination amendment retain the relevant authority boundaries.

    Keep your question's reference and ask which candidate or recorded decision the response affects. When a next step or access arrangement is unclear, use the member guide. Do not create a parallel public discussion containing private evidence simply to make the question more visible.

    Comments

    Loading comments…