The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Checking of contract drawings and standards relating to the projects from the customers.
Understanding the complexity of the project.
If the design drawing parameters are not matching updating the issue to the engineer. The RFI will be considered if it is provided by the engineer.
Checking the connection possibilities & feasibility as per AISC & OSHA standards
Checking D-sheet as per contract drawing for fabrication dimension.
Updating the model team for any correction to be taken up based on errors found while checking design parameters in the connection.
I know the basics of shop drawing editing & basic modelling.
I have 4 years of experience in Tekla steel detailing as a engineer checker (QA,QC).
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
A pricing section should make the next step easier.
What’s included? Which option fits? How do I get started?
I designed this pricing section for a web design and development agency with those questions in mind.
For founders comparing services, clear scope matters just as much as the price.
Building a website for your business or need a design and development partner for your agency? Let’s talk.
Having 'What's included' right under each price makes this easy to scan. Nice and clear.
Which stage takes you the longest?
✏️ Sketch: too many options, and all of them look good
🎨 Color: cracking a safe, looking for the combination that clicks
✨ Final: nothing left to decide, just do it well and listen to the client
I’m team color 🙋
Team color here too. Cracking a safe is the perfect metaphor, finding the combination that clicks is where all the hours quietly go. The three color variants prove how much one palette changes a character's whole personality.
Edge cases found in QA often turn into additional work nobody planned for.
Before planning a feature, ask:
→ What slows the user down?
→ Where does the system block them?
→ What if it fails to load?
→ What if it returns no data?
You’re usually able to find more decisions that need to be made by asking.
The four questions you listed are so simple yet so easy to skip in planning. That flowchart mapping out the no-access and error paths is a great artifact, it makes the invisible work visible.