Start with the decision
A register is most useful when it shows what information the team needs and why. Alongside the query, record the affected activity and the decision required. Keep a link to the source correspondence so a summary never replaces the actual response.
Give every open item an owner
Distinguish the party expected to respond from the person responsible for following up. “With consultant” is a location, not a next action. Name the role responsible for the next step and agree how overdue responses reach the PM.
Separate receipt from resolution
A response may ask for more information or leave part of the query unresolved. Use a status that describes the real position. The authorised project team should confirm whether the response resolves the issue before the register is closed.
Agree dates and escalation
Record the agreed response date and the date the information is needed for the work. These may differ. A weekly summary should highlight the gap and the responsible decision-maker, rather than simply colouring every late row red.
A useful minimum record
Reference; issue; source document and revision; response party; follow-up owner; response due; activity affected; status; latest follow-up; next action; closure basis. Keep that structure consistent, then add fields only when they support a decision.
See an example
Explore fictional registers and a downloadable weekly report in the sample Control Centre.
Open sample workspace