Trace shared property services to the quantities each record can support
Two properties can share a contractor, gate and invoice account without sharing the same measurement boundary. A tanker empties into a common tank; sealed waste containers remain separately identifiable on one truck. The evidence supports different property-level answers even though both services use the same entrance.
This fictional exercise is for property managers and reporting coordinators preparing water and waste records for individual buildings. It asks which physical quantity can be connected to which property. It does not decide ownership, corporate consolidation, waste classification, treatment suitability or compliance.
Name the property, the service point and the record
The selected estate has two towers, A and B, and a shared service area S. Both towers are included in the internal management report, but their quantities are requested separately. S is retained as a third, shared row. This reporting layout is stipulated for the exercise, not an external reporting requirement. No allocation of S has been approved.
Gate G is physically beside tower A. A common water tank T and loading bay L stand in S. The facilities map confirms that T supplies both towers and that L receives their separately tagged waste containers. The contractor account uses A’s postal address for every invoice. That address identifies where the paperwork goes; it does not change the map.
Keep three links visible: property to physical service point; service event to that point or identified container; and measurement record to the event. The contractor name and invoice account belong beside these links. They cannot replace them. A match on the word A alone would merge the postal address, tower identity and shared gate.
Locate the tanker quantity before splitting it
For the selected day, 12 June 2026 at UTC+05:30, delivery ticket D18 records 18 m³ discharged into T through inlet W. The ticket, inlet location and delivered quantity are stipulated as correct. The selected record set covers this one delivery, not a month or the estate’s complete water inventory. No tower-specific outlet readings are initially supplied.
The invoice charges 60% of the delivery cost to A and 40% to B. Its note explicitly calls this a service-charge convention and provides no physical-volume basis. Multiplying 18 by these fractions produces 10.8 and 7.2 m³, but those numbers are a proposed allocation, not two measured deliveries. The amounts paid do not resolve the missing volume evidence.
Even if the entire delivery left T for the towers with no change in tank contents or other flow, 10 m³ to A and 8 m³ to B would fit the 18 m³ total. So would 6 m³ and 12 m³. These are alternative invented possibilities, not estimates. One combined quantity cannot choose between them. The supported initial entry is 18 m³ delivered to shared tank T.
GRI 303 distinguishes withdrawal, discharge and consumption, and asks for compilation methods and assumptions. Its water-withdrawal guidance includes supplies from other organisations. These definitions provide context; this case does not establish a complete disclosure, source-quality classification or water-stress assessment.
Use the next record at its actual physical boundary
Now consider a separate follow-up state for that same day. A checked inlet record confirms the 18 m³ as the only inflow to T. Checked branch meters record 11 m³ leaving T for A and 6 m³ leaving T for B. Tank records show 5 m³ at the start and 6 m³ at the end. The example stipulates no other inflows, outlets, transfers or losses and matched reading instants.
The shared-system check is 5 + 18 − 11 − 6 = 6 m³. It closes. The 17 m³ distributed to the towers and the 1 m³ increase in shared storage together explain the day’s 18 m³ input. The 1 m³ is a net increase in shared storage. Keep it on T’s schedule rather than assigning it to a tower; it does not identify how much of D18 remains.
Label A’s 11 m³ and B’s 6 m³ as transfers from the shared tank. At the estate boundary, adding those transfers to the 18 m³ external delivery would count an internal movement again. These readings also do not establish water consumption; the case supplies no tower discharge data.
The 11 and 6 describe water leaving the tank during the selected window. Because T held 5 m³ at the start, they do not trace which part of delivery D18 physically reached either tower. Keep the delivery event and the distribution-period records connected without claiming that they identify the same individual water volume.
Check whether sharing a truck actually erased identity
For a separate collection on the same day, A seals two containers and B seals one. The pickup list links each container and its unique seal to the originating tower before it reaches L. The three containers travel together but are never opened, exchanged, emptied together or relabelled before individual receiver measurements. The record identities, unchanged contents and net-mass bases are stipulated as correct for this exercise.
Pickup event P12 lists A/C1/seal S41, A/C2/seal S42 and B/C3/seal S43. Receiver record R12 reports separate net contents of 80 kg, 60 kg and 160 kg against those same event, container and seal references. Its control total is 300 kg. No other property or container is included.
A’s selected containers total 80 + 60 = 140 kg. B’s selected container is 160 kg. Together they match 300 kg. These are property-linked documentary quantities for this collection. The shared truck does not force an allocation because the individual measurement links survived. Conversely, the truck total alone would not establish the split.
Dividing 300 kg by the three containers would assign 200 kg to A and 100 kg to B, contrary to the supplied 140/160 records. The containers are equal in count, not in stated contents mass. Applying the 60/40 service-charge split would instead give 180/120 kg. Neither shortcut uses the individual receiver records.
GRI 306 asks for contextual information on waste data and distinguishes generation, recovery and disposal information. Its guidance discusses direct measurements and contractor transfer notes. The selected pickup quantities here do not by themselves establish total waste generated, recycling or final treatment. Those are separate evidence questions.
If R12 instead listed only 300 kg for the combined load, the container identities would still show which towers participated. They would not establish 140 and 160 kg. Request existing individual measurements and their links if available. If there were none, retain the combined quantity and the unresolved property split; do not recreate measurements from a later invoice.
If C1 is reused next week, its container number alone is no longer a unique measurement key. Preserve P12 and S41 with this occurrence. A future C1 collection is a different event. This is an identification rule for the supplied records, not a recommendation for physical waste handling or a seal-validation procedure.
Send the contractor two different questions
For water: ask which inlet the delivery record names, what the facilities map says that inlet serves, and whether matched distribution and tank records exist. Ask the custodian to explain the coverage of each measurement. A request for “A’s share” before establishing those facts invites a billing split to be returned as if it were a measured property volume.
For waste: ask for the pickup-event schedule, the originating property and container or consignment references, and the receiver quantities at that same level. Ask whether materials were combined before any individual quantities were recorded. The answer determines whether more document matching can recover a property quantity or whether the original measurement never distinguished it.
Hand over four rows for the follow-up state: T delivery 18 m³; A/B transfers 11/6 m³; shared storage increase 1 m³; and A/B selected collection quantities 140/160 kg. Keep unlike units separate. Attach the map and event links beside each row. Do not total all water rows together or turn a selected collection into a property’s full-period waste total.
A second reader should be able to remove the branch readings and see the tower water quantities become unresolved. Removing only the common postal address should change neither waste subtotal. Removing individual receiver quantities should make the waste split unresolved too. These tests locate the evidence that changes the answer; another consolidated invoice does not supply it.
Use the water-balance guide for a broader site reconciliation, and the waste vendor-record guide for dispatch-to-receiver matching. This exercise isolates the earlier question: which property, if any, the surviving measurement identifies.
For a scoped property-record review, contact Nitium Advisory with a non-confidential outline of the shared services and the unresolved quantity.
Sources and limits
GRI 303: Water and Effluents 2018, Disclosure 303-3 and glossary.
GRI 306: Waste 2020, Disclosures 306-3 to 306-5 and compilation guidance.
Primary sources checked 14 October 2026. All properties, contractors, quantities, dates, records and scenarios are invented. This is an original reporting-evidence exercise, not a GRI method or worked example. No real site, supplier performance, legal obligation or independent assurance conclusion has been assessed.
Comments