What belongs on the list for a drawing-issue log?

A dependency is a risk with someone else's clock attached.

Each line needs an owner. The document controller is the starting owner for the revision still in markup.

  • Usual slip: listing dependencies as admin rather than risk.
  • Useful move: giving each dependency an owner on your side and a needed-by date.
  • Put the shared outcome in both views and review it once on a drawing-issue log.
  • Done means the revision is issued or returned with comments.

What do you leave off the list?

On a drawing-issue log, the usual slip is listing dependencies as admin rather than risk. The document controller can see the revision still in markup. Each team reports its own tasks and nobody states the joint result. Left unnamed, the same item is still open when the week runs out.

Stop treating a dependency log nobody reads before the date as the update.

When do you look at it again?

The useful move is giving each dependency an owner on your side and a needed-by date. Put the shared outcome in both views and review it once. Done, for this work, means the revision is issued or returned with comments. The document controller should be able to say that without translating it for a colleague elsewhere.

On a week when two teams share one outcome, use a risk review for a drawing-issue log. Whether the morning starts in Pretoria, the site is in Midrand, or the decision sits in Johannesburg, a drawing-issue log needs one version of events. Each team can look busy while the shared outcome does not move.

Who holds the habit?

MetaServ is based at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157. From that base the same work happens on-site in Pretoria, on client sites in Midrand, and with teams in Johannesburg, including on a drawing-issue log. The useful move here is giving each dependency an owner on your side and a needed-by date.

If you are weighing giving each dependency an owner on your side and a needed-by date, read A second opinion without a takeover in Gauteng and A change note people can find in Gauteng. The wider frame is project management and the approach used with a delivery team.

If the revision still in markup is already stuck, talk to MetaServ and bring what you have today. Stop treating a dependency log nobody reads before the date as the update.

Questions before the register grows again

What belongs on the page for dependencies are risks with a clock?

A dependency is a risk with someone else's clock attached. For risk management, start with giving each dependency an owner on your side and a needed-by date.

What should the document controller watch for on dependencies are risks with a clock?

Done means the revision is issued or returned with comments. The slip to watch is listing dependencies as admin rather than risk.

Who should Johannesburg contact about dependencies are risks with a clock?

Call +27 10 880 6465 or email info@metaserv.co.za. The office is 340 Witch-Hazel Street, Highveld, Centurion.