Project Background

This inquiry came from a construction contractor in Africa who wanted to enter the event rental and stage-building market.

Unlike a new event company starting from zero, he already owned a relatively complete Ringlock scaffolding system, including:

• standards;

• ledgers;

• diagonal braces.

His idea was therefore very straightforward:

Why buy another complete stage support system if the Ringlock structure is already available?

He wanted to reuse as much of his existing scaffolding as possible and purchase only the components needed to turn the top of the structure into an event stage.

The proposed concept was:

existing Ringlock structure + top forks + aluminum-framed plywood stage decks

rather than purchasing a more dedicated Layher-style stage arrangement with additional stage beams.

This made the inquiry primarily a question of reuse and compatibility, not simply product supply.

The Customer Wanted to Avoid the Most Expensive Additional Part

The customer had already invested in a complete Ringlock scaffold inventory.

For him, the major attraction of the fork-type concept was that the existing:

• standards;

• ledgers;

• braces

could continue to form the main lower support structure.

At the top, he hoped to add only fork-type deck supports and compatible stage platforms.

Suggested caption: The proposed concept used the customer's existing Ringlock standards, ledgers and braces, with fork-type supports added at the top for the stage deck system.

The alternative was a more typical dedicated Ringlock/Layher stage configuration.

In that type of stage, additional stage beams are used below the deck platform.

For a customer who already owned most of the Ringlock base structure, those beams represented a substantial new investment.

His position was clear:

He did not want to buy another large group of stage-support beams if he could make the existing Ringlock do the job.

That was the commercial logic behind the fork proposal.

Option A — Build a More Dedicated Modular Ringlock Stage

One possible direction was to use the customer's Ringlock equipment as part of a more conventional modular stage arrangement and introduce the required deck-support beams.

Conceptually, this would give us a clearer stage-specific system:

Ringlock base structure
↓
dedicated stage support beams
↓
modular aluminum-plywood decks

Suggested caption: A dedicated modular Ringlock stage normally introduces stage-support beams between the scaffold structure and the deck platform.

From our point of view, this had an important advantage:

the relationship between the support grid and the deck system could be defined around known stage components.

But it had the exact disadvantage the customer was trying to avoid:

more equipment to buy.

The customer was entering a new business and wanted to reduce the first investment as far as possible.

So we continued discussing his preferred fork-type idea.

Option B — Reuse the Existing Ringlock and Add Only Forks and Decks

The customer's preferred solution was much simpler commercially.

Keep the existing scaffold structure.

At the top of each selected standard, install the required fork/support component.

Then place the compatible stage deck system onto those supports.

In principle, this could reduce the amount of newly purchased lower-stage structure.

The idea itself was not the main problem.

The problem was that we still did not know what Ringlock system the customer actually had.

And that became the turning point of the entire inquiry.

The Compatibility Problem Started With a Very Basic Question

To customize a top interface for an existing Ringlock system, we needed to understand the customer's actual scaffold dimensions.

But during repeated communication, the customer could not tell us:

• the Ringlock brand;

• the system dimensions;

• the exact ledger lengths;

• the relevant center-to-center spacing;

• enough interface dimensions to confirm the proposed fork/deck arrangement.

This meant that a sentence such as:

“I already have Ringlock.”

was not enough information to design the new stage interface.

Different Ringlock inventories can look very similar in photographs while still having dimensions or interfaces that affect the final platform layout.

The reuse idea therefore introduced a compatibility question that a completely new supplied system would not have had.

We Tried to Explain How to Measure the Existing System

The problem was not that we simply asked for a dimension once and stopped.

We tried to guide the customer through the measurement.

We:

• recorded video explanations;

• sent screenshots;

• marked the locations that needed to be measured;

• explained which Ringlock horizontal dimension we needed.

Suggested caption: We sent marked drawings and screenshots to explain which dimensions of the customer's existing Ringlock system needed to be confirmed.

For us, these dimensions were essential quotation inputs.

For the customer, however, the measurement request never became clear enough for him to provide reliable dimensions.

So we reached an unusual situation:

We understood what the customer wanted to achieve, but we still could not confidently define the interface between the new stage components and the equipment he already owned.

That prevented us from finalizing the customized system properly.

Why We Did Not Simply Guess the Ringlock Size

This is one of the most important parts of this case.

It would have been easy to assume that the customer's Ringlock used a common bay dimension and prepare a fork and deck quotation around that assumption.

But that would have created a much bigger risk later.

If the actual Ringlock grid did not match the proposed deck system, the customer could receive:

• forks that did not sit where required;

• deck modules that did not align with the support grid;

• gaps or overlaps in the stage layout;

• additional components he had not planned to buy;

• a system requiring site modification before it could be assembled.

For a project specifically intended to reuse existing equipment to save money, a compatibility mistake could remove the very saving the customer was trying to achieve.

So we did not treat an unknown dimension as if it were confirmed.

That follows the DragonStructure rule that existing-equipment reuse is valuable only when the required interface information can actually be established.

The Customer's Priority Was Different From Ours

During the discussion, another difference gradually became clear.

Our approach was based on modular event-stage thinking:

define the grid → match the interface → use repeatable modules → reduce adjustment during installation.

The customer approached the problem differently.

His first priority was:

minimize new equipment investment.

From our conversations, this particular customer did not place the same economic value on reducing installation labor that an event-rental company in a high-labor-cost market might.

He was willing to accept more manual work on site if that reduced the amount of specialized equipment he needed to purchase.

This distinction matters.

A modular stage system usually has value because repeated setup becomes more predictable and less dependent on site fabrication or adjustment.

But if a customer places far more weight on initial purchase cost than on repeat installation time, the same value proposition may not persuade him.

This was not a technical disagreement.

It was a difference in operating priorities.

The Final Turning Point: He Chose a Local Traditional Method

Eventually, the customer described the method he expected to use locally.

Instead of continuing to develop the fork + modular deck interface with us, he planned to:

• erect the Ringlock scaffold structure;

• fix timber boards directly onto the structure;

• adjust the surface level on site;

• cover the completed surface with carpet.

At that point, the project moved away from the modular stage solution we had been discussing.

There was no longer a clear reason to force the fork/deck proposal forward.

The customer already had a construction method that:

• used the materials available to him;

• matched his budget;

• relied on local labor;

• did not require him to resolve the Ringlock compatibility information we had been requesting.

So the final result of this inquiry was:

the customer did not adopt the fork-type modular stage proposal and returned to his existing local construction method.

That is the actual outcome of the project.

It should not be rewritten as a successful sale.

Why This Is Still a Useful Case Study

At first, a project that did not lead to an order may seem less valuable for a website.

In fact, this one teaches something important about reusing existing scaffolding.

The question is not simply:

“Can Ringlock be used for a stage?”

The better question is:

“Can this customer's existing Ringlock be integrated with this particular stage deck system using known and compatible dimensions?”

Those are very different questions.

Ringlock can certainly be used as the main support structure for many temporary stage platform structures. The DragonStructure Stage Platform section covers the structural role of such systems.

But when the plan is to reuse a customer's own stock, compatibility becomes part of the proposal.

The fact that the steel tube “looks like Ringlock” is not enough.

What Information We Needed but Never Confirmed

The project could have developed differently if the existing equipment information had been clearer.

The missing information included the actual Ringlock grid and component dimensions.

For this type of reuse project, we would normally want to confirm items such as:

The exact dimensions in this project were never reliably confirmed.

Therefore, this Case Study should not invent them.

Why the Fork Was Not Really the Hard Part

The fork looked like the special component in the proposed system.

But it was not the hardest part of the quotation.

The real problem was everything around it.

A fork only works as part of a relationship:

existing Ringlock grid
→ fork position
→ deck support point
→ deck dimensions
→ complete stage layout

If the first value in that chain is unknown, the remaining dimensions cannot simply be assumed.

This is a useful reminder that customization is often less about manufacturing a special metal part and more about confirming the interface between two systems.

BOQ Evolution

The BOQ logic changed significantly during the inquiry.

Customer's preferred starting point

Existing Ringlock:

• standards;

• ledgers;

• braces.

New purchase:

• forks;

• compatible stage decks.

This was the lowest-investment direction the customer wanted.

Alternative modular-stage direction

Existing Ringlock where usable, plus:

• stage support beams;

• deck platform system;

• related stage interfaces.

This required more investment and was therefore not preferred by the customer.

Final customer decision

No finalized modular stage BOQ.

The customer decided to continue with the local method of adding timber to the existing Ringlock structure and leveling the stage surface on site.

So unlike many Case Studies, the BOQ here did not evolve toward a larger final quotation.

It effectively stopped, because the information required to validate the reuse proposal never became available and the customer chose another construction method.

That is itself a legitimate quotation outcome.

Our Experience-Based Judgment

Our practical judgment during the inquiry was that a more modular stage arrangement could provide advantages for repeated event rental:

• predefined platform modules;

• more repeatable setup;

• less site fabrication;

• clearer component relationships;

• easier future replication of the same stage layout.

But these are practical event-system advantages, not proof that the customer's local timber method could not work.

We did not receive enough project-specific information to evaluate or certify his final locally built stage.

Likewise, we do not have supplied structural calculations for the fork-type proposal.

Therefore, this case does not establish:

• load capacity;

• allowable stage loading;

• safety factor;

• foundation requirements;

• structural compliance;

• certification;

• engineering approval.

Those would require actual system dimensions, configuration, material data and project-specific verification.

This distinction is required by the DragonStructure Case Study standard.

What We Learned

The biggest lesson from this case is not:

Fork stages are better than timber stages.

Nor is it:

Layher-style stage beams are always necessary.

The real lesson is:

Reusing existing equipment only saves money when the existing equipment can be identified and measured well enough to design the new interface around it.

The customer came to us specifically because he wanted to avoid buying unnecessary structure.

That goal made sense.

But the more components you want to reuse, the more important compatibility information becomes.

There is a useful paradox here:

“I already own most of the structure” can reduce the BOQ—but it can increase the amount of information needed before the BOQ can be finalized.

That is probably the most valuable sentence in this entire case.

When Reuse Makes Sense — and When It Becomes Difficult

Reusing an existing Ringlock system can be commercially attractive when:

• the system dimensions are known;

• the main components are complete;

• the intended stage dimensions are known;

• the top interface can be confirmed;

• the deck grid can be matched to the scaffold grid.

It becomes much more difficult when:

• the system brand is unknown;

• dimensions cannot be measured reliably;

• the existing stock contains mixed components;

• the stage deck system has already been selected independently;

• the customer expects new components to fit without confirming interfaces.

For general Ringlock stage products and system principles, readers can also refer to the DragonTruss Ringlock Stage System.

That page is better suited to the product/system question.

This Case Study is about the decision problem created by trying to reuse unknown existing equipment.

Planning a Stage With Your Existing Ringlock?

If you want to reuse an existing Ringlock scaffold inventory instead of buying a complete new stage-support system, send us the existing-system information before we finalize the deck or fork quotation.

The most useful starting information is:

• clear photos of the existing Ringlock;

• ledger dimensions;

• standard spacing;

• rosette and connection photos;

• overall intended stage length and width;

• stage height;

• deck size you want to use;

• whether you already own decks;

• whether forks, beams or other top interfaces already exist.

If the brand is unknown, that is not necessarily a problem.

But the actual dimensions cannot remain unknown.

FAQ

Can I build an event stage using my existing Ringlock scaffolding?

Potentially, yes, but the existing system dimensions and the intended deck/support interface must first be confirmed. “Ringlock” identifies the general system type, not every dimension required to guarantee compatibility.

Can I use forks instead of buying dedicated stage beams?

That depends on the complete stage configuration and the deck-support arrangement. In this project, a fork-type concept was discussed because the customer wanted to minimize new investment, but we could not finalize it because the dimensions of his existing Ringlock system remained unknown.

Why do you need the length of my existing Ringlock ledgers?

Because the ledger/grid dimensions determine where the standards and top supports are located. The deck dimensions and support points need to be coordinated with that grid.

What if I do not know the Ringlock brand?

The brand is helpful but not always essential. Clear dimensions, photos and interface details may be enough to evaluate compatibility. In this case, however, neither the system identity nor the necessary measurements could be confirmed reliably.

Why not just make the decks after seeing a photo?

A photo can help identify the general structure, but it cannot reliably establish all dimensions needed for a custom deck/support system. Guessing those dimensions could result in incompatible components.

Did the customer finally buy the fork stage?

No. The proposal was not finalized. The customer ultimately decided to continue using a locally familiar method involving timber boards over his existing Ringlock structure, on-site leveling and a carpet finish.